When a catastrophic issue arises on your project, the immediate push is to get in there and fix it as soon as possible.
How can we patch?
How can we get to the bottom of it?
How can we make it work better?
We do this, without fully understanding the extent or impact to the problem as a whole. We do this without possible fully understanding all the issues at large but wanting to do something, to show progress and make it look like we have resolved the issue.
The better strategy is to take a step back and look at the problem from all the angles, understand what’s happening and where it’s hurting us. This doesn’t mean you go from days to months, it does mean, you take those steps to ensure you understand what is happening before jumping to conclusions.
When done wrong, the rush to fix can sometimes lead to the creation of a new problem.
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.