Why Product Rhythm
Product Rhythm is my personal site: the home for my work, my writing, what I teach and the things I build. The name comes from how I think about product work.
For me, rhythm has always been a compass.
In choir, I learned that harmony comes from listening.
In running, that it's not speed that takes you far, but cadence.
In product, I've learned that teams don't fail for lack of talent, but for lack of rhythm.
Product Rhythm comes from this understanding. When rhythm is present, people think more clearly. Decisions become lighter. Work begins to make sense again.
Every team has a rhythm
Sometimes it flows. Sometimes it breaks. And almost always, rhythm tells more than metrics.
Rhythm doesn't break because of lack of talent. It breaks when we stop listening. When we react instead of understanding. When pressure replaces intention.
In the best teams I've worked with, rhythm wasn't imposed. It was shared. Built through trust, protected by clarity, and sustained by the space to think.
What rhythm means in practice
In product work, rhythm shows up in how decisions are made and revisited. In how teams balance exploration and execution. In how much space there is for thinking, learning, and adjusting course.
- Clarity of intent before speed
- Enough structure to move forward, enough freedom to adapt
- Trust as a prerequisite for good decisions
- Space to notice when something feels off
When rhythm is present, work flows. When it's missing, even strong teams struggle to move together.
Product Rhythm in practice
This way of thinking shapes how I work with teams.
I focus on creating conditions where good decisions can emerge: not by controlling outcomes, but by strengthening the environment around them.
- Discovery and learning loops
- Decision-making under uncertainty
- Alignment across product, design, and engineering
When rhythm returns
You feel it in every decision, every conversation, every outcome. It's a subtle shift, but unmistakable. The team breathes again.