Strategic Challenge Map

Where it came from

This one was not taken from a textbook. It was built for a particular situation: proposing a change into a large organisation, where the reader is a sceptic who has heard "this fixes everything" before and stopped believing it the second time. The method borrows the habits that survive that reader. Evidence with a date, because an undated citation ages silently and is worth nothing in a year. Challenges sorted into four categories, because a technical fix can’t solve an organisational problem and mixing the categories hides that. And an honest verdict on each challenge: does what you are proposing remove it, reduce it, or not touch it?

"Does not touch it" is the answer that gives the method its credibility. A map on which everything is improved reads as a pitch. A map that says plainly what it leaves alone is believed on the things it claims.

The four categories are technological, regulatory, competitive and commercial, and organisational, which are the four ways organisations fail. The last step, naming the proof a sceptic would demand before they ask for it, is what separates a proposal from a pitch.

Why it works

Listing the challenges is easy and useless. Categorising them, attaching dated evidence to each, and then judging honestly which ones your proposal moves turns a worry list into an argument somebody can check. Half the challenges usually evaporate at the evidence step, which is the point of having one.

The ranking is by urgency and hard deadlines, not by how interesting a challenge is, and the proof metrics are volunteered rather than extracted. Stating the standard you will be judged against, before you are asked for it, is the single most persuasive thing a proposal can do.

When to reach for it, and when not to

Reach for it when you are proposing something into an organisation, a school, a club, a council, a company, and the people who decide are sceptical, busy and have been burned before. A Challenge whose outcome depends on being believed, or a Project that has to be approved before it can start.

It is far too heavy for a personal decision, and it is the wrong tool when the challenge is inside you rather than in the organisation. Of the fourteen, it is the one most obviously built for work rather than for a kitchen table, and the worked example below scales it down deliberately. Greggle suggests it first on a Challenge, and on a Project.

How to run it

With a pen, on one sheet of paper.

Write the strategic context in a paragraph: what the organisation has to keep running, what it is trying to change, and the pressure it is under while doing both. Then name what you must not position against: the people, systems and decisions that are off the table.
Work four categories in turn: technological, regulatory, competitive and commercial, organisational. Under each, list the challenges, at least two, stated as things that are the case rather than things you dislike.
For every challenge, cite the evidence that it is real and the date that evidence carries. A challenge with no citation is an opinion.
For every challenge, say whether your proposal removes it, reduces it, or does not touch it, and justify the verdict mechanically: what changes that makes this stop being true. Then name the proof a sceptical expert would insist on.
Rank the challenges by urgency, driven by deadlines and consequences. Everything critical means nothing is. For each, judge how well a lightweight intervention fits versus changing something at the core.
Define the proof: the metrics that would satisfy the sceptic, each stated so two people would collect the same number, sorted by the kind of doubt it answers, with the artefact you would put in front of them.

There is a one-page card with these steps and a blank grid to fill in, made to print on A4. Or the PDF.

On a Greggle board

Pick Strategic Challenge Map on a Challenge board and Greggle proposes the context, four category steps with two challenges each to start, a ranking with three to start, and the definition of proof.

Let the canteen take cards, inside the forensic analysis: technological, regulatory, competitive and organisational, the last selected — a real board · the canteen, the four categories · click a step to open it

Inside 2 — Categorised forensic analysis: the board one level down — a real board · the canteen, the four categories · click a step to open it

1Strategic contextThe clash between keeping things running and changing them, and the pressure from outside. What you must not position against.

2Categorised forensic analysisTechnological, regulatory, competitive and commercial, organisational. Two challenges each to start, up to eight.

each challengeThe challenge, and the documented evidenceThe date of that evidence. Remove, reduce, or does not touch it. Justification. Proof demanded.

3Ranking and prioritisationEach ranked challenge: the strategic driver, urgency from critical to low, and how well a lightweight intervention fits.

4Definition of proofThree to twelve metrics. Each: what kind of doubt it answers, and how it would be measured and shown.

the ruleSay what you don’t touchA section where everything is improved reads as a pitch. One honest "does not touch it" buys belief for the rest.

Nothing is added until you have looked at it. Open any step and it becomes a board of its own. Steps that cannot sensibly be cut smaller get marked as actions, and every action collects in one flat list.

What the check looks for

One button reads the whole branch back. On this method it reports, among other things:

Challenges have been written and not one says when its evidence was true.
Every challenge in a category is one you improve. A section without a "does not touch it" reads as a pitch rather than an analysis.
A challenge is claimed as removed with no proof named. The strongest claim is the one that will be tested hardest.
All the ranked challenges carry the same urgency, so the ranking cannot say what to do first.

A worked example

a Challenge · persuade the school to let the canteen take card payments

ContextThe canteen has to feed 900 people in 40 minutes every day while the school is being told to go cashless by the council. The queue is the pressure. Not positioning against: the canteen staff, the existing till supplier, the bursar’s decision last year to keep the catering contract.

TechnologicalThe tills are ten years old and have no card reader. Evidence: the supplier’s end-of-support letter, March this year. The proposal removes this, by replacing the readers only, not the tills. Proof demanded: a trial reader on one till for a week, with the transaction log.

RegulatoryCard data from under-16s falls under the school’s data protection obligations. Evidence: the trust’s data policy, updated January. The proposal reduces this but does not remove it: the reader handles card data, the school still holds account records. Proof: the reader supplier’s compliance certificate and a one-page data flow the bursar can read.

Competitive and commercialThe corner shop across the road takes cards and a third of year 11 go there. Evidence: the head of year’s count in the spring term. The proposal reduces this. Proof: the canteen’s daily takings for year 11 before and after the trial.

OrganisationalTwo of the three canteen staff have never used a card reader and one is retiring in July. Evidence: the catering manager, when asked in April. The proposal does not touch this. Training is the caterer’s job and saying so is more credible than pretending a reader trains people.

RankingThe council’s cashless deadline next January: critical. The end-of-support letter: high. The corner shop: medium. Staff training: medium, and not ours.

ProofQueue time at 12.40, timed by a prefect with a stopwatch, before and during the trial (operational). Failed transactions per day from the reader log (data integrity). A signed one-page data flow the bursar has read (governance).

The organisational challenge is the one the proposal honestly doesn’t touch, and saying so is what makes the bursar believe the other three. A version that claimed to solve training would have lost her at that line.

Where it falls down

Without the evidence step it becomes a list of fears. With the evidence step but without dates, it becomes a list of things that were true once. The dates are the discipline, and they are the part people skip because finding them is tedious.

It is also heavy. Run in full on a small decision, it produces a document nobody asked for. The scaled-down version in the example above kept all four categories and all four verdicts and took an afternoon; the point is the honesty of the verdicts, not the length of the map.

Pairs well with

Stakeholder and Influence Map. The sceptic you are writing for has a name. Find out what they actually want before you decide which proof to volunteer.
Answer First. Once the map exists, the proposal itself should open with the answer and hang the categories beneath it.
First Principles. When the challenges all rest on how things have always been done here, strip the assumptions before you evidence them.