📚 Book review: Becoming a Technical Leader

Becoming a Technical Leader, by Gerald Weinberg is typical of Gerald’s books – anything but conventional. He presents his ideas with humor and humility, often from his own mistakes, and not from the elevated pedestal of the “expert” speaking down to us. Gerald digs deep into the truths of how people work. There are no easy shortcuts, fast answers, or quick fixes, but rather a process. These are truths that can only come from diligently observing how things work over a long period of time.

As I’m typing up my notes from this book, I thought I would try a different approach and share “installments” of a chapter or two. If you have any thoughts, please feel free to share in this thread.

These notes include mostly quotes that stood out to me. There is obviously much more in the book to consider.

Table of Contents

  • Preface
  • Forward
  • Part One: Definition
    • 1 - What Is Leadership, Anyway?
    • 2 - Models of Leadership Style
    • 3 - A Problem-Solving Style
    • 4 - How Leaders Develop
    • 5 - But I Can’t Because …
  • Part Two: Innovation
    • 6 - The Three Great Obstacles to Innovation
    • 7 - A Tool for Developing Self-Awareness
    • 8 - Developing Idea Power
    • 9 - The Vision
  • Part Three: Motivation
    • 10 - The First Great Obstacle to Motivating Others
    • 11 - The Second Great Obstacle to Motivating Others
    • 12 - The Problem of Helping Others
    • 13 - Learning to be a Motivator
    • 14 - Where Power Comes From
    • 15 - Power, Imperfection, and Congruence
  • Part Four: Organization
    • 16 - Gaining Organizational Power
    • 17 - Effective Organization of Problem-Solving Teams
    • 18 - Obstacles to Effective Organizing
    • 19 - Learning to Be an Organizer
  • Part Five: Transformation
    • 20 - How You Will Be Graded as a Leader
    • 21 - Passing Your Own Leadership Tests
    • 22 - A Personal Plan for Change
    • 23 - Finding Time to Change
    • 24 - Finding Support for Change
  • Epilogue

1 - What is Leadership, Anyway?

  • Preface
    • These leaders were not the pure technicians produced by the engineering and science schools, nor were they the conventional leaders trained in the schools of management. They were a different breed, a hybrid. What they shared was a concern for the quality of ideas. Like the butcher, they wanted everything in their shop to be the best. We called them technical leaders.
  • Forward
    • Fortunately for us, Jerry Weinberg has made unraveling the complexities of technology and management his life’s work, in particular, the curious mixture of the two that occurs in modern organizations. Everything he says touches home. Over and over, I found myself laughing and being embarrassed at the same time.
  • Part One: Definition
    • 1 - What Is Leadership, Anyway?
      • If you are a good leader, Who talks little, They will say, When your work is done, And your aim fulfilled, “We did it ourselves.” – Lao-Tse
      • If you have always felt there was something slightly wrong about one person telling another person what to do, perhaps your experiences were like mine.
      • I have a curious way of dealing with difficult issues. Whenever I want to learn about something, I arrange to teach a course on the subject. After I’ve taught the course enough to learn something, I write a book.
      • Organic models can be contrasted with linear models on several dimensions: the way events are explained, the way a person is defined, the way a relationship is defined, and the attitude toward change.
      • Underlying organic models is the fundamental idea of systems thinking: “It is impossible to change just one thing at a time.” Linear models tend to be most effective in relatively stable situations, but when things start changing, they get us into trouble.
      • Instead of leading people, as in the threat/reward model, organic leadership leads the process. Leading people requires that they relinquish control over their lives. Leading the process is responsive to people, giving them choices and leaving them in control. They are empowered in much the same way a gardener empowers seeds – not by forcing them to grow, but by tapping the power that lies dormant within them.

Congruence

This below section is one I often come back to when trying to improve communication. The idea is to start with what we are feeling or perceiving, instead of trying to fix the other person or accurately label the problem, because what is inside us is the only thing we really know is true. This is really hard for technical people, because we want to just fix the problem. However, until we understand what is going on, we can’t fix anything.


When problem definitions differ, learning is almost impossible. The only way I know to arrive at clear, common definitions is to concentrate on controlling the quality of communication. As always, the only leverage I have is on myself, but quality breeds quality. If my communications are of high quality, I’ll receive high-quality communications—from which I can learn to do even better.

When I’m able to be congruent, then even if the communication is bungled, I’ll have more reliable information to use in learning how to do it better the next time. Suppose I start a difficult interaction with Rod by shouting, “We would be on schedule if it weren’t for your malingering. Why don’t you get your act together?” When Rod shouts back at me, or clams up, I have no way of knowing whether he’s reacting to the form or the content of my message. The interaction doesn’t come out well, but I don’t know whether it’s Rod or me.

