How to Identify the Real Team Problem

To identify the real team problem, begin with one important result that is repeatedly late, weak, costly, or difficult to produce. Do not begin with broad labels such as poor communication, low trust, lack of accountability, or weak teamwork.

Reconstruct one recent incident from the original promise to the final outcome. Find the first point where the work stopped moving well. Then ask what people needed to know, decide, say, hand over, support, or finish at that moment—and what made the weak response seem normal or safe.

A useful team diagnosis should name four things:

• The objective being delayed
• The friction preventing movement
• The commitment missing from the team’s way of working
• The proof that would show improvement

The goal is not to discover who is defective. It is to find the pattern the team must change.

For a wider view of team needs and interventions, begin with our complete guide to team building.

The “communication problem” that was not about communication

A company once asked me to conduct a communication workshop.

“Our people don’t speak during meetings,” one manager explained. “They need to become more confident and learn how to express themselves.”

That sounded reasonable. A workshop could teach people how to organize their ideas, listen actively, ask questions, and communicate with confidence.

But before designing the program, I asked what actually happened during their meetings.

The manager became quiet.

A few months earlier, an employee had questioned an aggressive project deadline. A senior leader interrupted him and asked why he was being negative. Another employee raised a customer risk and was told, “Don’t bring us problems. Bring us solutions.”

People had not forgotten those moments.

They knew how to speak. They had decided that speaking was dangerous.

This was not primarily a communication-skills problem. It was a psychological-safety problem reinforced by leadership behavior. A workshop that taught people how to speak more clearly would have treated the visible symptom while protecting the condition that caused it.

Amy Edmondson’s field study of 51 work teams found that psychological safety was associated with learning behaviors such as discussing mistakes, requesting help, and seeking feedback. When those interpersonal risks feel unsafe, useful information stays hidden even when people possess the necessary communication skills. Read Edmondson’s original research on psychological safety and team learning.

The company did need an intervention. But the intervention had to begin with the leaders and the way they responded to uncomfortable information.

A wrong diagnosis can produce a well-delivered solution to the wrong problem.

A symptom is not yet a diagnosis

Leaders often describe team problems using familiar labels:

“Our people lack accountability.”

“Communication is poor.”

“The departments work in silos.”

“They need to trust one another.”

“Nobody takes initiative.”

These statements may point toward something important, but they are not yet precise enough to guide action.

Consider “lack of accountability.” It could mean several different things. Members may not understand the objective. Ownership may never have been assigned. Deadlines may be unrealistic. Employees may be waiting for approval. The manager may repeatedly take back delegated work. A dependable employee may quietly rescue missed commitments, preventing the real pattern from becoming visible.

Each cause requires a different response.

What people usually say	What may actually be happening
“We have a communication problem.”	Information arrives too late, a handover is incomplete, authority is unclear, or people are afraid to raise concerns.
“People are not accountable.”	Ownership was never made visible, expectations differ, follow-up is absent, or rescue work hides missed commitments.
“The departments work in silos.”	Departments are rewarded for competing wins or lack a clear process for coordinating interdependent work.
“There is no trust.”	Commitments are repeatedly missed, leaders respond inconsistently, important information is withheld, or past conflict remains unresolved.
“People resist change.”	The proposed change is unclear, previous initiatives disappeared, people expect another short-lived campaign, or the change creates an unaddressed loss.
“Nobody takes initiative.”	Members lack authority, earlier initiative was punished, priorities are unclear, or every decision is eventually reversed by the manager.
“The team has a bad attitude.”	Employees may be exhausted, confused, unheard, unfairly rewarded, or protecting themselves from another failed initiative.

Do not use the possible causes in this table as new labels. Investigate what happened in your team’s actual work.

The difference between a label and a diagnosis is evidence.

Research supports looking beyond personalities

Ruth Wageman, J. Richard Hackman, and Erin Lehman developed the Team Diagnostic Survey to assess the strengths and weaknesses of work teams. Their study involved 2,474 members from 321 teams across different organizations.

The instrument did not examine only whether members liked one another or had positive attitudes. It examined how well the team was structured, supported, and led, together with its work processes and members’ reactions to the work. Read the Team Diagnostic Survey research.

