The work you just completed is never your best possible work.
I had a wonderful evening tonight – a reader of the site visiting Saigon reached out to me, and we spent five hours having coffee and discussing philosophy, writing, history, traveling, government, business… amazing guy. Great conversation. Really enjoyed it, the time flew.
Now, I tell you – this is a guy with amazing creative ability and insights. He’s spent a lot of time thinking about and researching and learning interesting things. He has a lot to share with the world.
Yet, he hasn’t released most of the writing he’s done. He’s a writer, and I’m guessing quite a solid writer – he reads a lot, writes a fair bit, and is a clear thinker, and that combination lends itself to solid writing. I’m almost certain he can at least write well enough that the writing doesn’t get in the way of the good insights, and he definitely has good insights.
But, he said to me – he’s looking to create timeless, masterpiece-level work, like the literature he really admires most.
I think that’s a tough thing to do, because of what I’m going to call “the creator’s curse” -
The work you just completed is never your best possible work.
Doing anything of significant magnitude means you’ll get better at your craft in the process. That means, as soon as you complete anything significant, you’ll notice how you could have done it better.
This seems to hold true of anything significant.
Some endeavors mean you can’t agonize after you finish. If you’re putting on an event, it happens at a fixed time and place. After you throw the event, you realize all the things you could have done differently to do a better event, but you can’t agonize over them – you just have to throw another event to put those ideas into motion.
But if you’re writing, painting, programming, composing, designing, anything like that – you could keep refining your work and never release it, and the work would keep improving. Every time you do significant work, you learn lessons and see how the work you created could be better.
This excerpt from “Art and Fear” on Coding Horror has burned the phrase “Quantity Always Trumps Quality” into my mind -
The ceramics teacher announced on opening day that he was dividing the class into two groups. All those on the left side of the studio, he said, would be graded solely on the quantity of work they produced, all those on the right solely on its quality. His procedure was simple: on the final day of class he would bring in his bathroom scales and weigh the work of the “quantity” group: fifty pound of pots rated an “A”, forty pounds a “B”, and so on. Those being graded on “quality”, however, needed to produce only one pot – albeit a perfect one – to get an “A”.
Well, came grading time and a curious fact emerged: the works of highest quality were all produced by the group being graded for quantity. It seems that while the “quantity” group was busily churning out piles of work – and learning from their mistakes – the “quality” group had sat theorizing about perfection, and in the end had little more to show for their efforts than grandiose theories and a pile of dead clay.
The answer, I think, is to stop comparing your work to the standard of perfection – which you’ll never reach. Instead, start comparing your work to what else is potentially available. If what you’re working on potentially fills a need by people that isn’t totally fulfilled, then release it and let people start benefiting from it. You can make your next work better.
The work you just completed is never your best possible work.
It can’t be your best possible work, because doing anything significant means you just learned new lessons. But that’ll be true even if you go back and do it from scratch again. Release your work into the world, imperfect and all. Let it start fulfilling people’s needs. Keep improving, and make your next work even better.


{ 7 comments… read them below or add one }
Thank you for this ‘in your face’ wisdom. I’d heard it before, but your examples made it finally make sense. Especially this one:
After you throw the event, you realize all the things you could have done differently to do a better event, but you can’t agonize over them – you just have to throw another event to put those ideas into motion.
It is good to improve and seek perfection, but we need deadlines. That’s when you really start thinking about the product or whatever it is you are working on, considering compromises you can make to ship on time, thinking about what you can release with a later update, focusing on the product itself.
For example, there was a trend amongst geeks to release Beta versions of e-books. The author is writing the book, at some point he releases it while it is still a ‘work-in-progress’ piece – then commentators help him improve it, he releases the next Beta version etc. And when the publishing date comes, he has a much more improved product – because he released it early and benefited from the feedback, learned from his mistakes, and when he starts his new book, he will have a better starting point.
I think people who do not ‘ship’ are maybe scared of negative feedback (I am sometimes guilty of it myself). How can you risk your ‘image’ as an expert if you can’t write a simple article without making some dumb mistakes… Well, you can’t be an expert on everything, and you can’t please everybody. It’s better to find a way to benefit (financially, intellectually or whatever way you are aiming for) from this ‘learning by doing and making mistakes’ exercise. It is better to get negative feedback on something you consider a ‘work-in-progress’ than to finish and polish a piece just to find people moaning about it.
And yes, this comment is full of mistakes and is poorly structured, but I am posting it :-) The next one I write will hopefully be better.
Good comment Rumena.
> I think people who do not ‘ship’ are maybe scared of negative feedback (I am sometimes guilty of it myself).
I think almost everyone is afraid of negative feedback to more or less extent… if you weren’t, at all, and you had a good work ethic… damn you’d do immensely huge amounts of stuff.
I think Steve Jobs said it best: Real Artists Ship.
Putting something you have created out into the world has to be one of the hardest things there is. But until you do, I don’t think you can really call yourself a creator or an artist. You are practicing, you are studying, but you aren’t creating until what you make is exposed to the world.
I also think that, while it is true that every time you build something you learn from it, regardless of if you ship it or not, you learn more from watching others interact with and react to your creation than you do just from considering it yourself. The work you just created is never your best possible work, but by testing it in the real world you help your next work take a larger step forward.
Yup, I’m huge fan of that Steve Jobs quote. I covered that topic a little here -
http://www.sebastianmarshall.com/what-separates-a-generalist-and-a-dabbler
Fully agreed. You gotta put the work out there.
A similar point from another angle:
In Romain Gary’s “Promesse de l’Aube”, Romain describes how he practiced juggling, and got to 7 balls but could never get to 8, and felt intensely frustrated to never be able to quite get there. He looked up to his juggling idol, the Great Rastelli, who could juggle 12 balls, and felt like a failure because he couldn’t do 8.
The one day he had an epiphany when he realised that all his life Rastelli must have chased the 13th ball like he was chasing the 8th. All his life he would have been frustrating by the fact that there was one more ball that he couldn’t manage, and that would be true no matter how many balls he could manage.
That is perhaps not so much the creator’s curse as the achiever’s curse, but then all successful creators are achievers, right?
(note: I can’t remember the actual numbers… but the relative differences were about that I think)
Ah, fantastic insights Daniel, yeah. To some extent, it really never gets easier – so celebrate and enjoy in the meantime. Great story, great point.
That’s right. It was you that inspired me a while ago to focus more on shipping that perfection, and I’d say it helped me tremendously. Now I always try to come up with a good enough version of a product, release it, and then iterate. It works better for me.
{ 3 trackbacks }