Team gets problem.

Team starts working on problem.

Problem becomes much bigger than initially thought.

Team is confused on where to start and begins implementing process upon process to fix problem.

In the middle of fixing problem, team realizes they are stuck and are not sure where to go from here.

As they start to demonstrate the problem being solved, the customer starts to ask for other things to be done “at the same time”.

Progress grinds to a standstill.

What’s happened?

They let the problem take over, they took the issue that was given to them and began working on it as was directed to them. It became such a big problem, it then required a slew of processes to be added in order to solve it.

What could they have done?

Break the problem down into logical components, look at what is needed now and what is needed later.

Keep it simple, achieve the goal and then move on.

Want more? Check out my book Code Your Way Up – available as an eBook or Paperback on Amazon (CAN and US).  I’m also the co-host of the Remotely Prepared podcast.


Write A Comment