Tag Archives: team problem solving

Would You Say It, If It Wasn’t True?

“You described the situation with your team like a rubber band. Your team is stretched, trying to deal with the problem,” I said, “what do you think the problem is?”

“The problem is that we are behind schedule,” Deana stated flatly.

“What if I told you the problem with the team has nothing to do with the schedule?” I proposed.

“What do you mean? That’s the problem, the ops manager is manipulating the schedule so it looks like we are on-time when we are behind.”

“So, you are on the side of the project manager?”

“Yes. I mean, outside the meeting, without the ops manager, everyone on the team talked about it, and the truth is, the ops manager is manipulating the schedule,” Deana insisted.

“The truth?”

“Well, yeah, I wanted to check with other team members, get my facts straight and that’s what everybody thinks. When the project manager brought it up in the meeting, that is exactly the way he said it. He told the ops manager straight to his face, ‘Everyone in here thinks you manipulated the schedule.’ I don’t think he would say that unless it was the truth.”

“There’s that truth word again,” I smiled.

This is the story of a team in the classic struggle of BAMs. BAMs is the mental state of any group that drives its behavior. BAMs is in one of two states, work or non-work.

  • Work Mode vs. Non-Work Mode
  • Rational vs. Irrational
  • Scientific vs. Unscientific
  • Cooperative vs. Collusive
  • Controlled vs. Uncontrolled
  • Conscious vs. Unconscious

Deana’s team has a problem. In a classic move of non-work, the team mis-identifies the problem. The team does not have to deal with the real problem if it can create the appearance of working a different problem. The problem you solve is the problem you name. The team named the wrong problem.

I woke up this morning in a cold sweat. This is not the story of a team (your team). This is the story of a nation. This is the story of a nation in BAMs. Has the nation named the wrong problem?

What’s Not to Talk About

“So, did your team deal with the issue, or did they avoid it and move on?” I repeated.

“Well, thank goodness my manager was there. When the project manager accused the ops manager of manipulating the schedule, no one knew what to say,” Deana replied.

“So, everyone checked out and looked to the senior-most manager in the room. Was the ops manager manipulating the schedule?” I asked.

“You know, no one is really sure. I was talking with one of my team members after the meeting and he thinks it was a big cover-up.”

“So, the situation was never resolved. We don’t know why we were behind schedule. We don’t if the schedule was accurate. We don’t know how to prevent this in the future.”

“What we do know,” Deana thought out loud, “if we are ever behind schedule and try to cover it up, we won’t talk about it in the meeting.”

Working Leadership comes to Austin TX. Ask me and I will send you a one page pdf about the program. Or you can follow this link to find out more.
Here are the dates –

  • Session One – Aug 25, 2017, 1-4:30p
  • Session Two – Sep 1, 2017, 1-4:30p
  • Session Three – Sep 8, 2017, 1-4:30p
  • Session Four – Sep 18, 2017, 1-4:30p
  • Session Five – Sep 22, 2017, 1-4:30p
  • Session Six – Sep 28, 2017, 9a-12p

To register, just ask Tom.

How to Cripple a Team

From the Ask Tom mailbag-

Question:
Faced with a problem to solve, my team never really comes up with anything. Sometimes it seems they just want me to tell them what to do so they don’t have to think. We are really busy, so most times, I give in, tell them the answer and get them back to work. But, at the end of the day, I am exhausted.

Response:
Of course they want you to tell them what to do. If you tell them what to do, then they are not responsible for the solution. Every time you solve a problem that the team should solve, you cripple the team from solving the next problem.

It’s a tough assignment for you to turn down. You get all the glory, you get to strut, you get to be the head Fred, you get to be the go-to guy when there is a problem to solve. It feels good AND it destroys your team.

Most of all, your team likes it that way. They are relieved of the difficult decisions.

This is not just a method called team problem solving, this is a mind-set on the part of the manager. If you want to build a team, give them a problem to solve. As the manager, you may have to help define the problem, facilitate alternate solutions and ask questions related to the best solution, but let the silence do the heavy lifting.

I can always tell a team is stuck when they fail to solve the same problem they had a year ago. I can always tell a team is growing when they trade in the problems from a year ago (now solved) for a new set of problems for tomorrow. -Tom

Not the Manager’s Problem to Solve

“Timing?” Miriam repeated. “I don’t wait for the team to struggle. I don’t wait for the panic when the problem emerges?”

“As soon as you put the problem on the table, the panic will ensue. Let’s say you have three head-strong team members, individually, they are all very competent in their roles. But, whenever they have to work together, the three butt heads, with their own opinions about the direction of the project. In this state, emotions run high, cooperation and support disappears, there is passive agreement in public and aggressive backstabbing in private. As the manager, on this project, you need mutual support and cooperation. What do you do?”

“When I see the misbehavior, I would sit them down, individually, and communicate my expectations. I would explain that I would monitor their behavior and that I would not tolerate disagreement and shouting.” Miriam stopped. “I think you are going to suggest something different.”

“This is not your problem to solve. Understand, you are accountable for the output of this team, but only the team can solve this problem. Your role is to name the problem, put it on the table, in front of everyone, and outlast the panic.” -Tom

