Prioritization
Prioritization determines the relative importance of business analysis information, requirements, needs or solution options, so as to know what to analyse further, what to build first and how much time and detail to give each one. Importance is judged against stated criteria, value, risk, implementation difficulty or others. The BABOK sorts the ways of doing it into four approaches: grouping, ranking, time boxing and budgeting, negotiation. Two convergence instruments out of facilitation practice, dot voting and the bullseye, add to the family the group vote that closes an ideation session. The six are told apart by one question: what is the deciding factor.
Goal
Prioritization determines the relative importance of business analysis information. A list longer than the capacity forces the organisation to say where it starts. The BABOK names the criteria: value, risk, implementation difficulty or others. The priority that comes out of it serves three decisions: which information to take further, which requirements to build first, how much time and detail to spend on each. It is an exercise in facilitation: the analyst runs a structured decision that forces trade-offs. For the BABOK, its strength is that it facilitates consensus building and trade-offs, which helps deliver the value of the solution and meet the initiative's timeline.
The deliverable changes with the approach: labelled categories, an ordered list, a scope trimmed to a fixed resource, an agreed set or a tally of votes. The six have three things in common: a criterion stated before the exercise, a group that accepts losing something and a record of the decision. A prioritization whose criterion stays implicit returns an order nobody can contest or replay.
The choice of approach is made, according to the BABOK, by considering who the decision is addressed to, their needs and their opinion of the value an item brings to their own domain. The same guide makes it a repeated exercise: priorities are replayed and the approach changes when the company's environment, the stakeholders or the business analysis information move on. An order set once and then frozen expresses nothing at the first change of context.
Usage
When to use it
- A list longer than the capacity: more requirements than the team, the budget or the delivery window can absorb.
- Analysis effort to spread: deciding what deserves further work and what stays coarse-grained.
- Entry into a fixed-cadence delivery cycle: settling the content of the next increment before committing to it.
- Competing priorities that no objective criterion settles: making the trade-off explicit and defensible.
- An ideation session that produces too many options: converging on a short list before leaving the room.
- A changed environment, stakeholder group or information base: replaying an order that no longer reflects the situation.
When not to use it
- Disagreement about a fact: no order settles a factual question; establish it through document analysis or an estimation, then come back to the trade-off.
- An item imposed by law or by contract: its rank changes nothing about its entry into scope; treat it as a constraint on the plan and prioritize the rest.
The deciding factor in each of the six
All six approaches produce a trade-off, and what separates them is what decides it. In grouping, it is categories agreed in advance: each item falls into one of them and the exercise stops there. In ranking, it is a strict order, one position per item from 1 to N. In time boxing and budgeting, it is a resource limit, a duration or an amount, fixed before anyone looks at the list; the scope adjusts to stay under that ceiling. In negotiation, it is the stakeholders themselves, who build an agreement where no objective criterion separates them. In dot voting, it is a tally of the votes the group has placed. In bullseye, it is each item's proximity to a goal written at the centre of a target.
Naming the deciding factor usually narrows the choice to one or two approaches. Two further traits finish the job. The first is the granularity expected of the result: categories are enough to sort a large set quickly, whereas a strict order becomes necessary as soon as a queue has to say what comes after what. The second is the nature of the disagreement: a divergence about facts is handled with criteria and figures, so through grouping or ranking, while a divergence about what matters goes through an agreement between people, so through negotiation or a vote.
Choosing between the six
| Approach | Typical trigger | What it leaves open |
|---|---|---|
| Grouping | A large set to sort quickly, on a first pass. | The order inside a category. |
| Ranking | A queue to establish, ties to break. | Where the achievable work stops. |
| Time Boxing and Budgeting | A firm deadline, an approved budget, a delivery cadence. | The rank of the items deferred beyond the cut line. |
| Negotiation | Competing priorities that no objective criterion settles. | Reproducibility: the agreement rests on the people who reached it. |
| Dot voting | An ideation session that ends with too many options. | The reason for the choice, which the tally does not carry. |
| Bullseye | A written goal and proposals to place around it. | The build sequence inside the central ring. |
The six follow one another more often than they exclude one another. A workshop closes its list of options with a dot voting round or a bullseye, the team sorts them into categories, the product backlog puts them in order and the fixed resource of the iteration draws the cut line there. Negotiation steps in wherever one of these transitions blocks. Expecting a single approach to carry the whole trade-off is the family's most common mistake. It shows up as a complaint: grouping is blamed for giving no sequence, or ranking for not saying where the work stops, when neither of them ever claimed to answer that question.
What makes a prioritization fail
The three limitations the BABOK records are behaviours more than method flaws, and they come back whichever approach is chosen.
Stakeholders avoid the hard choice and refuse to accept that a trade-off is called for. The symptom: everything is high priority, the categories lose their meaning and the order serves no purpose. The answer is to move towards the approaches that set an outside constraint, a capacity announced per category, a unique rank per item or a resource fixed in advance: they make avoidance impossible.
The delivery team can bend the result by overstating the difficulty or the complexity of certain items. The BABOK records this without presuming intent: deliberate or not, the bias operates. The counter is to produce the difficulty estimate separately, before the trade-off and by people other than those who make it.
Metrics and performance indicators are often missing when prioritizing, so a stakeholder's judgement of importance can stay subjective. Writing down the criterion chosen, its source and the date of the decision makes the subjectivity visible and the order open to challenge.
AI considerations
The help lies in the preparation and in the checking. From a list of requirements and a written criterion, an assistant produces a first assignment that the group corrects, which saves session time, the most expensive resource in the exercise. It spots suspect distributions: half the backlog at high priority, a category left empty, an item whose justification contradicts the stated criterion. It compares the proposed order with the previous one and flags the items that moved without a reason being recorded. On a long list, it groups the duplicates and near-duplicates that distort any tally of votes.
Judgement stays whole on what does the deciding. The criterion itself, the value an item brings to a domain, the relative weight of value and risk belong to the stakeholders. The difficulty estimate is where the BABOK flags a bias: a model returns a figure that is plausible by construction; it enters the trade-off as an assumption to be verified. Negotiation and voting draw their value from the presence of the people concerned: an order produced outside the room commits nobody. Finally, a product backlog carries commercial information and a roadmap: passing it through an external service assumes the clearance that permits such processing.
Cost
| Phase | Level | Rationale |
|---|---|---|
| Preparation | Medium | The cost the family has in common sits here: settling the criterion, gathering the stakeholders entitled to a say in the decision and getting the list into a comparable state, items of similar granularity and duplicates removed. |
| Execution | Low to high | A grouping or a dot voting round is held in an hour of workshop; a negotiation over competing priorities takes several sessions and a ranking of two hundred items demands a tie-break criterion held to the last position. |
| Documentation | Low | The result is short, a list, categories or a tally. The effort goes into what accompanies it: the criterion chosen, the date and the items set aside with their reason, without which the decision cannot be replayed. |
Tooling
The available tool weighs on the approach. The BABOK records that many requirements management tools carry the priority category as an attribute of a requirement: a fixed-value field makes grouping immediate and ranking painful, since a total order assumes a position of its own for each item and a renumbering at every insertion. Backlog tools do the opposite: order there is a property of the list itself and the category attribute becomes secondary. Settling the approach without looking at that constraint means choosing a method the tool will fight.
The collaborative whiteboard carries the instruments that run in session and require everyone to see what the others are doing, in the room as well as remotely. The spreadsheet stays useful for a weighted ranking on several criteria, where the score column recalculates and sorts without a dedicated tool. A portfolio management tool takes over when the unit being decided becomes the whole initiative, with its own budgets and deadlines.
Sources
- IIBA, A Guide to the Business Analysis Body of Knowledge (BABOK Guide) v3, §10.33 Prioritization: the definition of prioritization as the determination of the relative importance of business analysis information, the criteria of value, risk and implementation difficulty, the classification into four approaches (grouping, ranking, time boxing and budgeting, negotiation), the choice of approach according to who the decision is addressed to and their needs, the repeated nature of the exercise, as well as the strength and the three limitations taken up here.
- Dave Gray, Sunni Brown and James Macanufo, Gamestorming: A Playbook for Innovators, Rulebreakers, and Changemakers, O'Reilly Media, 2010: dot voting as an instrument for converging a group on a set of options, absent from the BABOK's four approaches.
- LUMA Institute, Innovating for People: Handbook of Human-Centered Design Methods, 2012, Bull's-Eye Diagramming method: the placing of items on concentric rings around a written goal, which gives a reading of centrality.