# The Embarrassment Test

*How to Build Your V1 in a 10-Day Sprint*

> "If your first version doesn't embarrass you a little, you overbuilt." — Reid Hoffman

Reid Hoffman didn't say this to be provocative. He said it because he watched hundreds of brilliant founders waste months building perfect products nobody wanted. The embarrassment test isn't about shipping garbage — it's about shipping something *real* before your brain has time to talk you out of it.

You're a Staff Engineer. You've shipped features that millions of people use. You know how to scope, execute, and deliver under pressure. But that course you've been "working on"? That SaaS tool? Six months. Maybe a year. Nothing to show for it except a sprawling to-do list and a quiet sense of failure.

This isn't a discipline problem. It's a plumbing problem. At work, you have standups, sprint reviews, a manager who asks about progress. At home, you have a wish and a Google Doc. You're trying to ship a product with the scaffolding of a daydream.

The 10-day build sprint fixes that. Tight enough to survive life's chaos, long enough to build something real, structured enough to work with your brain instead of against it.

## Why 10 Days Is the Sweet Spot

Most people think bigger timelines mean better outcomes. They're wrong.

A 30-day build turns into a 60-day build. A 60-day build turns into "I'll finish it when I have time." Open-ended timelines don't create focus: they create decision fatigue. Every day becomes a negotiation: "Should I work on this today? Which part? For how long?"

Ten days eliminates the negotiation. You know exactly what you're building. You know when it's done. There's no ambiguity, no room for scope creep to sneak in disguised as "one more feature."

The science backs this up. Research on creative work shows that **daily momentum beats marathon sessions**. Your brain isn't a battery that needs to be fully drained and recharged. It's a muscle. You strengthen it through consistent, focused use. One hour a day for 10 days builds more real progress than two 12-hour weekend binges, because:

- **Daily activation** keeps the problem-solving parts of your brain engaged. You start fresh, but you're not starting from scratch.
- **Momentum stacking** compounds. Finishing a task on Tuesday makes Wednesday's task easier. By Day 7, you're not pushing forward; you're rolling forward.
- **Life happens**. A 10-day sprint is short enough to survive your kid's birthday party, that work emergency, and the cold going around. A 30-day sprint has to weather all of that *and* maintain motivation.

