Operational PM, in the open.
Essays on how teams actually coordinate. Build notes on what we built and why. Field notes from inside. Anti-patterns. Technical architecture. And the changelog. Filter by what kind of writing you're after.
Managers ask "are we on track?" more than "what's the roadmap?"
Operational visibility outranks planning fidelity by 4x.
The Three Evils of Modern Project Management
On visibility, fragmentation, and the friction nobody admits to.
Roadmap theater
The show beneath the plan. Why quarterly roadmaps optimize for the wrong audience, and what to swap in.
Three weeks of standups. Zero blockers logged. Five real blockers happened.
Standup-as-ritual is not the same as standup-as-signal.
The team cap is suggested at twelve, not enforced.
Every team we've watched over 12 develops coordination drift within a month.
The hidden tax of stale task systems
Every "we'll update later" task compounds into operational fog. How to measure the cost, and why it doubles every quarter.
We caught our own PM board lying inside our dogfood instance.
The same drift we describe in essays, in our own dashboard.
We tried sprints. We removed them.
Six months of sprints, then six months without. The without version is unambiguously better. Here's why.
How sparQ handles real-time team status
Server-sent events, presence tracking, and the trade-offs we made to keep p99 under 200ms.
The green board illusion
"Everything is on track" is the most dangerous sentence in PM. Here's the mechanism that produces it.
One unmarked-done task in week 1 cost us five "what's the status?" pings by week 3.
The blast radius is wider than it looks.
Why presence matters more than status
"Available" and "in focus" tell you something. "On track" tells you nothing.