October 8, 2025
One Year as a Product Owner: What I Learned After Leaving the Code Behind
From architect to PO: prioritization, saying no, and why the messy middle of a career leap is the point.
I left a role where my value was architecture and shipped systems. A year later my calendar was prioritization, saying no, and sitting in the messy middle while other people wrote the code. That leap looks clean on LinkedIn. It does not feel clean in week six.
What I learned wasn’t a new framework. It was how often clarity is the product: which bets get airtime, which tickets are really decisions in disguise, and how psychological safety shows up when the roadmap is wrong on purpose.
This is the honest year-one report — what I had to unlearn, and why the awkward middle is the job.
That's the setup. Continue on Medium
Follow the work
New essays by email: a list I own, not a Medium follow.