From Analysis to Action
Strategy isn't about running frameworks in isolation. The real value emerges when outputs from one analysis become inputs for the next. This map traces how raw environmental and internal data is progressively synthesised into actionable strategic recommendations.
Stage 1
External Scan
Mapping the environment the organisation operates in
PESTEL Analysis
Political, Economic, Social, Technological, Environmental, Legal
Scans the macro-environment for factors beyond the organisation's control. Each factor is assessed for its current impact and likely trajectory.
Opportunities identified
Threats identified
Trend trajectories
Stage 2
Internal Scan
Evaluating the organisation's own resources and capabilities
VRIO Analysis
Valuable, Rare, Inimitable, Organised-to-capture
Tests each internal resource or capability against four criteria. Only resources passing all four qualify as sustained competitive advantages.
Confirmed strengths
Exposed weaknesses
Competitive implications
PESTEL factors populate
Opportunities & Threats
Opportunities & Threats
VRIO results populate
Strengths & Weaknesses
Strengths & Weaknesses
Stage 3
Synthesis
Combining external and internal findings into a unified picture
SWOT Analysis
The convergence point where external meets internal
SWOT doesn't generate its own data. It is a synthesis framework that organises outputs from the upstream analyses into four quadrants, creating a single integrated view of the strategic position.
Strengths
VRIO-confirmed advantages, core competencies, resource strengths
Weaknesses
Resources failing VRIO, capability gaps, competitive disadvantages
Opportunities
Favourable PESTEL trends, market gaps, emerging demand, regulatory openings
Threats
Adverse PESTEL trends, competitive pressures, regulatory risks
SWOT quadrants are cross-matched
to generate strategic options
to generate strategic options
Stage 4
Option Generation
Systematically producing strategic options from the SWOT picture
TOWS Matrix
Turning the SWOT picture into strategic options
TOWS is the action engine of the synthesis process. It systematically crosses each internal factor (S/W) against each external factor (O/T) to force out strategic options that wouldn't surface from SWOT alone.
Opportunities
Threats
Strengths
SO Strategies
Use strengths to exploit opportunities
Maxi-Maxi
Use strengths to exploit opportunities
Maxi-Maxi
ST Strategies
Use strengths to counter threats
Maxi-Mini
Use strengths to counter threats
Maxi-Mini
Weaknesses
WO Strategies
Address weaknesses to exploit opportunities
Mini-Maxi
Address weaknesses to exploit opportunities
Mini-Maxi
WT Strategies
Minimise weaknesses and avoid threats
Mini-Mini (defensive)
Minimise weaknesses and avoid threats
Mini-Mini (defensive)
Strategic options are prioritised, evaluated,
and refined into recommendations
and refined into recommendations
Stage 5
Recommendations
Evidence-based strategic recommendations with clear lineage
Strategic Recommendations
The output of the entire synthesis chain
Every recommendation traces back through the chain: which TOWS combination generated it, which SWOT factors informed it, and which PESTEL/VRIO findings originated the data. This audit trail is what makes the strategy evidence-based rather than opinion-based.
SO-derived growth plays
ST-derived defensive moves
WO-derived development priorities
WT-derived risk mitigations
Traceability Example
How a single recommendation traces back to raw data
PESTEL Finding
Government announces mobile money interoperability mandate (Political/Technological)
→
Enters SWOT as
Opportunity: New interoperability rules create level playing field for mobile banking expansion
→
TOWS crosses with
Strength (from VRIO): Established digital platform with large existing user base = SO Strategy
→
Recommendation
Accelerate cross-platform mobile banking services leveraging existing user base before competitors catch up
The Synthesis Principle
PESTEL and VRIO are data-gathering tools. SWOT is a synthesis framework. TOWS is a generation engine. Each plays a distinct role in the chain. Running them in isolation produces lists; running them as a connected pipeline produces strategy. The discipline is in the connections between the frameworks, not in any single framework itself.