MGT2382 Learning Journal – May 18-19, 2026

posted at later date than dates listed in reflection

Groups, Teams, Organic Teams, Team Dynamics, Trust, Norms, and Decision-Making Under Pressure

Category suggestion: MGT2382 Learning Journal / Field Lab: Learning Journals

Phase lens: Phase 3 – rebuild systems, with Phase 0 warning-light implications and Phase 1 implications whenever people are making decisions under pressure.

Source note: This blended entry brings together the May 18 and May 19 team-dynamics drafts into one seamless reflection on groups, teams, task interdependence, team design, norms, trust, cohesion, shared mental models, self-directed teams, remote teams, and decision-making under load.

Reader’s Moment

You have probably seen this happen. A workplace says “team” because the word sounds healthy. It sounds collaborative. It sounds mature. Then the actual conditions underneath the word are a mess: unclear authority, bad information flow, weak trust, too many handoffs, hidden resentment, and reward systems that quietly punish the very cooperation everyone claims to want.

Or maybe you have been told to “be a team player” while the structure around you made real teamwork almost impossible. No clear authority. No shared information. No stable process. No safe way to raise a problem. No time to coordinate. No reward for collaboration. Then, when the work starts to wobble, someone points at the people inside the mess and says, “The team failed.”

That is where this reading lands for me. The team is not the word team. The team is the design, the task, the interdependence, the trust, the norms, the roles, the decision process, and the environment around it. If those pieces do not line up, teamwork can become another tax on already strained people.

A team does not fail in isolation. A team fails inside an environment, inside a structure, inside a set of norms, inside a pattern of communication, and inside a distribution of power. Sometimes individuals make poor choices. That is true. But if the system creates confusion, starves the team of resources, punishes honesty, rewards silence, and then demands performance, the failure is not only personal. It is structural.

That is why this section of the course connects so strongly to Standing on the Ledge. Collapse rarely appears out of nowhere. Often, the warning lights were already flashing in the way people were expected to coordinate, absorb, guess, cover gaps, and call it collaboration.

From Group to Team

The May 18 entry began with the distinction between groups and teams. All teams are groups, but not all groups become teams. A team needs more than proximity, friendliness, a shared location, or a loose connection. It needs some form of interdependence, shared accountability, coordination, and connection to an objective.

The lunch-table example still helps. People who eat together may be an informal group. They may matter deeply to each other. They may provide belonging, stress relief, conversation, and identity. But unless their work requires shared task responsibility, they are not automatically a team in the organizational behaviour sense.

At the same time, I still push back on the word “mandated.” If a textbook says a group lacks a mandated purpose, the next question has to be: mandated by whom? If the organization means formally assigned by management, then fine. But if purpose means a real reason for existing, informal groups can absolutely have purpose. Their purpose may come from shared pressure, shared need, shared identity, shared frustration, shared hope, or a shared need to name what the formal structure keeps missing.

That is where the organic team idea comes in. Sometimes a group begins as a relationship or a pressure point, then becomes coordinated around a shared objective because the work itself has already crossed the boundaries of the official chart. The chart says one thing. The work says another. The organic team forms in the gap.

Organic Teams

I am keeping the phrase “organic team,” but tightening it. An organic team is not just a group of people with a common label. It behaves more like living tissue. Signals move. Pain is noticed. Pressure gets redistributed. Damage is named early. Work is adjusted before the whole organism starts to fail.

In an unhealthy team, the signals get blocked. People see the problem but stay quiet. People know the workload is uneven but normalize it. People sense that expectations are changing but do not know who is allowed to respond. People keep absorbing pressure until the first visible breakdown gets blamed on the person closest to the surface.

That is not organic. That is a bruise pretending to be a structure.

This is why I keep translating team theory through the SOTL frame. A crisis eventually becomes a team problem, even if the team is only two people sitting at a kitchen table trying to decide what bill gets paid first. When the work is interdependent, people need more than motivation. They need a working structure.

Team Environment: The Conditions Outside the Boundary

The reading defines the organizational and team environment as the conditions beyond the team’s direct boundary that influence team effectiveness. In plain language: a team is never just the people in the room. The team is also the workspace, information flow, resources, leadership support, coordination systems, customer feedback, conflict climate, and reward structure around them.

