Momentum Over Perfection: Build a JGSD Operating System

Eran Goldman-Malka · July 30, 2026

Leadership Productivity

Over the past week, we’ve built a framework for execution: embrace The Terrible Ten, build to 1,000 reps, Just Get Shit Done, apply Strategic Abandonment, and maintain a 48-Hour Rule.

Here’s the problem: You can’t sustain this on willpower alone.

The Willpower Trap

Right now, you’re motivated. You’ve read the series. You’re ready to push through your first 10 messy attempts. You’re going to stop planning and start shipping. You’re going to ruthlessly abandon low-value work.

Give it two weeks.

A deadline hits. You skip your 10-rep sprint to fight a fire. Your inbox balloons to 300 unprocessed items. You defer that strategic abandonment exercise “until next quarter.” You’re back where you started, except now you also feel guilty about it.

This is not a failure of character. It’s a failure of system design.

Why Discipline Is a Terrible Strategy

Behavioral science has known this for decades: Discipline is a finite resource. Psychologists call it “ego depletion”—every decision you make, every temptation you resist, every act of willpower depletes a limited reserve.

By the time you hit noon, you’ve:

Resisted checking Slack during deep work (willpower)
Forced yourself to write that difficult email (willpower)
Chosen to do the hard task instead of the easy one (willpower)
Pushed through the awkward 1-on-1 instead of rescheduling (willpower)

Now it’s 2pm, and you need to start your 10-rep sprint on a skill that makes you uncomfortable. Your willpower tank is empty. So you defer it. Again.

This is why discipline fails. You’re trying to power high-performance execution on a resource that runs out daily.

Systems Beat Goals (And Definitely Beat Motivation)

James Clear’s Atomic Habits makes the case clearly:

“You do not rise to the level of your goals. You fall to the level of your systems.”

Goals are aspirational. Systems are operational.

Goal: “I’m going to complete 10 one-on-ones this month.”
System: “Every Tuesday at 2pm, I run a one-on-one. It’s on my calendar. My team knows it’s blocked. No exceptions.”

The goal requires daily decisions: “Should I do this today? Do I have time? Maybe tomorrow…” The system removes the decision: “It’s Tuesday at 2pm. This is what happens now.”

The same applies to execution.

Motivation: “I’m going to Just Get Shit Done!”
System: “Every Thursday at 4pm, we ship whatever we’ve built, ready or not.”

Motivation is an emotion. It comes and goes. Systems are infrastructure. They persist regardless of how you feel.

The Agile Insight: Fast Feedback Beats Long Planning

Product teams figured this out 20 years ago.

The Agile Manifesto and Lean Startup methodology are built on one core insight: You cannot plan your way to the right answer. You must iterate your way there.

Traditional approach:

Spend 3 months planning the perfect feature
Build it for 6 months
Launch it
Discover users don’t want it
Repeat

Agile/Lean approach:

Build a rough prototype in 2 weeks
Show it to users
Learn what’s wrong
Fix it
Ship iteration 2 in another 2 weeks
Repeat

The key difference: Agile teams engineer rapid feedback loops. They don’t rely on motivation to iterate—they build rituals that force iteration.

Sprints. Demos. Retrospectives. Ship days.

These aren’t optional practices for when the team “feels like it.” They’re non-negotiable infrastructure.

And they work for individuals and managers just as well as they work for product teams.

Your JGSD Operating System: Four Core Rituals

If you want to sustain execution, you need to stop relying on discipline and start building infrastructure.

Here are the four rituals that turn “Just Get Shit Done” from a motivational slogan into an operating system.

Ritual 1: Ship Days (Deadline-Driven Execution)

What it is: A recurring, non-negotiable deadline when work goes live—ready or not.

Why it works: Deadlines create forcing functions. Without them, “good enough to ship” turns into “I’ll polish it a bit more” which turns into “I’ll finish it next week.”

How to implement:

For teams:

Pick a day and time: “Every Thursday at 4pm, we ship.”
Define “ship”: Code goes to production, document goes to stakeholders, prototype goes to users—whatever “live” means for your work.
No exceptions: If it’s not ready, you ship a reduced scope version. Never move the deadline.

For individuals:

Pick your own ship day: “Every Friday at 3pm, I publish whatever I’ve written this week.”
Commit publicly: Tell your team, your manager, or post on LinkedIn. Social pressure helps.
Ship ugly: Your first 10 attempts are supposed to suck (see The Terrible Ten). Ship anyway.

Examples:

Role	Ship Day Commitment
Engineer	Every Friday at 4pm, merge at least one PR to production
Writer	Every Tuesday at noon, publish one blog post or send one newsletter
Manager	Every Wednesday at 2pm, send weekly team update
Designer	Every Thursday at 3pm, share design iteration with stakeholders
Founder	Every Monday at 10am, demo product progress to team or advisors

