Sprint 3 · Week 9

Problem Stake Day

Today you build something. By end of class you own a specific human moment.

The Arc

Where We Are

Sprint 1 ✓ Foundation — Yourself. You solved for yourself.

Sprint 2 ✓ Mirror — A Partner. You solved for someone you know.

Sprint 3 → Complexity — External Stakeholder. You're solving for someone whose world you have to learn.

Sprint 4 ○ Mastery — Full Autonomy. No scaffolding. Your stakeholder, your problem.

The Domain

Bhutan MDRO

1.27 million deaths per year globally from antibiotic-resistant infections. A 28-page clinical guideline exists. It doesn't help clinical workers in the moment they need it.

Piranavan Selvanandan

Technical consultant — brought this problem to us. He'll be with us in Weeks 10 and 11.

Your job is not to solve the whole problem. Your job is to find one specific human moment where you can make a real difference.

Round 1 — Individual

Write Your Problem in One Sentence

A clinical worker in Bhutan reads your sentence. They say: "Yes, that's exactly my problem."

If they'd say "sort of" or "kind of" — rewrite it.

5:00

Round 2 — Pair

Read Each Other's Sentences

You and your neighbor. Two questions only:

1. Agreement

Where do you agree about what the AI needs to know to be useful here?

2. Disagreement

Where do you disagree?

The disagreement is more interesting than the agreement. Write it down. You will need it.

7:00

Round 3 — Two Pairs Combine

Four People, Two Sentences

Combine them into one prompt — but you must resolve the disagreement from round 2 explicitly. You can't just average. You have to make a choice and be able to say why.

7:00

The Class Prompt

One Sentence From Each Group

Surfaced and discussed. Then: we enter the final prompt together. I type, you tell me what to say.

What are we watching for when the response comes back?

→ What question did the AI answer that we didn't ask?

→ What's missing that a real clinician would immediately notice?

The Differentiation Rule

Your Stake Is Yours. But It Has to Be Specific Enough to Own.

No two students may work on problems more than 50% similar.

Now: 90 seconds each. State your candidate problem in one sentence.

Class listens for collisions.
If there's a collision, both students have 48 hours to differentiate.
First to stake a specific, clear claim owns the territory.
Vague claims don't count.

1:30

90 seconds per student — manually reset between students

First Build

Design the Human Process First

You have 35 minutes. Do not open your code editor yet.

Three questions. Answer them in writing — notebook or doc, visible to your partner:

1. What does your user do right now when they encounter this moment without your solution? Walk through the steps.

2. Where exactly does that break down?

3. What is the smallest thing that would make it better?

When you've answered all three: then you can touch a computer. Build the smallest possible version of that smallest thing. Embarrassing is fine. Not existing is not fine.

35:00

Before You Leave

What You're Leaving Class With Today

✓A staked problem — a specific human moment

✓A draft of the human process you're supporting

✓Something that exists, even if it barely works

Problem Stake Brief

Your user, the moment, your territory. 300 words max.

Weekly Build Reflection #1

What human moment are you designing for? Handwritten, photographed.

Read pages 1–8 of the MDRO guideline if you haven't. Come to Week 10 having built something further.

→ Sprint 3 Landing Page