# The V1 Manifesto

*How to Kill Scope Creep and Actually Ship*

You've made it past the paralysis. You validated your idea. Ten people said they'd buy it. You're excited.

Now you're about to do the most dangerous thing possible: start building without defining exactly what V1 looks like.

I've watched brilliant engineers, people who ship flawlessly at Google and Meta, blow up their side projects at this exact stage. They have momentum. They think, "Let me just start and figure it out as I go." Two months later, they're 40% done with 70% scope. The ship date has slipped twice. Momentum is dead.

This happens because of a simple miscalculation: **most builders don't understand the difference between what they want to build and what they need to build to ship.**

The goal of V1 isn't to build your perfect product. It's to prove two things: (1) the core idea has legs, and (2) you can finish what you start.

## The One Framework That Kills 80% of Scope Creep

Before you define *what* you're building, define *why* your customer needs it. Not from your perspective. From theirs.

This is **Jobs-to-Be-Done (JTBD)**, and it's the single most effective scope filter I've ever used.

The JTBD sentence is deceptively simple:

> **"When [situation], I want to [motivation], so I can [outcome]."**

Notice it doesn't mention your product at all. It's about the customer's situation, their desire, and the outcome they're trying to achieve.

**Example 1: Expense Tracker**

- Weak: "I built an expense tracking app."
- JTBD: "When I've spent money throughout the week, I want to quickly log where it went, so I can understand my spending patterns before my monthly review."

See the difference? The second one tells you *why* the customer cares. You don't need fancy charts. You don't need multiple categories. You need speed and clarity. That guides every decision.

