Writing
What I'm working out
I write to work things out, not to report conclusions I already have. It starts as a question I'm stuck on in something I'm building.
Latest posts
- Token budgets are a product problem now
It’s about tokens — specifically, how many to send, how many to generate, and what happens to your product when you get that decision wrong.
- What I Learned Designing an AI Assistant I Actually Trust
I Built a Personal AI Assistant. Here's What I Got Wrong First
- Using AI daily doesn't mean you're good at it
About the Practical AI Fluency Framework (PAFF) for mid-career PMS & professionals
- The Product Trap: When to Build with AI vs. When to Keep It Simple
Every product cycle has its shiny object.
- The Silent Cost of Decision Debt
We talk a lot about technical debt.
The questions I'm working on
What has to be true before an AI agent reaches production?
What it knows, what it may do, the record it leaves, and where a person decides.
Which trade checks can an agent take on?
Every bank, buyer and customs office checks the same documents again. Which checks an agent can take, and how to trust what arrives.
Can every party in a shipment trust the same document?
Exporter, bank and customs each check it again today. One document they can all access and trust cuts the time and cost of a shipment, and leaves nothing to finance twice.
What does work become when AI does most of it?
When building gets cheap, deciding what to build is the hard part, and judgment is worth more than output.
Books

Tech Unlocked for Non-Tech Product Managers
Building products, using AI and working with engineering teams, for product managers who don't write code.
Buy on Amazon →
Blockchain: Internet of Transactions
A handbook for blockchain beginners, co-written with Gursimran Jit Oberoi.
Buy on Amazon →Get the newsletter
One email when I've built or learned something worth sharing: what I decided, what it cost, what surprised me. Every Sunday.