Dependencies Need Owners Before They Need Slides
Planning artifacts become more useful when they expose overdue, unowned, and blocked work instead of just presenting milestones cleanly.
Plans often look healthier than the work underneath them. The milestones are there, the dates are there, and the swimlanes are there, but the risky middle is still invisible. That usually means the plan is missing the things that decide whether it will actually move:
- who owns the dependency
- whether the dependency is already late
- what is blocked downstream
- which blocker is missing entirely from the plan
The failure mode is usually in the middle
Most teams can see the top line. They know the launch date and the headline milestones. What gets fuzzy is the chain between them, and that is where plans start failing quietly. A dependency gets mentioned but not owned. An item slips but still looks present on the slide. A blocked team keeps showing "in progress" because there is no better bucket for "waiting on someone else."
What I want a planning artifact to do
I do not need every planning tool to be sophisticated. I mostly want it to answer a few practical questions quickly:
- what is overdue right now
- what is unowned right now
- what is blocked by an open dependency
- what is blocked by something that is not even tracked cleanly yet
That is a much better operating view than another polished timeline.
Why I still like tiny utilities for this
This is exactly the kind of problem I like using a small script for. Not because a script replaces planning, but because it forces the plan into a shape where the risks become legible. That is often the real value of a tiny tool. It does not make the work disappear. It just removes one more place for the ambiguity to hide.