/ 1 min read
Finishing is a skill
No delivery, no invoice - what consulting taught me about finishing, and why the compromises belong in scope, not standards.
Finishing is a skill. I learned it in consulting, where the rule was simple: no delivery, no invoice.
For an engineer, there is always a better way. You get smarter as a project moves along, and halfway through you can see the cleaner solution you should have chosen at the start. That instinct is a good one, but left alone it’s also how projects never end.
As a founder, the perfect version is rarely an option. You run out of time and money long before you run out of ideas. At some point the job is to get the thing from A to B and accept the compromises that come with it.
The tricky part is that the people you most want on a team usually care deeply about the work. Their professional pride is part of why the result is good, and you don’t want them to care less just because the deadline is getting closer. So the compromises have to go somewhere else - into scope, not standards. Shipping half-baked work just means the deadline won.
That’s where leadership comes in. Someone has to decide what doesn’t get built, explain why, and own that decision when it’s uncomfortable, so the team can keep their standards without trying to solve everything. It takes structure, calm and momentum. Data where you have it, judgment where you don’t.
Finishing is a skill.