Week 2 · Requirements discovery
Everything it knows about them comes from what you find out and write down.
Building Real Systems with AI · Gonzaga University
Warm-up
Open your live URL on your phone. Add something.
Now open it on your laptop.
Where did your data go?
Hold that thought. Week 3 explains it.
Why this matters
An agent can build almost anything you describe, in an afternoon.
So the expensive mistake is no longer building it wrong.
It is building the wrong thing.
Discovery reduces uncertainty before you spend a sprint on an answer.
Same work, two vocabularies
| In the reading | In Systems Analysis and Design |
|---|---|
| Interviews and observation | Requirements elicitation |
| Jobs to be done, personas | User and stakeholder analysis |
| What they do today, journey map | As-is process model |
| Riskiest assumption | Feasibility and risk analysis |
| MVP scope: in and out | Requirements baseline |
Discovery is truth-seeking
Two ways most products fail:
"I know users want this." Believed, wrong, and never checked.
The truth was one interview away. You built on a guess instead.
Today's running example
A student club collects dues. Members pay the treasurer on Venmo.
Every Sunday, the treasurer matches payments, one by one, against a sign-up sheet to see who still owes.
A student thinks: "One page that shows who has paid would save that Sunday."
Does the Sunday matching hurt enough to switch? Can the app even get the Venmo data? Would anyone use it twice?
The example is invented for teaching.
Part 1
Jobs to be done
A fast-food chain improved the recipe. Sales did not move. So they asked: what job are people hiring the milkshake to do?
Most were bought in the morning by commuters: something to make a boring drive interesting and keep them full until lunch.
Not other milkshakes. Bananas, bagels, and donuts. The fix: thicker, fruit chunks, faster at the drive-through.
People don't want your product. They want progress in a specific situation.
Christensen et al. 2016, Competing Against LuckJobs to be done
Dues treasurer: When I'm closing out dues on Sunday night, I want to know who still owes without checking every payment, so I can remind the right people and be done.
Trap The middle slot invites a feature: "I want to scan Venmo with an app." Write progress the person would recognize even if your product never existed.
Try it · 90 seconds
| Job statement | The mistake |
|---|---|
| "When I'm studying, I want to use an AI flashcard generator, so I can learn faster." | Names a product |
| "When I'm hungry, I want to eat, so I can not be hungry." | Too vague You can't observe "hungry." When, where, doing what? |
| "When I'm running a club event, I want a Slack integration for RSVPs, so I can track attendance." | Names a feature Where the progress should be. |
Map the whole job
Opportunities sit under the dips. This is your as-is process, and it goes in your requirements.
The real competitor
Push: Sunday spent matching Venmo to a sheet
Pull: one page that shows who has paid
Anxiety: "What if it's wrong and I chase someone who paid?"
Habit: everyone already Venmos; the sheet mostly works
So in every interview, ask: "What do you do today?"
Lab 3 · Part A
Open the problem discovery worksheet. For three rows, fill in:
Pick the row with the strongest evidence and a user you can actually reach.
Who can you talk to by Thursday?
"Fix campus parking" fails. "The club treasurer I sit next to" passes.
Part 2
The Mom Test
She loves you. Her feedback is useless.
People lie to be nice about your idea. They rarely lie about what they did last Tuesday.
Rewrite the question
| Bad | Why | Good |
|---|---|---|
| "Would you use an app that does X?" | Hypothetical. Everyone says yes. | "Tell me about the last time you tried to do X." |
| "Do you think this is a good idea?" | Opinion, not fact. | "What have you tried? What happened?" |
| "How much would you pay for this?" | They'll guess to be nice. | "What are you paying to solve this now?" |
| "Would you recommend this to friends?" | A promise, not behavior. | "Have you told anyone about this problem?" |
The most useful question
"Walk me through the last time this happened."
it really happens
not what they say they'd do
and why it didn't work
Watch what changes
"So I'm building an app that tracks club dues. Would you use something like that?"
"Do you think other treasurers would want it?"
"What would you pay for it?"
"Tell me about the last time you had to keep track of who paid you for something."
"Walk me through what you did, step by step."
"What was the most annoying part? What did you do about it?"
What did you learn from each?
How much can you trust it?
Each rung costs the person more to fake. "Users want this" with only said evidence is an assumption dressed up as an insight.
Try it
| "I'd definitely pay for something like this." | Said |
| She showed you a Google Sheet with 14 tabs she maintains by hand. | Did |
| He asked if he could beta test it. | Said until he shows up |
| Three people put down a $10 deposit on a pre-order page. | Paid |
| "I hate doing this every week." | Said ask about last week |
| He forwarded your email to two friends with the same problem. | Did risked his reputation |
Lab 3 · Part B
Then 4 minutes: mark each line of your notes
said did paid
Rules
Starters
Lab 3 · Part C
Paste your notes into Claude Code with the Lab 3 prompt. It must quote your notes for every finding.
The AI will invent findings if you let it. It has read a million interviews, just not yours.
Treasurer is frustrated by matching payments "I spend every Sunday on this"
Treasurer wants automatic reminders
↑ No quote supports it. Strike it.
Write how many you struck at the top of synthesis.md.
Part 3
What could make it fail?
Value: will they want it enough to switch?
Usability: can they figure it out?
Feasibility: can we build it?
Viability: does it work as a business?
An agent settles feasibility in an afternoon. A working app is not proof anyone wants it.
Before you build
Dropbox posted a demo video before the product existed. The waitlist jumped from 5,000 to 75,000.
Do the job by hand for a few people. Food on the Table started with one customer.
Looks automated; a person does the work. Zappos bought shoes at full price, one order at a time.
Three treasurers send you their Venmo export each Sunday. You send back a "who has paid" list built by hand. In two weeks you know if they keep sending it, with no code at all.
MVP scope
| MoSCoW | Means |
|---|---|
| Must | The MVP fails without it |
| Should | Important, but it works without it |
| Could | Only if time permits |
| Won't | Out of scope, on purpose |
Most "musts" are "shoulds" at best.
Your requirements baseline: In = the musts. Out = everything else, and why.
Cut to the minimum, then make what's left excellent. A barely-working app gets polite answers that teach you nothing.
Lab 3 · Part D
discovery/requirements.md
Tell an agent "build a dues tracker" and it fills every blank with a guess from the average app it has seen.
Your requirements replace its guesses with your evidence.
Privacy and usability are requirements too.
Exit ticket
By Thursday
Two real interviews · Lab 3 due before class · Sprint 1 plan discussion post
By Tue, Nov 24
Three interviews total for Sprint 1 · names removed from all notes