That is a major SOTL point. When a team struggles, the lazy explanation is to blame attitude. The better explanation asks whether the team has what it needs to do the work. Are people rewarded for collaboration or quietly rewarded for individual competition? Is information visible or hidden? Are problems surfaced early or punished? Does the team have authority equal to its responsibility?

Visual management ideas such as an Obeya can be useful here. An Obeya is not magic. It is a shared physical or digital space where the work becomes visible: goals, customer voice, timelines, problems, countermeasures, decisions, and performance information. Used well, it reduces fog. Used badly, it becomes another performance stage where people display confidence while the real risks stay underground.

So the question is not, “Does the team have a board?” The question is whether the board tells the truth.

Task Interdependence: The Myth of the Lone Performer

Task interdependence is the extent to which people must share materials, information, expertise, or outputs to get the work done. Some work can be done independently. Some work depends on shared resources. Some work moves in sequence, where one person’s output becomes another person’s input. Some work is reciprocal, where people must keep adjusting to one another in real time.

The more interdependent the work becomes, the less useful the lone-performer myth becomes.

A lot of workplaces still talk as if performance belongs only to the individual. Who worked hard? Who cared? Who showed up? Who dropped the ball? Those questions may matter, but they are incomplete if the work itself requires coordination.

If one person cannot complete the task without timely information from someone else, then communication is not a soft skill. It is part of the production system. If one shift’s work determines whether the next shift can function, then handoff is not paperwork. It is survival infrastructure. If one department makes promises that another department has to fulfill, then authority, responsibility, and resources had better line up.

Type of interdependence	Plain meaning	SOTL translation
Pooled interdependence	People share common resources but complete most work independently.	The risk is resource conflict, uneven standards, or invisible contribution.
Sequential interdependence	One person’s output becomes another person’s input.	The risk is bottleneck, delay, rework, and blame traveling downstream.
Reciprocal interdependence	Work moves back and forth between people or units.	The risk is coordination overload, misunderstanding, and weak feedback loops.

The higher the interdependence, the more people need to communicate, adjust, and understand each other’s constraints. Reciprocal interdependence especially requires trust and fast feedback because the work keeps moving back and forth. If the structure treats reciprocal work like independent work, people will spend their energy compensating for the design failure.

This is where the weakest-link problem appears. In an interdependent system, one unresolved weakness does not stay local. It becomes a delay, a workaround, a resentment, a quality issue, or a confidence problem somewhere else. The issue may look personal by the time it surfaces, but the root may be structural.

Team Size and Composition: Enough People, Not Just More People

The reading is careful about team size. There is no perfect number that works everywhere. The ideal size depends on the task. A complex problem may require more knowledge, disciplines, and perspectives than one small group can hold. But larger teams also create process losses: more coordination, more social distance, more hiding places for effort, and more time spent managing the team instead of doing the work.

That sounds obvious until you look at real pressure situations. When things are messy, the instinct is often to add more bodies. More people in the room. More people on the email chain. More people in the meeting. More people “looped in.” But a larger group can create more noise if roles are unclear. It can slow decisions. It can give people room to hide. It can create the illusion that someone must be handling the problem because so many people are technically present.

A team should be large enough to contain the expertise required, but small enough that people still know who is doing what, can speak honestly, and can feel their contribution matters. When a team gets too large, accountability gets blurry. When it is too small, the work may overload the few people inside it.

SOTL translation: size is not an administrative detail. It is a pressure setting. Too few people and the system burns out the reliable ones. Too many people and the system creates fog.

Composition matters too. Teams need the right mix of knowledge, skill, judgment, perspective, authority, and temperament for the task. A team can fail not because people are lazy, but because the composition is wrong for the work.

Diversity can improve problem solving, creativity, customer understanding, and decision quality because the team has access to more perspectives and fewer identical blind spots. But diversity does not do its best work automatically. It needs a container. It needs norms. It needs trust. It needs psychological safety. Otherwise, difference can get misread as friction, and friction can get punished before it becomes useful.

