Run Your First Brief-Clarification Meeting

Made for Architects

Run Your First Brief-Clarification Meeting

Also useful for: Project Managers, people in Creative

90 min Advanced Creative Architect Communicate Better Career outcome: Avoid Professional Risk

Build a meeting plan, ask targeted questions about requirements and adjacencies, settle conflicting statements, and send a written record of decisions and open items.

We'll use them to write your prompt.

Make Your Play

Give us the situation. We’ll build the prompt.

You prevent vague requirements from turning into design rework.

Your answers save as you type.

What you'll do

This is the plan inside your prompt. Add your details first. Then follow these steps with ChatGPT or Claude.

01 Define the meeting decisions You turn a broad clarification meeting into a short list of decisions or confirmations needed for your next design move.
02 Sort facts, assumptions, conflicts, and gaps You separate what is known from what only sounds settled so your meeting doesn't treat assumptions as requirements.
03 Check decision authority You identify who can provide information, shape a choice, and approve each important decision.
04 Build your question sequence You prepare questions that move from project purpose to space, flow, constraints, tradeoffs, and approval.
05 Prepare the timed agenda You assign time to the issues that matter most and protect time for decisions and recap.
06 Open with scope and rules You make the purpose, available decisions, and recording method clear before discussion expands.
07 Test requirements and adjacencies You turn broad preferences into usable requirements and check how people, materials, privacy, security, and services need to move.
08 Resolve conflicting statements You expose tradeoffs without forcing agreement that your participants aren't ready or authorized to give.
09 Read back the record You verify your notes while everyone is present instead of relying on later corrections.
10 Send the follow-up and update the brief You convert your discussion into a traceable record that directs the next design action.

Use this when

Use this before concept design, after receiving an incomplete brief, when stakeholder requests conflict, or when your team can't tell which requirements should guide the next design move.

You'll need

  • Project summary
  • Project stage
  • Meeting participants
  • Current brief
  • Known constraints
  • Open issues
  • Meeting length

Fill these in the prompt workspace.

You'll get

  • A timed agenda, prioritized questions, and clear decision goals
  • Requirements, constraints, stakeholders, and adjacencies tested
  • Each decision, conflict, owner, and due date recorded
  • A follow-up record ready to send, with confirmed points clearly separated from unresolved items.

By the end of this playbook

You will have:

  • A timed agenda, prioritized questions, and clear decision goals
  • Requirements, constraints, stakeholders, and adjacencies tested
  • Each decision, conflict, owner, and due date recorded
  • A follow-up record ready to send, with confirmed points clearly separated from unresolved items.

Part of a collection

Turn the Brief Into a Real Design Problem

10 playbooks

You clarify what the project needs, who can shape it, which constraints matter, and what deserves your design attention first.

Next: Turn Your Competing Priorities Into Design Principles

View collection

Best next playbooks

Suggest an idea

What should we add?

Loading the suggestion form…