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.
sparQ Software LLC incorporated. AGPL v3 decided.
sparQ Software LLC is incorporated and the project will ship under AGPL v3.
Public release architecture finalized. Python codebase cleaned and documented.
The architecture for the public release is locked.
DevEx category positioning finalized. sparQ Pulse named.
sparQ is the open-source Developer Experience suite; the anchor product is named sparQ Pulse.
GitHub connector hardened. Derived status working end to end.
Status derived from GitHub activity now works end to end.
Repo structure finalized. Public repo opening at sparqsoft/sparq.
The repository structure is finalized ahead of going public.
Team completed work but nobody marked tasks done.
Three days of "in progress" on shipped features.
Why we flag stale work after 3 days, not 7
The argument took two weeks. The wrong threshold makes the flag noise. The right one makes it a confession.
The team status card, version 14
From scrolling list to compact panel. Every version, the screenshots, what users actually clicked.
The PM board looked healthy while Slack showed chaos.
The board is a lagging indicator of how people feel about the work.
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.