The problem is not difference. The problem is a team that has not learned how to hold difference productively.

The Five Behaviours: What Teamwork Actually Looks Like

The chapter presents five broad teamwork behaviours: cooperating, coordinating, communicating, comforting, and conflict resolving. I like this because it keeps teamwork from becoming a vague moral word. It turns teamwork into observable behaviour.

Teamwork behaviour	What it asks of people	When it breaks
Cooperating	Sharing resources, adjusting, accommodating, and helping the work move.	People protect turf, hoard information, or use “not my job” as a shield.
Coordinating	Aligning work, timing, priorities, and handoffs.	Everyone is busy, but the work does not connect.
Communicating	Sharing information efficiently, respectfully, and accurately.	People guess, withhold, over-explain, or use channels that make the problem worse.
Comforting	Supporting psychological well-being and emotional steadiness.	People treat stress signals as weakness or attitude problems.
Conflict resolving	Naming and addressing disagreement before it becomes damage.	The team avoids conflict until it leaks as sarcasm, withdrawal, blame, or sabotage.

The comforting piece stands out. In some workplaces, support is treated like softness. But under load, people do not make better decisions because they are shamed, isolated, or left guessing. They make better decisions when the environment allows them to stay regulated enough to tell the truth and act on it.

Conflict resolving matters too. A team with no visible conflict is not always healthy. Sometimes it is mature. Sometimes it is afraid. Silence is not the same thing as peace.

Team Development: Forming, Storming, Norming, Performing, and Coming Apart

The reading uses the familiar development model: forming, storming, norming, performing, and adjourning. Forming is orientation. People are trying to understand the task, one another, and the rules. Storming is where the real pressure starts showing. Competing expectations surface. Control issues appear. People test boundaries. Some conflict is not a sign that the team is failing. It may be the first honest evidence that the team is becoming real.

Norming is where the team develops shared expectations. This can be healthy, or it can quietly become dangerous. A norm can be “we tell the truth early.” A norm can also be “we do not talk about what is obviously broken.” Performing is where the team has enough trust, role clarity, and shared understanding to focus more on the work than on itself.

Adjourning matters too. Teams end. Projects finish. Contracts close. People move on. If an organization does not handle endings well, the residue follows people into the next structure. A poorly ended team can become a future trust problem.

The model is useful, but it should not be treated as a neat staircase. Real teams loop. They regress. A new member, new manager, new pressure, new deadline, or new conflict can throw a team back into storming. That does not always mean failure. It may mean the team is renegotiating reality.

This matters for collapse recovery too. A person rebuilding a life also loops. A system rebuilding after a blow-up also loops. The question is not whether the team ever storms. The question is whether storming becomes information or just another courtroom.

Norms: The Unwritten Laws of the Team

Team norms are the informal rules and shared expectations that guide behaviour. They may form through explicit statements, early habits, critical events, or the beliefs and values people bring with them.

A policy manual may say one thing. The norm may say another. The manual may say safety comes first. The norm may say, “Get it done and do not slow the line.” The manual may say communication matters. The norm may say, “Do not bother management unless the building is on fire.” The manual may say teamwork matters. The norm may say, “Protect your own position and let the next person deal with it.”

This is where culture becomes behaviour. A value is what the organization says. A norm is what people learn will actually happen.

Norms can protect a team, but they can also train people into silence. They can build reliability, or they can build complicity. They can make a team efficient, or they can make it blind. This is why culture is not automatically good just because it is strong. A strong norm can carry a team toward excellence, or it can carry the team straight into a ditch with everyone clapping in rhythm.

Roles: The Work People Are Assigned and the Work They Actually Carry

Formal roles matter. Someone has to organize. Someone has to do. Someone has to challenge weak thinking. Someone has to connect the team to the outside world. Someone has to watch timelines. Someone has to protect the standard.

But informal roles appear too: the fixer, the peacekeeper, the person everyone vents to, the unofficial trainer, the scapegoat, the person who sees the risk first, the person who says what everyone else is thinking.

These informal roles can strengthen a team, but they can also trap people. The reliable doer becomes the dumping ground. The challenger becomes the problem person. The connector becomes unpaid emotional infrastructure.

