Home > Articles > Software Development & Management > Agile

  • Print
  • + Share This
This chapter is from the book

Introduce a Metaphor for High Performance

Metaphor is a powerful thing. Professional coaches have known this for a long time. In fact, "metaphor" is a core skill taught in professional coaching courses (Whitworth et al. 2007).

  • "I'm the glue that holds this family together."
  • "I'm the pebble in your shoe, reminding you to tread lightly."
  • "I am a thousand candles lighting the way."
  • "I am a bird soaring above it all."
  • "I am a beacon calling you forth."

Coaches ask questions that help clients create their own metaphor, one that is visceral and resonant. Clients use the metaphor to guide them through the events unfolding in their lives.

If it's keeping one's head above water during a time of rapid and unpredictable change, perhaps the metaphor "I am a bird soaring above it all" serves to help the client stay balanced as waves of change crash all around. Perhaps the client has a calling, something important to share with the world. Maybe then the metaphor "I am a thousand candles lighting the way" helps keep the juiciness of the purpose alive and resonant as it fuels their work.

Teams use metaphors the same way. Through your coaching, a team may create their own metaphor to help guide them through turbulent or exciting times. To get them started and to help them create a vision for high performance, offer images that spark metaphor. One such image features a tree: the High Performance Tree.

The High Performance Tree

The High Performance Tree came into existence when I was coaching several teams that had been together for some time. They were doing fairly well with the basic practices of agile (standard meetings and accomplishing sprint goals), and they were consistently delivering results that mattered, yet their managers knew there was more to get.

As their agile coach, I had no idea how they were going to move toward high performance, and I knew each team would do it their own way no matter what I offered, so creating a highway or even a meandering pathway for them to follow wouldn't work. I had to come up with something evocative that would kindle their desire to pursue high performance on their own terms, something each team could use to come up with their own highway or pathway. Fresh from my own learning about the power of metaphor, I created the High Performance Tree (see Figure 2.1).

Figure 2.1

Figure 2.1 High Performance Tree

Introduce the tree to the team any time. Doing so at the beginning, perhaps in the team start-up, sets them up well, but it also works to introduce the tree as a way to look at a problem or deficiency when one crops up. Once introduced, refer to it as situations arise in the team and use it as material for retrospectives.

To introduce the tree to the team, just draw the tree from the roots up as you teach the meaning of the Scrum values and as you list the characteristics of high performance. You can see from the illustration that you need not be a good artist to do this.

As you write the words for the roots of the tree, teach the Scrum values. Simply stated, they are as follows:

  • Commitment: Be willing to commit to a goal. Scrum provides people all the authority they need to meet their commitments.
  • Focus: Do your job. Focus all your efforts and skills on doing the work that you've committed to doing. Don't worry about anything else.
  • Openness: Scrum keeps everything about a project visible to everyone.
  • Respect: Individuals are shaped by their background and their experiences. It is important to respect the different people who comprise a team.
  • Courage: Have the courage to commit, to act, to be open, and to expect respect (Schwaber and Beedle 2001).

If you don't use Scrum but think these values will serve, remove the references to the word Scrum. (You don't even need to mention that they come from Scrum.) You can also use Extreme Programming values in place of, or in addition to, the Scrum values if your team develops software. The definitions of these values assume Extreme Programming practices occupy the center of the team's software development repertoire:

  • Communication: Keep the right communications flowing by employing many practices that can't be done without communicating. Problems with projects can invariably be traced back to somebody not talking to somebody else about something important.
  • Simplicity: What is the simplest thing that could possibly work? Make a bet that it is better to do a simple thing today and pay a little more tomorrow to change it if necessary than to do a more complicated thing today that may never be used anyway.
  • Feedback: Concrete feedback about the current state of the system is absolutely priceless. Optimism is an occupational hazard of programming. Feedback is the treatment.
  • Courage: Have the courage it takes to develop good software, which may mean throwing away code and changing direction, even late in development. What's to say that you won't ever develop yourself into a corner? Courage (Beck and Andres 2004).

If neither of these sets of values fits and your company has established values that will work well, then use those instead. Here's the key: The values you use must be defined so that they are relatable to agile, easily understandable (not full of abstract notions or business jargon), and resonant. Use only those values that evoke a sense of desire in the team members. You know you have a good set when team members consider the definitions and say, "Yes, I want to be more like that. I want us to be more like that. I want our company to be more like that."

As you continue the drawing, go on spinning a vision for them. If the roots are strong, they nourish the tree, and the tree grows up to the sky—straighter and taller. It sprouts leaves that gather in more and more sunlight. As the leaves gather light, they, in turn, nourish the tree. Everything grows stronger, taller, and greener. The tree has become an inviting place, and the team notices they have sprouted some things themselves—the characteristics of high collaboration and, thus, high performance (adapted from Tabaka 2006):

  • They are self-organizing rather than role- or title-based.
  • They are empowered to make decisions.
  • They truly believe that as a team they can solve any problem.
  • They are committed to team success vs. success at any cost.
  • The team owns its decisions and commitments.
  • Trust, vs. fear or anger, motivates them.
  • They are consensus-driven, with full divergence and then convergence.
  • And they live in a world of constant constructive disagreement.

