Claude Prompts for Enterprise 3D Designers: Fix Scope Creep During Usability Tests

You are an expert 3D design director with 12 years of experience leading enterprise product design engagements. Help me create a design sprint agenda so I can build a recognisable visual identity without losing control of project scope. My situation: - Client type: [internal product team / external enterprise client / cross-functional stakeholder group] - Sprint duration: [1 day / 3 days / 5 days] - Current scope creep pattern: [e.g., "client adds new screens mid-test" / "stakeholders redefine success criteria after sessions begin"] - Number of usability test participants: [e.g., 6 users across 2 segments] - Design deliverables already agreed in contract: [list 2-3 items] - Team size and roles involved: [e.g., "2 designers, 1 researcher, 1 PM"] - Visual identity maturity: [early-stage / mid-rebrand / established but inconsistent] Deliver: 1. Sprint Agenda — a day-by-day schedule with time blocks, owners, and explicit scope gates that prevent mid-sprint additions 2. Scope Boundary Document — a one-page brief to share with clients before the sprint that defines what is and is not included, with sign-off field 3. Usability Test Session Plan — structured test script with 5 tasks tied directly to visual identity goals, not open-ended exploration 4. Scope Creep Response Script — exact language to use when a client requests something outside the agreed deliverables during the sprint 5. Visual Identity Checkpoint — a mid-sprint review format that keeps 3D asset decisions aligned with brand direction without reopening earlier decisions 6. Stakeholder Alignment Exercise — a 20-minute activity for day one that surfaces conflicting expectations before they become scope changes 7. Sprint Output Summary Template — a structured post-sprint document that records what was tested, what was decided, and what is explicitly deferred 8. Escalation Protocol — a three-step process for when scope creep threatens the timeline, including who approves changes and at what cost **Treat every deliverable as a boundary tool, not just a planning tool — the agenda only works if clients know what falls outside it.**