Getting Your Hands Dirty

How do you really, really know a problem? You get your hands dirty at it.

Steve Blank talks about the origins of his success, and strangely enough, they involve doing physical things and encountering the problems he would later help overcome through the engineering:

When I got to my first airbase my job was lugging electronics boxes on and off fighter planes under the broiling hot Thailand sun, to bring them into the technicians inside the air-conditioned shop, to troubleshoot and fix. The thing we dreaded hearing from the techs was, “this box checks out fine, it must be a wiring problem.” Which meant going back to the aircraft trying to find a bent pin in a connector or short in a cable or a bad antenna. It meant crawling over, under and inside an airplane fuselage the temperature of an oven. Depending on the type of aircraft (F-4’s, F-105’s or A-7’s – the worst) it could take hours or days to figure out where the problem was.

A few months later, I was now the guy in the air-conditioned shop telling my friends on the flight-line, “the box was fine, must be a cable.” Having just been on the other side I understood the amount of work that phrase meant. It took a few weeks of these interactions, but it dawned on me there was a gap between the repair manuals describing how to fix the electronics and the aircraft manuals telling you the pin-outs of the cables – there were no tools to simplify finding broken cables on the flightline. Now with a bit more understanding of the system problem, it didn’t take much thinking to look at the aircraft wiring diagrams and make up a series of dummy connectors with test points to simplify the troubleshooting process. I gave them to my friends, and while the job of finding busted aircraft cabling was still unpleasant it was measurably shorter.

My next career lesson: unless I had been doing the miserable, hot and frustrating job on the flightline, I would never have known this was a valuable problem to solve.

Not all of us can be fortunate enough to have done the work that the people using our applications do with our applications, but it’s important to step outside the IT bubble mindset and recognize, as best we can, what they’re trying to do outside the context of our software to best provide them software to do that job.

Here’s a little ode to those guys out in the field to make up for my lack of a QA Music post yesterday:

Comments are closed.

wordpress visitors