This matters because leaders frequently begin in the wrong place. They diagnose motivation when the direction is unclear. They diagnose personality conflict when decision authority overlaps. They diagnose weak communication when information has no dependable path through the work.

Eduardo Salas, Dana Sims, and C. Shawn Burke reviewed teamwork research and identified five core components: team leadership, mutual performance monitoring, backup behavior, adaptability, and team orientation. These are supported by shared mental models, mutual trust, and closed-loop communication. Read their “Big Five in Teamwork” research.

These components direct attention toward what people do together. Can members monitor the shared result? Do they help when the work is at risk? Can they adjust when conditions change? Do they understand the situation similarly enough to coordinate? Is communication completed when the receiver can act, or merely when the sender has sent a message?

Michelle Marks, John Mathieu, and Stephen Zaccaro add another important idea: teamwork happens through performance episodes. Teams use different processes while preparing, acting, and managing relationships during the work. Read their framework for team processes.

This gives leaders a practical instruction:

Do not diagnose the team only by asking members how they generally feel. Study a specific episode in which the team attempted to produce an important result.

That is where the pattern becomes visible.

Diagnose the episode, not the reputation

A team may have a reputation for being slow, difficult, passive, or resistant. Reputations combine hundreds of incidents into one judgment. They hide the details leaders need.

Choose one recent incident.

Perhaps a customer order was delayed. A decision remained open for three weeks. A project reached its deadline through overtime and management rescue. Two departments argued over an incomplete handover. A concern was raised privately but not during the meeting.

Reconstruct what happened.

Who made the original promise? What information was available? Who received the work next? What decision was required? Who believed they owned it? When did the first concern appear? What happened when someone asked a question? Which action was delayed? Who eventually rescued the result?

You are not collecting details to build a case against somebody. You are looking for the first moment when the team’s way of working stopped supporting the objective.

The final failure is usually the loudest moment.

The real problem often began earlier.

Step 1: Name the objective being delayed

Begin with the result, not the behavior you dislike.

“Improve communication” does not tell the team what its communication must help accomplish.

“Build trust” does not explain what members must become able to do together.

“Strengthen accountability” does not identify the promise the team keeps failing to fulfill.

Ask:

What must this team produce reliably that it cannot produce reliably today?

A sales and operations team may need to confirm complete customer orders within 24 hours. A leadership team may need to make cross-functional decisions within five working days. A project team may need to report risks early enough to protect the delivery date.

The objective should be important, shared, and observable.

If departments are protecting different objectives, that may already be part of the diagnosis. Sales may be maximizing booked revenue while operations protects production efficiency. Both departments may reach their targets while the customer waits.

Your team-building goals and objectives should name the work result, the behavior that must change, and the evidence the team will watch.

Without a clear objective, every frustration looks equally important.

Step 2: Describe the visible gap using evidence

Once the objective is clear, describe how actual performance differs from it.

Avoid words such as always, never, lazy, careless, toxic, and uncooperative. These words carry judgment but provide little information.

Compare these two statements:

Operations is always slow.

And:

During the past month, seven of twelve customer orders were returned to sales because required specifications or approvals were missing. The average confirmation time was three days instead of 24 hours.

The second description gives the team something it can investigate. It identifies an outcome, a frequency, and a gap.

Useful evidence may include:

• Missed or extended deadlines
• Repeated rework
• Customer complaints
• Decisions reopened after meetings
• Orders returned because information is incomplete
• Unplanned overtime
• Escalations to senior leaders
• Tasks completed through rescue
• Commitments without owners
• Risks reported only when failure is near

Numbers help, but not every problem needs a dashboard. A clear timeline, an email exchange, a meeting decision, or one failed handover can provide enough evidence to begin.

The question is not, “Can we prove everything?”

Ask, “What can we see?”

Step 3: Reconstruct one recent episode

Invite the people involved to rebuild the sequence without immediately explaining or defending their actions.

A simple timeline may look like this:

1. Sales promised Friday delivery.
2. The order was forwarded to operations on Tuesday.
3. Operations noticed two missing specifications.
4. Operations did not return the order or contact the salesperson.
5. Finance had not approved the special price.
6. No person owned confirming that the order was complete.
7. On Thursday, the manager learned that production had not started.
8. The team worked through the weekend to complete the order.

