Brief Decoder

Turn a vague brief into one workable problem.

Brief Decoder

What this fixes

A vague brief arrives - “make the dashboard better”, “modernise onboarding”, “look into churn” - and the team starts building before pinning down what’s actually being asked. Each person quietly starts solving a different problem, the work goes in different directions, and no one notices until it’s late. The problem isn’t that someone misread the brief; it’s that the brief had several workable readings and the team never chose one.

A vague brief is not the problem. Acting on it too early is.

How this works

Three people get the brief “improve the onboarding flow”. One sets out to cut the number of steps, one to fix the confusing copy, one to add a guided tour. All three are reasonable - and all three are different problems. They were never going to build the same thing, and no one had spotted it.

Each person writes the problem they think the brief is asking them to solve. The readings are compared side by side, the team chooses one, and sharpens it into a concrete problem everyone will work from.

Team: one person runs the activity using the Facilitator Guide. The people who’ll act on the brief take part.

Time required

Team ✓

Team: 45–60 minutes, with a facilitator.

The time required is indicative and will depend on the nature of the problem and the size of the team.

The facilitator must read the short facilitation guide first - about 8–10 minutes. It is a downloadable PDF on this page.

When to use

Bring a real brief you’re about to act on - vague enough that you’re not certain what it’s asking.

Use it whenever:

  • a brief or request is open to more than one reasonable reading
  • you’re about to start building from something you only half understand
  • different people seem to be describing different versions of the same task
  • a request came down with no clear definition of done
  • you’ve had problems before by solving the wrong version of an ambiguous ask

What you get

One workable problem the whole team can act on.

  • The different ways the brief was being read, side by side
  • One concrete problem everyone agrees to solve
  • A shared definition of what “done” means

You’ve done it well when: the team has a single, concrete problem it can act on - specific enough that no two people could read it differently.

What you’ll notice

  • The team wasn’t solving one unclear problem - it was solving several different problems hidden inside the same brief
  • There was no single “right” reading to uncover - only one to choose
  • The work stops going in different directions once the problem is fixed

Why this works

A vague brief allows several reasonable readings of the same words. People fill the gaps in an ambiguous ask with their own reading, so a team can start confidently and still be building different things. Surfacing the readings makes the difference visible, and choosing one concrete problem is what lets the work converge.

What you need

Everything comes in one kit. Here is each part, and when you use it:

Interpretation cards (core). Blank, write-on cards. Each person writes the problem they think the brief is asking them to solve. These are what you compare.

The comparison board. A board where every reading is laid out side by side, so the different problems hiding in the brief are visible at a glance.

Sharpening prompt cards. Prompts that turn a chosen reading into a concrete, workable problem - who it’s for, what changes, what “done” looks like. Used when the team converges on one problem.

Starter-brief cards (optional). Example vague briefs. Use one only if the group has no real brief of its own to work on. Otherwise, set them aside.

Roles - Team: a facilitator (runs the flow, keeps interpretation private until the reveal, holds the team to one concrete problem) and participants (interpret the brief, compare readings, build the problem).

Steps

  1. Set up (4–5 min). Appoint a facilitator first - they run the activity from the Facilitator Guide. Put the real brief in front of everyone, exactly as it was given.
  2. Write your version (7–9 min). Each person privately writes the problem they think the brief is asking them to solve - in one or two plain sentences. No conferring. Write the problem, not a solution.
  3. Compare the readings (11–13 min). Put every version side by side on the board. Read them out. Look at how far apart they are - that difference is the brief no one had actually agreed on.
  4. Choose one reading (11–13 min). Decide which problem the team will actually solve - and which readings you’re explicitly not choosing. There’s no “correct” reading to find; pick the one that best fits the real intent and the work in front of you.
  5. Make it workable (8–10 min). Sharpen the chosen problem into something concrete: who it’s for, what changes, what “done” looks like. Specific enough that two people couldn’t read it differently.
  6. Commit (4–6 min). Lock the one workable problem. Agree it’s what everyone now builds from, and who owns it. If new requests arrive later, compare them against this agreed problem before changing it. Photograph the board.

Output / Takeaways

  • Each person’s reading of the brief, side by side
  • One concrete, workable problem the team will build from
  • Who owns the problem statement, and what “done” looks like

Important rules

  • Write the problem, never a solution
  • Interpret privately first, reveal together - don’t let one reading set the direction for the rest
  • There’s no single right reading to find - the team chooses one
  • Don’t stop at choosing - make the problem concrete enough to act on

Planning to facilitate this activity? Access the resources below to get started.

MIndn
Execution must be smooth. Not chaotic or stressful.
Built by Witmer.