My Product Process
My Product Process
Nested, non-linear loops driven by business impact
Nested, non-linear loops driven by business impact
Embedded Files
This isn’t a product framework.
It’s how I actually work.
---
For most of my career, I couldn’t answer: “What’s your product process?”
Because the honest answer was: …it depends.
Different problems.
Different systems.
Different constraints.
---
But over time, I realized something:
I wasn’t working step-by-step.
I was operating in loops.
And those loops aren’t theoretical — they’re happening in parallel, constantly influencing each other.
That’s what eventually became my “process.”
The Loop
The Loop
Identify — what’s actually worth solving
Evaluate — what holds up under pressure
Design — what can work as a system
Deliver — what we can actually ship
Validate — what proves itself in reality
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.
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.
Where Most Product Work Breaks
Where Most Product Work Breaks
The gap between a good idea and a real system.
That’s where:
Constraints show up
Edge cases multiply
Delivery gets messy
That gap is where I spend most of my time.
What This Actually Is
What This Actually Is
This isn’t about following a process.
It’s about constantly connecting...
Business problems
Technical constraints
Real-world outcomes
...early enough that what you build actually works when it matters.
How This Was Built
How This Was Built
I Don’t Memorize — I Map
I Don’t Memorize — I Map
From early math to relational database design, I kept noticing the same thing: everything connects if you’re looking for structure.
Now I’m almost always running a parallel thread:
How does this connect?
Where does this break?
Is this efficient?
That applies to systems, workflows, and even everyday decisions.
I’m also aware this might not be perfectly measurable — but the output tends to validate it.
Product Has No Single Truth
Product Has No Single Truth
Product isn’t an objective discipline — it’s a collection of perspectives.
Most people are reacting to one slice — discovery, delivery, growth, UX — and presenting it as the whole.
That realization changed how I work:
I don’t follow a single approach.
I connect multiple perspectives at once.
Product is like the sun — everyone is reacting to it, but most people only see one ray.
I’m continuing to refine this thinking and document it in smaller pieces.
I’m continuing to refine this thinking and document it in smaller pieces.
See “Thinking” for short insights
Page updated
Google Sites
Report abuse