Suppose I start the same interaction with the more congruent statement, “I feel angry because we’re not getting the job done on time, and I don’t know why it’s happening. When I look around for reasons, I notice that you’ve been absent six times this month. Do you feel that your absence is contributing to the schedule problem? Or is there something else?”

Rod now has an accurate problem statement to work with. Suppose the reply is “Gee, I didn’t know we were having a schedule problem. Don’t we have until next Friday?” Now you have several opportunities to clear up crossed wires.

But if Rod shouts back, or clams up, then I have a better idea that the problem does lie somewhere within him, not within me or my interaction with him. I could still be wrong—I may not have been as congruent as I thought—but I’m off to a better start.

The Payoff for Being Congruent

As with any communication skill, being congruent is not some-thing you ever learn one-hundred percent. But the payoff is so great, you don’t have to be perfect. Even if one person manages to act once in a congruent manner when the rest of the group is acting in a twisted way, the results can be worth a thousand failures.

Many years ago, when I was teaching at the IBM Systems Research Institute in New York, several faculty members complained about a student who was “trying to get away with something.” Steve, a student from Kansas, had failed to turn in any of his assignments for several weeks, and the outraged faculty members proposed sending him home. Steve wasn’t in any of my classes, so I didn’t get quite so emotional about the situation. When I suggested that perhaps we didn’t under- stand the problem, I was forcefully reminded that all of the students had been carefully selected from among IBM’s elite employees. Steve could certainly do the work, if only he was motivated.

Even so, I argued, sending him home would probably destroy his career, so we should be doubly sure that we understood the circumstances. They reluctantly agreed to allow me to speak with him, but I was to be his last chance. After an hour with him in my office, I felt we were getting nowhere. I thought I started out in a congruent fashion by asking Steve, “What’s going on? Can you explain why you’re not doing the work?” but Steve denied that there was any problem. I noticed, however, that Steve didn’t look like there was no problem. He sat stiffly in his chair, and couldn’t seem to look me in the eye. I began to convince myself that he had something to hide, and that it wasn’t something honorable. I was about to start accusing him of dishonesty when I realized that I was making inferences about what was inside him, rather than making statements about what was inside of me. [I think this is the key …]

So I decided to try restarting the conversation on a more congruent note. “Steve,” I said, “I’m sitting here getting angrier and angrier because I feel I’m trying to help you and you won’t even talk to me about what’s going on. You’re telling me that there’s no problem, but to me it seems that there is a problem. The other faculty members want to throw you out of the Institute and send you home. If that happens, you’ll probably lose your job. To me that sounds like a serious problem, but you say it isn’t. What am I missing that I need to help you?”

At this point, Steve’s appearance changed from stiff avoidance to violent anger. He looked me in the eye and shouted, “Who the hell do you think you are? What makes you think you can help me? You think you’re so big and powerful, but you’re nobody! Nobody!” Then he stopped talking and turned away.

My first—my “natural”—impulse was to shout back at him, but somehow I realized that he was in terrible pain. Even though I didn’t know what the pain was, I overcame my “natural” training, said nothing, and reached out and laid my hand gently on his arm. Suddenly, he started shaking all over, then sobbing and uttering incomprehensible words. I sat there, my hand on his arm, until he recovered himself sufficiently to talk. Then he told me the whole story.

A week before he left for the Institute, Steve’s wife had been diagnosed as having terminal cancer. She wasn’t expected to live more than six months. He naturally decided he would not attend the Institute, but she insisted that he go, arguing that he would hurt his career by refusing this opportunity. After she was gone, he would be the sole support for their three children, so it was doubly important that he do well in his work.

To me, it was easy to see that he had made the wrong decision, but blinded by grief and unable to go against her expressed wishes, Steve went to school in New York. Under the circumstances, the homework assignments looked meaningless, and Steve couldn’t bring himself to do anything but sit in his hotel room and weep. He was afraid to tell anyone, so his teachers assumed the worst.

When Steve attacked me for assuming I could help, he was exactly correct. There was no way in the world I could help his wife recover from cancer, which was a problem infinitely greater than his schoolwork. Had I not resisted my “natural” instinct to attack him when he attacked me whole story might have been an even greater tragedy. I couldn’t help with his wife’s cancer, but I could help him deal with his wife’s cancer in a less destructive way.

Once the circumstances were understood, IBM arranged to send Steve home to Kansas, giving him paid leave to be with his wife in her final days. A year later, he was able to return to the Institute and make a fresh start. You may have to succeed one hundred percent of the time to be perfect, but you don’t have to succeed one hundred percent of the time to be powerful.