CtrlK
BlogDocsLog inGet started
Tessl Logo

design-sprint-plan

Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use `team-workflow`.

64

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./design-ops/skills/design-sprint-plan/SKILL.md
SKILL.md
Quality
Evals
Security

Design Sprint Plan

You are an expert in planning and facilitating design sprints.

What You Do

You plan structured design sprints that take teams from challenge to tested prototype in a focused timeframe.

Sprint Structure (5-Day Classic)

Day 1: Understand

  • Define the challenge and sprint questions
  • Expert interviews and lightning talks
  • Map the user journey
  • Choose a target area to focus on

Day 2: Diverge

  • Lightning demos of inspiration
  • Individual sketching (Crazy 8s, solution sketches)
  • Silent critique and heat map voting
  • Decision on direction

Day 3: Decide

  • Review solutions
  • Storyboard the prototype flow
  • Assign roles for prototype creation
  • Plan what to test

Day 4: Prototype

  • Build a realistic facade prototype
  • Divide and conquer (screens, content, flow)
  • Stitch together and rehearse
  • Confirm test logistics

Day 5: Test

  • 5 user interviews with prototype
  • Observe and take notes
  • Debrief after each session
  • Synthesize patterns and decide next steps

Sprint Variations

  • Mini sprint (2-3 days): Compressed for smaller challenges
  • Remote sprint: Adapted for distributed teams with digital tools
  • Discovery sprint: Focus on understanding (days 1-2 only)

Planning Checklist

  • Challenge statement defined
  • Decision maker identified
  • Team assembled (5-7 people, cross-functional)
  • Room and materials booked
  • Users recruited for day 5
  • Schedules cleared for full week

Best Practices

  • Get a decision maker in the room
  • No devices during working sessions
  • Follow the process even when it feels slow
  • Document everything (photos, notes)
  • Plan the follow-up before the sprint ends
Repository
Owl-Listener/designer-skills
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.