This is where a team can quietly become unfair. If the informal role carries real responsibility but no authority, the team has created a hidden load. That hidden load matters. It is one of the places collapse begins.

A person can be praised as “reliable” while being overloaded. A person can be called “difficult” because they are the only one naming a structural problem. A person can be treated as the emotional shock absorber for a team that refuses to build healthier norms.

SOTL translation: role drift is a warning light. When the role a person actually carries is heavier than the authority, resources, and recognition attached to it, the system is borrowing against that person’s nervous system.

Cohesion: Closeness Is Not Automatically Good

Team cohesion is the attraction people feel toward the team and their motivation to remain part of it. It sounds positive, and often it is. People who care about the team may support one another, communicate better, and stay through difficult moments.

But cohesion is not automatically good. The chapter’s performance logic is important: cohesion helps most when team norms support organizational goals and good work. High cohesion with healthy norms can produce high performance. High cohesion with destructive norms can protect bad habits, normalize absenteeism, punish dissent, or make the team more loyal to itself than to the work.

That is the part I would underline. Belonging can become a shelter, or it can become a muzzle.

In crisis recovery, this matters because people often mistake loyalty for agreement. A loyal person may be the one who raises the hard issue before the damage spreads. A disloyal person may be the one who keeps everyone comfortable while the structure rots.

Cohesion needs direction. It needs goals worth supporting. It needs norms that make honesty safe. In SOTL terms: belonging is valuable, but belonging should not override evidence.

Trust: What the Team Actually Has Under Load

The reading describes trust as moving from lower to higher foundations: calculus-based trust, knowledge-based trust, and identification-based trust. Calculus-based trust is fragile because it depends on consequences. Knowledge-based trust is stronger because people know what to expect from one another. Identification-based trust is strongest because people share values and understand each other’s intentions.

That map makes sense because pressure reveals the trust level a team actually has. When the work is easy, teams can look more trusting than they are. When stress rises, the real trust level shows up. Do people tell the truth? Do they hide mistakes? Do they assume good intent? Do they weaponize small failures? Do they protect one another from unfair pressure? Do they protect the work?

Trust is not a motivational poster. It is a working condition. Without trust, people spend energy managing self-protection. With trust, more energy can go toward the task.

Identification-based trust can create real safety and speed. It can also make people slow to see drift because the team feels like family. That is the caution. Trust should make truth easier, not harder.

Team Mental Models: The Map Inside the Team

A team mental model is the shared or complementary picture members carry about the work: the task, the process, the equipment, the customer, the risks, each person’s role, and how success is supposed to look. Good teams do not only communicate more. They often understand the work similarly enough that less communication is needed to stay aligned.

When a team has a shared mental model, people do not have to stop and renegotiate reality every five minutes. They can anticipate. They can coordinate. They can notice when something is off.

When mental models do not match, conflict often appears as personality conflict even when the real problem is a map problem. One person thinks the priority is speed. Another thinks it is detail. One person thinks the baseline includes one standard. Another thinks the baseline has changed. One person thinks a request was temporary. Another thinks the whole operating picture has shifted. Then people start blaming each other for not caring, when the deeper issue is that no one has made the operating picture explicit.

This connects directly to the invisible org chart idea. Formal structure shows reporting lines. Mental models show how people believe the work actually moves. If those maps do not match, people can use the same words and still mean different things.

A collapse-recovery tool should not only ask, “What happened?” It should ask, “What map is everyone using?”

Self-Directed Teams: Empowerment or Abandonment?

Self-directed teams sound attractive because they have autonomy. They can plan, organize, and coordinate much of their own work. They can respond faster, solve problems closer to the work, and reduce unnecessary management layers.

But autonomy is not the same as abandonment. Self-directed teams work best when the task is whole enough to own, interdependent enough to require coordination, and supported by skills, information, trust, and clear boundaries.

If leadership removes supervision but does not provide authority, resources, training, or clear boundaries, then self-direction becomes abandonment dressed up as empowerment.

A team cannot be self-directed if it is still punished for making decisions, denied the information needed to make those decisions, or held responsible for outcomes controlled elsewhere. Again, responsibility and authority have to meet in the same room.

