Drive: The Peopleware of this Generation?

imageThe 70’s and 80’s had The Mythical Man-Month. The 90’s had Peopleware. These works helped software managers understand and communicate to non-software people the dynamics involved in effectively managing software teams. The management models that got cars and TVs built at ever cheaper costs didn’t work on software projects. Brooks, Lister, and DeMarco helped thoughtful software managers figure out how to best manage professionals who must bring a challenging combination of creativity and technical rigor to their work.   

In Drive: The Surprising Truth About What Motivates Us, Dan Pink provides the same kind or resource for a more general audience. He argues that the models for understanding human motivation that worked in the past are outdated and don’t apply to today’s knowledge workers.

Pink contrasts internal and external motivation. Our internal motivation is driven by three needs: autonomy, mastery, and purpose.

Autonomy: We need more than “buy in” or even independence. We crave true self-direction.  To provide meaningful autonomy to our teams, we need to give our people choice over:

  • Task – What they do
  • Time – When they do it
  • Team – Who they do it with
  • Technique – How they do it

Mastery: We are driven to grow, improve, and be increasingly capable of solving more and more complex problems.

  • Mastery is a mindset: It requires the capacity to see your abilities not as finite, but as infinitely improvable. Internally motivated people tend to have an incremental theory of intelligence, prize learning goals over performance goals, and welcome effort as a way to improve at something that matters.
  • Mastery is pain: It demands effort, grit and deliberate practice. The path to mastery – becoming ever better at something you care about – is a difficult process over a long period of time.
  • Mastery is asymptotic: It’s impossible to fully realize, which makes it simultaneously frustrating and alluring.

Purpose: The old models for understanding motivation assumed that we are primarily motivated by money. Today we see money as a necessary but not sufficient reward of our work.  We want to know that what we do makes a difference in the world.

Much of Drive is derivative of the research done in cognitive psychology and behavioral economics, but Pink brings it all together in an engaging and practical way that will allow managers to put these ideas into action. I highly recommend it to anyone who oversees the work of anyone else.

For a small taste of the ideas in the book, check out this presentation.

Who Needs Vision?

image

I admit it—I don’t like Successories, the pretty pictures with inspiring sayings that don the walls of corporate America. In fact, my first purchase to decorate my team’s new space was the poster-sized Demotivator Calendar from despair.com. I (and virtually every good developer I’ve ever met) love these spoofs on the ever-present corporate décor.

You might think I enjoy mocking Successories because I believe the words they portray like Values, Vision, and Mission are meaningless corporate-speak meant to manipulate shallow-thinking cubical jockeys. If that is what you conclude from a “demotivator” on my wall, you would be dead-wrong. image

I despise Successories for just the opposite reason. I believe the concepts these pretty posters are meant to inspire employees with are vitally important–way too important to trivialize with a one-size-fits-all platitude and poster.

Over the years, I’ve seen so many leaders (in both the social and commercial sectors) that struggle with communicating concepts like values, vision, mission, and strategy. So, it’s no wonder that so many people have completely written off the words themselves. They now associate a word like vision with the vapid trivialization that is the meaningless poster. This is tragic.

What to Do About It

I have found that the confusion starts when we fail to define our terms. How does mission differ from vision, and is either really any different from strategy? What do we mean by values? If we cannot define the terms, we cannot think clearly about them, and we certainly cannot communicate them to our teams. We’re left simply resorting to something like “We are a company with an obligation to shareholders to make money. Bottom line: we need to make money.” While this is completely true, our people hear this as “We do anything for money.” We have some unpleasant names for people with this mission statement. No one wants to sign up for that. We must do better.

Defining Terms

Let’s start with some definitions…

Values articulate the core things we care about. Our values inspire our vision.

Vision is our picture of how the world could and should be. Our vision defines the end we strive for.

Mission is what we do every day. Mission is executable and it doesn’t change lightly.

Strategy lays out a plan for executing on our mission.

Goals are surfaced by our strategy.