Ask members what they knew at each point, what they believed someone else owned, and what response they expected if they raised the issue.

Different people may remember the episode differently. Do not force agreement too early. The differences themselves can reveal the problem.

Sales may believe the order was accepted because nobody objected. Operations may believe sales knew that incomplete orders could not proceed. Finance may believe special pricing requires a formal request. The manager may believe the team understood that customer commitments must be escalated immediately.

Everyone may have acted logically according to a different version of the process.

That is valuable diagnostic evidence.

Step 4: Find the first meaningful break

Do not begin with the final emergency. Trace the episode backward until you find the earliest moment when the team could have protected the objective but did not.

In the customer-order example, the final delay occurred when production missed Friday’s delivery. But the first meaningful break may have happened when sales made a promise before the order was complete.

Or it may have happened when operations saw the missing specifications and remained silent.

Look for points where:

• A promise was made without necessary input.
• Ownership moved but was not acknowledged.
• Information was sent without confirming understanding.
• A decision was discussed but not assigned.
• Someone noticed a risk but did not raise it.
• A request for help was delayed or ignored.
• A manager reversed an authorized decision.
• A task appeared complete to the sender but was unusable to the receiver.
• The team agreed but did not establish a next move.
• A dependable member rescued the work and hid the original failure.

At Team Bayanihan, we call these points the seams.

The seam is where one contribution must connect to another. Many team failures happen because the connection is assumed rather than designed.

Step 5: Identify the friction at the seam

Friction is the repeated condition or behavior that makes movement difficult.

Do not name the friction as “Person A failed to do the job.” Describe what repeatedly happens where the work connects.

For example:

Orders move to operations without complete customer specifications, and operations waits instead of notifying the salesperson immediately.

That sentence is more useful than “Sales and operations do not communicate.”

Examine four possible sources of friction.

Direction friction

Members are protecting different definitions of success. Priorities compete, trade-offs are unresolved, or the objective remains too vague to guide decisions.

Design friction

Roles overlap, ownership disappears between departments, decision authority is unclear, essential members are excluded, or the workflow requires unnecessary approvals.

Interaction friction

Members withhold information, avoid disagreement, send incomplete handovers, delay requests for help, or assume understanding without confirming it.

Reinforcement friction

Targets, rewards, leader reactions, workload, or organizational practices make the harmful behavior reasonable. The company asks for collaboration but rewards departmental wins. Leaders ask for early warnings but punish the people associated with bad news.

These sources can combine.

Sales may submit incomplete orders because its incentive rewards booked revenue. Operations may remain silent because earlier objections were treated as resistance. Nobody may own checking order completeness because the task falls between two job descriptions.

There may not be one magical root cause. Your goal is to develop a strong working diagnosis of the connected pattern.

Step 6: Find the missing commitment

Once the friction is visible, ask:

What should teammates be able to expect from one another at this point in the work?

The Five Team Commitments provide a practical lens.

When this pattern appears	Examine this commitment
People protect different targets or priorities.	Play the Same Game
People are abandoned, overloaded, or repeatedly rescued.	Back Each Other Up
Information or unfinished work breaks during a handover.	Serve the Next Person
Risks stay hidden or disagreement becomes personal.	Face the Friction
Actions, decisions, and promises remain open.	Finish the Last Mile

These commitments should not be used as slogans or instant answers. They help the team translate its diagnosis into a practical expectation.

For the customer-order problem, Serve the Next Person may produce this commitment:

Before sending an order to operations, sales will complete the five required order details. Operations will acknowledge receipt within two hours and immediately identify anything missing. The salesperson remains responsible for obtaining customer clarification.

If operations members have been afraid to challenge aggressive promises, the team may also need Face the Friction:

When operations sees a delivery risk, the concern will be raised during the order review. The leader will examine the risk before judging the person who raised it.

A useful commitment states what people will do, when they will do it, and who retains ownership.

Step 7: Test the diagnosis through a small practice

Do not treat your first diagnosis as permanent truth.

