Tag Archives: work

State of Mind of the Group

1 Reply

“It’s the difference between work and non-work,” I said. “Both work and non-work are states of mind. Non-work is an unconscious state of mind. Work is a conscious state of mind. Non-work just happens on its own with no particular direction. Work only happens when there is a purpose.”

Nathan and I had been discussing a simple start to a meeting where he asked each team member to contribute a piece of good news to start the meeting.

“So, I am connecting this exercise at the beginning of the meeting with a state of mind?” Nathan asked.

“Absolutely,” I responded. “Thoughts drive behavior. And if your thoughts connect to a purpose, then you are more likely to engage in work. If your thoughts are not connected to a purpose, then your behavior is likely to be unconscious and non-productive. How you think is everything.”

The First Sea Change

Leave a reply

The first sea change for every organization is the way we organize work. The startup asks this question of every new team member. “What do you do well, where can you help us?”

“I can do this and I can do that.”

“Great, because we have some of this and some of that for you to do.”

We always start off organizing the work around the people. People with special talents get special work, others not so much.

Is there work left over? There is always work left over. It doesn’t take long for the founder to understand we can no longer organize the work around the people. We have to organize the people around the work. And, that is the first sea change for every organization, the emergence of roles.

Humpty Dumpty Sat on a Wall

Leave a reply

All the king’s horses and all the king’s men couldn’t put Humpty together again.

Yesterday, someone asked me, as we move from shelter-in-place to a re-open of the economy, what should a CEO think about? Of course, there is work to be done, and we will bring people back to do that work, but what should the CEO think about?

  • What does my market environment look like in three months time, one year’s time, two years time? This includes market demand, regulations, capital requirements, availability of labor and technology.
  • What should my company look like in three months time, one year’s time, two years time?
  • What are the internal functions necessary to support my product or service in that market demand?
  • Inside each function, what is the level of decision making and problem solving?
  • What roles do I need to make those decisions and solve those problems?
  • Do I have people on my team who can effectively play those roles?

There are two concepts embedded in these questions.
Necessity
Levels of work (levels of decision making, levels of problem solving)

Necessity
If your company considered the purchase of a $100,000 machine, and it was NOT necessary, would you buy it? That same decision has to be made about the roles inside the company. Now, is an opportunity to examine your organizational design and ask, is this necessary?

Levels of Work
Most CEOs do not think about the work necessary to make the product or provide the service. Understanding the level of decision making and the level of problem solving are specific clues to the talent you need. Now, is an opportunity to examine the levels of work and ask, do I have the people on my team who can effectively make those decisions and solve those problems.

How Culture Touches the Work

1 Reply

Culture is that unwritten set of rules that defines and enforces the required behaviors in the work that we do together. Many things we do are written down and comprise our standard operating procedures. But most things are unwritten. And, when we think of culture, here are some things that are often missed.

  • Who can belong to our team? (Membership)
  • Who has the authority to make decisions, in what situations?
  • How are team members given work assignments?
  • How often are team members given work assignments?
  • Do team members depend on work product from other team members?
  • How do team members hand off work to other team members? (Integration)
  • When a team member completes a work assignment, how does their supervisor know?
  • When a team member completes a work assignment, how do they know what to work on next?
  • Does anyone review or inspect their work?
  • How often is their work reviewed or inspected?
  • Are they permitted to continue on additional work before their current work has been reviewed?
  • Do they work on multiple assignments simultaneously?

The people system is the most important system you work on. This is just the start.

Two Armed Octopus

1 Reply

Chase left our conversation abruptly. Across the plant floor, he had spotted a problem and rushed to make a correction. He was apologetic on his return. “Sorry, but that is why I called you today. I feel like a two armed octopus. There are eight things that need to happen, but I can only work on two problems at a time. Things get out of control about fifteen minutes into the day. And they never stop. At the end of the day, I look at my boss’ list of projects and the important things never seem to get worked on. There is always a crisis.”

