MN Executive Coach reveals how to solve system problems
Did you know your business is a series of systems … all linked together?
This troubleshooting process allows you to perform each step in isolation. Oftentimes problems in systems are intermittent, which may trick you into believing that you’ve solved the problem only to have it reappear later.
Requirements:
This process requires you have a system diagram of all component parts or at least a complete understanding of the parts of the overall system and how they integrate together.
You will also need an escalation list of people, teams, departments that are responsible for systems connected to yours.
Process
C – Confirm
I – Isolate
R – Resolve or attempt to resolve
V – Verify resolution has solved the problem
E – Escalate to another if resolution process fails
Confirm – This step asks you to ensure you can recreate the problem consistently. Once you can recreate the problem consistently you can more readily isolate (the next step).
Isolate – This step requires the system diagram. Systems are usually designed in a linear or ‘chain link’ fashion, which means each component is linked to (or dependent upon) 1 or 2 other components before it. This uses the old ‘garbage in-garbage out’ idea – if you’re having trouble with the output of a particular component, look at the components that are connected before that component and also component in question.
One easy way to perform this step is to temporarily replace the component or modify the procedure and then re-confirm the problem (the previous step) disappeared.
In human systems you can ask the person to ‘imagine… for the sake of argument…’ an alternative idea, feeling, response or thought. This allows the person to ‘try on’ or ‘swap out’ one thought, feeling or response for another.
Resolve – Once you are sure you’ve found the root cause, replace the faulty component or procedure. In business systems, this might mean you improve, change or delete the procedure. In human systems ask the person to try a 30 day experiment – where they agree to act as if this new thought, feeling or response is a normal response. The agreement is after 30 days if they don’t like the feedback they get from the new behavior then they can go back to the ‘old’ way of doing things.
Verify – This step is important and overlooked. It’s more than just rebooting the system or declaring the ‘problem is solved’. It includes monitoring for a period of time to ensure the system is stable. If the system is not stable, you may either go back to the Confirm step or Escalate (the next step).
Escalate – Systems operate within systems – which means they have isolated inputs and outputs. Therefore the entire system may be getting an input that needs to be fixed. Computer systems may be getting incorrect data from a database. Human systems may be getting bad information. If the source of the fault is outside of the system, then escalate using the escalation list.
This process is a simple method for continuous business improvement. You easily implement this by teaching it to your team with instructions to place blame on the process, not the people. Teach them to use this method everytime there is an irate customer, a product delay or other business problem.
Here’s a secret, you don’t have to wait until something is broken to use this process and improve things.
Check us out at http://quantumcommonwealth.com for more great ways we can help you grow your business.
Posted by alanhill
Posted by alanhill
Posted by alanhill 
