Why IT work stalls

Notes on why important IT work stalls, why familiar fixes fail, and what changes the result.

The Assembly Lines: You can’t scale what you can’t name.

A request sits for nine days. When someone finally asks about it, the answer is that it was handed to the next team and everyone assumed it'd been picked up. No one was idle during those nine days and no one made a mistake.

Read the note

History

The Intake Gate: No context, no startThe WIP Trap: If everything is started, nothing finishesThe Urgent Trade: If urgent enters, something leavesThe One Queue Rule: If there are two backlogs, the org runs on escalationThe Side Door Problem: Why IT Spend and Delivery Keep Surprising You