How do you satisfy customers during issue resolution?

You satisfy annoyed customers with the Visual 8D™ / Visual CAPA™.
Negative customer experiences can destroy your business! Have you been faced with any angry customers this year? If so, read on.
THE PAIN: I recall thinking during one particular unresolved quality issue: “Not again! 10AM, time to get screamed at by the customer.” My team's daily update calls were a total disaster.
THE CAUSE: Our team was just reacting to random customer questions. Meeting agendas were unclear. The customer didn't understand our action plan. The customer began driving the action, not us. We'd lost control of the issue response!
THE VISION: If only we had been able to take charge, showing curated agendas, communicating not just action lists but visual diagrams to clarify our plans and demonstrate the evidence of our progress. We needed a better way!
THE SOLUTION: CAEDENCE's Visual 8D™ / Visual CAPA™ enhanced problem-solving toolkit was the answer. It integrated seamlessly with our existing problem-solving approach and systems. The customer loved it! Without any extra effort, my team was instantly creating work products the customer could understand and an update storyline they could have confidence in.
It's not your customer's bad attitude, it's how you're communicating your approach to issue resolution.
Over the years we’ve been exposed to Six Sigma, Juran, Deming PDCA, 8D, Dale Carnegie, A3, Shainin, and more. Each technique works pretty well, and has been demonstrated many times in a wide variety of industries and circumstances. At the core they are all essentially the same!
Each approach relies on an underlying logical flow that goes like this: [a] make sure the problem is clearly defined; [b] be open to all sources of information; [c] vet the information for relevance and accuracy; [d] use the process of elimination to narrow down all possible causes to the most likely few; [e] prove which of the suspects is really the cause of the issue; [f] generate a number of potential solutions; [g] evaluate the effectiveness, feasibility and risk of the potential solutions; [h] implement the winning solution(s); and [i] take steps to make sure your solution(s) don’t unravel in the future.
The differences between the paradigms resides in supplementary steps and toolkits. For example, 8D contains the important “In
Your primary role as a manager is to ensure your team’s success. Internalize this. Make sure your team members know this. Build an environment of trust and collaboration. A direct report of mine would frequently leave me out of the loop as problems escalated, preferring instead to “work harder”. It was clear that he felt uncomfortable delivering bad news to me (his boss) when things were not going according to plan. Let me tell you the rest of the story.
I was struggling to get updates from my regional project management directors. Sensing my frustration at having to constantly repeat my (apparently futile) requests to the team to provide their updates consistently, my boss suggested, “If you want something done, schedule it.” He meant that if updates are needed at a specific time, actually schedule them directly on people's calendars, making the expectation and reminder "automatic" each month, and emphasizing the importance of the updates by turning them into meetings – people tend not to show up empty handed to meetings where they're expected to present. Scheduling removed a bit of "friction" and created a sense of urgency that resulted in real progress. Amazingly, they didn’t miss any updates after that point!
