The Gapp-Fisher Model
How ideas actually become reality in a small business.
You decide your team needs to communicate better. Six months later, nothing has changed.
You decide to be more customer-focused. A year later, customers complain about the same things.
You decide to encourage innovation. Your team still defaults to the same playbook.
None of these failures are about effort or commitment. They’re about something most strategy advice skips entirely: the work that has to happen between a decision and a reality. Between what a business says it does and what it actually does day to day.
The Gapp-Fisher Model gives that work a shape. It was developed by Rod Gapp and Ron Fisher at Griffith University in 2007. In my PhD research with Australian small and medium business owners, I used it as a lens to understand how good ideas survive the trip from a whiteboard to a way of working — and why so many don’t.
If you’ve ever wondered why a clear plan doesn’t translate into clear behaviour, this is the framework that explains it.
What the model says
The Gapp-Fisher Model describes how ideas travel from thought to reality through five stages: Discover, Invent, Transformation Zone, Produce, Generalise. Discover and Invent are the thinking phases. Produce and Generalise are the doing phases. The Transformation Zone is the bridge between them — and it’s where most ideas die.
Chris Argyris called the two ends of this bridge espoused theory and theory-in-use: the version of how things work that lives in the strategy document, and the version that actually plays out on a Tuesday afternoon.
Espoused theory
What we say we do. The values on the wall. The agreed approach. The strategy document.
Theory-in-use
What we actually do. The defaults under pressure. The way decisions really get made. The behaviours customers and staff observe.
The gap between those two is the gap the Gapp-Fisher Model is designed to close. Not by trying harder. By learning differently.
Stage 1 of 5
Discover
You can’t fix what you can’t see. Discover is where the real problem becomes visible.
Discover is about noticing — honestly — what’s actually happening inside the business. Not the version reported in the management meeting. The real version. The one the people closest to the work see every day.
For most small business owners, Discover gets skipped or rushed. You spot a symptom (a drop in repeat orders, a senior person resigning, a customer complaint), reach for the most obvious cause, and start fixing. That’s not Discover. That’s reacting.
Real Discover is slower. It asks: what’s the pattern underneath this symptom? What do my staff know that I don’t? What’s the difference between what we said we’d do and what we’re actually doing?
The founders I spoke with treated Discover as a habit, not an event. They created small, regular ways to surface uncomfortable information before it became a crisis. Honest one-to-ones. Customer conversations without a script. Walking the floor with no agenda. The point wasn’t to gather data. It was to notice the gap between the espoused version of the business and the lived one.
In practice:
- Ask your team where they think the business loses time, money, or goodwill — and listen without correcting.
- Spend a week noticing decisions that contradict your stated values. Don’t fix them yet. Just notice.
- Read your last three customer complaints as feedback, not as failures.
Stage 2 of 5
Invent
Once you’ve seen the problem clearly, the next step is making sense of it — together.
Invent is the stage where understanding gets built. Not a solution, yet. Understanding. The founders in my research were unusually patient at this stage. They resisted the urge to jump from “we have a problem” to “here’s the fix.” They brought people together to look at the problem from different angles first.
This stage relies on what I called the holistic collective — a small, diverse group of people who care about the same outcome. Diverse not for the sake of it, but because a problem looks different from inside finance than it does from inside sales. The team’s job in Invent is not to agree quickly. It’s to surface the disagreements early, while they’re still useful.
The friction this creates has a name in Argyris’s work: dissonance. It’s the productive discomfort that happens when one person’s understanding rubs up against another’s. Dissonance is uncomfortable, but it’s where double-loop learning starts. Skip the dissonance and you’ll skip past the real problem.
In practice:
- Bring three to five people who see the problem differently into one conversation. Don’t chair it like a meeting; let it breathe.
- Ask each person what assumption they’re making that the others might not share.
- Resist closing too early. If the room agrees in fifteen minutes, you haven’t found the real problem yet.
Stage 3 of 5 · The bridge
Transformation Zone
This is where most ideas die. It’s also the stage most strategy advice ignores.
The Transformation Zone is the bridge between thinking and doing. It’s where an espoused idea — what the business says it will do — either becomes a theory-in-use, or doesn’t. You can’t measure your way across it. You can’t write your way across it. You can only walk across it, deliberately, with the people who’ll be living the change.
In the businesses I researched, this stage looked almost mundane. People testing small versions of the new way. People talking about what they tried, what surprised them, what felt wrong. People adjusting before anyone called it a project. There was no grand launch. There was a steady accumulation of small, observable shifts in behaviour — and a willingness to keep talking about why.
What makes the Transformation Zone hard isn’t the work itself. It’s the defensive routines that show up when an idea starts to threaten how things have always been done. Quiet resistance. Polite agreement that goes nowhere. Loud agreement that goes nowhere. The Transformation Zone is the stage where soft systems thinking earns its keep, because the obstacle is almost never the idea. It’s the established way of being that the idea is trying to displace.
If your strategies usually stall right after the kick-off, you have a Transformation Zone problem.
In practice:
- Choose one small, visible behaviour that would change if the new idea were real, and start there.
- Build in deliberate moments to talk about what’s actually happening — not what was planned to happen.
- Watch for “yes, but” patterns from senior staff. That’s the espoused-theory and the theory-in-use talking past each other.
Stage 4 of 5
Produce
Now the new way is real. The job is to make it better — through cycles of small, honest improvement.
Produce is where the new behaviour, product, or process is being done — and where it gets refined. This stage is powered by the PDSA cycle (Plan-Do-Study-Act) that Deming made famous. PDSA runs inside every stage of the Gapp-Fisher Model, but it earns its keep in Produce, because this is where the question shifts from “should we do this?” to “what’s the next improvement?”
The founders I spoke with were unusually open at this stage. They expected to be wrong about some of the details. They built in regular review points so that being wrong was useful, not embarrassing. They treated mistakes as information.
This is also the stage where most businesses lose the soft-systems advantage they built earlier. The team that had honest, diverse conversations in Invent goes quiet. The leader who walked the floor in Discover stops walking. The work returns to a small group, and the broader understanding of the problem evaporates. When that happens, the loop closes and improvement stops — even if the new process keeps running.
In practice:
- Set a fixed cadence to review what’s working and what isn’t. Weekly is usually right; monthly is usually too slow.
- Make the review safe enough that people will tell you about the small frustrations before they become big ones.
- Treat each round as a chance to learn, not a chance to grade.
Stage 5 of 5
Generalise
The new way becomes the way. And what you learned becomes useful somewhere else.
Generalise is where the new theory-in-use settles into the business as the default. It’s also where the lessons become portable — applicable to other parts of the business, other problems, other teams. Generalise is not the end of the cycle. It’s the beginning of the next one.
In the businesses I researched, this stage was rarely formal. It looked more like: a new way of running meetings becomes “how we run meetings here.” A new way of handling customer complaints becomes “how we handle customer complaints here.” A new way of making decisions becomes the unwritten standard, observable in the behaviour of new hires three months after they join.
The risk at this stage is calcification. The new way works, so it stops being questioned. Six months later, conditions shift, and the now-default behaviour quietly stops fitting. The strongest small businesses in my research treated Generalise as provisional. The current way was the best they knew right now. They expected to come back to Discover sooner or later.
In practice:
- Codify the new way lightly — enough that someone new can pick it up, not so much that it can’t change.
- Ask, regularly, what conditions made the new way necessary, and whether those conditions still hold.
- Treat the next Discover as a sign of health, not a sign of failure.
How the stages fit together
The Gapp-Fisher Model is a cycle, not a checklist. You’ll often be in more than one stage at once. A single conversation might surface a new Discover while you’re still in Produce on something else. That’s normal.
What matters is that all five stages get the time they need — especially the Transformation Zone, which is the one most likely to be skipped under pressure. A business that consistently moves through all five tends to learn faster than its competitors. A business that runs straight from Discover to Produce, skipping Invent and the Transformation Zone, tends to keep solving the same problem over and over without ever asking whether the problem was framed correctly in the first place.
There’s a useful pairing here with single-loop and double-loop learning. Single-loop learning is when you stay inside one Gapp-Fisher cycle, refining what you’re already doing. Double-loop learning is when a cycle prompts you to question the goal itself — and start a new cycle further upstream. Both matter. Businesses that only do single-loop learning get more efficient at the wrong thing. Businesses that only do double-loop learning never finish anything.
If the cycle has a heartbeat, it’s the PDSA cycle running inside each stage — small tests, honest study, deliberate change. The Gapp-Fisher Model is the macro view; PDSA is the micro view. You need both.
Where this comes from
The Gapp-Fisher Model was developed by Rod Gapp and Ron Fisher in 2007 to bring the human side of organisations back into focus in fields — like quality management and innovation — that had drifted toward purely technical, resource-based thinking. It draws on Chris Argyris’s work on theory-in-use, espoused theory, and double-loop learning, and on W. Edwards Deming’s PDSA cycle.
In my PhD research at Griffith University, I used the Gapp-Fisher Model as a lens to study how small and medium business owners in Australia actually take ideas from concept to reality. The model held up across nineteen founders and fifteen industries — not as a rigid sequence, but as a recognisable pattern in how learning organisations work
Where to go next
If this framework was useful, the related ideas worth exploring next are: