You’ve been in three meetings this week about the same initiative. There’s a Miro board with 47 sticky notes. Everyone agrees it’s important. The Slack thread has 200 messages.
And exactly zero actual work has shipped.
The Comfortable Trap of Perpetual Planning
Let me guess: You’re smart, ambitious, and genuinely trying to do good work. So you do what smart people do. You analyze. You gather input. You whiteboard the strategy. You schedule alignment meetings.
And somewhere between the third brainstorm and the fifth revision of the project brief, the thing you were supposed to build is still theoretical.
This is the trap. Planning feels productive. Talking about the work feels like you’re moving forward. But you’re not. You’re just getting really good at describing the thing you haven’t done yet.
The hard truth: Until you ship something, anything, you have created exactly zero value.
Motion vs. Action: The Difference That Matters
James Clear (author of Atomic Habits) draws a critical distinction between motion and action:
- Motion is planning, strategizing, researching, and talking about what you’re going to do.
- Action is the behavior that delivers an actual result.
Motion is comfortable. It looks like work. You can show up to meetings, contribute to documents, and feel busy. But motion doesn’t change anything in the real world.
Action is uncomfortable. It requires you to commit. To put something out there that might fail. To discover that your brilliant idea has a flaw you didn’t see in the whiteboard session.
Motion is risk-free. Action has consequences. That’s precisely why motion is so seductive and action is so rare.
Why Smart People Get Stuck in Motion
You’re not lazy. You’re not avoiding the work. You’re stuck because:
1. You’re Waiting for Perfect Information
“Let me do one more round of research before we decide.”
You’ll never have perfect information. The market will shift. Competitors will move. Customer needs will evolve. Waiting for certainty is waiting forever.
2. You’re Building Consensus Instead of Shipping
“We need buy-in from all stakeholders before we proceed.”
Consensus is expensive. Every additional stakeholder adds another layer of delay. By the time everyone agrees, the opportunity has passed.
Amazon’s leadership principle of “Bias for Action” explicitly values speed over perfection: “Speed matters in business. Many decisions and actions are reversible and do not need extensive study.”
3. You’re Confusing Process with Progress
“We need to formalize the workflow before we start.”
Process is a tool, not a goal. If your process creates more meetings than output, the process is broken. The best processes emerge after you’ve shipped something and learned what actually matters.
The GSD Loop: A Framework for Actual Execution
Enough theory. Here’s the loop that moves work from “we should do this” to “we did this.”
Step 1: Choose One Specific Outcome
Not a vague goal. Not a vision statement. A specific, measurable outcome you can ship.
Bad: “Improve customer onboarding”
Good: “Ship a 3-minute product tour video that new users see on first login”
Bad: “Better team communication”
Good: “Run 10 one-on-ones with direct reports over the next 3 weeks” (see From 10 to 1,000)
Bad: “Build a new feature”
Good: “Ship a clickable prototype of the feature to 5 beta users by Friday”
The narrower the outcome, the harder it is to hide in motion.
Step 2: Start Right Now (Not Tomorrow)
This is the step where most people fail.
You have the outcome defined. You know what needs to happen. And then you say: “I’ll start tomorrow after I finish [other thing].”
No. Start now. Even if it’s imperfect. Even if you only have 15 minutes.
- Writing a proposal? Open the doc and write the first paragraph. Right now.
- Building a feature? Write the first function. Right now.
- Need to give feedback? Send the calendar invite for the conversation. Right now.
The gap between “I’ll do it” and “I’m doing it” is where momentum dies. Close that gap immediately.
Step 3: Ship a Rough Version
This is the step that separates high performers from chronic planners.
You do not need to ship the perfect version. You need to ship a version.
Reid Hoffman (founder of LinkedIn) famously said: “If you are not embarrassed by the first version of your product, you’ve launched too late.”
This applies to everything:
- First draft of the document? Ship it for feedback.
- First version of the process? Run it once and see what breaks.
- First prototype of the feature? Get it in front of a real user.
The rough version is not the failure. The failure is keeping the polished idea locked in your head where it generates zero impact.
Seth Godin’s entire philosophy is built on this principle: Ship the work. Done is better than perfect. Shipped is better than planned.
Step 4: Learn from the Real-World Result
Here’s the magic: You cannot learn from a plan. You can only learn from what actually happens when you ship.
The document you thought was clear? Users found it confusing.
The process you designed? It broke on edge case #3.
The feature you built? Users wanted a different version of it.
This is not failure. This is data.
You now know something you couldn’t have known from another brainstorm session. You know what the real world looks like. And that knowledge is infinitely more valuable than another round of theoretical planning.
Step 5: Repeat
Take what you learned. Ship version 2. Learn again. Ship version 3.
This is how real progress happens. Not in a single perfect launch, but in a tight loop of ship → learn → ship → learn.
Each cycle takes days (or hours), not months. Each cycle generates real feedback. Each cycle compounds.
By the time your competitors finish their planning doc, you’re on version 10. You’ve made mistakes. You’ve fixed them. You’ve built something that actually works because you tested it in the real world 10 times.
That’s the compounding power of execution.
The “Embarrassingly Rough” Standard
Let’s get specific about what “ship a rough version” actually means.
For a document or proposal:
- Typos? Ship it.
- Formatting a little off? Ship it.
- Sections that could be tighter? Ship it.
You can polish in version 2 after you get feedback on whether the content makes sense.
For a process or workflow:
- Not documented yet? Run it once manually and document after.
- Unclear who owns what? Assign it loosely and clarify after the first run.
- Might have edge cases? Handle them when they come up, not preemptively.
You can formalize after you know what actually matters.
For a product or feature:
- UI is rough? Ship it to internal users first.
- Only handles the happy path? Ship it with a note: “Edge cases coming in v2.”
- Missing nice-to-have features? Ship the core, add the rest later.
You can iterate after you see what users actually care about.
The standard is not “perfect.” The standard is “real.”
If someone can interact with it, give feedback on it, or break it—it’s real. That’s the bar. Everything else is motion.
The Meetings That Should Be Executions
Here’s an audit for your calendar this week. For every meeting, ask:
“Could we replace this meeting with someone just doing the thing and sharing the result?”
- “Brainstorm session on the new feature” → Could one person sketch 3 rough options and share them in Slack?
- “Alignment meeting on the Q3 strategy” → Could the owner write a 1-page doc and ask for comments asynchronously?
- “Planning call for the launch” → Could someone just draft the launch timeline and circulate it?
If the answer is yes, cancel the meeting. Do the thing. Share the result.
Execution generates clarity faster than discussion ever will.
When Planning Actually Matters
I’m not arguing for zero planning. I’m arguing against planning as procrastination.
Good planning:
- Takes 20% of the time
- Produces a rough direction, not a perfect blueprint
- Leads directly to execution (not to more planning)
Planning as procrastination:
- Consumes 80% of the time
- Produces polished documents that never get implemented
- Leads to “we need one more round of alignment”
If your planning doesn’t result in someone starting actual work within 48 hours, it’s not planning. It’s avoidance.
The One-Week Challenge: GSD in Action
This week, pick one thing you’ve been talking about but haven’t shipped.
Maybe it’s:
- A document you’ve been “meaning to write”
- A process change you’ve been “discussing”
- A feature you’ve been “designing”
- A difficult conversation you’ve been “preparing for”
- A 10-rep sprint you’ve been “planning to start” (see The Terrible Ten)
Now apply the GSD Loop:
Monday: Define the specific outcome. Write it down. One sentence.
Monday afternoon: Start. Do the first 15 minutes of work. Right now.
Tuesday-Wednesday: Ship a rough version. Not perfect. Just real.
Thursday: Get feedback from one person. Learn what you didn’t know.
Friday: Ship version 2 with the improvement.
By Friday, you will have created something that exists in the real world. You will have learned something you couldn’t have learned from planning. And you’ll be further ahead than 90% of people who are still in their third alignment meeting.
The Uncomfortable Truth
Here’s what nobody tells you about execution:
It’s scary because you might be wrong.
The plan feels safe because it’s theoretical. The shipped work feels risky because it’s real. People can see it. Critique it. Break it.
But here’s the thing: Being wrong quickly is infinitely better than being theoretical forever.
When you ship something that’s flawed, you learn. You iterate. You improve.
When you keep refining the plan, you learn nothing. You just get better at planning.
And nobody ever built anything meaningful by being really good at planning.
Stop Talking. Start Shipping.
Right now, you have something you’ve been meaning to do. Something you’ve talked about in meetings. Something that’s “on the roadmap.”
What’s the roughest version you could ship today?
Not the perfect version. Not the version you’d be proud to show at a conference. The version that proves the concept. The version that teaches you something.
Define it. Start it. Ship it. Learn from it. Repeat.
Everything else is just motion.
What are you going to ship this week? I’m on LinkedIn tell me what you’re committing to getting done (not planning, not discussing, actually done).
References & Further Reading
- The Terrible Ten: Why Your First 10 Attempts Must Suck - Why your rough draft should exist
- From 10 to 1,000: How Repetition Becomes Second Nature - Building execution muscle through reps
- Motion vs. Action: James Clear - The difference between looking busy and being productive
- Amazon’s Leadership Principles: Bias for Action - Why speed matters more than perfection
- Reid Hoffman: If You’re Not Embarrassed, You Launched Too Late - The philosophy of shipping rough
- Seth Godin: Ship It - Overcoming the fear of putting work into the world