Notes on product thinking
Short, practical notes on how I approach product work in regulated and enterprise contexts. No frameworks for their own sake. Just the reasoning I actually use. Subscribe via RSS →
7 min read
Your backlog is a contract, not a to-do list
Every user story is an agreement between compliance, engineering, and the business. Treating it that way is what cuts rework.
Read →8 min read
Turning a sprawling API into a five-step wizard
A real client PRD, reverse-engineered: turning a prerequisite-heavy API into a flow a non-technical founder can finish alone.
Read →6 min read
What an engineering background changes, and what it doesn't
Not the cliches. The specific ways it helps, the ways it doesn't, and the trap it sets.
Read →6 min read
The stakeholder map nobody draws
In a regulated fintech product, legal, compliance, delivery, and ops all have to say yes before a feature ships. Silence isn't a signature.
Read →6 min read
Your pricing dashboard is a trust problem, not a data problem
Every dashboard project I've seen stall got blamed on the data. It was never the data. It was three teams calculating the same number differently.
Read →6 min read
The best scope cuts happen in discovery, not sprint three
Every scope gap that showed up as a change request was visible in discovery. It just wasn't looked for.
Read →7 min read
A curriculum is a product roadmap wearing a different outfit
Designing a K-12 coding curriculum under a real budget taught me more about roadmapping than most software projects have.
Read →6 min read
I learned product-market fit before I had the words for it
Years before I could define it, I was matching training programs to what students actually needed, not what looked good in a brochure.
Read →