Reviews
Part of Marketing frameworks: how to choose and combine them
Marketing frameworks best practices: keep, merge or retire
Marketing frameworks best practices for upkeep: register each model with its decision and owner, fix drifting terms, then keep, merge or retire it.
What to take away
- List every marketing framework in use in one register, with its decision, user, owner, source trail, downstream action and retirement condition.
- Track two measures for eachthe time it takes to run and the decisions it changed.
- Keep one controlled definition for each shared term, so a segment or conversion means the same thing everywhere.
- Retire duplicate fields and abandoned templates, and keep the original versions and decision reasons.
- Run the audit every year and after any material change.
Start with a framework register
Put every framework your team uses into one register before judging any of them. A model that nobody can place in that register is already a candidate for retirement. Each row answers the same six questions, so gaps stand out at a glance.
| Register field | Question to answer | If it is blank |
|---|---|---|
| Decision | Which choice did the model change? | Candidate to retire |
| User | Who reads the output? | Candidate to retire |
| Owner | Who acts on it? | Name one or retire |
| Source trail | Can a reviewer find the evidence? | Rebuild before reuse |
| Downstream action | Did it reach delivery? | Add the handoff |
| Retirement condition | What would end it? | Write one now |
Entries are the models in use: SWOT, Porter's Five Forces, the 4Ps and 7Ps, jobs-to-be-done, STP, AARRR, the BCG matrix, the Ansoff matrix, RACE or the brand key. Each answers a different question, so a model used outside its question is the first to collapse under real work.
Measure what each one costs and changes
Track two numbers for every framework: the time required to run it and the decisions changed because of it. Log both in the marketing frameworks benchmarks record, so the comparison is made on evidence rather than on habit.
A framework survives contact with real work when someone can name the decision it changed and the owner who acted on it. A SWOT that returns every quarter with the same four lists has survived nothing. Framework quality shows in better choices and learning, not in a growing library of canvases.
Fix drifting definitions
Check the terms before you check the models. Use consistent identifiers and definitions for customers, products, offers, initiatives, claims, channels, metrics and periods. A segment or conversion should not change meaning between the strategy, the brief, the budget, the analytics system and the review meeting.
Put those controlled definitions on the marketing frameworks checklist and require every model to use them. When two documents disagree about a term, the audit has found a defect, and the fix is one definition with one owner.
Check the handoff to work
Ask whether each analysis ever reached delivery. The UK Government's whole-problem mapping guide connects user research, service fields, cross-team journeys, broken handoffs, prioritization and an improvement backlog. Marketing teams can apply that operating link without copying a government service model wholesale.
Every conclusion should lead to a choice, a rejected option, a test, an owner, a resource, a dependency, a guardrail, a stop rule or a review. Connect the framework with briefs and plans, claim evidence, delivery, measurement and customer support, rather than leaving it in a workshop file.
Record what the audit leaves out
Write down what will not be pursued, which objective takes priority, what uncertainty remains and which risk can disqualify an option. A register that lists only what was kept hides the choices behind it.
Use ranges and sensitivity instead of letting a weighted score or a single forecast manufacture confidence. A tidy number on a canvas looks decisive, but it adds no evidence the sources did not already hold.
A plain example. A team finds two canvases that both summarize the market for the same quarterly review. Only one has a named owner and a source trail. The audit merges them into that one, archives the other with its reason, and notes which fields were dropped.
Match the effort to the stakes. Increase research, specialist review, approval and monitoring with consequence and irreversibility, and keep the lightest process for low-risk work.
Merge and retire in five steps
- Sort the register by blank fields and by the two measures.
- Merge frameworks that answer the same question with the same evidence.
- Retire duplicate fields and abandoned templates.
- Keep the original versions, decision reasons, forecast ranges, observed results and revisions.
- Record what was retired and the condition that would bring it back.
Retiring is not deleting. The archive is what lets a later reviewer see why a model was dropped and what it had produced before it was.
Schedule the review
Schedule an annual architecture review and earlier ones after material changes in evidence, products, markets, rules or ownership. Confirm that every retained framework still has a decision, a user, an owner, a source trail, a downstream action and a retirement condition.
Digital.gov's introduction to human-centered design describes discovery, design, delivery and measurement as sequential and cyclical phases. The same loop suits an audit: what the framework found, what it changed, what it delivered and what it measured should feed the next choice. A context analysis is a good first case to run through it.
