In a previous blog I talked about asset-based thinking, here’s another example.
Most of us at some time have found ourselves in the position where something we are working on isn’t going right – we can’t seem to find the right answer, one little snag is holding up the whole project, we can’t get things to be as good as we want them to be. When this happens it’s quite common to feel frustrated with ourselves and to have negative thoughts such as ‘I’m not going to be able to do this’ or ‘I’m not good enough’.
Asset-based thinking encourages us to focus on what we have got and what we can do, rather than what we haven’t got and can’t do. So, when you’re struggling to get a piece of work to a state that you’re happy with you might remember that ‘at least you know it’s not good enough!’ This might seem an insignificant and obvious thought, but just think of the opposite – without this thought you might believe that what you’ve managed to do so far is ‘good enough’, and as a consequence you’ll turn in a second rate piece of work.
Would you rather be the person who struggles to produce something really good/efficient/fast/beautiful/meaningful, or would you prefer to be the one who goes home thinking that they’ve done a good job when actually they’ve produced something second rate?
A great thing to say to yourself is ‘it’s not good enough YET’.
When you know it’s not good enough there’s a much better chance or producing something that’s really amazing.
And, knowing when something IS good enough is important too. It’s important to know when something is good enough to be fit for purpose, or as good as it can or needs to be given the constraints of time, budget or specification. This is good time and project management, and it stops the stress and over-work of perfectionism (the fruitless or unnecessary striving for a state that cannot or need not be reached).