I spent a decade writing about products. Now I'm making them.
I'm a Senior Product Manager in San Francisco. I've spent my career in fintech, subscription and ERP products — the kind of software where a wrong assumption costs a real person real money, and where the interesting problems are almost never in the interface.
For most of that time my job was to describe what should exist: the spec, the trade-offs, the reason we were doing it at all. I got very good at the describing. What I couldn't do was find out whether I was right, without asking a team of six people to build it first.
So I started building. Badly at first — a broken little script, a table that didn't load — and then less badly. What pulled me in was three things at once: I could finally make the small thing I'd been describing, I could see how these models actually behave once you're the one holding the edges, and I could talk to my engineering partners as someone who had spent a Saturday inside the problem instead of around it.
The fastest way to become a better product thinker is to ship something no one asked you to ship.
That's what this notebook is for. I write here about what I'm building, what product work still teaches me, the events worth showing up for in San Francisco, and the things I got wrong. It isn't a portfolio in the polished sense. It's the record of an ongoing education, kept in public because that's the part that makes it stick.
If you're a PM wondering whether you should learn to build: you should, and it's less about the code than you think. If we met at an event and you found your way here, say hello. I'd like to hear what you're working on.