Why I Write

You only find out whether you have really thought something through when you write it down.

For a long time I assumed that “thinking clearly” and “explaining clearly” were the same thing. Then I started writing my ideas out in full, and discovered how much of my thinking was just vague intuition — conclusions first, floating evidence, logic quietly skipping the hard parts. Writing is the cheapest form of self-verification: no audience required, no meeting, just a blank page.

Writing is product thinking made visible

A product manager’s job is turning chaos into clarity: gathering scattered signals, telling real problems from fake ones, weighing constraints, and then organizing the conclusion so that others can read it and act on it. That process is structurally identical to writing.

A good PRD and a good essay rest on the same underlying ability: making complicated things simple, in a way that survives questioning. So this blog doubles as my training ground for product thinking — whatever I cannot write clearly, I probably have not thought through.

What you will find here

Roughly three things:

• Products and AI: projects shipped, mistakes made, judgments overturned;
• Traces of reading: what stuck after the book closed;
• Thoughts from the road: the screen-free thinking that shows up on long rides.

No hot takes, no fixed schedule. The only standard: every post has to come from something I have genuinely thought about.

Uniting knowing with doing starts with writing down what you know.