Prioritisation and dependencies
Sequence work according to outcome, risk, dependency and delay impact.
What you will learn
- Define the outcome and deadline.
- Map dependencies and consequences of delay.
- Separate urgency from noise.
Priority is not determined by who asks most forcefully. A defensible sequence considers impact, time sensitivity, dependencies, reversibility and the cost of interrupting current work.
Core method
Priority is not determined by who asks most forcefully. A defensible sequence considers impact, time sensitivity, dependencies, reversibility and the cost of interrupting current work.
- Define the exact decision or claim before analysing detail.
- Use evidence that is relevant to the stated context.
- Record uncertainty instead of replacing it with confident wording.
Applied case
A team has a public accessibility defect, an internal formatting request and a routine report due tomorrow. The defect prevents keyboard users from completing registration.
Apply the method
Recommend a sequence and state the reasoning.
Review answer guidance
Address or contain the accessibility barrier first because it blocks access and may affect current users. Preserve the report deadline through reassignment if possible, and schedule the formatting request after consequential work.
Use in an assessment
Apply the method to the information provided in the task. A strong response makes its reasoning traceable and does not rely on specialist facts that are absent from the evidence.
- Read the requested outcome and constraints first.
- Eliminate responses that exceed the available evidence.
- Review whether the conclusion answers the precise question.