The power of iterations

Problem? Solution. What is between the two? Thinking.

There is a problem. I think it through. I provide a solution.

That sounds easy, but let’s bring in more complications.

If there is a problem, I will evaluate what kind of problem that is. How much impact can the solution have? How important it is to solve it the best possible way?

Do I have enough competence to solve this problem? What will my solution look like if I am not an expert? And the solution — how do I know if it is the best solution? What is best? Fast enough? Good enough?

What if these decisions take place in a fast-pace environment? Speed is of the essence, of course, but what can I do to make it good enough?

Can I make corrections along the way? As the solution is implemented there might be feedback of the shortcomings and then I could have more iterations, and come up with better and better solutions. I initially didn’t know or understand all the nuances of the problem, but now I have a better view. How far did we get?

The power lies in recognising what is the dynamics between the problem and solution, and also the context. There are occasions when it is not just necessary but you must focus for a lengthier amount of time on the best possible solution within a given timeframe. There are other times when it is rewarding to be quick and test your solution. And yet there are other problems for which quickly pulling in an expert and making a decision is more worthwhile than you deciding.

Ultimately, everything is a return on investment. Time and effort are costs, too. Make decisions accordingly a priori to making decisions.