Treat it as a useful explanation the team can test.

Use the Team Bayanihan movement:

Objective → Friction → Commitment → Practice → Proof

The objective is to confirm complete orders within 24 hours.

The friction is an incomplete and unacknowledged handover.

The commitment defines what sales and operations will provide and confirm.

The practice applies the new handover to the next ten live orders.

The proof may include:

• Percentage of orders complete on first submission
• Number of orders returned for missing information
• Average confirmation time
• Risks raised within two hours
• Emergency escalations and unplanned overtime

If the practice improves the result, the diagnosis was probably useful.

If nothing changes, examine the episode again. Perhaps the real constraint is approval authority, workload, technology, or an incentive that still rewards incomplete orders.

Diagnosis is not a ceremony performed before action. It is a cycle of seeing, testing, learning, and adjusting.

A complete Team Problem Trace

Use this worksheet on one real incident.

Diagnostic question	What to write
1. Objective	What important result must the team produce reliably?
2. Visible gap	What evidence shows that the result is late, weak, costly, or inconsistent?
3. Episode	What happened from the first promise to the final outcome?
4. First break	Where did the work first stop, slow down, or move backward?
5. Friction	What repeated behavior or condition made that break likely?
6. Missing commitment	What should teammates be able to expect at that moment?
7. Practice	Where will the team test the new commitment during real work?
8. Proof	What should become visible if the diagnosis is useful?

Complete this for one problem before discussing ten others.

In Teamwork Everyday, I recommend a simple movement: one problem → one experiment. Leaders do not need to solve everything before they begin. They need to choose a meaningful problem, test a practical shift, and learn from the result.

Three sources of evidence are better than one

A team survey can be useful, but it should not become the entire diagnosis.

Combine three kinds of evidence.

1. Work evidence

Look at deadlines, complaints, rework, decisions, handovers, escalations, customer results, and unfinished commitments.

2. Episode evidence

Observe or reconstruct what members did during a real meeting, decision, project, service failure, or handover.

3. Experience evidence

Ask members what they understood, expected, feared, or believed they were allowed to do.

These three sources prevent an easy mistake.

The records may show that risks are reported late. The episode may reveal that employees notice risks early. Interviews may show that members expect leaders to become defensive when they raise them.

Now you can see that the problem is not the team’s ability to detect risk. The problem is what happens between detecting and reporting it.

When safety is uncertain, gather individual views before the group conversation. Junior members may not contradict the leader while the leader is present. Anonymous input can help, but leaders must eventually create conditions where important truths can be discussed openly.

Five mistakes that create the wrong diagnosis

Mistake 1: Diagnosing personalities

Personality differences influence team dynamics, but personality labels often become shortcuts.

“The introverts do not contribute.”

“The older employees resist change.”

“The new manager is too controlling.”

“The younger employees lack commitment.”

Study what happens instead. Perhaps meetings reward fast speakers. Previous change programs disappeared. The manager lacks reliable information and therefore keeps taking control. Employees are making commitments without enough authority or resources.

A label makes the person the problem. A diagnosis examines the interaction between the person, the task, and the conditions surrounding the work.

Mistake 2: Listening only to the leader

Leaders see important parts of the work, but they do not see everything.

The manager may believe people are refusing to take ownership. Members may believe every decision will eventually be reversed. The manager sees repeated requests for approval. Employees see evidence that acting without approval is unsafe.

Both views matter.

Include the people who send, receive, approve, use, and depend on the work.

Mistake 3: Asking only general questions

“How is our communication?”

“What are our trust issues?”

“Why are people not accountable?”

These questions invite opinions and familiar complaints.

Ask about behavior:

• When did the problem last happen?
• What was the team trying to accomplish?
• Who knew what at that point?
• What decision was required?
• What did people expect would happen?
• Where did ownership become unclear?
• What happened when someone raised the concern?
• Who eventually completed the work?

Specific questions bring people back to evidence.

Mistake 4: Jumping from the symptom to training

Not every team problem is a training problem.

If employees do not know how to conduct a difficult conversation, training can help.

If they know how but expect retaliation, the leader must change the environment.

If a handover repeatedly fails because nobody owns it, the workflow must be clarified.

