First day after the holiday, Dongchedi stomped and broke 3 Maextro V800 brake pedals.
In less than half a day, public opinion entered a battlefield we know very well. More and more people took magnifying glasses to question the test data; some studied human leg strength and doubted how a normal person could exert 4589N, and some even thought the test was faked.
Battle-hardened Dongchedi quickly released more test videos and also explained the possible causes of 4589N. But whenever this kind of serious safety problem arises, there is always a voice online that, intentionally or not, steers the issue toward technical discussion. Even a problem like this—where the brake pedal bracket breaks during emergency braking—was almost diluted by discussions of the test environment, operating conditions, and so on.
But no matter how many N, if it broke, it broke. We can’t ask car owners, when danger strikes, to first calculate exactly how deep to press the pedal to stop the car.
Repeated “technical” discussions repeatedly argue about whether the problem is valid, yet never move toward solving it. This seemingly rational and neutral technical discussion is exactly the obstacle slowing us down from solving the problem.
The customer’s problem is already burning, but internally people are still analyzing parameters and explaining processes, with no one deciding what to do. You may have experienced this scene too.
Technical discussions without a way out can only provide a meaningless sense of security.
When a problem occurs, we start discussing parameters, standards, and processes. On the surface, we are all conducting objective, neutral, and rational analysis, but in essence we are avoiding the problem itself.
Just like this pedal break: is the problem that the angle of pressing doesn’t conform to Newtonian mechanics? The problem is the pedal broke. If an accident really happened, a whole car of people could be gone.
But why do we always obsess over technical discussion when facing this kind of problem?
Because discussing technology allows us to temporarily avoid making a decision, while solving the problem requires bearing the consequences.
Parameters can continue to be checked, standards and processes can also be explained item by item and repeatedly verified. Everyone can contribute opinions, and if things don’t progress, it can be said that further research is still needed. Once we truly start handling the problem, we must characterize and assign responsibility for the problem, set goals, plans, and resources. Many original work arrangements may have to be overturned or started over.
Imagine a project is delayed, product quality has problems, and public opinion is starting to ferment. In the meeting room, a group of people who have worked overtime until they are disheveled don’t want to burn themselves, but have to take a stance, so one by one they start taking turns chanting sutras. Something like “strengthen quality awareness,” “improve coordination mechanisms”, everyone is demonstrating the depth of their understanding of the problem, but no one is pushing things forward.
Technical discussion makes everything that is standing still look like it is being handled. But in the end the customer still doesn’t know what to do, and there is no clear decision on how to handle it. Everyone is performing “effort.”
“Improve the review process” was shouted out, but no one followed up with “Where did the original process go wrong?” Each department put forward its own analysis, and every sentence they said was correct. But if someone really asks how the customer’s problem should be handled—whether to initiate a recall or compensate—the meeting room immediately falls silent.
Processes can be optimized until the end of time, but “initiate a recall or go with compensation” is something that must be signed and sealed by someone, and the consequences borne. The former costs time; the latter costs people.
Some companies can keep chanting sutras forever, until the project falls apart, and no one is held accountable. For those who still have to face customers, customers won’t waste their lives alongside them. After all, no matter how many sutras are chanted, the problem won’t automatically disappear.
When encountering business problems, every similar technical discussion is losing market and customers. Therefore, to make discussions truly drive problem solving, the easiest place to start is to make every discussion land on a concrete action. Every time you hear an explanation, you must follow up and ask: “So, what should be done next?”
To improve the review process, you should clarify what was missed this time and which step needs to be added. If further evaluation is needed, then determine who evaluates, what the evaluation criteria are, and when the evaluation will be completed. After the evaluation is completed, what decision should be made based on it must also be made clear.
If the handling approach cannot be decided for a long time, then make clear who will decide, and by when at the latest.
Finally, who will accept the results of this action, and by what standard.
Discussions need a way out; actions need results.
If the matter is still not resolved, continue to advance to the next step. Fill in whatever is missing. Don’t use “the process is imperfect” to explain the problem anymore; instead, clarify which step was missed this time and who will fill it next.
Problems can be very complex, but actions must be concrete. Customers won’t pay for technical analysis; they only want to know when the problem they encountered will actually be solved.