improve things a bit

Author: kentcdodds

epicshop/package-lock.json

@@ -0,0 +1,33 @@
+# Clarify MVP Outcomes
+
+👨‍💼 We need an MVP scheduling app so small teams can quickly find a time that
+works for everyone. Before anyone writes implementation code, we need to be
+clear on the outcome we are trying to produce.
+
+🐨 In this step, do not change application code. Create a short discovery note
+that includes:
+
+1. The top 8-12 questions you would ask before building
+2. A first-pass list of assumptions (labeled as assumptions)
+3. Explicit MVP success criteria that could be validated later
+4. Known constraints (time, scope, dependencies, compliance, data concerns)
+
+In real MVP work, start with a small, high-leverage stakeholder set:
+
+- 💼 Berry the Business Owner (business goal and success metric owner)
+- 👤 Una the User (workflow reality and usability pain points)
+- Engineering counterpart (technical feasibility and delivery constraints)
+- Optional fourth stakeholder only if needed (legal/compliance or support/ops)
+
+📝 As you work, keep your questions specific and decision-oriented. If an answer
+would not change your plan, that question is probably too vague.
+
+💰 Helpful prompt format:
+
+- What decision does this answer unlock?
+- What risk appears if this is wrong?
+- How would we validate this in the MVP?
+
+📜 Reference your own planning notes while drafting. Keep your assumptions,
+constraints, and success criteria in one place so you can validate them in
+later steps.

exercises/01.building-an-mvp/01.problem.clarify-mvp-outcomes/README.mdx

@@ -0,0 +1,24 @@
+# Clarify MVP Outcomes
+
+👨‍💼 Great work. Before implementation, we now have a clearer definition of the
+problem we are solving and how we will judge success.
+
+🦉 The important outcome is not perfect requirements. It is making ambiguity
+explicit early so tradeoffs can be intentional instead of accidental.
+
+A strong deliverable from this step includes:
+
+- Decision-oriented stakeholder questions
+- Clearly labeled assumptions
+- Measurable MVP success criteria
+- Constraints and risks that will shape implementation
+- Input from a small, relevant MVP stakeholder set (for example 💼 Berry and 👤 Una)
+
+🧝‍♀️ I added a separate reference file with example stakeholder questions:
+`example-stakeholder-questions.md`.
+
+Use it to calibrate quality and compare your own list. Your questions do not
+need to match word-for-word.
+
+📝 Capture your final notes in a place you can reference in later steps. You
+will use this artifact to evaluate whether the MVP actually matched the intent.