Stop 8 of 9 · Daily
Stakeholders
The six-field intake form that ends the corridor request, the reply that sets scope by naming what moves, and the campaign presentation built in Claude Design for management.
Every request is a trade and nobody writes it down
Farah's queue is not full of design problems. It is full of a marketing manager who needs a version for a partner deck, a sales lead who wants the poster in a third size, and a country manager who saw something on a competitor's feed. None of them are wrong. All of them arrive as a sentence in a corridor, and none of them say what they cost.
The fix is three artefacts: a form that makes the request real, a reply that prices it in days and displacement, and one presentation a quarter that makes the whole system visible to the people who fund it.
The intake form
Six fields. Any more and people stop filling it in.
| Field | Why it is there |
|---|---|
| What it is | Turns a wish into a named deliverable |
| Where it runs, at what size | Decides the layout before anyone argues about taste |
| Launch date | A date somebody typed, not a date asserted in a corridor |
| Approver | One name, agreed before the work, not three after it |
| Copy source and language | Says whether the Arabic exists or is being invented |
| What it displaces in the queue | Makes the trade visible before Farah makes it alone |
Write our design request form. Six fields maximum, each with a one-line explanation and an example answer, in Arabic and English. One field must ask what this request displaces in the current queue. Then write the two-sentence auto-reply the requester sees on submit, saying what happens next and by when they hear back. Keep every word usable by someone who has never briefed a designer.
The reply that sets scope
Here is the request as submitted: [paste the form fields]. Write my reply. Give two scoped options: what each one delivers, how long it takes and what it displaces in the campaign queue by name. Say which one I recommend and why in one sentence. Do not promise a date I have not given you, do not add deliverables that were not asked for, and finish by naming who has to approve the trade.
The word that does the work is displaces. A reply that says "Thursday is tight" starts a negotiation. A reply that says "Thursday means the A3 poster moves to Monday, and the country manager approves that" ends one.
This request breaks a brand rule: [paste the request and the rule]. Write the reply that declines the version as asked, explains the rule in one sentence a non-designer accepts, and offers the nearest thing we can do inside the rule with a date. Warm, short, no apology, no lecture.
The presentation
Once a campaign has shipped and stop 6 has produced the learnings, management sees it once. That presentation is a Claude Design artefact, built from the concept sentence, the boards and the report, and it exists to get one decision.
Build the campaign presentation for management. Structure: the concept sentence, one board per format family with three assets each, the split results by language, the three learnings as design decisions, and one ask with what it costs and what it returns. Bilingual titles, our brand palette and type, fifteen minutes of talking. Link the full asset folder rather than embedding it, and leave every unlaunched item out entirely.