Build a five-day remote design sprint schedule
Set up a structured, timeboxed agenda for running an effective remote design sprint across distributed teams without video call fatigue.
Prompt
You are an expert design sprint facilitator. Create an operational, remote-first 5-day design sprint schedule based on the proven Design Sprint methodology, tailored for distributed teams working across multiple time zones. Cap synchronous video sessions at 4 hours per day to prevent meeting fatigue, with structured asynchronous preparation and handoffs for the rest of the day. Specify explicit exercises, timing, deliverables, and role responsibilities (Facilitator, Decider, Designers) for each day. Output format: A Day-by-Day schedule (Monday to Friday) with time allocations, synchronous exercises, asynchronous tasks, and clear completion gates for each day.Example output
Run this prompt directly in ChatGPT, Claude or Gemini without any edits. To adapt it to your team's specific working hours, ask the model in a follow-up to map the schedule across your team's precise time zones.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Uncover business goals behind stakeholder design requests
Turn rigid feature demands into diagnostic interview questions that expose actual business constraints, metrics, and problems.
Brainstorm product and feature names with positioning rationale
Generate distinct, memorable product or feature name candidates paired with brand positioning and potential trademark or cultural risks.
Build a content-first wireframe specification
Generate a structured wireframe copy specification with strict character counts and layout hierarchy before visual design begins.
Consolidate duplicate components across design libraries
Scan a messy inventory of UI components to find duplicates, confusing synonyms, and overlapping variants. Use this during design system cleanups and mergers.
Write component deprecation notices and migration paths
Produce clear deprecation notices and step-by-step replacement guides for UI components. Use this to help product teams upgrade design systems without breaking views.
Draft a design critique response without sounding defensive
Turn harsh or blunt stakeholder critique into a collaborative, objective reply grounded in user data and shared goals.
- Define a Semantic Design Token Scale for CSS
- Design a Progressive Disclosure Pattern for Complex Settings
- Structured Design Critique and Feedback Framework
- Critique a Slide Screenshot with Scored Areas and Five-Minute Fixes
- Design Brief from Client Notes with Assumptions and Next Actions
- Competitor UX Pattern Research Plan with Evidence Table and Design Recommendation