The Problem With Strategic Frameworks Before They Got Any Good
Most people still reach for SWOT analysis and Porter's Five Forces when they need to make an actual decision. Those tools aren't broken, but they haven't evolved. The gap between theory and execution is where most strategy initiatives die. That was the frustration driving a shift that eventually crystallized around what people now refer to as the Stuart Marts Revolutionary Vision How One Thinker Reshaped Strategic Frameworks In Modern Practice.Stuart Marts Revolutionary Vision How One Thinker Reshaped Strategic Frameworks In Modern Practice
The core idea is straightforward: strategic frameworks need to account for the way decisions actually get made in organizations, not the way textbooks assume they should. Traditional models treat strategy as a linear process — analyze, plan, execute. Real organizations don't work that way. Decisions cascade, get revised, get overridden by operational pressure, and then everyone looks back and calls it adaptation. The modern framework approach acknowledges that from the start.
The practical method involves mapping decision authority before you map objectives. Most people start with objectives. That's backwards. You need to know who can change direction, who can reallocate resources mid-cycle, and where the informal power structures sit. Without that map, your strategic framework has no traction. It looks good on a slide deck and falls apart in week three of execution. The biggest shift isn't a new diagram or a new acronym. It's the introduction of recursive planning cycles. Instead of annual strategy sessions followed by twelve months of execution, the framework treats strategy as a continuous feedback loop with built-in revision points at twenty-eight day intervals. Research from organizational behavior studies suggests this cadence aligns reasonably well with how knowledge work actually flows in most companies. Another change is the treatment of constraints as first-class citizens. Traditional frameworks treat constraints as obstacles to work around. The modern approach treats them as design parameters. If your budget is fixed and your timeline is fixed, those aren't problems to solve. They're the problem statement itself. This sounds obvious until you watch a strategy team spend six weeks finding ways to bypass constraints instead of designing within them.
The framework also introduces what I call the reversibility test. Before committing to a strategic initiative, ask whether the decision can be reversed within a reasonable timeframe at acceptable cost. If the answer is no, the framework demands a smaller experimental bet first. Most organizations skip this step because they confuse commitment with conviction. They're not the same thing.
How to Build a Strategy That Actually Sticks
Start by identifying your decision rights map. List every strategic initiative you're considering. For each one, answer these questions: who proposes it, who approves it, who executes it, who can veto it, and who absorbs the consequences if it fails. If any of those roles overlap or are unclear, flag it. Unclear decision rights is the number one reason strategic frameworks fail in practice. Next, build your feedback cadence. Twenty-eight days is a useful default. Shorter and you create unnecessary re-planning overhead. Longer and the feedback loop becomes academic. At the end of each cycle, measure three things: what changed in your external environment, what changed in your internal capacity, and whether your current plan still matches both. If two out of three are different from the previous cycle, you need a revision session, not a status meeting. Then apply the reversibility filter to every major initiative. If a decision is irreversible, break it into reversible components. If you can't break it down, you don't have enough information to proceed. I've seen teams push forward anyway. They usually do it under time pressure from above. The results are predictably expensive.
Get the Full Details
Document everything in a living format. Not a presentation. A document that multiple people can edit in real time. When strategic frameworks exist only in slide decks, they become performance artifacts rather than working tools. The moment someone locks them in a static format, the framework starts decaying. Information goes stale. People stop updating it. Then everyone refers to the stale version and calls it strategy.
Where This Approach Breaks Down
It doesn't work in highly hierarchical organizations where decision-making is centralized and opaque. If the real decisions are made in rooms you don't have access to, mapping formal decision rights gives you a false sense of control. You'll follow the framework perfectly and still miss the actual dynamics. The workaround is to supplement formal mapping with informal relationship mapping — who influences whom, what information flows through which channels, where are the unofficial approval points. This takes more time and it's harder to institutionalize, but it's necessary in those environments. The twenty-eight-day cycle doesn't fit all industries. Regulated industries with long compliance review periods may need longer cycles or a hybrid approach where operational decisions cycle at twenty-eight days while strategic decisions follow a slower rhythm. Forcing a single cadence across both creates friction. Let them run at different speeds and schedule alignment points at natural breakpoints. The reversibility test can also create paralysis if applied too rigidly. Some decisions genuinely require commitment. The framework should be used as a thinking tool, not a gatekeeper. Use judgment about which decisions are reversible and which aren't. If you apply it mechanically to everything, you'll spend more time analyzing reversibility than making decisions.
One more thing that catches people off guard: this framework assumes a baseline level of organizational transparency. If your company culture punishes bad news or rewards optimism bias, the feedback cycles will produce sanitized data. Everyone will report stability because stability is safe. The framework is only as good as the signals it receives. No amount of structural design fixes a culture that rewards dishonesty.
