Run a single weekly priority-setting meeting
Replace ad-hoc priority requests with one weekly meeting where the whole team re-sorts together.
Key takeaways
- What it is: Replace ad-hoc priority requests with one weekly meeting where the whole team re-sorts together.
- Why it works: Ad-hoc priority requests throughout the week are a source of manufactured urgency: each one feels urgent in isolation and disrupts the recipient’s actual Q2 work. Batching these into one weekly priority session means the team sees all the requests together, can compare them, and can make deliberate trade-offs instead of responding to whoever asked most recently or most forcefully. This moves prioritization from reactive to systematic.
- Evidence: Backed by observational / correlational evidence.
- Avoid: Letting the meeting become a status update that doesn’t actually produce decisions. The test of a good priority meeting is that something changed — a task moved up, another moved down, or something stopped.
Why it works
Ad-hoc priority requests throughout the week are a source of manufactured urgency: each one feels urgent in isolation and disrupts the recipient’s actual Q2 work. Batching these into one weekly priority session means the team sees all the requests together, can compare them, and can make deliberate trade-offs instead of responding to whoever asked most recently or most forcefully. This moves prioritization from reactive to systematic.
How to do it
- 1Designate one weekly meeting — 30–45 minutes — as the sole venue for changing priorities.
- 2Require that new priority requests be submitted before the meeting, not raised ad-hoc between meetings.
- 3At the meeting, review all requests against the current quadrant state and make explicit trade-off decisions.
- 4Communicate decisions clearly to stakeholders and hold the line between meetings.
What the evidence says
ObservationalBatching interruptions rather than handling them as they arrive is supported by attention research showing that task-switching has a significant cognitive cost and that deep work suffers most from fragmented interruptions. A dedicated priority cadence is the structural implementation of this finding.
Honest caveat: Task-switching costs are well established; the specific "one weekly priority meeting" format is a practitioner convention rather than a tested schedule. In environments with genuinely fast-moving dynamics, a weekly cadence may be too slow.
- — Rubinstein, Meyer & Evans (2001), executive control in mental task switching, Journal of Experimental Psychology: General
Common mistake
Letting the meeting become a status update that doesn’t actually produce decisions. The test of a good priority meeting is that something changed — a task moved up, another moved down, or something stopped.
IX Coach structures the weekly priority session to produce an explicit output — a sorted list with documented trade-offs — and tracks whether decisions from the meeting actually hold through the week or get overridden by ad-hoc urgency.
Practice this with IX Coach →