Home / Sprint 3 / Build Plan v1

Build Plan v1 IS AB

Sprint 3 · Due · 10 points

You've interviewed peers, talked to Piranavan, and sharpened your stake. This is where you commit. A plan that names its own failure mode is stronger than one that pretends everything will work.

— Prof. Sathya

What to Submit

Four things, clearly labeled. 150 words max.

  1. My user + moment: Who are you designing for, and what specific moment are you addressing? (Should be sharp from Wednesday's peer interview — not a new pitch, a refined commit.)
  2. What I'm building: One sentence. What does this thing do to support the human process you designed?
  3. What has to go right: The one thing that must work for this to be useful in that moment.
  4. What could go wrong: One realistic failure mode. What would it look like if your design fails the user? What assumption are you most uncertain about?
▶ Go Deeper

What makes a good "what could go wrong"

It should be something about the user or the context, not about your technical skills. "I might not finish coding it" is about you. "The nurse might not have 3 seconds to look at a screen during handoff" is about the design.

How to use Wednesday's Piranavan conversation

What did he say that confirmed or challenged your assumptions? If he described a workflow detail you didn't expect, that's evidence. Use it to sharpen your "what has to go right" and "what could go wrong."

Submit

Written text in the Canvas submission box. 150 words max.

Format: Written text in Canvas submission box, 150 words max
Due:
Points: 10
Submit on Canvas →