Surprise – Your Customer Just Fired You!
Our New Product Development team was following what seemed like the best-practice formula for success. They held several weekly engineer-to-engineer meetings and monthly management meetings with the customer, and regular internal management reviews to monitor progress. It was quite a shock when the customer fired us shortly before the product was supposed to launch - after 2 years of development effort and investment!
The product was custom and complex. Numerous engineering changes were made over the first 12-months to improve the design and better align with evolving customer needs. All changes were discussed frequently with the customer engineers, including ballpark estimates of the cost impacts of those changes. The customer engineers advised us to wait until all the changes were settled before issuing an updated quotation. Following that advice was a huge mistake!
Nearly 24 months after project kick-off, and innumerable requirement changes and optimizations later, the specification and design were frozen. It was time to quote the updated product (at its corresponding new, higher price, resulting from all the additional features the customer’s engineers had asked for along the way) formally to the customer’s Purchasing Management. Customer Purchasing Management felt blindsided by the new price and immediately canceled the project! We had assumed all along that our engineering counterparts were communicating within their own organization. They were not.
Analysis after the fact showed that despite direct contact with customer engineers and mid-level management, engagement with the right top-level contact people (the ones who make the budget/spending decisions) had not happened. The pricing surprise resulted in a loss of confidence in our team by the customer’s senior management team. There’s no such thing as “The Customer”. Each customer is made up of a variety of constituencies, each with their own motivations, goals, and metrics. It is your responsibility to keep all the relevant players in the loop.
Several lessons can be drawn from this expensive, unpleasant experience:
1. Make your own efforts to over-communicate to customers at all levels.
2. Do not assume the customer communicates internally across departments or between levels.
3. Set up a regular, formal way to quote the impact of any engineering changes to the customer.
4. Ask for written confirmation of product and process changes.
5. Maintain a change log document jointly used by both parties.
If you want your message to land, it's essential to select the correct mode of communication. What's the correct mode? It depends.
Juran realized that all defects can be classified as "operator-controllable" or “management-controllable". Management (and engineering) plays an absolutely essential in quality outcomes.
Networking and communication build and sustain the relationships that make business work. Avoid these bad habits immediately or people will dislike you immediately.
Mastering these 5 missing skills quickly maximizes your productivity and influence, which in turn enhances both job security and advancement potential.
I explained the goal in designing any component. Overly tight specifications would make it harder to find suppliers and would drive up costs. The engineer's entire approach changed.
Preparing for a presentation is vital in enabling team members to convey critical points, and influence outcomes with customers. Here are the steps involved.
When customer tensions rise, the right approach can turn friction into collaboration. At CAEDENCE, we call it the 3C’s: Calm, Clarify, Control. Here's more detail.
Will AI Replace Direct Customer Communication? Absolutely Not! In an age of chatbots and algorithms, the highest-impact discussions still happen person-to-person.
B2B customer relationships are not a breeze. We’ve navigated hundreds of challenging accounts and distilled five secrets that consistently turn friction into forward progress.
Ever notice how a quick fix from the top can feel like a shortcut, but it ends up stunting your team’s growth? When managers rush to answers, they inadvertently affect team development.