The rule: You can ship less than planned. You cannot skip the ship day.

Ritual 2: Short Demos (Normalize Unfinished Work)

What it is: A recurring meeting where you show work-in-progress—explicitly unfinished, rough, “embarrassingly bad” work—to get feedback.

Why it works: Most people don’t ship rough work because they’re afraid of judgment. Demos create a safe space to show ugly drafts. Once it’s normalized, shipping becomes easier.

How to implement:

For teams:

Schedule it: “Every Tuesday at 10am, 15-minute demo slot.”
Rotate presenters: Everyone shows something every 2-3 weeks.
Set the tone: The presenter must say “This is rough, I need feedback on [specific thing].”
No polish allowed: If it looks finished, you’ve waited too long.

For individuals (if you work solo):

Find an accountability partner: Another founder, peer, or mentor.
Schedule a weekly 15-minute call: “Show me what you built this week.”
Commit to showing something, even if it’s a sketch on a napkin.

Demo structure (5 minutes per person):

Context (30 seconds): “I’m working on [X]. I’m on attempt [N] of my 10-rep sprint.”
Show the work (2 minutes): Screen share, prototype, document—whatever it is.
Ask a specific question (30 seconds): “Does this solve the problem?” “Is the structure clear?” “Which version do you prefer?”
Feedback (2 minutes): Open discussion.

Why this ritual is powerful: It removes the pressure to ship perfect work. If your team sees rough drafts every week, shipping rough drafts externally becomes normal.

Ritual 3: Failure Logs (Remove the Stigma of Mistakes)

What it is: A shared document (or personal journal) where you log what went wrong during your 10-rep sprints, ship days, or any execution attempt.

Why it works: Fear of failure is the #1 reason people don’t ship rough work or push through The Terrible Ten. Failure logs normalize mistakes by making them visible and routine.

How to implement:

For teams:

Create a shared doc: “Failure Log Q3 2026”
After every ship day or sprint, spend 5 minutes logging:
- What we shipped
- What broke
- What we learned
- What we’ll do differently next time

For individuals:

Keep a personal failure journal.
After every 10-rep sprint or major execution push, write:
- What attempt number was this?
- What felt terrible about it?
- What surprised me (good or bad)?
- What will I try next time?

Example failure log entry:

Date: July 23, 2026
Sprint: First 10 one-on-ones as a new manager
Rep: 7 of 10

What went wrong:
- Talked way too much. Employee barely got 3 sentences in.
- When they mentioned being overwhelmed, I jumped to solutions instead of listening.
- Ran 15 minutes over because I didn't timebox.

What I learned:
- I'm uncomfortable with silence. Need to count to 5 before filling the gap.
- Listening ≠ waiting to talk. Actually processing what they said takes effort.

What I'll try next time:
- Set a timer for 30 minutes. Hard stop.
- Ask "Tell me more" at least 3 times before offering any advice.

Why this ritual is powerful: Once you normalize logging failures, they stop being shameful. They become data. And data makes you better.

Ritual 4: Weekly Reviews (The 48-Hour Rule on Autopilot)

What it is: A scheduled 30-60 minute block every week to process your backlog, close open loops, and plan the week ahead.

Why it works: Without a recurring review, the 48-Hour Rule becomes aspirational. You’ll process things “when you have time,” which means never. A scheduled review makes backlog processing automatic.

How to implement:

The Weekly Review Checklist (30-60 minutes):

Step 1: Inbox Zero (15 minutes)

Process every unread email using the 4 Ds: Do, Delegate, Defer, Delete
Goal: 0 unread, 0 flagged by the end

Step 2: Task List Audit (10 minutes)

Review every task older than 2 weeks
Apply Strategic Abandonment: Delete or schedule
Goal: Every task has a clear next action and a specific date

Step 3: Calendar Review (10 minutes)

Look at next week’s calendar
Block time for your highest-priority work (ship days, 10-rep sprints, deep work)
Decline or delegate meetings where you’re not essential

Step 4: Reflect & Plan (15 minutes)

What shipped this week?
What failed?
What’s the one big win for next week?
What’s one thing you’re abandoning?

When to schedule it:

Friday afternoon (before you disconnect for the weekend)
Sunday evening (to start Monday with clarity)
Pick one and make it non-negotiable

Why this ritual is powerful: The review removes the mental load of tracking everything. Your brain can trust the system because the system runs weekly whether you feel like it or not.

The Four Rituals in Action: A Week in the Life

Here’s what a week looks like when you build the operating system:

Monday 9am: Weekly Review complete. Inbox at zero. Week planned. You know your one big win.

Tuesday 10am: Short Demo. You show the rough draft of the document you’re writing. Get feedback. Realize you need to restructure section 3.

