Perfect the Why, Ship the How

You know the feeling before you have words for it.

The thing is built, or nearly. Months of work, maybe years. It sits there, finished enough to ship and not finished enough to feel safe. Your hand is on it. And you can’t press publish.

Not because you’re lazy. You’re the opposite of lazy — that’s the whole problem. You care about this at a depth most people would find exhausting. You’ve refined it, tested it, imagined every way a stranger might misunderstand it. And still there’s a rock somewhere in your chest that says not yet, not like this, who are you to put this into the world half-formed. 

I want to say something to the people who live in that moment, because I don’t think the usual advice is for you.

The advice that doesn’t fit

The internet has one answer for perfectionism: lower your standards. Ship the ugly version. Done is better than perfect. Move fast and break things.

This advice isn't wrong for everyone. It’s that it was written for a different kind of person — someone who needs permission to care less. If that’s you, take it. But if you’re the kind of person who has never once suffered from caring too little, being told to lower your standards lands like an insult. It asks you to become worse at the one thing you’re actually good at.

The Weird Ones — the visionaries, the nonlinear builders, the ones who see three moves ahead of the room — do not have a caring problem. Telling them to care less is like telling water to be less wet. So they nod at the advice, feel vaguely ashamed that they can’t follow it, and stay frozen.

Perfection causes trouble only when it’s pointed at the wrong stretch of ground.

Where perfection actually lives

Here is the distinction I keep arriving at, session after session, and I’m going to give it language even though I’m still testing its edges.

When you build something that already exists — a better app in a known category, a cleaner version of a familiar service — “perfect” has a definition. There’s a standard in the world. You can measure yourself against it, close the gap, and know when you’re done.

But when you build something that has never existed, there is no standard yet. You are pawing the territory. And you cannot perfect a domain you are still discovering. There is no finished map of a country you are the first to walk into.

This is the thing perfectionism can’t accept: for genuinely pioneering work, “the perfect final version” is not a thing you’re failing to reach. It’s a thing that does not yet exist, and cannot exist, until the work is out in the world teaching you what it’s actually for.

The iteration is the structure of pioneering itself. You ship, the world responds, the territory reveals its shape, and only then do you learn what the next version wants to be. What looks like a failure is the mechanism at work.

The shortcut, not the surrender

Now — and this matters, because I know who I’m talking to — none of this is permission to be sloppy.

I’m not asking you to stop wanting perfection. I would never ask that. I’m telling you that you’ve been aiming it at the wrong layer, and that once you re-aim it, you get to perfection faster, not slower.

Because there is one thing in pioneering work that can be perfect from the start. Not the features. Not the polish. Not the interface or the pitch or the fifteenth refinement of the onboarding flow. Those are supposed to move — they’re the parts the world hasn’t finished shaping yet.

The thing that can be perfect is the intention beneath it. The why the thing exists. The precise human problem it exists to answer.

When the intention is clear, whole, and non-negotiable, it becomes the fixed point everything else can move around. You stop trying to make the features perfect and start letting them be accurate — accurate to an intention that already is perfect, already is fully itself, already knows exactly what it’s for. The imperfection lives in the execution, where it belongs, where it’s supposed to be provisional. And the perfection lives in the intention, where it can actually hold still long enough to be perfect.

That’s the shortcut. Not lower your standards — relocate them. Perfect the one thing that can be perfected, and let it steady everything that can’t.

The rock in the chest is rarely really about the features. It’s the feeling of trying to make something hold still that was never meant to hold still — the product — while the thing that would steady you, the intention, sits unexamined underneath. Attend to the intention, and the rock tends to dissolve. Not because the work got easier. Because you finally aimed your perfectionism at something that could actually receive it.

Lead with the vision, let the features follow

This is why I’ve come to believe that for deeply new work, you have to express the Intention before the features — to yourself first, and then to everyone else.

If you begin with the features — what it does, how it works, why it’s better — you’re describing a territory nobody has a map for, in a language built for territories that already exist. Of course it feels flat. Of course you can’t find the “right story.” You’re translating something unprecedented into the vocabulary of the precedented, and the vocabulary keeps failing you.

But if you begin with the Intention — the shift this makes possible, the human thing it protects, restores, or sets free — then the features arrive as evidence, not as the pitch. People don’t fall in love with what a thing does. They fall in love with what becomes possible because it exists. The features are how you keep the promise the vision made.

I’ve watched what happens when a builder stops leading with function and starts speaking from intention. The voice changes. It stops apologizing. It becomes certain —  authoritative, in the old sense of the word: speaking as the author of something, the one who gets to say what it means. The rock is gone, and what’s left is someone finally standing in their own league.

What this is a piece of

I’m calling this early on purpose. This is one of a handful of ideas I keep circling as I work out something larger — a way of understanding a company or a product not as a machine to be optimized but as a living thing with an intention of its own. An organism, not an org chart. I’ve started calling that direction Evolutionary Business, and I’m not going to pretend I’ve finished thinking it through. I haven’t. I’m thinking it through in public, which is the only honest way I know to build something that’s actually new.

But this part I’m sure enough of to say plainly:

The reason you can’t ship isn’t that you aren’t perfect enough. It’s that you’ve been asking the features to be perfect, when perfection was never their job. Give that job back to the intention. Let the features do what features are supposed to do in pioneering work — move, learn, and become accurate over time.

Perfect the why. Ship the how. Let the world teach you the rest.

Birgitta Granstrom

What is the thing you can’t press publish on — and are you sure it’s the work that isn’t ready, or the intention you haven’t let yourself name?