C · Value judgment and direction setting

Prioritization and trade-offs

Choosing, deferring, and dropping under limited capacity.

Classification boundary

Include: Include sequencing, deferral, and stopping decisions when work competes for capacity.

Choose a neighboring leaf when: Use planning for long-term direction and phases, and D capacity/dependencies for operational allocation.

This capability may appear in standards across different stages. Explore stage expectations

26 questions

Choose a group based on the evidence you need. Groups follow existing question formats, not difficulty or mandatory prerequisites. Each batch has up to eight questions.

Judgment and options24

Compare goals, constraints, options, and trade-offs.

Questions 1–8

Next quarter, the team can keep only one initiative that directly drives growth and one foundational capability project, and each option has strong advocates. How would you compare them and choose a portfolio?
The team needs to test a growth hypothesis while customer-impacting maintenance work keeps arriving. How would you set capacity, triggers, and stop rules?
A market window is short and a full solution takes two months. A reversible one-week pilot is possible, but cannot validate every long-term risk. How would you choose the sequence?
The team lacks capacity for all three: a short-term revenue project, strategic exploration, and technical refactoring. What criteria would you use to compare and rank them? How would you explain strategic value or maintenance risk that cannot be measured directly?
A new product exploration has consumed two quarters. Pilot completion stays below target, while the team argues one more feature will fix it. How would you judge evidence for further investment and stopping?
In a review, three candidate projects are each marked P0 by their owners, all for the reason 'very important.' How would you turn the review from arguing about order into a trade-off people can check?
Choose a project you are working on. Given its goal and ranking criteria, what are the three most important things to do and the two easiest to pause or stop?
The release window moves up by two weeks, and the team can finish only three of six planned items. Business, reliability, and compliance leads each say their work cannot slip. How would you prioritize and explain what is cut?

Questions 9–16

A critical flow is two weeks from launch when a review finds that keyboard users cannot complete one step. A full redesign would affect the date. How would you assess the impact, negotiate scope with the team, and explain what can be staged versus what cannot safely ship?
Two projects are both committed for this quarter and depend on the only expert familiar with a legacy system; splitting that person's time would slow both. How would you compare delay cost, alternatives, and investment in shared capability?
The team can launch a limited but imperfect experiment this week, or wait three months for broader research before a large commitment; the latter may miss a key market window. How would you compare learning value, delay cost, and decision risk?
A failure affects few requests but can cause unrecoverable data loss; a new feature is expected to add revenue but would delay reliability work. How would you compare probability, severity, detectability, and opportunity cost?
Growth, Support, and Product each want a new home-page entry; each change helps one group but could make the core task harder for first-time users to find. How would you choose the entry priority and experiment sequence?
A new market opportunity emerges mid-quarter and leadership wants an immediate pivot; customer promises, team goals, and partner schedules have already been published. How would you compare the opportunity window with the cost of breaking commitments and decide what to keep, reduce, or renegotiate?
Several teams spend hours each month resolving deployment configuration problems; a platform change could remove repeated work but adds no immediate revenue, while product features have explicit revenue targets. How would you estimate attributable platform value and investment limits?
A redesign improves average conversion but increases task failure for a constrained user group; expanding the sample requires more research time. How would you prioritize the risk and decide whether to pause rollout?

Questions 17–24

The team completed its top-ranked projects, but engineers with critical skills are idle while other teams are overloaded. How would you improve allocation?
A roadmap aims to reduce customer configuration failures, but the department OKR becomes “ship 12 configuration features.” How would you restore the causal link between objective and work?
How do you prioritize when several important projects compete for limited resources?
How would you plan next quarter if capacity only allowed two initiatives?
A security defect is unlikely to recur but would have severe impact; other projects have more certain revenue upside. How would you compare and document the decision?
The team can pursue one direction: one offers a certain small revenue gain, while another may open a market but rests on an untested assumption. How would you prioritize and set a stop condition?
Three initiatives target revenue, operational risk, and compliance, but need the same engineers. How would you create a comparable decision rule?
A brand partnership produces broad reach, but sales cannot trace lead sources and short-term conversion is limited. How would you combine leading indicators, validation, and stop conditions?

Experience and reflection2

Use past facts to examine contribution, results, and learning.

Questions 1–2

Looking back at work you have already finished, which three things do you now think were not worth doing? Why did you do them then, and what changed in your judgment?
Looking back over the past six months, what were the three most worthwhile things you did? Why those, what benefit did they bring, and how did you confirm that benefit?

Back to the whole domain