Frameworks Ecosystem Method for Strategy Consultants
For strategy consultants and internal planning leads · Based on BSC Designer Strategic Frameworks Ecosystem Method
// TL;DR
Strategy consultants and internal planning leads often deliver strong insight that decays after the engagement—leaving clients with artefacts they don't maintain. The Frameworks Ecosystem Method gives you a repeatable system: map the client's position on the Ecosystem Diagram, select a framework bundle by decomposition need, convert findings into Strategic Ambitions, and build a single source of truth with traceable links between analysis and execution. Use it to deliver strategy that survives between cycles and lets clients trace the rationale for every goal—turning one-off workshops into living scorecards.
Why does our strategy work stop being used after the engagement?
The classic consulting failure isn't weak analysis—it's that the output is an ad hoc collection of spreadsheets and slides the client can't maintain. The Frameworks Ecosystem Method treats this as the most dangerous pattern in strategic planning and prescribes its antidote: a single source of truth where all framework results, scorecards, and analysis versions live in one shared workspace with traceable rationale.
For consultants and internal planning leads, this reframes your deliverable from a report to a living strategy system.
How do I diagnose where a client's planning is weak?
Start every engagement by mapping the client against the Frameworks Ecosystem Diagram:
- Inner Circle — strategic scaling and execution (Balanced Scorecard).
- Middle Circle — strategy description.
- Outer Circle — strategy formulation and analysis (PESTEL, Porter's, Ansoff).
Identify the weakest circle. This determines where you add frameworks—driven by the client's actual gap, not by what's fashionable. A client with a mature scorecard but no environmental scanning needs Outer Circle work; a client drowning in analysis but unable to execute needs Balanced Scorecard cascading.
How do I select the right framework bundle?
Use the recommended top-five as a starting checklist, then match to challenges:
1. Stakeholder Analysis — clarify stakeholders and their Strategic Ambitions.
2. PESTEL — analyse external factors.
3. Porter's Five Forces — analyse the competitive environment.
4. Ansoff Matrix — formulate growth strategies.
5. Balanced Scorecard with Strategy Map — describe, cascade, and execute.
The governing question is: which decomposition axis is missing from the client's current picture? Select accordingly. You don't have to use all five.
How do I make findings survive the handover?
This is where consultants add lasting value. Convert every raw finding into a Strategic Ambition—with specific impact, stakeholders, sub-goals, action plans, risks, and quantified value—then cascade confirmed ambitions through the Balanced Scorecard perspectives.
Crucially, maintain contextual linkage: a dynamic link or history-of-changes record connecting each scorecard goal to its source analysis. Store framework templates with your team's remarks in a 'Strategic Analysis' folder. Remarks are what make an archive usable—a template without context is a dead artefact in the next cycle.
How does this differ from a one-off strategy workshop?
A workshop produces insight that fades; this method produces a self-maintaining system. Because every goal traces back to the analysis that justified it, the client can re-run frameworks at the next cycle as an update rather than a rebuild—comparing new findings against archived versions. Your engagement becomes the foundation clients keep returning to, which strengthens retention and referrals.
Next step: On your next engagement, open with an Ecosystem Diagram diagnosis, agree the framework bundle against the client's specific challenge, and commit to delivering a single source of truth with linked source analysis—not a slide deck.
// FREQUENTLY ASKED QUESTIONS
How do I choose frameworks for a client instead of defaulting to favourites?
Map the client on the Frameworks Ecosystem Diagram to find their weakest circle, then ask which decomposition axis is missing—internal/external factors, cause-and-effect, or time. Select frameworks that fill that gap, not the ones you personally prefer or that are trending. Selecting by popularity rather than the client's specific challenges and planning maturity is an explicit pitfall of the method.
How do I make a strategy engagement outlast the project?
Deliver a single source of truth rather than a report: all scorecards and framework templates in one shared workspace, with team remarks archived in a 'Strategic Analysis' folder and dynamic links from every goal to its source analysis. This lets the client re-run frameworks next cycle as an update, not a rebuild, so your work remains the reference point—and the retention driver.
What's the biggest mistake consultants make with these frameworks?
Treating framework outputs as finished strategy instead of raw ideas. A PESTEL or Porter's finding is an input, not a goal. You must convert each into a Strategic Ambition—with impact, stakeholders, sub-goals, risks, and quantified value—before cascading it into goals, initiatives, and KPIs. Skipping this step, or archiving results without remarks, leaves the client with artefacts they can't act on or revisit.