How to Engineer Design Critique Meeting Agenda in Microsoft Teams: Operational Blueprint

Most teams underestimate the structural cost of design critique sessions producing surface-level commentary because the question being critiqued isn't sharpened in advance. This is not a generic message scaffold — it is a operating-rhythm instrument tuned to the operating rhythm of design leaders balancing craft, throughput, and the never-ending demand for explanatory artifacts around the work, with stage-appropriate feedback embedded as a non-negotiable structural element. Running a design critique where past sessions produced opinion-spraying because designers didn't articulate the design question. Deployed correctly, this prompt eliminates the recurring pattern of having to re-explain decisions, chase down owners, or rebuild context that should have lived in writing from the first post.

The Core Blueprint

Software Environment: Teams (Enterprise AI: Copilot, ChatGPT, Claude, etc.)
Role Focus: Design
Execution Complexity: Standard
Taxonomy Tag: #CRITIQUE

PROMPT TEMPLATE

"Build a design critique meeting agenda with designer context, goals, constraints, design walk-through, critique prompts, feedback themes, and next steps."

964 RUNS

Strategic Use Cases

By enforcing markdown layouts and conciseness, this prompt prevents miscommunication during critical chat blasts:

Coaching a designer on framing critique requests so they receive useful feedback rather than aesthetic preferences.

Running a design critique where past sessions produced opinion-spraying because designers didn't articulate the design question.

Execution Workflow

Broadcast your formatted alert without breaking chat etiquette:

1
Open the target Microsoft Teams channel and pin the prompt at the top of the post composer so the structure is visible before any text is typed.
2
Substitute the bracketed variables with situation specifics — names, dates, owners, scope — without restructuring the scaffold itself; the scaffold encodes stage-appropriate feedback that arbitrary edits will quietly destroy.
3
Publish into the channel, immediately tag named owners in thread replies, and link any pre-reads or referenced artifacts so the post stands alone as a self-contained record rather than a placeholder for context that lives elsewhere.

Advanced Optimization

Tailor the chat output for maximum asynchronous impact by modifying the core snippet:

Question Sharpness
"...the designer states what feedback they want before showing work; un-framed critique invites un-useful opinion."
Stage Appropriateness
"...feedback is calibrated to design stage; nit-picking polish on exploratory work derails progress."
Designer Agency
"...the designer owns which feedback to integrate; critique informs decisions, doesn't make them."