Identifying Goals and Defining Criteria
In short Stakeholders often state goals that are not their real ones, without any intent to mislead. This page covers four reasons for the gap, Ackoff’s idealized redesign for surfacing real goals, and how to turn goals into a set of criteria and constraints that adequately represents them.
Based on: F. P. Tarasenko, Applied Systems Analysis (in Russian), ch. 5, sections 5.6–5.7 (stages 6 and 7), drawing on R. L. Ackoff.
On this page
Key ideas#
The goal mess#
By analogy with the problem mess, Tarasenko calls the set of all stakeholders’ desired futures the “goal mess”. Any move from the problem mess toward the goal mess is an improvement.
Four reasons stated goals differ from real ones#
- Goal substitution. Experts impose their own view: the operation was a success but the patient died; an award-winning building is unfit to work in. Remedy: involve the stakeholders themselves; do not speak for them.
- Confusing ends and means. Goals form a hierarchy in which each item is a means for the level above and an end for the level below, so it is easy to pick the wrong level. Ask “What do you need this for?” In one of Tarasenko’s cases, a request to choose a site for a new hospital turned out to serve the goal “improve medical care”, better met by upgrading existing facilities.
- Incomplete goals. People forget or underrate part of a composite goal. In another case, a merger met its stated efficiency criterion but was blocked because nobody listed the goal of keeping tax revenue for the local budget. A warning sign: goals described in fewer professional “languages” than the stakeholder actually uses.
- Inability to express a goal. People may not know what they want. Offer a real choice among concrete options, so the goal shows in what they pick, or derive it downward from values they are already aware of.
Idealized redesign#
Ackoff’s technique: imagine the current system vanished last night, and design the one you would want now, ignoring resources and feasibility. Tarasenko reports three effects: it breaks people out of their narrow current view, the play element raises engagement, and a later feasibility check usually shows most of the design is achievable. The main obstacles were self-imposed. The design must still be technologically possible (no science fiction), compatible with its environment and laws, and able to learn and adapt.
Goals of organizations#
Declared goals can differ from actual ones when the organization’s interests conflict with society’s or with its managers’ personal interests; the analyst should notice the gap. The mission sits at the top of the goal tree and should reflect the interests of all stakeholders, not just “grow” or “be more profitable”. Ackoff grades ends as goals (reachable within the planning period), objectives (not reachable within it, but progress is planned) and ideals (never reached, but approachable). Good goal statements are realistic, specific to this problem, and measurable.
Criteria and constraints#
A criterion is a quantitative model of a qualitative goal. You need exactly as many criteria as it takes for the set to model the goal adequately. One criterion is easiest to use but rarely enough: in a city case Tarasenko cites, cost of garbage collection per apartment said nothing about cleanliness and was replaced by measures of disease, garbage fires and rat bites. His practical tip: for each significant attribute, use at least three criteria, covering quality, quantity and time.
Constraints differ from criteria. You trade criteria against each other, but constraints must be met. If constraints make the goal unreachable, raise their relaxation with the decision maker: in another case, an overly strict radar false-alarm limit existed only so that the chief would not be disturbed too often.
How to apply it#
- Record each stakeholder’s stated goals.
- For each, ask “What do you need this for?” until you reach a goal the person recognizes as their own.
- Check completeness against the stakeholder’s professional languages (finance, operations, legal…).
- Where people cannot say what they want, run an idealized-redesign session or offer concrete options.
- Build the goal tree from the mission down.
- For each goal, define criteria for quality, quantity and time; list the constraints separately.
- Challenge every constraint that blocks the goal.
Example#
The Workshop’s owner asks for online booking. “What for?” Fewer no-shows and less phone time. “What for?” More repairs per mechanic-day and happier customers. That is the real goal, and online booking is one means. Mechanics add a goal nobody listed: predictable workloads. Criteria: share of repairs right first time (quality), repairs per mechanic-day (quantity), days from drop-off to pick-up (time). Constraints: a budget cap and data-protection law. An idealized-redesign session with managers produces the idea of drop-off lockers, which turns out to be feasible in two shops.
Pitfalls#
- Taking a requested feature as the goal → ask what it is for.
- Writing goals for stakeholders → have them state their own.
- One convenient metric → model the goal with several criteria.
- Treating every limit as untouchable → separate real constraints from habits.
Sources and further reading#
- F. P. Tarasenko. Applied Systems Analysis (in Russian). KnoRus, 2010, ch. 5, sections 5.6 (goal identification) and 5.7 (criteria).
- R. L. Ackoff. Redesigning the Future. Wiley, 1974 — idealized design, which Tarasenko retells as idealized redesign.