Choose a sequence that fits the stated constraints.
Review priorities, capacity, dependencies and revised commitments through explicit fictional plans. Counts are practice, not a workplace-judgement rating.
Five original scenarios each contribute one matched answer. Your count out of five describes these explicit fictional conditions, not a measured competency, personality trait, percentile or hiring decision. Every rationale and this guide is free at every count.
Which constraint takes precedence?
A priority decision needs more than the task that feels loudest or easiest. These five scenarios supply an ordering rule, deadline, capacity, dependency or agreed delivery change. The key follows those particular facts. An earlier arrival, a familiar requester or a quick cosmetic improvement is not automatically more important than a blocking task when the prompt gives the blocker precedence. First identify the rule that decides the order, then apply any tie-break only where it belongs.
A fresh capacity example
Suppose you have 55 minutes. A required review takes 35 minutes and a second task takes 30. Their total is 65, leaving a ten-minute shortfall. If the agreed plan says to protect the review and ask the coordinator to move the second task, that is the supported response. Promising both within 55 minutes does not create the missing capacity. Nor does working 27 minutes on each establish completion of either estimated task.
Read readiness as a prerequisite
A near deadline can make a missing confirmation uncomfortable, but it does not satisfy a rule requiring explicit readiness. Name the dependency owner, ask for the required fact and tell the scheduling owner what remains uncertain. This preserves a route to a new slot. Do not silently convert absence of an objection into positive approval. The exercise does not say every real workflow needs that confirmation; the prerequisite exists because the scenario states it.
Keep the tie-break inside its group
In a separate fictional queue, M is priority 3 due at 09:00, N is priority 1 due at 12:00 and P is priority 1 due at 11:00. With priority first and earlier deadline second, P comes before N and M. Looking only at clock time would incorrectly choose M. Write a two-column comparison if needed: first priority, then deadline among matching priorities. This is a deterministic queue rule rather than a universal method for all urgent decisions.
A valid plan includes the affected update
When a prompt explicitly requires telling a requester when their work will start, doing the higher-priority item is only part of the answer. Compare options for both execution and communication. A truthful later start can be acceptable when the scenario allows it; claiming that work is already complete is different. Preserve a previously authorized later delivery instead of inventing a new deadline conflict. An accurate short update often satisfies more of the supplied brief than an unrealistic promise.
Rehearse with one changed constraint
After reviewing an explanation, change one quantity or rule in a new fictional plan. Increase available time, reverse the priority order or provide the missing confirmation, then check whether the recommended action changes. State why. If your answer stays fixed regardless of the new facts, you may be repeating a slogan rather than applying the scenario. Keep the example on paper; this tool does not schedule work, message colleagues or assess how you act under real pressure.
Interpret five matched answers
A count such as 3/5 indicates three choices matching this edition’s explicit conditions. It is not a speed score, management qualification or evidence that you always prioritize well. There is no timer, normative sample or validated competency scale. Repeating the same five items after reading their keys can reward memory. Use the examples to explain a decision and its assumptions; use the actual rules, authority and support available in a real workplace for real decisions.