Leadership: don’t say it

You may have a very good point.

You may be entirely in the right.

It may be that you’ve understood their (bad) motivation perfectly, that they are wrongheaded, inconsiderate and rude to boot.

It may be that there’s a values-conflict that’s going to take a lot of deep and difficult work to address.

Some of the above is probably true. All of it may be true*… But saying it to them now – saying it how you’d most like to say it, maybe throwing in a few of the things that you’ve been carrying for a while – saying it now, in the heat of the moment, won’t help.

Grit your teeth. Breath deeply. Don’t say it. Instead do the harder work of fixing the deeper issues and slowly, slowly getting the boat moving in the right direction.

 

P.S. Of course, I said it. 

*And of course, it’s just possible that many of them are not true, or that you need kick in the empathy to know how to respond properly

Tom Peters on ‘People Stuff’

I’ve made a start on The Excellence Dividend and really like what Tom Peters has to say, and how he says it. Here he is in his inimitable ALL CAPS style:

WHILE I’VE BEEN ON THE EXCELLENCE DIVIDEND  BOOK TOUR–MOSTLY PODCASTS — I’VE BEEN ASKED OVER AND OVER TO EXPLAIN MY “OBSESSION” WITH THE “PEOPLE STUFF.”

I USUALLY ANSWER, SNIPPILY, “WELL WHAT THE HELL ELSE IS THERE?”

ORGANIZATIONS, NO MATTER HOW MUCH TECHNOLOGY THEY USE, ARE NO MORE AND NO LESS THAN ‘PEOPLE SERVING PEOPLE’.

AND AS A LEADER, YOUR JOB IS: SERVE THE PEOPLE WHO SERVE THE PEOPLE.

(ONE LAST THING: THE PEOPLE WE SERVE ARE OUR EMPLOYEES AND OUR CUSTOMERS AND OUR COMMUNITIES.)

Tom PetersExcellence Dividend Fundamentals Slideshow

Parallel processing: finding the right people

In computers, parallel processing is the processing of program instructions by dividing them among multiple processors with the objective of running a program in less time.

TechTarget

.

Vision of the future

Computer processors haven’t actually got much faster since the early 2000s. The speed of an average computer’s CPU has hovered around 3 billion cycles per second (think about that for a minute) since the Pentium 4 in 2002.

Computers as a whole, though, have got a lot faster. This is in large part because of parallel processing – more processing units doing different jobs in parallel.

CPUs often have six cores where they used to have one. High-end graphics cards – processing high resolution graphics is about the most intensive work most computers do – can have thousands. And you’ll need them to run a 4K computer display (8 million-plus pixels) at 100 frames-per-second: each pixel requires a complicated set of calculations to determine its colour.**

Get with the program

We often call the things our organisations do ‘programs’ too. One way of looking at your team is a system running a set of instructions that together make up your ‘program’. You take your inputs, the system runs, and the combination of all the operations (a successfully operated ‘program’) creates a desired result.

There’s lots that you can do to improve a system like this – simplify or improve the quality of the inputs, write a more efficient set of instructions or script for each operation (having a script at all is a good start), identify and cut out unnecessary steps – and all of these things will make you more productive, and your life easier.

Once you’ve got good scripts, you can hand off parts of the operation to other people, and give yourself more time to focus on the intensive processing – and this will help a lot too, if you do it right.

But you’re a bottleneck. Everything. Still. Comes. Through. You.

The people you really need to find are people with the ability and the will to shoulder an entire area of activity – a whole process – entirely independently.

You decide what needs to happen and leave them with it. Pow. Now you can do something else – something entirely different – at the same time.

You’re parallel processing.

** = with apologies if I’ve completely murdered the technical analogy. A little knowledge is a dangerous thing.

“How do I take these thoroughbreds and turn them into a team?”

Getting a team together? Start building it before you’re even in the room.

Kathy Delaney-Smith is the coach of the Harvard woman’s basketball team… A few years ago she was asked to be the coach of Team USA in the international basketball competition. And what she was going to have was a dozen kids who’d been selected from a hundred who tried out, the very best female basketball players in the United States. And the problem was that they were going to be competing for five starting positions and moreover came from schools that were highly competitive.

So she had this question: “How do I take these thoroughbreds and turn them into a team?” And she was only going to have four days of practice before they went to Turkey to actually do the competition.
And what she did was … she started building the team over a month before people came to Colorado Springs to the training center for their first practice.

She formed diads or triads … of women ahead of time by email and gave them little assignments to do, things like, since the tournament was going to be in Turkey, “What are the best museums in Turkey?” or “How would you teach the Turkish alphabet to someone who didn’t know it?”, and they had to do these things by email before they showed up and then make their presentation of their report when they arrived at Colorado Springs.

And it was amazing, she said, when they arrived they made their presentation to the rest of the team and the team USA staff, and it was all very funny, and they had started to bond as a team even before they started practice, which she said transcended the latent competitiveness that they were arriving with. So there’s all kind of creative things that you can do to try to help this set of people who are really individuals come together and experience themselves as a team.

Richard Hackman on the People and Projects Podcast

Team performance (3): Learning and individual growth

Richard Hackman‘s third lens on teams and team performance looks at what happens to the individuals on the team.

Individual Growth

What happens to the individuals? Did they learn something? Did they grow and develop professionally, or was this a waste of their time or something that frustrated and alienated them?

Richard Hackman

.

Team growth and individual growth are interrelated, but distinct. Team growth is (primarily) related to the team’s ability to work well together as a team, and whether their ability to get the job done is improving, and the improvement is sustainable.

Individual growth is about personal learning and development:

  • Are the members of my team developing their own vision?
  • Are they and exercising and deepening – or possibly redefining – their values?
  • Are they gaining new tools – ideas, skills, understandings – that will serve them and others well, beyond the team?
  • Are they developing significant relationships and resources that will help enrich their lives and the lives of those around them?

How is what you’re doing now going to make their lives better in future? How is the work of your team an act of generosity the teams of the future?

.

I listened to Andy Kaufman interviewing Richard Hackman on the People and Projects Podcast.