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 1.2.0
1.2.0 - 2026-07-23 Changed - Update service — the daily update check now reports a small, non-identifying payload sparQ version and edition, operating…
sparQ 1.1.0 released!
1.1.0 - 2026-07-21 Changed - Self-hosted frontend libraries — vendored frontend assets instead of loading from a CDN, and cache them with per-file…
sparQ goes open source. Public launch on GitHub under AGPL v3.
sparQ is now publicly available and open source. The full codebase is live on GitHub under AGPL v3.
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 gosparq/sparq.
The repository structure is finalized. The public repo will open at github.com/gosparq/sparq.
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.