TOPIC
Prioritization
These are the same questions found in the library, grouped here by the capability each one mainly examines.
53 questions
Questions 1–50 of 53 on this page.
A · Professional problem solving and implementation1
No questions in this section match your target. ·
C · Value judgment and direction setting36
- A major customer will pay a high price for a custom feature, but reuse by other customers is uncertain. Ongoing maintenance, permissions, and data rules add cost, and sales has promised a delivery date. How would you compare a one-off build, productizing it, a service, or declining—and decide whether to invest?
- 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?
- A major competitor makes a feature free that large customers have repeatedly requested, but you have not observed customer losses because of it. How would you determine whether this is an emerging competitive risk, a negotiation signal, or a feature gap not worth following?
- The team needs to test a growth hypothesis while customer-impacting maintenance work keeps arriving. How would you set capacity, triggers, and stop rules?
- The team proposes pausing feature work to rebuild a core module, but past refactoring benefits were hard to quantify. How would you set a baseline, pilot, and stop criteria?
- One section of a community has stayed quiet for a long time. How do you judge whether it deserves continued investment or should be shrunk or merged?
- For the whole, is the part you own a lever, a fulcrum, or just one link? How do you judge that, and how do you show it is not merely important-looking?
- The team wants to keep optimizing the performance of a core API. What basis do you use to decide how far is far enough, and when to stop investing more?
- What were the short-term and long-term benefits of this project? When the two conflicted, how did you trade them off?
- You discover that a new direction you pushed is wrong. How do you cut your losses, how do you judge whether to continue, adjust, or stop, how do you treat sunk cost, and how do you explain it to those involved?
- The business wants new features while the team has built up technical debt. How do you decide how much to invest in each this quarter?
- Several teams changed the product, pricing, and operations at once, and the overall outcome improved. How would you assess each contribution?
- An experiment shows no expected lift, but also does not prove the idea ineffective. How would you decide whether to continue, change, or stop?
- Two projects each meet some goals, but one delivers more user benefit per unit of investment. How would you reallocate resources?
- Your quarterly plan leaves out several important items. How do you record them so that when someone wants to revisit one later, the discussion rests on the judgment rather than re-arguing how important it is?
- 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?
- 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?
- 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?
- 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?
- 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?
- A high-traffic flow was changed into sequential steps, raising overall completion. Support reports, however, show users struggle to find exit, undo, or change options. How would you determine whether this is a real experience improvement, a segment difference, or a metric artifact?
- 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?
- 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?
No questions in this section match your target. ·
D · Delivery and ongoing operations5
- Four months after delivery, the targeted cost reduction has not appeared in financial reports. The sponsor says the system is still in a learning period, while finance considers the project closed. How would you clarify benefit ownership and the validation window?
- A serious production incident pulls two specialists from a project team for a full week, putting a milestone at risk. How would you update the forecast, separate incident and project responsibilities, and help stakeholders make trade-offs?
- After a strategic shift, several in-flight projects no longer support the new goals, but teams have invested effort and made external commitments. How would you decide what to stop immediately, what to close out, and how to transfer knowledge, contracts, and capacity?
- A project depends on another team for an interface or data contract, but there is no clear delivery owner, plans keep changing, and the work may not fit next quarter’s schedule. How would you establish a commitment, prepare alternatives, manage critical-path risk, and decide when to escalate or change scope?
- Engineering tells you that, because of the underlying architecture, the feature you specified will slip two weeks, while the business side wants it tomorrow. How do you cut half the features in a short time and keep a minimum viable version that can ship, and what do you rely on to decide what stays and what goes?
No questions in this section match your target. ·
E · Collaboration, communication, and influence3
- How do you explain something clearly enough for your manager to see its value or its problem? When they do not take it seriously at first, how do you organize what you say and choose the evidence and the timing?
- Two owners agree on the data but prioritize short-term revenue versus long-term retention. How would you clarify the disagreement?
- What would you do if your manager's priorities differed from the team's judgment?
No questions in this section match your target. ·
F · People and organization building2
- The organization plans to add another lead layer to reduce executive span, but the main pain points are approval delays and conflicting goals. How would you assess whether another layer solves the problem and evaluate side effects?
- Five teams each ask for another senior lead, and the budget covers two. How do you decide which two to hire first, and which problems you will not solve by hiring? How do you explain the decision to the teams that did not get a slot?
No questions in this section match your target. ·
G · Learning, adaptation, and sustained growth3
- In one week, support asks you to fix an unstable issue, your manager expects a committed feature, and another team invites you to a review that could prevent future rework. How would you choose what comes first and help unmet stakeholders understand the choice?
- Your role is unchanged, but new requests, routine maintenance, and a long-term goal have accumulated, and finishing everything is unrealistic. How would you define a work budget and make it visible?
- You find a neglected maintenance problem that has not caused an incident, but fixing it will take several days and will not produce an obvious short-term result. How would you decide whether to invest, secure time, and set stop or escalation conditions?
No questions in this section match your target. ·