Thursday 4pm: Ship Day. You publish the document. It’s not perfect, but it’s real. You send it to stakeholders.

Friday 3pm: Weekly Review. You log the week’s failure: “Document took 2 days longer than planned because I over-scoped section 2.” Adjust for next time.

Result: You shipped something imperfect. You learned from it. You processed the feedback. And you’re set up for next week. All without relying on motivation or discipline.

The Culture Silo Effect: Why You Don’t Need the C-Suite

Here’s the best part: You don’t need company-wide buy-in to build this system.

In my work on culture silos, I’ve observed that department heads and team leads dictate the real culture of execution far more than the C-suite does.

Why?

Because your day-to-day rituals—the meetings you attend, the deadlines you enforce, the behaviors you normalize—define how work actually gets done in your team.

The CEO can say “we value execution,” but if your team doesn’t have ship days, demos, or failure logs, that value doesn’t exist in practice.

You can build a JGSD operating system for your team of 5 even if the rest of the company is drowning in planning meetings.

How to Build a Local JGSD System

Step 1: Pick one ritual to start with

Don’t implement all four at once
Choose the one that addresses your biggest execution bottleneck
If you’re drowning in polish: Start with Ship Days
If you’re afraid to show rough work: Start with Short Demos
If mistakes feel shameful: Start with Failure Logs
If your backlog is chaos: Start with Weekly Reviews

Step 2: Schedule it for this week

Put it on your calendar right now
Invite your team (if applicable)
Set the expectation: “We’re trying this for 4 weeks. Then we’ll decide if it’s working.”

Step 3: Run it for 4 weeks

Don’t optimize it yet
Don’t debate whether it’s perfect
Just run it 4 times and see what happens

Step 4: Reflect and iterate

After 4 weeks, ask: “Did this make us ship more? Learn faster? Feel less overwhelmed?”
If yes, keep it. Add a second ritual.
If no, adjust or try a different one.

You don’t need permission. You just need to start.

Systems Compound, Motivation Doesn’t

Here’s why systems beat motivation:

Week 1 with motivation:

You’re fired up. You ship 3 things. You complete 5 reps of your sprint. You feel amazing.

Week 12 with motivation:

You had a bad week. You’re tired. You shipped nothing. You feel guilty.

Week 1 with a system:

It’s Thursday at 4pm. Ship day. You ship 1 thing because that’s what the system says to do.

Week 12 with a system:

You had a bad week. You’re tired. It’s Thursday at 4pm. Ship day. You ship 1 thing because that’s what the system says to do.

Motivation is a spike. Systems are a baseline.

And baselines compound.

If your system ships 1 thing per week for 52 weeks, you shipped 52 things this year. Most people who rely on motivation ship 12.

That’s the difference between “I want to execute” and “I have an execution system.”

The Full Stack: Connecting the Series

Let’s tie it all together:

The Terrible Ten: Your first 10 attempts will suck. Systems normalize this by making “ship ugly” the default behavior (Ship Days, Demos).
From 10 to 1,000: Mastery comes from repetition. Systems create the forcing function for consistent reps (10-rep sprints tracked in Weekly Reviews).
Just Get Shit Done: Execution > planning. Systems remove the decision of “should I work on this?” by making deadlines non-negotiable (Ship Days).
Strategic Abandonment: Focus on what matters. Systems build in regular culling of low-value work (Weekly Reviews, Task Triage).
The 48-Hour Rule: Clear your mental backlog. Systems automate this with recurring reviews (Weekly Reviews).
Momentum Over Perfection: You can’t sustain 1-5 on willpower. Systems make execution the default, not the exception.

Together, they form an operating system for high-output, low-burnout execution.

Your Challenge: Pick One Ritual, Start Tomorrow

Right now, you have four rituals to choose from:

Ship Days (force yourself to publish)
Short Demos (normalize rough work)
Failure Logs (remove stigma of mistakes)
Weekly Reviews (automate backlog processing)

Pick one. Schedule it for this week. Run it.

Don’t wait for motivation. Don’t wait for the perfect moment. Don’t wait for your C-suite to mandate it.

Just schedule it, show up when the calendar says to, and execute the ritual.

By next month, you’ll have run it 4 times. It will start to feel normal. That’s when you add the second ritual.

By Q4, you’ll have all four running. Your team (or just you, if you work solo) will ship more, learn faster, and feel less overwhelmed than anyone relying on motivation.

That’s the power of systems. They don’t care how you feel. They just work.

Which ritual are you starting with? I’m on LinkedIn—tell me which one you’re implementing this week and what your first ship day / demo / review is scheduled for.

References & Further Reading

The Series:

Systems & Habits:

Execution Culture:

Why Department Heads Out-Culture the C-Suite - Culture silos and local execution systems