Strategy and Risk Analysis Frameworks

These are eight classic business analysis frameworks turned into editable worksheets: SWOT, PEST, 5 Whys root cause analysis, a 5x5 risk assessment matrix, force field analysis, gap analysis, scenario planning and FMEA. Managers, business and operations analysts, product and engineering leads use them to prepare strategy reviews, investigate problems and argue for or against a change with something more structured than a slide of bullet points.

8 free tools · no sign-up · no ads

All Business Analysis (8)

Which tool do I need?

  • Map external trends before a strategy review

    List political, economic, social and technological factors with dates, then turn the biggest uncertainties into scenarios with planned responses.

    PEST AnalysisScenario Planning

  • Summarise our position against competitors

    Fill the four SWOT quadrants with evidence, keeping internal strengths and weaknesses apart from external opportunities and threats.

    SWOT Analysis

  • Trace an outage or defect back to its cause

    Write the problem statement, answer why up to five times with evidence, and record the root cause and actions.

    5 Whys Root Cause Analysis

  • Rank project risks for a steering committee

    Place risks on the 5x5 probability and impact grid for a quick view, and use FMEA where a process needs a detailed RPN breakdown.

    Risk Assessment MatrixFMEA Analysis

  • Plan how to get from today's process to a target state

    Describe each gap with its current and desired state, then weigh the forces that will help or block the change.

    GAP AnalysisForce Field Analysis

About Business Analysis

Each framework answers a different question. PEST and scenario planning look outward at forces you do not control and at how the future might unfold. SWOT and gap analysis describe where you stand and how far you are from where you want to be. Force field analysis weighs the pressures for and against one specific change. The 5 Whys, the risk matrix and FMEA deal with problems: what caused this, which risks matter most, and which failure modes in a process deserve attention first. They feed each other. PEST factors become the Opportunities and Threats of a SWOT, a SWOT weakness becomes a gap with an owner, and the risk matrix gives a quick ranking that FMEA can break down for the highest-scoring process.

The frameworks structure thinking; they do not supply answers. Scores in the risk matrix and FMEA only mean something when the team has agreed written definitions for each level, and multiplying severity by occurrence can hide a rare but catastrophic failure, so treat the top severities as urgent whatever their total. SWOT and PEST save to localStorage and export JSON. Force field analysis saves nothing automatically, so export before closing the tab.

Guides

Frequently asked questions

What is the difference between a risk matrix and FMEA?

A risk matrix ranks a list of risks by probability and impact on a 5x5 grid. FMEA goes deeper on one product or process, rating each failure mode for severity, occurrence and detection and multiplying them into a Risk Priority Number.

Should I do a PEST analysis before a SWOT?

Usually, yes. PEST collects the external factors, and the ones that matter most become the Opportunities and Threats in the SWOT, which keeps that half of the matrix grounded in evidence.

Is PEST the same as PESTLE?

PESTLE adds Legal and Environmental factors to the four PEST headings. The PEST board here has four columns, so teams that use PESTLE usually prefix legal and environmental items within the closest column.

How many frameworks should one strategy review use?

Two or three is plenty. A common set is PEST for context, SWOT for position and gap analysis for actions. Running all eight on one question tends to produce volume rather than decisions.

Why do teams argue about risk scores?

Usually because nobody wrote down what each level means. Agree definitions such as "impact 4 means more than a week of delay" before scoring, and most disagreements disappear.