Some of you already know that I gave notice at work and I’m moving to Chicago this week. I actually gave conditional notice a couple of months ago. Among other things, I asked to work on different projects.
The roles for technical communicators are pretty set at our company, but other departments do change and restructure quite a bit. I wanted to work on internal and external audience research and content strategy. It was a long shot, but not inconceivable.
My manager asked me, in several different one-on-one meetings, about what I wanted to work on. She took notes, and took those notes to her managers, but nobody ever said anything more about it, beyond my manager apologizing for the delay, and eventually it became clear that my long shot was out of range.
The Gauntlet is Not Just an E-Book
My manager explained that if I were to stay, one of my main focuses would be on mentoring.
What I heard was that I would work on .chms and WebHelps in a Tech Comm department silo until it was too late to break free into the next tax bracket.
This, of course, was an overreaction. But to call the mentoring role a cul-de-sac probably wasn’t an exaggeration, and that was hard to face. It was a skill set I wanted, but it wasn’t the time or the place.
I was intrigued, though, by her insistence on the team’s autonomy, and by my reaction to it. Consequently, it seemed everything I read or heard in the following weeks was related.
I had already seen this RSA white-board animation, actually, of a talk by Dan Pink, in which he says what people want most is autonomy. Okay, but how does that translate into a successful team?
I heard a bit on NPR about Frank Oppenheimer’s hands-off running of the Exploratorium in San Francisco, and the brilliant research that was produced in that environment. I’m having a hard time finding that July 13 story on NPR, but here’s an interview with his biographer. Anyway, I thought, “Well, but maybe you have to have people with the right experience and talent.”
In a nutshell, I picked at my blind spot. I could tell that I had an irrational resistance to something that I was fundamentally misunderstanding. Then I heard a podcast that, when it reminded me of work, made me wonder if I might be pushing the healthy limits of thinking on a work problem. I’ll share it with you anyway.
A Great Department Takes Time, and Manuals Aren’t Babies
One of my favorite radio shows is “This American Life” on Chicago Public Radio. Four months after the 2009 earthquake in Haiti, they did a show about the lagging relief efforts there.
The show outlines the obstacles in a program for helping mango farmers, a history of failed aid efforts in Haiti, and the contrast between a long-running missionary hospital and the Haitian-run clinic to which a doctor from the missionary hospital has transferred.
The doctor could be much more effective, in the short term, at the missionary hospital. The site was equipped for many more procedures than the Haitian-run clinic, and the American staff were trained to run in an efficient manner that was not the case at the Haitian-run clinic.
The trade off was the level of control and paternalism. Until recently, the wife of one of the founding doctors had worn the key to the medicine closet around her neck. One night when she was ill, they’d had to carry her out of her bed to unlock it for an emergency surgery.
The doctor ran the American clinic. At the Haitian clinic, he was one doctor among many. He was not in charge of anything. He had to watch people with injuries–including babies–that were relatively simple to treat suffer inefficient care, travel great distances from facility to facility to get their needs met, and sometimes die as a result.
It was frustrating, but perhaps less so than having the Haitian people resent the help they were receiving. The doctor was rejecting the “benevolent dictatorship” of the missionary hospital, which he saw as a failed model.
“The choice to then go the other extreme; to purposely work hard at not becoming a dictator for the sake of building community means that people are going to suffer, people are going to die. Goods will not be provided; services will not be rendered.”
In our case, no one is likely to die. Deadlines may not be met. Clients may not be impressed. They might be so unimpressed that they never press F1 again. Maybe those things will happen, and if we’re not measuring, we’ll never even know.
It’s a risk I’ll train myself to take.

