Solving Problems

Solutions to problems almost never are obvious.  The reasons for this are many–there could be fatal flaws in the implemented solution, the environment has changed, or there has been a technology shift for example.  Additionally, people always cause huge variability where the system is dependent on human performance for success.  Similarly there is never one answer to a problem–solutions can incrementally improve to a reasonable level (lean methodologies) or a brand new approach (new computer or technology architecture) could solve the problem immediately.  Choices often depend on urgency, cost, or available resources.   It is the team’s or manager’s role to select the optimal approach for that moment in time and see it through.

It remains critical to frame the problem well enough to find a reasonable solution that positively impacts your business situation.  I would suggest it is important to understand the overall system the problem is within in order to not make the problem worse or have unintended consequences.  It is key to dig down into as many layers of “why” as possible to get to the root of a problem.  I have also found that the person doing the actual work likely has the best description of what is the problem AND would give the best feedback on proposed solutions.  Once you think you know what the root issue is, I believe it important to test it against the problem and collect data to validate your theory, often you will find additional data points that will impact your thinking.  Resist the urge to blame an associate but focus on the process or equipment, it is very rare in my experience that anyone comes to work to intentionally sabotage their work.

Dig deep!!