Systems, Stories, and Signals
We’re not short on data. We’re short on understanding. This series explores how complex systems become something people can actually use, combining observability, product thinking, and a focus on user education.
-
-
Community First: Where Developers, PMs, and Users Exchange Language and Ideas
A community is your bridge between roles: where everyone is heard and benefits. Product Managers, Developers, Members – all aligning and accelerating together.
-
If I Had to Build an Observability Platform from Scratch Today
Build an observability platform around understanding, correlation, narrative, and resilience—not just logs, metrics, and dashboards.
-
Your Dashboards Are Bad and You Should Feel Bad
A dashboard isn’t decoration. It’s a narrative. Good ones don’t just show data—they tell you what matters right now.
-
Breaking Down a Complex System So Anyone Can Understand It
Complexity isn’t the enemy. The real challenge is explaining complex systems clearly enough that anyone can see how it fits together.
-
The Care and Feeding Playbook: How to Build a Community That Lasts
A tactical playbook for product, community, and ops teams: staffing models, onboarding flows, moderation policies, and the metrics that prove community value without exploiting members.
-
Communities Fail When They’re Treated Like Features
All communities are living systems. Treat them like a feature and they’ll will behave like one: temporary.
-
Why Enrichment turns Logs into actual Observability
In my opinion, true observability comes from enrichment—connecting fragmented log lines into coherent events that actually explain what happened.
-
Documentation is the Product (We just Pretend it Isn’t)
Docs aren’t an afterthought – they’re the product’s voice. When they fail, the system fails with them.
-
The Gap Between Users and Systems (and Why It Still Exists)
Systems work as designed, but users build their own mental models. When those diverge, adoption stalls. The gap isn’t complexity — it’s translation.