Remote Teams: Distance Is Not the Real Enemy

Remote work creates real challenges: less face-to-face contact, weaker informal bonding, different time zones, communication delays, and a greater chance that people will misunderstand one another.

But distance itself is not the enemy. Unmanaged distance is the enemy.

Remote teams need deliberate structure: clear communication channels, defined roles, agreed response times, documentation, trust-building, and sometimes richer communication when the stakes are high. A remote team cannot rely on hallway repair after a bad message lands wrong.

That has a broader lesson too. Any team under pressure becomes remote in a psychological sense when people stop sharing the same reality. They may be in the same building and still be miles apart if the mental models, norms, and decision rules are not aligned.

Team Decision-Making: When the Room Gets Dangerous

The decision-making section matters because teams are often praised as better decision-makers than individuals. They can be. More information. More perspectives. More error-checking. More creativity.

But teams can also make worse decisions together. Time pressure can push teams into shallow choices. Production blocking can stop people from contributing because only one person can speak at a time. Evaluation apprehension can make people censor ideas because they fear judgment. Pressure to conform can turn agreement into performance. Overconfidence can convince the team it is better than it is.

Confidence is not proof. A team can feel certain and still be wrong.

This is where psychological safety becomes practical, not sentimental. Psychological safety means people believe it is safe enough to speak, ask, disagree, and identify risks without being punished or humiliated. That does not remove accountability. It makes accountability usable because people can bring reality into the room before reality becomes a crisis.

Constructive conflict is part of good decision-making. The issue is not whether disagreement exists. The issue is whether the team has a clean way to use disagreement without turning it into personal attack.

Brainstorming, brainwriting, electronic brainstorming, and nominal group technique are all attempts to protect idea generation from the usual group traps. The deeper principle is this: do not confuse silence with agreement. Do not confuse fast agreement with good judgment. Do not confuse confidence with evidence.

A better process can protect the signal. Writing ideas down first, gathering input anonymously, rotating turns, or separating idea generation from evaluation can help prevent the loudest voice from becoming the team’s intelligence. When the room is under load, design the process so truth has more than one doorway.

Two Case Patterns

The operating-room example shows one extreme of teamwork: specialized roles, tight timing, high consequences, and deep task interdependence. In that kind of environment, role clarity is not bureaucracy. It is safety. Trust is not decoration. It is functional necessity.

The cross-location team example shows another pattern: a so-called team formed across locations and boundaries, but without enough communication, shared identity, or trust to make the team real. That is the danger of naming something a team before it has the conditions to behave like one.

Both examples point to the same core truth. Teamwork is not created by a label. It is created by structure, practice, trust, norms, role clarity, and shared work.

Standing on the Ledge Application: The Team Under Load Check

This reading suggests a practical field tool: a Team Under Load Check. When a group is struggling, do not start by asking who is the problem. Start by checking the operating conditions.

1. What kind of task interdependence exists here: independent, pooled, sequential, or reciprocal?
2. Is the team small enough to coordinate and large enough to carry the work?
3. Does the team have the right mix of knowledge, skill, perspective, temperament, and authority?
4. What stage is the team actually in: forming, storming, norming, performing, or ending?
5. What are the real norms, not the official slogans?
6. What informal roles are people carrying, and are any of those roles becoming hidden burdens?
7. Is cohesion supporting the goal, or protecting avoidance?
8. What level of trust actually exists under pressure?
9. Does everyone share the same mental model of the work?
10. Are people being asked to self-direct without real authority?
11. If the team is remote or divided, what structure replaces the missing hallway conversation?
12. During decisions, what is being suppressed by time pressure, fear, conformity, or overconfidence?
13. Does the environment support the team through resources, information, rewards, and leadership?

That checklist matters because it moves the conversation away from shame and toward evidence.

SOTL Field Translation: Before Blaming the Team, Check the Conditions

