For most of my career, I never had a clean answer to the question:
“What's your product process?”
Not because I didn't have one — but because every situation felt different.
Different stakeholders.
Different systems.
Different constraints.
So my honest answer was always… “it depends.”
Recently, I forced myself to actually map how I really operate.
What came out wasn't a linear process — it was a set of overlapping loops:
- Identify real problems (not just requests)
- Frame and pressure-test them from multiple angles
- Architect solutions that actually hold up technically
- Orchestrate delivery in a way that can ship incrementally
- Validate based on real-world impact, not assumptions
And the key realization:
I'm not moving step-by-step — I'm constantly working across all of these at once.
The biggest thing I've learned is that product isn't just about getting to delivery — it's about making sure what you're building can survive contact with reality, both technically and operationally.
Still refining how to visualize this (turns out translating your own thinking is harder than building systems 😄), but this exercise alone helped me clarify where I actually add value.