The most expensive failure usually isn’t the flop. It’s the non-launch.

It’s the moment right before it, when something could have shipped, but finding out felt unbearable.

Something is “done enough.” The cursor hovers. Publish. Send. Ask. Post. Then the mind offers a deal: “Polish it a little more, avoid looking naive.”

That deal kills projects.

The Bravado Line

I can’t shake a line that sounds like pure bravado: act as if it’s impossible to fail. Taken literally, it’s nonsense.

Markets don’t care about my confidence. Reality doesn’t negotiate. I can build the wrong thing, price it wrong, explain it wrong, or hit a season where I don’t have the energy to keep going.

But the sentence isn’t trying to predict the outcome. It’s trying to change what to do in the hover-moment.

Here’s the only version that works: failure becomes “impossible” when the work is designed so that one bad result can’t stop the loop.

That sounds like a small shift. It changes everything.

It moves the focus from belief to mechanics. It turns a mantra into a constraint: make the next attempt cheap enough that ego doesn’t need protection.

Why Belief Breaks

Psychology has a term that gets close to what I mean: self-efficacy, the belief that I can execute the actions required for a specific goal.¹

What matters isn’t believing the world will hand out a win. What matters is believing I can take the next step when the first one doesn’t land.

This is why mindset-only advice feels brittle. Slogans can feel good, but the evidence for broad “mindset interventions” is more modest and more context-dependent than the culture implies.²

If “impossible to fail” is just positive thinking, it collapses the moment a real signal arrives.

It becomes an engineering problem.

So here’s the sentence, rewritten into something I can actually use: Act as if it’s impossible to fail by making it easy to take another attempt.

That only works if attempts create real freeze points, which is exactly the argument in The Problem Hidden Inside "Work in Progress" and How to Fix It.

The Loop

Indie hacking is living inside loops. Build. Ship. Watch what happens. Adjust. When the loop is tight, everything feels lighter. When it’s long, everything becomes existential.

If an attempt costs a month, the outcome starts to feel like a referendum on my taste. If an attempt costs an afternoon, it feels like doing a workout.

Photography taught me this before code did. Early on, every shot felt like it mattered. A few frames. A quick review. Embarrassment. Stop.

Then it clicked. Serious photographers don’t bet everything on one frame. They shoot a lot, then they edit hard. The contact sheet exists because selection is part of the craft.³

Now that I’m more experienced, it’s different. I usually take two or three shots because I trust I’ll get it. And sometimes I still shoot a lot. Either way, the pattern holds: make enough attempts for the uncertainty, then choose ruthlessly.

That’s what “impossible to fail” looks like in practice: enough attempts, ruthless selection, no melodrama.

Music has a cousin version of the same idea. In improvisation, a tense note doesn’t end the song. It asks for a resolution.

The “mistake” becomes a prompt for the next phrase. Building is full of tense notes: a day with no signups, feedback that stings, a feature that felt clever and turns out to be confusing.

When those moments become verdicts, freezing happens. When they become tension, motion continues.

The Trap

There’s a strong counter-argument here.

“Act like failure is impossible” can become permission to ignore evidence. It can also become an excuse to keep grinding on an idea that has clearly run out of oxygen.

I’ve seen that version too. “I can’t fail” can quietly turn into “I don’t need to look.” That’s not courage. It’s blindness wearing confidence.

There are good reasons to distrust my inner narrator. Humans are famously bad at predicting how long things will take. The planning fallacy is the name for the pattern: even after seeing similar projects go late, my mind still insists this time is different.⁴

The Fix

So the useful question becomes: how does failure become impossible without making reality optional?

My answer is to combine optimism in motion with pessimism in planning, and then add honesty in measurement.

Optimism in motion is the part that makes shipping happen. It’s the stance of “I’ll figure it out by doing.” It keeps ego from overprotecting itself.

Pessimism in planning is the part that prevents identity from getting tied to a story. It’s the outside view. Swap “how fast can this be done” for “how long did this take for similar people, in similar conditions?”⁵

Honesty in measurement is the part that keeps the loop real. If I don’t define what counts as signal, I can “stay in the loop” forever while quietly avoiding the truth.

Tools That Keep It Real

This is where a premortem helps.

A premortem is simple. Assume the project failed. List plausible reasons why. Fix what can be fixed before reality fixes it.⁶ It protects against delusional confidence without returning to paralysis. It turns fear into a checklist.

Which brings me back to loops.