Question	What it reveals
What type of interdependence is present?	Whether the team needs independent effort, handoff discipline, or constant feedback.
Is the team the right size for the work?	Whether performance is being lost to overload or coordination fog.
Does composition match the task?	Whether the team has the skills, perspectives, and roles required.
What norms are actually being enforced?	Whether stated values match lived behaviour.
What roles have emerged informally?	Whether unseen labour is being carried without authority or recognition.
Is cohesion aligned with healthy performance norms?	Whether closeness supports the work or protects dysfunction.
What level of trust is present?	Whether people are cooperating from fear, predictability, or shared identity.
Do members share a usable mental model?	Whether people understand the work the same way.
Are decision methods protecting honesty?	Whether the team can surface dissent, risk, and minority viewpoints.
Does the environment support the team?	Whether resources, information, rewards, and leadership match the work being demanded.

That is the bridge from course material to SOTL. A team is not healthy because it uses team language. A team is healthy when its structure lets people coordinate without eating themselves alive. When the structure does not do that, the problem is not only interpersonal. It is architectural.

What This Adds to the Bigger Work

This chapter gives language for something Standing on the Ledge keeps circling: people break down inside systems, and systems reveal themselves through people.

A failing team may show up as conflict, resentment, silence, missed work, poor communication, bad decisions, or one person carrying too much. But those symptoms are receipts. They point back to the structure.

The job is not to excuse every behaviour. The job is to diagnose honestly.

Did the person fail to communicate, or did the team never build a safe channel for communication? Did the team resist change, or was the change introduced without trust, role clarity, or shared understanding? Did conflict appear because people were immature, or because the work finally exposed a mismatch between responsibility, authority, and resources?

Those are better questions. They do not let individuals off the hook. They put the hook in the right wall.

Key Terms to Carry Forward

• Organic team: An informal or semi-formal group that begins coordinating around a shared objective because the work, pressure, or opportunity requires it.
• Organizational and team environment: The outside conditions that support or inhibit team effectiveness: resources, space, information, leadership, reward systems, and culture.
• Task interdependence: The degree to which team members must share resources, information, expertise, or outputs to complete the work.
• Process loss: The coordination, motivation, and decision-making friction that reduces the team’s actual performance below its potential.
• Team norms: The informal rules that tell members what behaviour is expected, rewarded, tolerated, or punished.
• Team cohesion: The attraction members feel toward the team and their motivation to remain part of it.
• Team trust: Positive expectations that another person or team will support rather than exploit vulnerability.
• Team mental model: The shared or complementary map members carry about the work, roles, process, and risks.
• Psychological safety: A team climate where people can speak, ask, disagree, and identify risks without fear of humiliation or punishment.

Questions to Carry Forward

• When the textbook says a group lacks a mandated purpose, who is assumed to be doing the mandating?
• Does a purpose only count when it serves organizational goals, or can purpose emerge from shared human need?
• Is the team failing because members lack motivation, or because the work is more interdependent than the structure admits?
• Where is the weakest link in the work system, and does the team have authority to repair it?
• Do the team’s reward systems reinforce cooperation, or quietly reward individual competition?
• What norms are actually being enforced when pressure rises?
• Who is carrying an informal role that has become heavier than their formal authority?
• Is cohesion helping the work, or protecting dysfunction?
• Does the team have a shared mental model, or only shared vocabulary?
• When people agree quickly, is that clarity, exhaustion, fear, or conformity?
• Would a visual management space help the team see reality, or would it become another stage for blame?

Closing Reflection

The clean takeaway for me is this: teamwork is not a virtue word. It is a design problem.

If the work is interdependent, the team needs communication. If the stakes are high, the team needs trust. If the team is diverse, the team needs norms that make difference usable. If the team is under pressure, the team needs psychological safety and decision rules. If the team is self-directed, the team needs authority. If the team is remote, the team needs deliberate structure.

And if the team is falling apart, the first question should not be, “Who failed?”

The first question should be: what conditions made failure more likely?

That is where the learning journal meets the ledge.

Evidence before shame. Structure before verdict. Agency after reality.

Godspeed.

Suggested WordPress Description

A blended May 18-19 MGT2382 learning journal entry connecting team dynamics to the Standing on the Ledge frame: groups, organic teams, task interdependence, team design, norms, trust, role clarity, psychological safety, and the structural conditions that make teams succeed or fail under pressure.