Objectives are framed by our goals.

Tactics are driven by our objectives and determine how we spend our time and energy.

I see these concepts as layers of foundation, each one flowing from and building off of the lower layers. The lower layers are more abstract, simple, and unchanging. The upper layers are more concrete, detailed, and subject to changing circumstances.

Vision

Values

I believe much of our values are universal. We all have a drive to leave our mark on the world, to give more than we take, and to be competent. Software people add to this a strong desire to create. We find it deeply satisfying to solve real problems with elegant models formed in our imaginations and elegantly crafted in code. I am sure it is the same rush a painter gets as he translates the scene in his mind onto canvas to the delight of his audience. He comes to love the smell of paint the same way we come to love the sight of clean code.

Vision

Vision is seeing what isn’t, but could be. Vision isn’t about what we do, it’s about how we want things to to be. Vision creates an anticipation of a better future. That anticipation motivates. It overcomes the apprehension that comes with change and drives us out of our comfort zone.

SmallerEinstein

Having, believing, and communicating a compelling vision for my team is the most important thing I do as a leader. Everything else flows from it.

Lewis Carrol’s famous “If you don’t know where you are going, any road will get you there.” has become cliché, but only because it expresses “common sense” that we often miss.

My team creates solutions for service businesses with field workers, like HVAC install and repair, plumbing, pest control, cleaning services, and others. The work these companies do is critical to the quality of life we all enjoy. We believe the tools these people currently have to run these businesses could be so much better. We burn untold gallons of fossil fuels routing drivers inefficiently. So many hours are wasted annually because, not only are we scheduling, but the entire process is unpredictable.

Our vision is of a transformed service industry—quicker response times, tighter scheduling windows, more customers served, and less fuel consumed. In order for us to accomplish this, our solutions must be highly scalable and allow for high levels of developer productivity.

Mission

If values and vision answer the why question, mission answers the what question. My team’s mission is to deliver software solutions that bring about the transformation of field service business we envision. We can only accomplish this mission if we have simple yet scalable architectures and clean code.

Strategy

If vision answers why and mission answers what, then strategy answers how. My team is executing on its mission through several high-level strategies.

  • We use iterative development cycles and the other agile techniques to ensure that we are always working on the highest value features for our market.
  • We are building a distributed system of event-driven services that each follow the Single Responsibility Principle so we can scale the application as well as the development team(s).
  • We are always striving to improve our skill in writing clean code.
  • We follow test-driven development to keep our designs clean and our code reliable.

Goals, objectives, and tactics each successively further flesh out the details of how we plan to make our vision a reality. Maybe more on those in another article.

Conclusion

image

Putting Successories on the wall is a substitute for vision like a Lunchables is a substitute for a fine steak dinner.

image

Peopleware: An Aging Classic

Peopleware: Productive Projects and TeamsSome months ago I was telling a friend at work how everyone in the software industry should read Peopleware by Tom DeMarco and Timothy Lister

I have always said that Peopleware should be required reading for anyone who manages software developers. I’ve also said that if you want to know my philosophy as a manager, just read Peopleware.

However, the first edition was written in 1987 and the second edition, which I had read, was written in 1999. I decided to read it again. I was curious to see how it holds up more than ten years later.

On second read, it is clear that Peopleware was written prior to the agile wave in software development. However, Peopleware was such a prescient work that in 2011 I still found it to be insightful and compelling. Much of what they call for has become more commonplace since 1999.

As DeMarko and Lister railed against public address systems in the office, I felt like I had taken a trip back in time. However, the principle that management too often optimizes the wrong factors in the workplace is as relevant as ever. I’ve seen too many situations where more care was put into color schemes and aesthetics than the mechanics of how the software team would work together (acoustics, workstation configuration, etc.).

The insights and anecdotes on management of software people made the second reading worth the investment. The chapters on building a high performing, jelled team were especially valuable.

Bottom line… I still believe that everyone in software should read Peopleware and that managers must read it.