These characteristics shape the leaves of the tree. If the roots are strong and the leaves gather in enough light, the tree will bear fruit. These are the fruits of high performance.

The first fruits you may notice are these: You get business value faster, and then you get the right business value more often. As the roots (values) and leaves (high performance) continue to grow, the team may even bear the fruit of astonishing results—the kind that causes a business to leapfrog its competition and the kind agile was meant to create. Through these, two other fruits appear: a team that can truly do anything and a team that offers room for team and individual growth. These two fruits are the ones that rejuvenate the whole tree and give back again and again. They fuel sustainable growth.

No matter when you introduce the tree, just having the drawing in the team's work room will be enough. It hangs there, a quiet reminder that high performance is normal and your ardent expectation. As in Figure 2.2, it hangs there when they get into trouble or get into a rut and you point to it and say, "Where are our roots weak?" It hangs there when they are showing all the signs of a high-performing team yet their products reek of mediocrity. You sense they can do better, so you say to them, "What fruits do you want to get now?"

Figure 2.2

Figure 2.2 Use the High Performance Tree to spur the team to take their next step toward high performance.

Using the tree this way, your questions become challenges to them, a way to call them forth to a brighter vision of what they can become together. When they take up the challenge, they create the next step in their journey toward high performance. In so doing, they lay down their own path.

For example, perhaps the team feels disappointed in the quality of their work and, through considering the High Performance Tree, concludes that they aren't truly consensus-driven. They recognize that they tend to jump to the first thing possible rather than hearing lots of ideas from all team members. They think that if they entertained a divergence of ideas before converging on the one to use, the quality of their products would increase. So, they might circle "Consensus-Driven" on the High Performance Tree and write themselves a reminder that doing this well means hearing a lot of ideas first. Getting better at being consensus-driven is this team's next step toward high performance.

A second team has been missing their sprint goals lately. Someone notices the word Commitment drawn as one of the roots of the High Performance Tree and muses aloud, "I wonder if our problem is that we're not really committed to what we say we are going to do." In the conversation that follows, the team discusses how they have been letting extraneous demands on their time and energy take away from their feeling of commitment. They recognize that as soon as they let one distraction in, a bunch more seem to follow until they are doing everything but what they said they would do. So, they make a pact: "From now on, we will help one another push away distractions so we can truly commit and deliver what we said we would. We will put aside our discomfort and challenge each other when we notice someone has become distracted. We will call distractions out for what they are—impediments." They write these words like a banner across the top of their High Performance Tree. Truly committing is this team's next step toward high performance.

As they address their shortcomings and make plans for getting better, encourage them to make their reflections and choices equal portions of lightness and heaviness. They need not be engaged in self-flagellation to prove to you or anyone else that they are in the act of improving. Hold out to them that the work of becoming high performing can be done with humor, curiosity, and appreciation, too.

  • Over-seriousness is a warning sign for mediocrity and bureaucratic thinking. People who are seriously committed to mastery and high performance are secure enough to lighten up.
  • Michael J. Gelb

Approached with amusement or anguish, moving swiftly or sluggishly trundling along, there are no two paths alike, and you cannot even begin to imagine what a team's path might look like in the end. So, it's best that you don't try and, instead, rely on the team to create the path that feels right for them.

You can tell when the tree has taken hold. It's when the team talks about the tree as a metaphor for themselves and their chosen pathway to high performance:

  • "We can grow if we strengthen our roots."
  • "We're a tree; we can bend."
  • "The wind may shake us, but it will not break us."

That's when the power of metaphor shines through and becomes something useful to them, helping them survive turbulent change or reach for that next big goal.

Another Metaphor: Building the Foundation

If the High Performance Tree doesn't grab you, try a different image. Make up your own. It need not be fancy or complicated; straightforward works well, too. Scrum trainer and mentor Tobias Mayer uses the imagery of "building a foundation" in his classes. It's a simple list of five things that make Scrum (and all agile methods) work. He tells people that if you have these five things, then you have everything you need, and the other details will work themselves out (Mayer 2009):

  • Empiricism: Succeed through a rapid progression of failures. Drive by hindsight, not foresight.
  • Self-organization: The people closest to the problem know best how to solve the problem.
  • Collaboration: Foster a "yes, and" mind-set. Re-conceive ideas; do not compromise (Austin and Devin 2003).
  • Prioritization: Focus! Do the next right thing.
  • Rhythm: Breathe, and the rest will follow.

About using these, Mayer says, "I see these five principles as the foundation of emergence, which (metaphorically) is Scrum in flower, blooming. Everything emerges in Scrum: ideas, teams, process, design, architecture, products...."

Introducing the imagery of "building a foundation" to the team creates a rich field for metaphor to surface and for them to generate a vision of their journey toward greatness together. See? You need not even call it high performance if that closes people down. Journey toward greatness works well, too. Perhaps you will hear team members use the imagery you offered to create momentum-producing metaphors for themselves:

  • "Where is our foundation weak?"
  • "Have we crumbled a bit lately?"
  • "If we were to lay a new cornerstone today, what would we chisel on it?"
  • + Share This
  • 🔖 Save To Your Account