How I think
Creating order out of chaos, in practice.
It isn't a slogan. It's the sequence I run when I walk into a situation where the information is scattered and nobody agrees on what's actually wrong.
The sequence
(a) · Problem solvingFind the different versions of the problem
Different people routinely describe the same problem differently. Collect the versions before choosing one.
Check the data and how it's being read
The data may be wrong, incomplete, or interpreted incorrectly. Verify before building on it.
Find the people who actually know
Firsthand knowledge, not assumptions passed through three layers of retelling.
Establish ownership
Who should actually be responsible for solving this? Unowned problems stay unsolved.
Define success
What does this problem being solved actually look like, concretely?
Organize fragmented information
The information usually exists, scattered across systems, teams, spreadsheets, tickets and people's heads.
Determine the path forward
Once the problem is understood, I can build a plan around the reality of it instead of around assumptions.
How I prioritize
(b) · Trade offsWhat I weigh
I'll take a hard initiative affecting fewer users over an easy one affecting many, when the harder one genuinely moves the product and the business forward.
Before a major commitment I want scoped requirements, a credible delivery plan, an estimated outcome, and real measurable value. Not one of those is optional.
How I use data
(c) · EvidenceNot because dashboards look impressive. Because I want to know what is actually happening. The pattern repeats: an important question, fragmented information, organize it, make reality visible, decide, measure, adjust.
"Can we actually deliver this?"
Capacity Planner
"Is Product actually behind?"
Epic Progress Tracker
"What are our customers asking for?"
Client Hot Sheets
"What are we building, and why?"
Interactive Roadmap
"Did we deliver what we committed?"
Quarterly delivery results
Important question
Information is fragmented or unclear
Organize the information
Make reality visible
Make the decision
Deliver
Measure
Adjust
Commitments and capacity
(d) · DeliveryCapacity is finite
Every priority creates another nonpriority. Pretending otherwise just moves the disappointment to the end of the quarter.
Something in, something out
Don't commit to what can't realistically be delivered. If new work must come in, understand what moves out, and say so.
Measure, then plan
Quarterly delivery performance feeds the next quarter's commitments. That's how 87% became 99%.
Customers
(e) · OrientationI like customers. Not as a stakeholder category. I like understanding their work and helping them do it. Product shouldn't be an order taking function that collects requirements and hands them to Engineering.
A customer request is information. The problem underneath it is what I'm after, and that's what connects customer needs to product strategy instead of to a backlog.
What I ask
- What are you trying to accomplish?
- What's getting in your way?
- Why does it matter?
- Who is affected?
- What does success look like?
Data should inform judgment, not replace it
(f) · JudgmentThe point of making reality visible is not to hand the decision to a dashboard. It is to make the trade offs clear enough to use judgment well.
AI is leverage, not identity
(g) · LeverageAI is leverage, not identity. I reach for it when it saves time, improves a decision, organizes information, finds patterns, cuts repetitive work, raises quality, prototypes an idea, or lets me build something that would otherwise have needed another team.
That's how a 3 to 4 week RFP gap analysis became a two day one, and how the interactive roadmap got built at all. The judgment stays mine.