Week 39 Day 7: Assignment: Cut Your Active Priorities by Half

Count everything the team is actively working on right now. Not planned work -- active work. Then force-rank the list using the process from Day 3. The top half continues. The bottom half is paused -- not canceled, paused -- until the top half is complete. Tell the stakeholders. Protect the boundary. Watch what happens to your team's throughput.

Here is the assignment process. Step one: inventory all active work. List every workstream, project, initiative, and recurring task that is currently consuming team capacity. Include the 'shadow work' that is not on any official list -- the maintenance tasks, the favors for other teams, the 'quick' fixes that consume hours. Most leaders discover 30-50% more active work than they were consciously tracking. Step two: force-rank the list. Use the stack ranking process from Day 3. No ties. Every item has a rank. Step three: draw the line at 50%. If you have 8 active workstreams, the top 4 continue and the bottom 4 are paused. If you have 12, the top 6 continue and the bottom 6 are paused. If cutting by half feels impossible, you have more priority debt than you realized. Step four: communicate the pause. For each paused workstream, notify the stakeholder: 'We are pausing this workstream to focus on our top priorities. Our current target is to resume in [timeframe]. This decision will allow us to complete [top priorities] faster and deliver more total value by end of quarter.' Step five: protect the commitment. The hardest part of cutting priorities is maintaining the cut. Within two weeks, pressure will emerge to 'just do a little work on the paused items' or 'squeeze in one more thing.' Resist. Every exception erodes the focus you are trying to create. If a genuinely critical change occurs (a new business imperative that ranks above your current top priorities), execute a formal trade: the new item replaces a current top priority, which moves to the paused list. No net additions. Step six: measure the impact. After 4 weeks, compare: how many items were completed in these 4 weeks versus the prior 4 weeks? What is the team's self-reported workload and stress? What is the stakeholder satisfaction with the items that were completed? Document these findings and use them to justify maintaining focused prioritization going forward.

The 50% reduction target implements what Womack and Jones (1996) call 'flow improvement through WIP reduction' in lean manufacturing -- the principle that the fastest path to cycle time improvement is to reduce work-in-progress by 50% and measure the effect, then adjust. Their research across manufacturing and service organizations found that a 50% WIP reduction typically produced a 25-40% cycle time improvement in the first iteration, with additional improvements possible through subsequent reductions. The communication protocol for paused workstreams implements what Edmondson (2012) calls 'psychological safety in boundary-setting' -- the practice of framing decisions in terms of team effectiveness and value delivery rather than in terms of refusal, which maintains the stakeholder relationship while enforcing the prioritization decision. The pressure resistance in step five is documented by Cialdini (2006) in his research on 'commitment and consistency' -- the principle that once a decision is made and communicated publicly, social pressure supports maintaining the decision. Public communication of the priority cut creates a commitment device that makes it psychologically harder to reverse the decision than to maintain it, which is exactly the dynamic the leader needs when facing pressure to add back paused work. The measurement step implements what Seddon (2003) calls 'check against purpose' -- measuring the results of a process change against the intended outcome (throughput improvement) rather than against activity measures (busyness), which prevents the common failure of reverting a successful process change because the team 'felt' less productive despite producing more.