Your first attempts are going to be bad
A technique used by many a brilliant inventor:
- Make something. Get it functional. Get it adequate. It’s okay if it’s subpar.
- Then, stumble around. Iterate until it’s good.
Now, that’s a better creative process than making something good on the first go.
Start, even if you’re bad at it
Case in point: Write bad first drafts quickly. Start by getting something—anything—down on paper. Let it all pour out. Let it romp all over the place. No one’s going to see it. You can shape it up later. You can gradually polish the thought flow and enrich the choice of words.
If you aren’t willing to be bad initially, you’ll never get started on anything new.
It’s vastly easier to revise your way into a cut above than drum up brilliance out of thin air.
The way you create something good is by launching into it and then iterating gradually rather than by going into your cave and trying to create that perfect masterpiece.
Essentially, this is agile development. The best programmers write functional code to prove some concept. Along the way, they’ll get a better understanding of the business need for the software and the workflow. Bit by bit, they rework snippets of code and improve continuously.
Idea for Impact: Just start. Do a bad first job.
Momentum is everything. Don’t put off any contemplated task thinking, “This is hard. I don’t know how to do this well. I’m going to have to do it perfectly. Or I need to wait till I have enough time.” The instant you stop cold and put something off, momentum starts the other way.
Motivation is often the result of an action, not its cause. Taking action—even in small, sloppy ways—naturally produces momentum. It’s a better solution than trying to do it right the first time.