A Framework for Thinking

How I'd Approach Your Problem

Twenty-five years of pattern recognition distilled into five questions worth asking before you spend a dollar, hire a consultant, or make a decision you can't reverse.

The Framework

Five Steps. Five Questions. One Diagnostic.

This isn't a business plan template. It's a thinking tool. Each step forces you to slow down at the exact moment most people speed up. The goal isn't to find the answer — it's to find the right question.

Step 01

Name the Real Problem

Not the symptom. The structure.

Most people come to me with a symptom: costs are too high, a vendor is underperforming, the board is nervous. The first thing I do is refuse to solve that problem. Instead, I ask: what system produced this outcome? What incentive structure made this inevitable? You can't fix a leak by mopping the floor.

The Question to Ask

What keeps happening despite your best efforts to stop it?

From the Field

A Fortune 500 company came to me saying their cloud costs were 40% over budget. The real problem wasn't cloud costs — it was that procurement, engineering, and finance had never been in the same room together. Three departments optimizing for three different metrics. The cloud bill was just the scoreboard.

Step 02

Map the Stakeholders

Who benefits from the status quo?

Every problem persists because someone is profiting from it. Not maliciously — structurally. The vendor who overcharges you has a quota. The consultant who extends the engagement has a mortgage. The internal champion who chose the failing platform has a reputation. Until you map who wins and who loses from change, you're negotiating in the dark.

The Question to Ask

Who would be uncomfortable if this problem disappeared overnight?

From the Field

In a $200M infrastructure deal, I mapped 14 stakeholders across 3 organizations. Seven of them had financial incentives to maintain the current arrangement. We didn't fight them — we redesigned the incentive structure so alignment became more profitable than resistance.

Step 03

Find the Leverage Point

Where does a small push create a large shift?

Donella Meadows taught me that systems have leverage points — places where a small intervention produces disproportionate change. Most people push on the wrong part of the system. They negotiate harder on price when the real leverage is in contract structure. They hire more people when the real leverage is in process design. Find the fulcrum.

The Question to Ask

If you could change only one thing, what would unlock everything else?

From the Field

A media company was spending $8M/year on content delivery and wanted to negotiate a 15% discount. Instead, I looked at their traffic patterns and found that 60% of their bandwidth was serving content nobody watched. We didn't negotiate the price down — we eliminated the waste. Saved $4.8M. The CDN vendor was happy to keep the contract.

Step 04

Design the First Move

Bias toward reversible action.

Analysis paralysis kills more good ideas than bad execution. But recklessness kills more companies than caution. The resolution: design a first move that is bold enough to generate real data but reversible enough that failure is a lesson, not a catastrophe. Jeff Bezos calls these 'Type 2 decisions' — doors you can walk back through.

The Question to Ask

What is the smallest experiment that would prove or disprove your thesis?

From the Field

A healthcare startup wanted to launch in 12 markets simultaneously. I suggested launching in 2 markets with deliberately different strategies — one premium, one value. Within 90 days, we had data that would have taken 18 months of planning to guess at. The premium market won by 3x. We killed the value strategy before it consumed capital.

Step 05

Build the Feedback Loop

What you measure is what you become.

The difference between a strategy and a wish is a feedback loop. Every move should generate information that makes the next move smarter. Most organizations measure outputs (revenue, headcount, deliverables) when they should be measuring learning velocity: how fast are we getting smarter about this problem?

The Question to Ask

How will you know in 30 days whether this is working?

From the Field

After restructuring a $10B technology sourcing operation, we didn't just track cost savings. We tracked decision speed — how long from identifying a need to signing a contract. That metric dropped from 14 weeks to 3 weeks. The cost savings followed naturally, but the real value was in the velocity.

Want to Apply This to Your Situation?

The five questions above are the same ones I ask before taking on any engagement. If you'd rather talk it through than write it down, that's what this is for.

Pick Up the Phone

"The problem is never the problem. The problem is that nobody asked the right question."

— Tony Greenberg