Every consultancy has a framework. Most of them share the same flaw: they map your organization, not your decisions.
The 7S model. The Business Model Canvas. The endless variations of the marketing mix. They are all excellent at describing what a business is. None of them tell you what a business must do — which is to make decisions, fast, and execute them.
That gap is why so many strategy projects end the same way: a beautiful deck, a satisfied steering committee, and absolutely nothing shipped six months later.
We built the RESOLVE Model™ to close that gap. It is not another checklist. It is a map of the decision chain — with a clock on it.
The Core Insight
Businesses rarely fail because they lack a plan. They fail because decisions are slow, poorly framed, or never executed.
Consider the evidence you have probably seen in your own organization:
-
Months of analysis that end in a decision everyone nods at — and no one owns.
-
A pilot that runs for a year and is quietly abandoned.
-
A strategy that was brilliant in the boardroom and invisible on the shop floor.
-
A market entry that stalled at the first regulatory hurdle.
None of these are failures of planning. They are failures of resolution — the capacity to move from uncertainty to execution without delay.
That is why we don't map your departments. We map your decisions.
The Architecture: Three Layers
Most frameworks confuse themselves by mixing levels of abstraction — putting "Product" next to "Paper" as if they were peers. RESOLVE separates three distinct layers, each answering a different question. RESOLVE Model™ is a trademark of HaagHarris Management Group.
| Layer | Question it answers |
|---|---|
| The Cycle | How does a decision travel from signal to sustained outcome? |
| The Domains | What does the decision affect? |
| The Time Gates | How fast must each phase move before it becomes a liability? |
Clean layers. No overlap. And crucially, no element that exists only because it made the acronym work.
Layer 1: The RESOLVE Cycle
Seven phases. Every one is an action verb — because a decision chain is made of actions, not categories. And every phase has a gate you must pass to move on, a failure mode if you skip it, and a way to compress it.
R — Recognize
Name the actual decision to be made. Not the symptom, not the project — the decision.
Skip it and you solve the wrong problem.
Gate: Have we stated the decision in one sentence?
E — Evaluate
Define what you are choosing between, and what you are giving up. Every real decision has a price.
Skip it and you get analysis paralysis — or decision drift.
Gate: Do we know the trade-offs explicitly?
S — Select
A named person commits, in writing, to a direction.
Skip it and you get consensus that no one owns.
Gate: Is there a single accountable owner, documented?
O — Organize
Get the right people, partners, and capital to the table.
Skip it and you get brilliant strategy with no capability behind it.
Gate: Do we have what — and who — we need?
L — Launch
Ship something. In 90 days.
Skip it and you enter pilot purgatory, from which few return.
Gate: Has anything actually shipped?
V — Validate
Measure whether it worked — and why.
Skip it and sunk-cost persistence takes over.
Gate: Do we know what the outcome was, and what caused it?
E — Evolve
Institutionalize the resolution. Make it how you operate, not a project you ran.
Skip it and the win is celebrated once and never repeated.
Gate: Is this now standard practice?
And then the loop closes. Validate feeds directly back into Recognize. That feedback arrow is the most important line in the model — because it is the admission that no decision is final, and the discipline of returning to the question is what separates resilient organizations from lucky ones.
Layer 2: The Five Domains
Every decision affects one of five things. Not nine. Five.
| Domain | What it covers |
|---|---|
| Market | Customers, segments, demand, brand position |
| Offering | Products, services, innovation, IP |
| Operations | People, process, systems, governance |
| Ecosystem | Partners, government, investors, cross-border relations |
| Capital | Funding, pricing, returns, risk |
This is a diagnostic in itself. If you cannot place a decision in one of these five domains, the framing is wrong. If a decision touches all five, you have found something genuinely strategic.
Notice what is in that list that most frameworks miss: customers, capital, and — most importantly for us — the ecosystem. The relationships with governments, investors, and international partners that determine whether a market entry succeeds or dies at the border.
That domain is not an afterthought for us. It is our home turf.
Layer 3: The Time Gates
This is where RESOLVE diverges most sharply from every framework you have seen.
Each phase carries a maximum time budget, beyond which it stops being diligence and becomes a liability:
| Phase | Time Budget |
|---|---|
| Recognize | Days |
| Evaluate | Weeks |
| Select | Hours - one room, one decision |
| Organize | Weeks |
| Launch | 90 days |
| Validate | Monthly loop |
| Evolve | Quarterly |
Why does this matter? Because your strategy does not compete against another strategy. It competes against the speed of your decision cycle. A competitor who decides in three weeks and ships in sixty days will beat a competitor who decides perfectly in nine months — every single time.
We call the cost of that delay decision drag. Most organizations have never measured it. Most are losing more to it than to any competitor.
The Diagnostic: Your Resolution Score
A model that only exists on a slide is decoration. So we made RESOLVE measurable.
Score each of the seven phases from 1 to 4. Chart the result. The lowest-scoring phase is your bottleneck — the gate where your organization is losing time and money.
Two things follow from that:
-
You don't need a nine-month audit. You need the bottleneck fixed.
-
You can measure progress. A resolution score can be tracked the way you track revenue.
This is what we mean when we say we don't sell hours. We sell the resolution of the one thing that is throttling everything else.
Why RESOLVE Is Different
he honest comparison:
The 7S model and the Business Model Canvas map your organization. The marketing mix maps your offer. RESOLVE maps your decisions — and puts a clock on them.
Organization-centric frameworks tell you what you have. Decision-centric frameworks tell you what to do next, by when, and who owns it.
For a world where complexity is the norm and speed is the only durable advantage, that is the difference that matters.
Where It Comes From
RESOLVE was built from practice, not from a whiteboard. It is the distilled pattern behind the work we do:
-
Facilitating a strategic roundtable between a Swiss pharmaceutical venture and a delegation from the Omani Ministry of Health — where the model's Select and Organize gates were the whole game.
-
Introducing four Swiss health-tech startups to government decision-makers in Bern, and moving from introduction to signed memoranda of understanding in a single morning.
-
Evaluating wearable technology at the University of Bern Innovation Lab, where the question was never "is this interesting?" but "should we commit, and by when?"
In every case, the value was not in the analysis. It was in the resolution.
Ready to Find Your Bottleneck?
If you recognize any of the failure modes above in your own organization — decision drift, pilot purgatory, consensus without ownership — the Resolution Score is a fast way to find out where you are losing time.
It takes a workshop, not a quarter. And it produces a decision, not a deck.
[Get in touch] — and let's find the gate that is slowing everything else down.
and let's find the gate that is slowing everything else down.
Add comment
Comments