![10-day sprint calendar showing momentum building from day 1 to day 10 with completed project](https://cdn.marblism.com/95KLsuMhYMY.webp)

## The Daily Build Protocol

At Google, I had systems. Standups. Code reviews. Sprint planning. Clear definitions of "done." That structure made shipping inevitable — not easy, but inevitable.

Your side project needs the same thing. Here's the exact protocol I use for every build day:

### The Startup Ritual (5 Minutes)

Before you open a single file:

1. **Environment Check**: Phone in another room. Do Not Disturb on. Water on desk. Headphones on (even if you're not listening to anything: they signal "deep work" to yourself and others).
2. **Review Your V1**: Glance at your one-sentence core outcome. Not the dream version. The embarrassingly small version you committed to shipping.
3. **Check the "Next Action"**: Look at the exact task you wrote down yesterday. You already know what to do. No decision-making required.
4. **Open the File**: Open the exact document, spreadsheet, or tool you need. Do not check email. Do not check Slack. Just open the file.

That's it. Five minutes. Then you move to the work.

### The Park Downhill Concept

This is what makes starting effortless.

At the end of your session: when your timer goes off or you hit a natural breaking point: don't just close your laptop. Write down the *exact* next action you'll take tomorrow. Be ruthlessly specific.

**Bad**: "Work on Module 2."
**Good**: "Write the opening paragraph of Module 2: the 'Why This Matters' section. Start with the hook about the blank page being the real enemy."

When you sit down tomorrow, you're not staring at a blank page wondering where to start. You skip the re-orientation tax entirely and roll straight into the work.

I learned this the hard way. For months, I'd end work sessions with a vague sense of what to do next. The next day, I'd sit down and spend 20 minutes re-orienting myself, trying to figure out where I left off. That 20 minutes was pure friction. It burned willpower. Half the time, I'd get distracted and never start.

Park downhill, and tomorrow's session starts itself.

### The Shutdown Ritual (5 Minutes)

When the timer goes off:

1. **Stop**. Resist the urge to "just finish this one more thing." Consistency matters more than an extra 20 minutes of burnt-out work.
2. **Commit**: Save your work. If you're using version control, commit with a message: "Day 12: Complete product outline."
3. **Park Downhill**: Write down tomorrow's exact next action.
4. **Close Loops**: Close all project-related tabs and windows. Leave your workspace clean.
5. **Celebrate**: Take 10 seconds to acknowledge that you showed up. You built something today.

That's it. Five minutes. Then you're done. You're protected.

![Park downhill concept diagram: pushing uphill vs rolling into tomorrow's task effortlessly](https://cdn.marblism.com/pH2JxcPlB07.webp)

## The 70/30 AI Rule: Kill the Blank Page

The blank page is your biggest enemy. Not AI.

For 20 years, I watched brilliant engineers get paralyzed by the blank page. It's not about ability. It's about activation energy. A blank page is uncertainty incarnate. Your brain sees it as a threat. So it avoids it. It finds a thousand reasons to research, plan, and defer.

AI doesn't solve your problem because it writes for you. It solves your problem because it *destroys the blank page*.

Here's how I use it: **AI writes 70% (the first draft, the structure, the ideas). I make it mine in the last 30% (editing for voice, adding specific examples, fact-checking).**

This isn't cheating. It's smart use of tools. Your job isn't to write every word from scratch. Your job is to ship a product that delivers on your promise.

The blank page isn't about content. It's about activation energy. The moment you have *something*: even if it's rough, even if it's wrong: your brain switches from "What should I do?" to "What should I fix?"

Fixing is action. Action is momentum. Momentum is what ships products.

### Make It Yours

Here's the only non-negotiable: **the product must sound like you.**

If you ship something that's clearly an AI output: stilted, corporate, generic: you've broken trust. People are buying *your* insight, *your* perspective, *your* experience. AI can help you shape that insight, but it can't replace it.

After AI generates the first draft, you must:

- Read it all the way through
- Edit for voice (make it sound like you talking)
- Add specific examples from your own work
- Fact-check everything
- Add nuance only you know

This is the 30%. It's work. But it's work you can do in a few hours, not the days it would take to write from scratch.

## The Real Embarrassment Test

What Reid Hoffman actually meant: if you're not a little uncomfortable shipping your V1, you waited too long.

Discomfort is the signal. It means you shipped before perfectionism could kill it. It means you built the minimum thing that proves the concept and gets you your first customer. It means you can now iterate based on real feedback instead of imagined needs.

The product I'm most proud of? A 4-module PDF-based system I shipped in 5 weeks. It was embarrassingly simple. No video. No community forum. No fancy design. Just a clear system with fillable worksheets.

I made $2,400 in the first month selling it to complete strangers.

That $2,400 did more to build my confidence than any amount of planning. It was evidence. It was real. And it only happened because I shipped the embarrassing version instead of waiting for the perfect one.

## Ship the Ugly Version

Perfection is the enemy of completion. The version you ship in 10 days will have flaws. The design will be basic. The features will be minimal. You'll know about three things you wish you'd done differently.

Ship it anyway.

Because the version you don't ship has no customers. It generates no revenue. It teaches you nothing. It's just another idea in the graveyard of "someday."

The embarrassment test isn't about lowering standards. It's about understanding that Version 1 is your launch pad, not your legacy. You can't build Version 2 until you've shipped Version 1. And you can't get real feedback until someone has paid you real money.

So build your 10-day sprint. Lock your scope. Park downhill every day. Use AI to kill the blank page. And ship something that makes you slightly uncomfortable.

That discomfort? That's the signal you did it right.

---

## About the Author

Molly Shelestak is a Build Partner for Side-Project Shippers. With 20+ years in tech — from Google to Heap to Contentsquare — she helps senior tech employees stop tinkering and actually ship their side projects in 6 weeks.

## Related

- [The V1 Manifesto](https://www.unstuckwithmolly.com/writing/v1-manifesto)
- [The 15-Minute Launch Plan](https://www.unstuckwithmolly.com/writing/launch-plan)
- [Work With Me](https://www.unstuckwithmolly.com/work-with-me)