Ship-It Studio
You now have every skill this module teaches: planning with four questions, slicing into working pieces, testing like a user, getting real feedback, sharing safely, crediting AI honestly, and building responsibly. This lesson puts them together. Ship-It Studio is a structured sprint — a compressed, end-to-end practice run where you take one idea from concept to a shared, working state. Not someday. Today.
The Ship-It Sprint — How It Works
A sprint is a fixed-time, goal-focused work session. Professional teams use them constantly. Today yours lasts the length of this lesson. Your sprint has five phases, each with a time budget: Phase 1 — Plan (5 minutes): Answer the four planning questions from Lesson 2. Write them down. Identify your MVP. Name your one scope risk. Phase 2 — Slice (3 minutes): Break the MVP into three slices. Write each as a one-sentence description of what a user can do when that slice is complete. Order them with core value first. Phase 3 — Build (25-40 minutes): Work through your slices using an AI assistant, your own code, or both. Stay focused on the MVP. When you feel the urge to add a new feature, write it on a sticky note and keep building. Phase 4 — Test and Check (10 minutes): Run the user testing routine from Lesson 4. Ask the three feedback questions from Lesson 5. Run the safety checklist from Lesson 6. Run the responsibility questions from Lesson 8. Phase 5 — Ship and Credit (5 minutes): Publish or share your project. Write your attribution label (Lesson 7). Share the link.
For Ship-It Studio, 'shipped' means: at least one person other than you can access and use your project right now, without your help. This could be a link to a hosted page, a shared document, a working prototype on your screen that a partner uses independently. The bar is real access, not imagined access.
Some things to expect during your sprint: You will hit a moment where you want to add one more thing. Do not. Write it down, move to the next phase. Your build will probably not look the way you imagined. That is normal. What matters is that it works and someone can use it. You may finish Phase 3 with something that barely works. Ship it anyway. A barely-working thing that someone can actually use is more valuable than a polished thing that nobody can access. After you ship, you will notice things to fix. That is fine. Iteration after shipping is how most great products were made.
Using AI as Your Sprint Partner
AI is most useful in a sprint when you treat it like a specific-task assistant, not a genie. Instead of: 'Build me a quiz app' — try: 'I am building slice 1: a page with a text input and a Submit button that logs the input to the console. Help me build only that.' Instead of: 'Fix my code' — try: 'This function is supposed to check if the user's answer matches the correct answer. It is returning false even when they match. Here is the function: [paste]. What is wrong?' Small, specific prompts in a sprint produce working code faster than large vague ones. You already know this from Lesson 3. Apply it now under time pressure.
Every time you want to add a feature that is not in your MVP, write it on a sticky note (physical or digital). This keeps your brain from losing the idea while protecting your sprint from scope creep. The sticky note pile after a sprint is your backlog — a real list of what to build next time.
Prompt Challenge
Write a focused AI prompt that asks for help building exactly one slice of your project — no more.
Your prompt should…
- describe the slice in one sentence stating what a user can do when it is complete
- specify the technology or tool you are using so the AI can give exact help
- tell the AI explicitly what NOT to build so it does not add unrequested features
Why should you keep building through your MVP slices even when the urge to add features hits?
In the Ship-It Sprint, what makes Phase 4 (Test and Check) important before Phase 5 (Ship and Credit)?
The Ship-It Sprint
- Step 1 — Plan (5 min): Write your four planning questions answers. Name your MVP. Name your scope risk.
- Step 2 — Slice (3 min): Write three slices. Core value first.
- Step 3 — Build (as much time as you have): Work through your slices with AI assistance, your own code, or both. No new features — use the sticky note rule.
- Step 4 — Test and Check (10 min): Have one person test it. Ask all three feedback questions. Run the safety checklist. Run the three responsibility questions.
- Step 5 — Ship and Credit (5 min): Share your project so at least one other person can access it. Write a one-sentence attribution label.
- Step 6 — Debrief: Write two sentences: what you shipped, and one thing you would do differently next sprint.