Achieving Wow! in Your Business
One of the best examples of a stellar company culture I ever saw was a team that implemented Tom Peters’ “Wow!” workplace. Rather than prescribing detailed goals from a high level, the business leader set the expectation that our objective was to Wow! our customer, empowering the team to establish its own detailed goals to this end. We had monthly team meetings of not just business staff, but everyone associated with the product – engineering, quality, procurement, production operators, administrative assistants – everyone came to understand how their contribution was impacting the product, the business, and customer satisfaction.
One day our toughest customer was coming to visit. After some discussions in the conference room, they were to tour the production line. At most plants, such tours are carefully curated by engineering staff, answering questions and carefully steering the visitors away from the (…ahem…) less polished areas. When our meetings were concluded and the production line tour was to begin, we handed the customer team off to our lead production operator and told them we’d meet up for coffee when they were finished.
They were shocked; after all, this was unprecedented. Later, they told us it was the most impressive line tour they had ever been on. They were amazed that nothing was off-limits, and especially impressed that the production operators truly understood how their actions impacted on the quality of the product, and how that would affect the end consumer. The amount of customer trust and confidence built on that visit was immeasurable. “Wow!” indeed.
CÆDENCE has the know-how and drive to help you Wow! your customers. https://www.linkedin.com/company/caedenceconsulting/
If you’d prefer to figure it out from scratch on your own, we highly recommend the classic:
The Pursuit of Wow! Every Person's Guide to Topsy-Turvy Times by Tom Peters, 1994.
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.
