1. During a user observation session, why should you avoid explaining the product when a participant gets confused?
The confusion is the data. Every moment of hesitation, wrong click, or abandoned action is information about where your product's assumptions don't match user expectations. Explaining removes that signal permanently.
The reason is purely about signal quality. The moment you explain, the session becomes a tutorial — you see how users behave when guided, which is very different from how they behave in real life. Confusion is the most valuable thing to observe.
2. The diagnostic test for whether feedback is workflow-critical vs. preference is:
The retention test is the cleanest classifier: "If this were fixed, would it change whether users stay?" Yes = workflow-critical. No = preference. Volume, implementation time, and user tier are all secondary to this fundamental question about retention impact.
Volume indicates prevalence but not importance. Implementation time is a resourcing question, not a priority question. User tier provides useful context but doesn't determine whether the issue is workflow-blocking. The single most actionable test is always: does this explain why people leave?
3. According to the lesson, which platform has the best reach-to-effort ratio for getting people to actually look at a project?
Right. The lesson explicitly names case study posts as high reach-to-effort. Most peers aren't writing publicly at all, so the bar for standing out is low.
GitHub is a floor, not a ceiling. Cold emails have low conversion. A ten-page site is high effort. The lesson specifically calls out the case study post as disproportionately effective.
4. The "launch avoidance loop" is best characterized as:
Correct. The key phrase: legitimate-sounding. The work Jordan was doing was real product work — but it was real product work chosen because it delayed external judgment, not because it was the most important thing to do next.
The loop isn't about research strategy, relaunch tactics, or feature methodology. It's about anxiety-driven prioritization that keeps the product from being publicly visible — using real work as a shield against real judgment.
5. A "decision log" is most valuable when it is:
Correct. The key attribute is real-time capture — reconstructed decisions lose the authentic "why" that makes the log valuable.
A retrospective version is better than nothing, but the lesson's definition specifies "kept during the build" because reconstructed reasoning is less accurate and less convincing.
6. What is the "infinite-horizon trap" as described in this module?
Right. No deadline means no forcing function. The project stays permanently "in progress" because it's always available to work on later. Sprints fix this by making "later" into a specific, bounded container.
The infinite-horizon trap is specifically about the psychological availability of "next week" as a perpetual escape valve. Without sprint structure, projects don't fail dramatically — they just drift indefinitely.
7. Which element of the five-part portfolio presentation do most people skip — and why is skipping it a mistake?
Right. The lesson specifically identifies this element and explains the reversal: what feels like a weakness signal is actually a maturity signal that evaluators value.
The lesson identifies "what you'd do differently" as the most commonly skipped element, and explains explicitly that it signals critical thinking rather than incompetence.
8. You have 200 users. 15 of them use your AI content tool specifically to repurpose podcast transcripts — a use case you didn't design for. What should you do?
Bright spot users deserve investigation before you act on them either way — neither dismissing them nor immediately pivoting based on them. The right move is five interviews: what are they doing, why does it work for them, and do they represent a real market segment? That information should drive the decision.
Both extremes — ignoring and immediately pivoting — skip the research step. 15 users self-organizing around an unintended use case is a strong signal worth investigating seriously. Interview them first. Then decide whether the podcast-repurposing use case represents a better premise than your original one.
9. Jordan's story in Lesson 3 illustrates which concept most directly?
Yes. Jordan invented a series of thresholds — 500 subscribers, then 1,000 — none of which were real market conditions. That's the permission problem in its purest form.
The story is specifically about psychological delay, not technical difficulty or competitive research. The lesson names this "the permission problem."
10. Which of the following is the correct non-negotiable hour commitment strategy for a sprint alongside a busy semester?
Correct. Named time blocks make the commitment real. A number without blocks is a wish, not a plan. Treating extras as bonuses prevents the demoralization that comes from consistently missing an aspirational target.
Vague commitments — "as much as possible," "recalibrate weekly" — don't survive contact with a real schedule. Named blocks with a specific number of hours are the only format that holds under pressure.
11. The primary purpose of "assumption mapping" in pre-build research is:
Correct. Assumption mapping is about surfacing what has to be true for your idea to work, and ranking by how likely each assumption is to be wrong — before you've built anything and become attached.
Assumption mapping is a strategic exercise, not a technical or legal one. It forces you to name what you're betting on before you've invested months building it.
12. Why is Reddit a particularly useful source of early user research signals?
The key is context: Reddit users aren't aware of being research subjects, so their descriptions of problems are unfiltered by social performance. They're asking for genuine help, which means they describe the actual situation rather than what they think someone wants to hear.
Statistical representativeness and SEO are real but not the core advantage for user research. The valuable thing about public complaints is their authenticity — nobody performs frustration for an imaginary researcher when they're just trying to get help with their actual problem.
13. Your friend says "I've been at this for six months — I can't just throw it away." This reasoning is an example of:
Sunk cost protection is one of the most expensive cognitive patterns in product development. The six months are spent regardless of what decision is made now. The question is forward-looking: what does current data say about this direction's viability? Past investment is not a reason to continue in a wrong direction.
The statement explicitly references past time investment as the reason not to change — that's sunk cost reasoning. Whether six months is long enough to evaluate is a different question and depends entirely on what the data shows, not on how the time felt emotionally. "I can't throw it away" is about emotional ownership, not evidence.
14. Why do solo builders benefit from sprints even more than teams do, according to Lesson 1?
Exactly. Teams use sprints for coordination. Solo builders need them for self-commitment. Without a standup to catch drift or a PM to reset scope, the sprint is the only external-feeling constraint — even though you're creating it yourself.
The key insight is the absence of external accountability. Teams have structural pressure; solo builders must manufacture it. Sprints serve as a self-imposed commitment device that substitutes for the social and institutional pressure teams experience naturally.
15. The two-part scoping test requires that a first version be buildable in 4–6 weeks AND that someone would actually use it. Why are both conditions necessary?
Right. The goal of the test is to identify whether you have something real enough to learn from. A useless-but-buildable thing teaches you nothing. A useful-but-unscoped thing never gets built. Both conditions are needed to close the loop.
The test is about generating conditions for learning. Something that could take 18 months isn't actually testable yet — it's still an idea. And something buildable in a day that no one needs doesn't teach you anything either.
16. A Definition of Done should be written:
Correct. Writing the DoD before the AI session is the key sequence. The AI should be helping you reach a pre-defined target, not helping you define a moving target.
The DoD needs to be written before the AI brainstorming starts — not during it. Once you're in a productive session, expansion pressure is already active. Pre-writing anchors the session before that pressure begins.
17. Three separate users all say versions of "I can't figure out where my saved content goes after I create it." How should you classify this?
Three independent users describing the same problem in different words is a cluster — a reliable signal of a structural issue, not an edge case. And "I can't find my content" is workflow feedback: it directly blocks users from getting value, making it top priority over any preference feedback regardless of volume.
The independence of the reports is what makes this significant. If three people who don't know each other arrived at the same frustration, the actual number experiencing it is much larger — most users never report. And this is clearly workflow, not preference: finding saved content is core to the product's value, not an aesthetic enhancement.
18. For an early AI tool priced in the $5–$10/month range, the lesson says this window is effective because:
Right. That's the dual logic the lesson provides: low enough to avoid deliberation paralysis, high enough to create real commitment and useful feedback from paying users.
The lesson's reasoning is behavioral, not cost-based or research-based. Below $5, the transaction feels trivial. Above $20, the product needs more polish. The $5–$10 window hits both psychological thresholds.
19. The three-question filter before accepting AI-suggested features asks whether users requested it, whether the core job can be done without it, and:
The three questions: did users ask for it? can they live without it? what's the maintenance burden? Every feature you add is a feature you'll debug, update, and explain. That cost is real and compounds.
The three questions are grounded in user validation, necessity, and maintenance cost — not competitive analysis, sprint timelines, or vision alignment. Those matter, but they're not the filter.
20. Darius built a Shopify flash sale app and lost his launch window because he spent weeks on a Google Ads integration suggested by a user. The core lesson from his story is:
Right. His friend's manually-run flash sale validated the market while Darius was still perfecting. Being second-to-market with a better product sounds good; being so late that the window closes does not. Market learning has a time value.
The lesson isn't about distrust of users or integration complexity — it's about opportunity cost. The time Darius spent building the Ads integration was time he wasn't learning whether his basic product worked. Market validation has a time value.