Lesson 2.4

Design Thinking/Module 2 · Define — framing the right problem

Lesson 2.4

The design brief, rewritten

From a client's wish-list to a designer's working document

6 min Lesson 13 of 32

The hook
The client handed you a wish-list: 'modern living room, Instagram-worthy, bigger kitchen, separate formal room.' Since then you've made Lakshmi vivid, mapped her inner life, excavated the real needs, framed the problem, turned conflicts into questions, turned constraints into fuel. None of that lives in the wish-list. The closing move of Define: rewrite the brief — not the one the client gave you, the one the project actually needs.

Why the wish-list was never the brief

The wish-list is a list of solutions with no problems attached, no understanding of who or why, no framing. The rewritten brief is a clear statement of the problem to solve, grounded in real understanding, that anyone on the project can work from. It serves three audiences: the client (reflects their life back so they feel understood and agree on the real problem before money is spent), the team and contractors (keeps a hundred decisions aligned), and your future self (the document you return to at midnight to ask 'is this idea solving the real problem, or have I drifted?').

What goes into a rewritten brief

A project understanding (one plain paragraph stating what this is really about). The people (personas, named, especially the overlooked). The core problems as POV statements. The key questions as HMWs, including collision questions. The constraints, sorted hard/soft/hidden, with the concept the tightest one generated. And success criteria — how you'll know it worked, tied to real needs ('Lakshmi has a dignified prayer spot she never has to request; two cooks can work without colliding; the room shifts from prayer-calm to family-evening'). These become the test in Module 5.

The brief as contract — and compass

The rewritten brief is a contract in spirit: you present it and get agreement on the real problem before designing, so that when you present concepts you're showing how your ideas solve the problem you both already agreed on. Disagreements get resolved at the cheap brief stage, in words, not at the expensive construction stage, in concrete. And it's a compass: through the messy work ahead you'll drift, and the brief is what you return to, asking 'does this serve what we agreed the project is really about?'

The brief, rewritten: a wish-list of solutions becomes a working document of needs, constraints and success criteria.

Go deeper — for practitioners & students

Write the brief for the client to read, not just for you — translate the internal tools (POV, HMW, personas) into their language; the test is whether the client feels more understood, not lectured. The brief is revisable, like everything in the loop — a hypothesis sharpened to its best current form, rewritten if prototype or test reveals you framed something wrong. And success criteria are the most undervalued and most powerful section — defining success up front converts the final judgement from subjective ('I don't like it') to objective ('does it meet what we agreed?'). You're writing the answer key before the exam.

Try it

1. Write down the original wish-list in the client's words (your 'before'). Assemble the rewritten brief: project understanding, people (named, including the overlooked), core problems (POVs), key questions (HMWs, including a collision one), constraints (hard/soft/hidden with the generated concept), and success criteria. Translate the project-understanding paragraph into warm plain language. Write the success criteria carefully — each tied to a real need, specific enough to judge later.

Check yourself

3 quick questions — pick an answer to see why.

Q1Why was the client's wish-list never really the brief?

Q2Which section does the lesson call the most undervalued yet most powerful in a rewritten brief?

Q3The rewritten brief acts as both a contract and a:

Key terms

Rewritten brief: The deliverable that closes Define — a framed statement of the real problem assembled from project understanding, named people, POVs, HMWs, sorted constraints, and success criteria.
Success criteria: Specific, need-tied measures of how you'll know the design worked, written up front so the final judgement becomes objective rather than subjective.
Brief as compass: The idea that the living brief is what you return to amid messy work to ask whether an idea still serves what the project is really about.

Recap

The wish-list was never the brief. The rewritten brief is the deliverable that closes Define: a framed statement of the real problem, assembled from project understanding, named people, POVs, HMWs, sorted constraints with their concept, and success criteria. The gap between wish-list and rewritten brief is the value you added. Once it exists, the brief is both a contract (agreement secured cheaply before you build) and a compass (what you return to so you don't drift). Write it for the client to feel seen, keep it living, never skip the success criteria.

Carry forward →

Your brief is done, your HMW door open. You step through and instantly your mind hands you an idea. Why is that first idea almost always a trap, and what discipline forces you to generate ten more before you choose?