When a project goes sideways, we must always diagnose the root cause.
- What happened?
- When did it happen?
- Why did it happen?
- What could have been done to prevent it?
- Who should have acted on the information?
And, there is a legitimate time to troubleshoot…but NOT when everyone is panicking over the problem.
This morning, I was alerted to a missing piece of equipment for one of our mobile campuses. There was only an hour of margin before it was going to impact the Sunday services. When that call comes first thing in the morning, our response should be “I’ve got this” and then start solving the problem. Don’t start diagnosing…start fixing. Rescue the mission and THEN start troubleshooting what went wrong.
After the mission is saved…after the tensions cool down…after we celebrate the rescue…you can begin your diagnosis.
Thanks for listening.