“Not really,” I said. “To me, your system is working exactly the way it was designed to work.”

Chase was puzzled. “What do you mean? It’s not working at all.”

“No, it is working exactly the way it is designed to work. The design of your day’s work is to drink coffee for the first fifteen minutes, then run around the floor solving urgent problems. At the end of each day, you check the list to make sure you didn’t do anything important.”

I paused. “Not a bad design. How’s that working for you?” Chase didn’t like what he was hearing.

“If you want to change your day, you have to change your design for the day. I see about four major design changes you might want to consider, but let’s start with just one. Don’t let anyone work during the first fifteen minutes of the day. Instead have a huddle meeting around the boss’ list of important projects. That one design change will be a good start.”

How is your day designed?

Legacy Thinking

2 Replies

The landscape is littered with technology initiatives that died. Some wimpered, some imploded, collecting significant collateral damage.

We know what happened and why it happened. The question – how to create technology initiatives that deliver on the promise?

What got you here, won’t get you there. – Marshall Goldsmith

The solution to a problem will not be found by the same thinking that created the problem in the first place. – Albert Einstein

Many technology initiatives fail in an attempt to preserve existing methods and processes. Adopting a piece of software supplants existing work. Technology changes the decision making and problem solving of humans. Human work changes.

It Was Never About the Schedule

1 Reply

Deana had my curiousity. “The ops manager said he was afraid to show everyone what he was doing. But, now that the cat was out of the bag, he explained. He understood the sandbagging. He said each person on the team, and he called them by name, thought they were being sneaky by adding extra days to the project schedule, when, in fact, sometimes things go wrong and those extra days might be necessary. He called those extra days, buffers.

“He showed us his secret project schedule where he took all the buffers away from each segment of the project and put them at the end. He was afraid that if people saw their buffers disappear, they would get mad at him, so he kept it a secret.

“The schedule still had the buffer days, but they were all at the end. As the project went along, some of the buffer days were needed, so he would move only the necessary buffer days back to the segment. So, if a project segment went long, they still had buffer days.

“When the last segment was completed, there were still eleven unused buffer days. Guess what that meant?” Deana teased.

I just stared. Waiting for her discovery.

“That means the project came in eleven days ahead of schedule. In all my time here, we never brought a project in ahead of schedule.”

“What was the most important lesson in all this?” I asked.

“You were right in the beginning,” Deana replied. “The issue had nothing to do with the schedule. It was all about the team.”
—
This series has been an illustration of Basic Assumption Mental State, affectionately known as BAMs. The mental state of a group can shift in seconds. Teams can go into BAMs in a heartbeat, moving from Work into Non-work. It takes courage, and some skill to shift back into work mode. BAMs is most clearly defined in the book Experiences in Groups, by Wilfred Bion, brilliantly captured by Pat Murray and now by Eric Coryell in the stories they tell.

Project buffers is a concept illustrated by Eli Goldratt in his book Critical Chain.

Underneath the Secret Schedule

Leave a reply

“What is different about the team, now?” I was curious.

Deana tilted her head back, looking for the answer in the corner of the ceiling. “The team is in learning mode,” she said.

“Are we back to that search for the truth?” I chuckled.

“I believe we are,” Deana smiled back. “Speaking for myself, of course.”

“So, tell me about the project schedule,” I wanted to know. “That’s how this all started. Now that the team is in learning mode, what was up with the project schedule. Was the ops manager the culprit? Did he manipulate the schedule?”

“Funny you ask.” Deana thought lots of things were funny. “It turns out the ops manager did have two schedules. He explained that when the estimates were made about how much time it would take for each segment of the project, everyone on the team sandbagged the schedule. I stopped him right there, and asked him not to use the word everyone. I said, if someone on the team was sandbagging the schedule, he should tell them directly, in the team meeting.”

“And, how did that go over?” I asked.

