There’s a quiet fantasy that runs through a lot of project thinking: that success means nothing went wrong. It’s a comforting idea and a dangerous one, because it sets a bar no real project ever clears.
Earlier this year, NASA’s Artemis II mission – the first crewed flight of its new Moon programme – was judged a success. The crew flew, the major systems performed, the test objectives were met, and the door opened to the missions that follow. And buried in the same reporting was a small, very human detail: the engineers were examining a hardware issue with a urine vent line, collecting data to fix it before the next flight. The mission also reached that point after an earlier delay caused by a fuel leak.
I find that combination clarifying. A genuine, celebrated success – with a known defect inside it, openly logged, being worked on for next time. That is what delivered actually looks like. Not flawless. Done, and honest about what wasn’t perfect.
We get this wrong constantly, in two opposite directions. The first mistake is to chase the flawless launch, to keep polishing and testing and refusing to ship until every imperfection is gone – which, on a complex project, is never, so the thing either never launches or launches so late it’s overtaken. The second mistake is the reverse: to ship and then quietly pretend the known problems don’t exist, to bury the defect log because admitting it feels like admitting failure. Both come from the same false belief – that success and imperfection can’t live in the same project.
They live together in every project worth doing. The skill isn’t eliminating every flaw. It’s judging which flaws are acceptable to fly with and which are not. A urine vent line you can study and fix before the next mission is not the same class of problem as a flaw in the heat shield. Mature delivery is the discipline of telling those apart – knowing what’s a “fix it for next time” and what’s a “we do not launch until this is solved.” Get that judgement right and you ship good things on time. Get it wrong in either direction and you either never ship, or you ship something dangerous.
What I admire most in the Artemis handling is the openness. They didn’t hide the vent line issue to protect the success story. They logged it, named it, and put it on the list for the next mission. That honesty is what makes the next mission safer, and it’s what makes the success real rather than fragile. A team that can say “this worked, and here are the three things we’re fixing before we do it again” is a team you can trust. A team that insists everything was perfect is a team that’s either lying or not looking.
Carry that into your own work. When you deliver – a project, an event, a product, a system – resist both the urge to wait for flawless and the urge to pretend the flaws aren’t there. Decide honestly which imperfections you can live with for now, fix the ones you can’t, and keep an open, unembarrassed list of the rest.
Done is not the same as flawless. The teams that understand that ship real things, learn from what wasn’t perfect, and come back stronger. The teams that confuse the two either never launch at all, or launch and hope nobody looks too closely. One of those is how good work actually gets made.
Leave a Reply