Outline Your 'Definition Of Done' To Avoid The Perfection Bug

Whatever your profession, it can be easy to work yourself into a frenzy by perfecting every single detail. Setting a specific "definition of done" from the outset of the project can help you move on to the next task.

Photo via OakleyOriginals

The phrase "definition of done" comes from a software development strategy called Scrum, but it can be applied to almost any situation. Stepcase Lifehack describes the technique.

Definition of Done describes clearly and explicitly what needs to be achieved until a task can be declared as done. And when you define your "done", you can get rid of your perfection bug.

For example, if your task is to create a marketing plan, you would create a checklist with items like "determine budget", "identify performance metrics" and "check work for grammar". Once every item on this list has been crossed off, you stop working. No more tweaking, no more double-checking. If you trust your definition of done, you won't need to let perfectionist tendencies bog you down and keep you from starting your next project.

What Can Software Developers Teach us About Crushing the ‘Perfection Bug'? [Stepcase Lifehack]


Comments

    All TO-DO lists should have 4 columns.
    1. What needs to be done.
    2. Why you need to do it.
    3. When does it need to be done?
    4. What 'done' means for this item.

    In my world, if it ain't got these, it ain't getin' done.

    The Cult of Done Manifesto summarises this nicely - also with a neat info graphic in the spirit of "Information is beautiful":
    http://www.brepettis.com/blog/2009/3/3/the-cult-of-done-manifesto.html

Join the discussion!

Trending Stories Right Now