![Jobs-to-Be-Done framework flowchart showing customer situation, motivation, and outcome path](https://cdn.marblism.com/xD1Itz_dhEC.webp)

**Example 2: Email Sequence Builder**

- Weak: "I built an email marketing tool."
- JTBD: "When I've just launched a new product, I want to automatically send a sequence of follow-up emails to my buyers, so I can turn one-time customers into repeat buyers without writing the same emails over and over."

This JTBD tells you your V1 isn't a full marketing platform. It's not a drag-and-drop builder. It's a simple template system + an automation trigger. That's it.

Here's the magic: once you have your JTBD statement, almost every feature request becomes easy to reject.

A team member says, "We should add user profiles so people can follow each other." You look at your JTBD. That feature doesn't help with the core job. It's scope creep. Into the V2 Backlog.

Someone asks, "What if we added an AI assistant to suggest categories?" Again, does it solve the core JTBD? No? V2 Backlog.

The JTBD statement becomes your product's North Star.

## The One-Page Scope: Your Anti-Scope-Creep Contract

Once you have your JTBD, you're going to define the product in brutal detail, on a single page.

This constraint forces ruthlessness. Every word has to count. Features have to be prioritized. Nice-to-haves have to be cut.

Here's the critical section that separates shippers from dreamers:

### V1 Features (Maximum 5)

You get 5 features maximum. Not 5 categories. Five total features.

A "feature" is something the customer can do with your product:

- "Log an expense with amount, category, and date."
- "View a list of all expenses for the current month."
- "Filter expenses by category."
- "Download expenses as a CSV file."
- "Set a monthly spending alert at $X."

Notice how specific these are. Not "reporting." "View a list of all expenses for the current month." These are things. Not concepts.

If you can't fit what you're building into 5 features, your scope is too big. Go back and cut.

![V1 scope document with five core features and crossed-out V2 backlog items separated by scissors](https://cdn.marblism.com/f3nUs6DgQum.webp)

### What's NOT Included (The Most Important Section)

This is where most people get it wrong. They list features. They should list *ideas they're rejecting*.

Go through all the ideas in your brain, the ones that popped up while you were validating, the ones your research showed were popular, the "stretch" ideas. Write them down. Then cross them out and move them to this section.

Examples:

- "User profiles and social following (V2)"
- "AI-powered category suggestions (V2)"
- "Multi-currency support (V2)"
- "Mobile app (V2)"
- "Custom domain for shared links (V2)"

This section should be longer than your features section. That's how you know you're thinking clearly.

Your V2 Backlog is not a graveyard. It's a gift shop. You're honoring great ideas by giving them a safe place to live, while protecting the timeline of your current commitment.

**Shipping V1 is the price of admission to start working on V2.**

## The Decomposition Method: From Blob to Step

You have a one-page scope. Now you need a map to actually build it.

Here's the principle: your brain cannot execute a blob. It can only execute a step.

"Build a product" is a blob. "Set up authentication with Firebase Auth" is a step.

### Break It Down in Three Levels

**Level 1: Identify 3-5 Milestones**

Break your V1 into 3-5 major chunks. Use the **Verb-First Rule**: A milestone starts with an action verb.

- Instead of: "Authentication"
- Write: "User can log in with email and password"

**Level 2: Break Milestones Into Tasks**

Take only your first milestone and break it into individual tasks. A task is something you can complete in a single work session (60-120 minutes).

Again: Verb-First Rule. "Authentication" is not a task. "Set up user login with email and password using Firebase Auth" is a task.

**Level 3: Your Very Next Action**

The only thing that matters is the very next action. Not the grand vision. Not Milestone 4. Just the first task.

Schedule it in your calendar with a date, time, and location. "Tuesday, 7:00 PM, at my desk: Set up new React project with Vite."

Every task you complete is evidence that you're someone who ships. Momentum is built not by dreaming about the summit, but by taking the first step, and then the next, and then the next.

![Project decomposition diagram: overwhelming project blob broken into manageable step-by-step tasks](https://cdn.marblism.com/gKbw4TuFlO1.webp)

## The Scope Lock Ceremony: Make It Psychological

This is not metaphorical. I want you to actually do this.

1. **Print your One-Page Scope** (or format it beautifully as a PDF)
2. **Sign and date it** (yes, really: this makes it real)
3. **Add this statement at the bottom:**

> "I commit to shipping this V1 by [DATE]. Everything not on this scope goes to the V2 Backlog. No exceptions. No scope creep. Done > Perfect."

1. **Photograph it and share it with your accountability partner.**

This is your psychological contract with yourself. The moment you make it public and signed, your brain treats it differently.

### The Scope Creep Detector: Your Final Defense

From this point forward, every new idea runs through a five-question checklist. If it fails, it goes to V2.

**Question 1: Is this absolutely essential for my V1 Core Outcome to function?**

- If No → V2 Backlog

**Question 2: Can my V1 ship without this?**

- If Yes → V2 Backlog

**Question 3: Does this add more than a day of work to my current plan?**

- If Yes → V2 Backlog

**Question 4: Am I adding this because I'm avoiding a harder, more important task?**

- If Yes → V2 Backlog (and complete that harder task instead)

**Question 5: Will I be proud to have shipped my V1, even without this feature?**

- If No → V2 Backlog (and re-evaluate if this is really V1)

If your idea passes all five questions, it's a legitimate V1 addition. But I'm betting most ideas will fail Question 2 or 3.

## The Real Story: My First Product

When I left Google to start building independently, I had big dreams. I envisioned a comprehensive video course with 12 modules, an interactive community forum, multiple output formats, downloadable resources, progress tracking, and a certification system.

I was paralyzed. The project felt impossible. For three weeks, I made no progress.

Then I forced myself to brutal honesty: What is the minimum I need to ship to prove this idea works?

I cut everything. The video became a PDF. The 12 modules became 4. The forum became "people email me." The certification became "they get a completion badge in email."

My final V1 feature list had 4 items:

1. Read 4 modules of written content
2. Complete worksheets for each module
3. Email the worksheets to me when done
4. Receive a completion certificate

It felt embarrassingly small. I was embarrassed to even write it down.

But it was shippable. And more importantly, it was real.

I shipped that 4-module PDF in 6 weeks. It was the beginning of everything that came after. Because I proved I could finish.

## The V1 vs. V2 Mindset Shift

Let me be clear about what happens after today:

| V1 (Now) | V2 (Later) |
|---|---|
| Scrappy, functional | Polished, refined |
| Solves the core job | Adds delight |
| Proves the idea | Scales the idea |
| Gets 1st customer | Gets 100th customer |
| Done in 4 weeks | Built over months |

You are not building the final version. You are building the first version.

---

## 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 Embarrassment Test](https://www.unstuckwithmolly.com/writing/embarrassment-test)
- [The Infrastructure Mismatch](https://www.unstuckwithmolly.com/writing/infrastructure-mismatch)
- [Work With Me](https://www.unstuckwithmolly.com/work-with-me)