A working brief is not a contract with the past. A practical note on keeping direction clear while the scope, material and collaborators continue to move.
Change is information
A brief usually contains two different things: what a project must achieve and a first guess at how to achieve it. Trouble starts when those are treated as the same promise. A new photograph, a conversation with a customer or a constraint discovered during production can change the method without changing the purpose.
When the brief moves, return to the outcome before defending a layout. Ask what the new information changes for the person who will use the result. A request for another page may actually be a request for clearer navigation. A request for a bigger image may be a response to a weak edit.
Record the decision
We keep a short record of consequential choices: what changed, why it changed and which parts of the work it affects. The record is not a second project plan. It is a way to keep a team from having the same conversation every week.
Writing down the reason also makes a reversal easier. If the condition behind a decision disappears, the team can see which choice to revisit. Nobody needs to defend an old answer simply because it was once approved.

Review the new direction with the material in front of the whole team.
Test a small complete part
A small finished sequence is often more useful than a wide collection of half-finished alternatives. Choose a representative part of the project and follow it from beginning to end. Include ordinary details: a long title, a caption, a link and the point where a person leaves the page.
That slice makes the consequences visible. It lets everyone judge the change in context before it spreads across the whole site. The question becomes whether the new direction works, not whether one isolated screen looks more exciting.
Keep a clear boundary
Being responsive does not mean accepting every addition. Some changes belong in the current work; others deserve another phase. State that boundary plainly and connect it to the result the project is trying to deliver.
A good brief stays useful because it can absorb information while remaining specific. It gives people enough direction to make decisions and enough room to notice when a better decision becomes possible.
Share this article ↗ ← All journal entries