Understanding Reinvention as a Systematic Practice
Olivier Giner has spent the last decade working with mid-cap and enterprise organizations on structural change, mostly in European markets but occasionally in North America. His approach to business reinvention isn't a single framework you can buy and implement over a weekend. It's a collection of principles that, when combined, produce something more durable than most transformation programs. The core idea behind his work is that most companies try to reinvent their products or services without first reinventing how they make decisions. Giner argues this sequence is backwards. You fix the decision architecture, and the product changes follow naturally. I ran into this exact problem at a client who had just hired a strategy consultant to redesign their go-to-market model. Three weeks in, the new model was being approved through the same five-layer approval chain that had killed three prior initiatives. The structure didn't change even though everyone agreed the old structure was broken. We spent two days mapping every decision that slowed customer-facing moves, then created a simple RACI matrix with explicit veto points. The turnaround from proposal to launch went from eleven days to four. Giner's method starts with what he calls institutional memory mapping. You document every process that exists today not as it should work but as it actually works. This means shadowing people for a full work cycle and recording where work stalls, where it gets redirected, and where someone overrides a procedure because the written version doesn't match reality. Most organizations skip this step and jump straight to benchmarking against competitors. Benchmarking tells you what good looks like somewhere else. It doesn't tell you what's actually blocking your own organization from moving faster.
After the mapping phase comes the constraint audit. You identify the three or four bottlenecks that, if removed, would unlock the most downstream flow. This is usually where people get uncomfortable because the bottleneck often traces back to a person or a team with real political power. I learned this the hard way during a retail transformation project where the constraint was an internal compliance review that nobody except one director could push through. The director was protecting liability exposure, which was legitimate, but the review process added eight days to every product launch. The workaround wasn't to remove the review. It was to restructure it into a parallel process with clear escalation criteria so that routine cases auto-passed and only exceptions required human attention. That cut the average review time from eight days to one and a half.
The Decision Architecture Layer
This is where Giner's work diverges from most management consulting. The decision architecture piece involves redesigning who can decide what, under which conditions, and with what information. It's not org chart gymnastics. It's about codifying authority boundaries so people stop asking permission for things they already have the right to decide. I've seen this reduce meeting volume by roughly sixty percent in organizations that had adopted it correctly, though the initial pushback is always intense. People mistake clarity for rigidity. They're not the same thing. Clarity means everyone knows exactly what they're allowed to do without checking. Rigidity means you can't adapt when circumstances change. Good decision architecture has both explicit authority and explicit escape hatches. The escape hatch is another concept worth understanding. It's a predefined condition under which someone can override the standard process and still face zero consequences. Without escape hatches, people either ignore the process quietly or freeze entirely when something unusual happens. With them, you get visibility into edge cases and the data to refine the process over time. I keep a simple spreadsheet tracking escape hatch usage across clients. Organizations that never use them tend to be the ones complaining about slow decision-making the loudest. That's not a coincidence.
Get the Full Details
Common Pitfalls That derTail Projects
The biggest mistake I see is treating reinvention as a project with an end date. Giner's work explicitly frames it as a continuous discipline. You don't complete reinvention. You maintain it. Companies that hire for a six-month engagement and expect to walk away with a permanent advantage almost always regress within eighteen months. The second mistake is starting with technology. Digital transformation without the organizational decision structure in place just automates inefficiency at higher speed. I watched a company deploy a sophisticated workflow automation tool that cut their internal approval cycle from five days to two while the actual decision quality got worse because nobody had clarified what criteria should govern those approvals. A less obvious pitfall involves measurement. Reinvention programs often define success as speed or cost reduction. Those are output metrics. The better leading indicator is the ratio of decisions made at the lowest appropriate level to total decisions in the organization. If that ratio isn't climbing over successive quarters, the reinvention isn't sticking. It's just a rebranding exercise with new slide decks.
What This Approach Doesn't Solve
Reinvention through decision architecture won't fix a company that lacks market demand for its products. It also doesn't help when leadership is fundamentally misaligned about direction. If the CEO wants growth and the CFO is actively blocking investment, no amount of process redesign will resolve the tension. You need strategic clarity before you need structural clarity. Structure amplifies strategy. It doesn't create it. There are also cases where the constraint isn't organizational at all. A supply chain bottleneck, a regulatory bottleneck, or a talent shortage outside your control won't respond to internal decision redesign. Misdiagnosing the constraint type is probably the most expensive error you can make, and it's surprisingly common.
Getting Started With the Method
If you want to apply this, start small. Pick one process that affects customers directly and map it for a full week. Don't fix anything yet. Just document what actually happens. Then run the constraint audit on that single process. Identify the bottleneck, design the escape hatch, and measure the change over thirty days. If the metric improves, expand to the next process. If it doesn't, you've only invested thirty days instead of thirty months. I recommend keeping a decision log alongside the process map. Every time someone escalates, bypasses, or disputes a decision, record it. Six weeks of that data will show you more about your actual organization than six months of strategy sessions ever will.