If workloads are impossible, another session on resilience or accountability may insult the people carrying the burden.

Select the intervention after the diagnosis.

Mistake 5: Trying to fix everything at once

When leaders ask teams to list their problems, the walls quickly fill with notes: communication, trust, motivation, respect, silos, accountability, leadership, engagement, and conflict.

The list may be accurate. It is rarely actionable.

Choose the objective that matters now. Find the pattern most directly preventing it. Replace that pattern with one practical commitment.

Movement creates better information than another hour of naming problems.

A 30-minute team diagnosis conversation

You can begin without a complicated assessment.

First 5 minutes: Name the result

Ask:

What important result are we having difficulty producing reliably?

Write one result that the whole team can see.

Next 10 minutes: Reconstruct one incident

Build the timeline without blame. Ask members what happened, what they knew, and what they believed someone else would do.

Next 5 minutes: Find the first break

Mark the earliest point where the work stopped supporting the objective.

Next 5 minutes: Name the friction

Ask what made that response likely. Look at direction, design, interaction, leadership, and reinforcement.

Final 5 minutes: Choose one experiment

Agree on the commitment the team will test, where it will be practised, and what proof members will review.

Thirty minutes will not explain every team dynamic. It can give the team a useful place to start.

Decide what kind of intervention the diagnosis requires

The diagnosis should help leaders distinguish among different responses.

What the diagnosis reveals	Likely response
Members lack a specific skill.	Training, coaching, guided practice, and feedback
Members need to see and discuss a recurring team pattern.	A facilitated team-building workshop connected to real work
Roles, authority, or workflow are unclear.	Work redesign, role clarification, or decision-process improvement
Targets or rewards encourage conflicting behavior.	Leadership and organizational-system change
The team needs continuing practice and review.	Team-development routines, coaching, and follow-through
People face retaliation, abuse, or serious misconduct.	Protection, investigation, leadership accountability, and appropriate organizational action

Sometimes the answer includes several interventions. A workshop may help members see the broken handover and practise a better one. Leaders may also need to change approval authority and performance measures.

Team building can create the mirror and the first practice. It cannot replace decisions leaders must make about the system.

The next guide explains what team building can—and cannot—fix. Once the problem is clear, you can also use it to design team building around real objectives.

Stop asking what is wrong with the team

That question encourages people to search for defects.

Change the question.

Ask:

Where does our shared work repeatedly stop moving, and what makes that pattern likely?

Begin with the objective. Study one real episode. Find the first break. Name the friction without shaming the people inside it. Decide what teammates must be able to expect from one another. Test that commitment during real work and watch for proof.

You do not need a perfect diagnosis before moving.

You need an honest and testable one.

“Poor communication” may turn out to be an incomplete handover. “Lack of accountability” may be ownership that was never assigned. “Resistance” may be protection from another initiative that leaders will soon abandon. “Low trust” may be the accumulated result of small commitments nobody finishes.

Once the real pattern becomes visible, the team can make a move that matters.

Do not begin by trying to fix the people.

Find the friction. Change the play. Help the team produce proof that it can work differently.

If your organization wants help diagnosing a real team challenge and designing an experience around the shift that matters, explore our facilitated team-building workshops.

Books and research behind this article

• Jef Menguin, Team First: 30 Small Shifts in Mindset, Behavior, and Leadership That Turn Groups Into Great Teams (2025).
• Jef Menguin, Teamwork Everyday (2025).
• Jef Menguin, The Team Experience Playbook (2025).
• Ruth Wageman, J. Richard Hackman, and Erin Lehman, “Team Diagnostic Survey: Development of an Instrument,” The Journal of Applied Behavioral Science (2005).
• Amy C. Edmondson, “Psychological Safety and Learning Behavior in Work Teams,” Administrative Science Quarterly (1999).
• Eduardo Salas, Dana E. Sims, and C. Shawn Burke, “Is There a ‘Big Five’ in Teamwork?,” Small Group Research (2005).
• Michelle A. Marks, John E. Mathieu, and Stephen J. Zaccaro, “A Temporally Based Framework and Taxonomy of Team Processes,” Academy of Management Review (2001).