Not So Fast, Don’t Solve the Problem, Yet

From the Ask Tom mailbag –

Question:
We are working on team problem solving. We think it’s a good idea, but we are not getting the results that we thought we would get. In fact, sometimes the team comes up with solutions that either don’t work, don’t solve the problem or create more havoc than the original problem. The team is eager and always has suggestions, so it’s not a matter of enthusiasm.

Response:
The problem we name is the problem we solve. So, if the group names the wrong problem (symptom), the underlying cause may never be discovered. I work with groups all the time that are trigger happy to solve the problem without understanding or probing. They believe that what they don’t know is probably irrelevant. They believe the way they understand the problem is accurate. They believe that other people’s perceptions about the problem are wrong. They believe the problem presented is actually the problem, when often it’s not.

Slow this group down, force them through the following steps, when confronted with the problem.

  • Have one, two or three people restate the problem as they heard it.
  • Open up the discussion with this rule, NO recommendations, NO observations, NO stories, ONLY clarifying questions. No exceptions. (This step in the discussion is always the most important. This is where the real work is done.)
  • Only after all clarifying questions are exhausted (you can tell, because clarifying the problem is exhausting), then open the discussion for recommendations, observations and shared stories.
  • Action (or commitment) step. Based on the discussion, what is the most potent action that can be taken to resolve the underlying cause of the problem (issue or opportunity).

Most groups move too fast toward recommendations. Slow them down.

Working Leadership Course – Fort Lauderdale

Aug 6, 2013 kicks off our next Working Leadership Series in Fort Lauderdale Florida. This program contains twelve modules in six classroom sessions. The program instructor will be Tom Foster (that’s me).

If you would like to pre-register for the program, use the Ask Tom link, tell me a little about yourself and we will add you to the pre-registration list.

Schedule (All sessions – 8:30a-noon)
Session 1 – Tue, Aug 6, 2013 – Orientation, Role of the Manager, Time Management
Session 2 – Mon, Aug 12, 2013 – Working Styles, Communication
Session 3 – Mon, Aug 19, 2013 – Positive Reinforcement, Team Problem Solving
Session 4 – Tue, Aug 27, 2013 – Planning, Delegation
Session 5 – Wed, Sep 4, 2013 – Decision Making, Accountability
Session 6 – Mon, Sep 9, 2013 – Effective Meetings, Coaching

Location – All classes will be held at Banyan Air Services in Fort Lauderdale FL in the Sabal Palm Conference Room.
Banyan Air Services
5360 NW 20th Terrace
Ft. Lauderdale, FL 33309

Tuition – $1600 per participant. Vistage member companies receive a $100 discount per participant. This includes all books and participant materials.

Curriculum

Session One
Orientation. During the initial Session, participants will create both a company and a personal framework, setting expectations and direction for this program. Participants, through directed discussion, create the connection between the program course material and their day-to-day management challenges.

Role of the Manager. Introduces the distinction between supervisor and managerial roles. Clarifies the specific goals necessary for effectiveness. This module creates the foundation on which rest of the course material builds. Incorporates source material from Requisite Organization – Elliott Jaques.

Time Management. Introduces the textbook Getting Things Done by David Allen. (Text included as part of the program).

Session Two
Working Styles.
Participants will complete a DISC survey (DISC is an online instrument published by TTI) and report on their own identified strengths and working style.

Communication. The largest challenge, for most managers, centers on issues of communication. This Session will introduce participants to a new level of conversational “reality.” Introduces the text, Fierce Conversations, by Susan Scott, as reference material. (Text included as part of this program.)

Session Three
Positive Reinforcement

This segment reviews the management research of Elliott Jaques and Abraham Maslow regarding “why people work.” Explores the role of positive reinforcement outlined in by Aubrey Daniels – Getting the Best Out of People.

Team Problem Solving.
Expands Fierce Conversations to the group setting. Designed to move a group into “real work,” using a team problem solving model. Demonstrates how to build a team through problem solving.

Session Four
Planning.
This segment introduces a results-oriented planning model, based on David Allen’s Getting Things Done, which participants can quickly use in any situation where planning would be of benefit.

Delegation. Participants are introduced to a specific model of effective delegation. Most managers hold certain mental blocks to delegation that prevents them from using this powerful developmental tool. This delegation model challenges these mental blocks so the entire team, manager included, can benefit from delegation.

Session Five
Decision Making
. This segment introduces three decision models that participants can use to make decisions in specific circumstances. All models can be used in a team setting or for an individual decision.

Accountability Conversation. Introduces a results-oriented method to hold individuals and teams accountable for desired results. This combines concepts of Time Span, QQT Goals and Management Relationships.

Session Six
Effective Meetings.
Moves from theory to the practical application of team dynamics. How to run a more effective meeting.

Coaching. This segment takes the communication models we have previously used and integrates them into a conversation specifically designed for coaching subordinates.

If you would like to pre-register for the program, use the Ask Tom link, tell me a little about yourself and we will add you to the pre-registration list.