·6 min read
Why metrics lie without context
Every metric needs three things: the number, the mechanism that caused it, and the counter-metric (what you sacrificed). Without all three, you're guessing.
Thinking out loud about product, engineering, and the space in between.
Every metric needs three things: the number, the mechanism that caused it, and the counter-metric (what you sacrificed). Without all three, you're guessing.
Remote PM fails when you solve timezone overlap with better scheduling. The real skill is async-first: persistent docs, written decisions, shared context.
When nobody disagrees, nobody's thinking. A PM with no position turns the roadmap into a parking lot of unrelated features.
Diagrams hide the hard parts. Building a real system, even a small one, exposes the architectural constraints that should drive product decisions.
If you want to see the reasoning applied to real products, the case studies have the details.