The Lean Startup frame calls this Build-Measure-Learn.⁷ It doesn’t moralize. It doesn’t tell anyone to “be confident.” It tells teams to run experiments where the world can answer quickly.

In experiments, a negative result isn’t a failure. It’s a result.

The failure I care about is quitting the loop because a result can’t be tolerated. The other failure is staying in the loop while refusing to hear the result.

This is also why Paul Graham’s advice about doing things that don’t scale holds up. Early on, the world rarely hands out momentum automatically. Momentum usually has to be cranked manually.⁸ Acting like failure is impossible can look like doing the awkward, manual things long enough to earn real signals.

The Four Moves

To make a project “impossible to fail,” four moves help, in this order.

  1. Shrink the unit of shipping until something meaningful can ship in a day, or at least in a weekend, without heroics.
  2. Pick one measurable signal that shows up quickly, even if it’s crude.
  3. Add a premortem pass so confidence isn’t carrying the risk.
  4. Decide in advance what would make me pivot, pause, or stop, then refuse to interpret the next result as identity.

A lot of consistency problems get easier once you stop confusing force with fit, which is the center of Why the Most Consistent People Don't Need Discipline (Free tool included).

Tactics can change. Direction can change. Shipping stays non-negotiable.

That last piece is the hidden trick.

Most “fear of failure” is really fear of what failure would imply about identity.

Separate outcome from identity, and “impossible to fail” becomes true in the only way that matters. Wins aren’t guaranteed. Attempts are. It’s like photography again. The best frame isn’t the one hoped for. It’s the one found by taking enough frames that hope stops being necessary.

The interesting question isn’t “what if this fails?” It’s “what loop am I running that makes stopping feel more rational than continuing?”

If the loop is too big, polishing becomes protection. If the loop is small, reality becomes a collaborator.

And when that happens, failure stops being a cliff.

It becomes a trail marker.

Rabbit Hole

  1. Albert Bandura’s concept of self-efficacy is about belief in my capability to perform specific actions, not generic optimism. It matters here because the essay’s claim is behavioral: staying in the loop depends on believing I can take the next step. Source: “Self-Efficacy,” Kinesiology LibreTexts (summarizing Bandura).
  2. The “growth mindset” idea became cultural shorthand for “belief changes outcomes,” but meta-analyses suggest the average effect on achievement is smaller and more context-dependent than most people assume. It matters because it pushes the essay away from slogans and toward loop design. Source: Sisk et al., “To What Extent and Under Which Circumstances Are Growth Mindsets Important to Academic Achievement?” Psychological Science (2018), summarized by MSU/ScienceDaily with DOI.
  3. A contact sheet is essentially a photographer’s first full view of what was captured and a selection tool for editing. It matters because it supports the idea that quality often emerges from many attempts plus hard selection, not one perfect shot. Source: “What is a contact sheet?,” Cleveland Museum of Art.
  4. The planning fallacy describes the tendency to underestimate how long tasks will take, even when past experience suggests otherwise. It matters here as a warning: acting like I can’t fail can turn into under-planning if I don’t correct for this bias. Source: Buehler, Griffin, and Peetz (2017), “The Planning Fallacy,” preprint PDF.
  5. The “outside view” (reference-class forecasting) is the move of using outcomes of similar projects rather than trusting the internal narrative about why this time is special. It matters because it lets me keep optimism for action while grounding estimates and risk in reality. Source: Lovallo and Kahneman, “Delusions of Success: How Optimism Undermines Executives’ Decisions,” Harvard Business Review (summary on PubMed).
  6. The premortem is a structured way to assume failure in advance and surface reasons before the project is “alive” enough to defend emotionally. It matters because it’s a practical guardrail against delusional confidence while still keeping me moving. Source: Gary Klein, “The Premortem,” plus “Performing a Project Premortem,” Harvard Business Review (2007) PDF.
  7. The Build-Measure-Learn loop is the core Lean Startup framing: build an experiment, measure results, learn, and iterate. It matters because it describes the “tight loop” this essay argues for, where negative results become inputs rather than stopping points. Source: Eric Ries interview, “The Lean Startup,” Wharton (University of Pennsylvania).
  8. Paul Graham argues that early growth often requires unscalable, manual effort, and that waiting for scale too early can stall a startup. It matters because “acting like failure is impossible” often looks like doing the awkward work long enough to get real signal. Source: Paul Graham, “Do Things that Don’t Scale” (2013).