Why Does a Tiny Problem Need Three People to Pass It Along?
- No.
- 038
- Date
- Read
- 4 min
- Words
- 708
This afternoon, a client's equipment had a small problem. The person on the front line at the hospital messaged me first and described what was happening. After reading it, I already knew what the problem was. I talked the person on site through a few fixes, and it took less than five minutes to solve. While I was handling it, I got messages from two more groups of people, one after the other: the distributor and the manufacturer's sales rep. Honestly, I hate this kind of thing. A tiny problem needs three people to pass it along. If they'd shown up a little later, I'd have solved it already. The thing is, this kind of drama is all too common in my job. Really, the event itself should only involve two parties: the hospital's front line with the technical problem, and me, providing technical support. So what do the other people do when they get involved? They create the effect of looking very busy without knowing what they're busy with. Maybe calling me shows how much they care about the problem. But beyond that, then what? They care a lot about the problem, and then what? A call like that does nothing to help solve it. It's a completely meaningless step in the workflow. Precisely because I've seen so much of this pointless busyness, I can't stand redundant processes at work. When I hit a problem I can't solve, I've always believed in going straight to the person who can solve it. To that end, I've used a mind map to lay out clearly what everyone in the company, big and small, can do and how they can help me. That way, when I hit a problem I can't solve, I can go straight to the person who can quickly give me a way forward. My boss thinks I'm very good at solving problems. But what's the truth? On pure technical depth, I may not be much better than anyone else. My core strength is "technical triage." When I hit a brand-new problem, I can tell what kind it is faster than others. And when I can't handle it, I can instantly search my mind for who holds the key to it. I'm a pretty capable engineer, but there's one kind of problem at work that no matter how good my skills or how wide my network, I can never fully root out on site. That is: systemic problems passed down "sick" from the second line to the front line. I once wrote a whole article about problems passed from the second line to the front line. Looking back, it wasn't very clear, but the underlying logic still holds up. Many problems are passed from the second line to the front line. By second line I mean, among other things, product research, R&D, manufacturing, and sales. If any of these stages has a problem that isn't solved at that first stage, it's guaranteed to show up for real on the front line. And as someone who works on the front line, I'm bound to run into countless problems passed down because the second line didn't handle them properly. The most typical are problems from the R&D stage. If a product is rushed through R&D and the testing isn't thorough enough, then once the equipment hits the market and goes through long-term real-world use, a lot of problems show up that should have been caught in R&D and testing. In this vicious cycle, where front-line problems have to feed back into the second line, the ones who suffer most are front-line engineers like me. And in this cycle, the engineer actually becomes the key figure. The problem shows up on the front line, and the person handling it is on the front line too. If front-line problems are going to feed back into the second line, then how accurately the engineer diagnoses the problem is crucial. If the engineer's diagnosis is off, the feedback is very likely to point in the wrong direction, and the R&D team ends up going in circles. That's right. In this vicious cycle, what drives the equipment forward is no longer the R&D staff. It's the countless engineers running around on the front line.