✏️Prompts

Design Brief Strategist Prompt

Prompt

You are a design operations manager creating templates and guidance that help non-designers brief designers effectively.
Your role is to establish shared language and expectations so design doesn't spiral into endless revisions.

Provide:
- [PASTE: Type of design work your team does most (web, marketing collateral, packaging, app, etc.)]
- [PASTE: Common issues with design briefs (vague, too prescriptive, missing business context, etc.)]
- [PASTE: Your design and marketing team sizes]
- [PASTE: Current brief/approval process]

Create:

1. Design brief template with instructions:
   - Project name and timeline
   - Business objective (why are we designing this?)
   - Target audience
   - Key message/call-to-action
   - Success metrics (how will we know it worked?)
   - Brand guidelines to follow
   - Constraints (budget, tech limitations, compliance, etc.)
   - Reference examples (what you like, what you don't, why)
   - Approval stakeholders and timeline
   - Revision assumptions (how many rounds of revisions included)

2. Guidance document:
   - How to describe your vision without dictating design
   - Common mistakes (over-specifying fonts, layouts, etc.)
   - How to give constructive feedback
   - What counts as feedback vs. out-of-scope requests

3. Design feedback template:
   - What's working well (specific observations, not vague)
   - What needs adjustment (be specific: readability issue, brand misalignment, etc.)
   - Questions for designer (don't assume they'll guess your intent)

4. Design scope/approval levels:
   - What counts as a revision vs. new direction
   - How many revision rounds for different project types
   - When work is out-of-scope (e.g., "can you also design a logo?" if that wasn't in brief)

5. Design component checklist:
   - Before sending to design, ensure you have:
     - Clear objective
     - Audience definition
     - Brand guidelines reference
     - 2-3 visual references you like
     - Constraints documented
     - Timeline realistic for scope

6. Process document:
   - How to brief the designer (kickoff meeting agenda)
   - How feedback works (email, comments, meetings)
   - Revision timeline (when feedback due, when revisions due)
   - Sign-off process

Provide as templates and guides your team can use immediately.

Why it works

Establishing brief templates reduces back-and-forth. Defining 'revision' vs. 'new direction' prevents scope creep that frustrates designers. Reference examples teach faster than written descriptions of what you want.

Watch out for

Even with great briefs, some requesters will dictate design choices. Process documents work only if everyone follows them; inconsistent enforcement breeds resentment. Designer quality still matters; great briefs can't fix poor design skills.

Used by

DesignersMarketers