“Oh, just peachy,” Deana said. “He started laughing, and said okay. He then went one by one around the room and told everyone about their contribution to this bloated schedule. He told Bob that he only needed three days, but put five days on the schedule. He told Joe that he needed six days, but put twelve on the schedule. Around the room he went, each person in turn.”

“And, how did each person respond?”

“Amazing. They all agreed that they sandbagged the schedule, because they didn’t want to be late.”

“Was the team in work mode or non-work mode?”

“Definitely, work mode. Everyone was paying attention, listening, contributing, speaking for themselves. And we were working the problem. We had sandbagging, a published schedule and a secret schedule.”

“So, what was with the secret schedule?” I asked.

How to Move a Team from Non-Work to Work

Leave a reply

“And?” I asked.

“And, the ops manager spoke up,” Deana continued. “He said he was sorry he had been so defensive, and that he had been so secretive about the project schedule.

“It was funny, the ops manager spoke for himself. And, when he spoke for himself, you could see the tension in the room relax. It was still intense, but the team went into problem solving mode.”

“No one rolled their eyes at this point?” I smiled.

“No, it was like something came over the team. Something shifted. In that moment, they stopped avoiding the problem and started solving the problem. They went from non-work mode to work mode. In non-work mode, they were in a trance, unconscious. They were talking in pairs outside the meeting, talking about each other behind our collective backs. There was collusion, a revolt was brewing. Worse, the problem was untouchable.”

“And what was the problem?” I asked.

“It had nothing to do with the schedule,” Deana nodded. “It had to do with the team.”

“And, what made the shift?”

Deana had to think through the chain of events. “Part of it was persistence. I knew the problem was still there, we just couldn’t talk about it. But, I talked about it anyway. And you made me speak only for myself.

“And, when I put the issue back out on the table, the team went right back into panic mode. Bob rolled his eyes. When I told him how it made me feel, that was the shift. The issue was on the table and it was going to stay there. No rolling of the eyes, no sarcastic remark was going to move the issue off the table. Even my manager didn’t dare shut down the discussion. This team was going to dig in and deal with it. That shift took about five seconds. Everything changed.”

“And your manager?”

“Yes, my manager,” Deana smiled again. “My manager was afraid the discussion would blow the team apart. Turns out, it welded the team together.”

Magic and Fairy Dust, Notions and Potions

Leave a reply

From the Ask Tom mailbag –

Question:
The best engineer on our team was recently promoted to VP-Engineering. Don’t get me wrong, he is a great engineer. But something is just not right. Relieved of his engineering duties, he seems to wander around, sticks his nose into a project without any background on its status. Since I was in your workshop last week, now, I understand that a VP (of anything) is an integration role. It is becoming clear that my boss made a mistake. This guy is not an integrator and we miss his contribution on the engineering team.

Response:
I don’t know the background, I don’t know your company and I don’t know what your boss had in mind when he made the promotion. Doesn’t matter. I hear these stories all the time. Here’s the problem.

Few companies take the time and effort to clearly define the role. Most companies promote without clarifying the work. Maybe your engineering team member has the right stuff to be a VP, but until we define the work, we have no clue.

Most hiring managers believe in magic and fairy dust when they make a hiring or promotion decision. Then, they are disappointed when the candidate doesn’t live up to the expectations that were never defined.

There is no magic. There is no fairy dust, just a little managerial elbow grease –

  • What is the purpose of the role? Why does it exist?
  • What are the key areas in the role? Key result areas (KRAs)?
  • In each key area, what are the tasks and activities?
  • In each key area, what is the output, goal, objective?
  • In each key area, what decisions have to be made? What problems have to be solved?
  • In each key area, what is the time span of the goal?
  • In each key area, what is the level of work?

This is the critical thinking that has to be done before you make the hire, before you make the promotion. The answers to these questions will lead you in the right direction. Without this data, there is no way to make a sound hiring or promotion decision.

But, no one wants to do the managerial work. They would rather rely on magic and fairy dust, notions and potions.