Before I start this is not a rallying call for mediocrity or dumbing down. There are many people with deeply held views on ‘good enough is not good enough’. I’d prefer not to offend them.
This a post prompted by frustration. Frustration at the ‘pursuit of perfection’, and how it slows down getting things done.
Just to illustrate, imagine this scenario. You need approval on a business case to start a low value pilot project. People up the chain keep returning the business case and asking for: more data, more detail on the return on investment, greater clarity on risks and absolute certainty on the outcomes and impact. All useful stuff but there has to be a cut-off point where good enough is good enough. The same applies if you a writing up a report. At what point does the effort you put in exceed the impact? Here are a few thoughts about written communication (mainly reports) and what ‘good enough’ means.
Why do reports need to be good enough?
- People need to understand the message. This is the most basic reason for writing the report. If you don’t achieve this you might as well not bother.
- It needs to be accessible so that the reader will engage. By this I mean; layout on the page, use of data/graphics/images, font size/type, sentence length, grammar, spelling etc. There is nothing like densely packed monolithic blocks of badly written text to switch off lots of people.
There are many variations of what could be done. I’d argue that the shorter and more straightforward something is, the easier it is for people to understand and quicker to implement.
Why do people pursue perfection? (Apologies if this sounds a bit cynical)
- It’s a power game. Messing about with what someone else has written can be a massive ego trip for some people.
- It puts off decision making. People are just covering up their inability to make a decision under the smoke screen of ‘seeking perfection’.
So what do you do about it?
- Massage egos. This is where ‘good enough is good enough’ really has benefits. You know things will be changed by someone, no matter how hard you work on it. Just accept the situation, produce good enough reports and shovel them up the line. At least that keeps things moving and the people making the changes think that they are doing something useful and making a difference.
- Draw a line in the sand. If someone is pursing perfection because they cannot make a decision just say, ‘no more amendments’. Easier said than done, but you might have to back this up with some numbers like how you have exceeded the cost benefit ratio through excessive administration costs (they like that sort of stuff). Better still say you will accept the blame for anything that goes wrong.
The world of IT Management describes this concept as The Principle of Good Enough (POGE). This article by Scott W. Ambler talks about the idea of Just Barely Good Enough in the context of agile project management. The graph he uses is a development of the Law of Diminishing Returns, something which is well worth reviewing if you’re stuck in a ‘pursuit of perfection loop’. The article does point out the there is no simple mechanical method of knowing when something is good enough. Good enough will be dependent upon; the situation, it will change with time and it is achieved sooner than you think. At the end of the day it’s a judgement call.
The important thing to remember is that ‘good enough’ does not represent low quality.
The graphic below is useful if you are locked into a ‘perfection loop’. Borrowed from an interesting read by Scott W. Ambler Associates http://www.agilemodeling.com/essays/barelyGoodEnough.html
So what’s the PONT?
- Pursuit of perfection can be a behaviour that creates delay by putting off having to make a decision.
- The good enough approach needs to reflect the situation and can change with time.
- Accept that some people like to change reports. Produce something that is ‘good enough’ and move it up the line to get closer to action.
Finally a quote from General George Patton: “A good solution applied with vigour now is better than a perfect solution applied ten minutes later”