The order I would actually use them.

Four frameworks for decisions the spreadsheet cannot settle: work out what kind of problem you are actually facing, rehearse the futures it could land in, price the choice branch by branch, then let the team fail the plan on paper while it can still be changed.

Cynefin Framework→Scenario Planning→Decision Trees→Pre-mortem

Four frameworks in the order I would actually use them: read the macro weather, judge whether the industry can pay you, name the risk you are really taking, then make a choice whose reasoning you can still defend a year later.

PESTEL Analysis→Porter's Five Forces→Ansoff Matrix→Decision Matrix (Weighted Scoring)

Four frameworks for a team that is not working: find the layer that is actually broken, judge whether you are watching a fault or a phase, check the team was built for the job in the first place, then have the one-to-one conversations that change things.

The Five Dysfunctions of a Team→Tuckman's Stages of Group Development→Belbin Team Roles→GROW Model

A launch sequence built on one hard-won lesson: work out what customers would actually hire your product to do before your enthusiasm spends the budget. Job, proposition, beachhead, then a rhythm of cheap tests once you are live.

Jobs to be Done→Value Proposition Canvas→Crossing the Chasm→Build-Measure-Learn

Change lands person by person or it does not land at all. Diagnose the culture underneath, respect the physics of unfreeze and refreeze, run the programme in the right order, and check where each individual has actually got stuck.

Schein's Three Levels of Culture→Lewin's Three-Step Model→Kotter's 8-Step Change Model→ADKAR Model

I built a business and stepped back from it myself, so I built this the way I wish someone had handed it to me: map who actually sits where before anyone argues about who's right, widen the circle to everyone else who has a stake, pin the decision rights in writing, then manage the human side of letting go, because the paperwork is the easy part.

Family Business Governance (Three-Circle Model)→Stakeholder Mapping (Power-Interest Grid)→RAPID Decision Roles→Bridges' Transition Model

A sequence for putting a number on your work without flinching: find the job customers actually hire you for, price the value rather than the hours, check the volume the price must sustain, then imagine the new price list failed and find out why before it does.

Jobs to be Done→Value-Based Pricing→Break-even Analysis→Pre-mortem

Governance is my day job, so this is the order I build it in for real clients: settle who owns risk and who checks it, pin decision rights to named people, take the same discipline down to task level, then give the whole structure a live risk register to manage.

Three Lines of Defence→RAPID Decision Roles→RACI Matrix→Risk Matrix

Annual planning as a chain of decisions instead of a writing exercise: surface the assumptions, make the real choices including what to stop, draw the logic on one page, then commit to numbers that report back every quarter.

SWOT Analysis→Playing to Win (Strategy Choice Cascade)→Strategy Maps→Objectives and Key Results (OKRs)

Diagnosis before initiatives. Find out whether each sale makes money, where the losses pile up and what is throttling output, then point the whole organisation at the few fixes that matter. A week of honest arithmetic saves a year of energetic guesswork.

Unit Economics→Pareto Analysis→Theory of Constraints→Hoshin Kanri

Customer understanding built in layers: choose whom to serve and whom to decline, learn the job they are actually hiring you for, sort your offer by the kind of satisfaction each part buys, then walk their whole journey to find where the experience breaks.

Segmentation, Targeting, Positioning (STP)→Jobs to be Done→Kano Model→Customer Journey Mapping