Activity: Culture Observation Exercise
Activity Overview
The Culture Observation Exercise is a practical leadership activity designed to help learners observe, analyze, and reflect on the real culture of a team. Culture is not always visible through formal values, policies, or leadership messages. It is often seen in daily behaviors, communication patterns, meeting habits, decision-making styles, conflict responses, and how people treat one another.
This activity helps learners move from simply understanding culture as a concept to observing culture in action. By carefully watching how a team behaves in real workplace situations, learners can identify signs of healthy culture, signs of unhealthy culture, visible and invisible cultural elements, and opportunities for improvement.
The purpose of this activity is not to judge people. The purpose is to understand repeated team behaviors and reflect on what those behaviors reveal about trust, respect, psychological safety, accountability, inclusion, collaboration, and leadership impact.
Activity Purpose
The main purpose of this exercise is to help learners develop the ability to observe culture objectively. Many new team leads react only when problems become serious. This activity trains learners to notice early cultural signals before they become major issues.
After completing this activity, learners should be able to:
- Observe team behaviors without immediately judging or blaming.
- Identify visible signs of team culture.
- Recognize possible invisible assumptions behind team behaviors.
- Differentiate between healthy and unhealthy cultural patterns.
- Understand how leadership behavior shapes culture.
- Reflect on trust, respect, psychological safety, and accountability within a team.
- Create practical improvement actions for building healthier team culture.
When to Use This Activity
This activity can be used after learners complete the chapter on culture. It is especially useful after covering topics such as team culture, visible and invisible elements of culture, psychological safety, healthy and unhealthy culture, and accountability.
This activity can be used in:
- Leadership development workshops
- Team lead training programs
- Agile leadership courses
- People management training
- New manager onboarding
- Team culture improvement sessions
- Reflection-based learning assignments
Recommended Participants
This activity is suitable for learners who are preparing to become team leads, current team leads, project leads, scrum masters, people managers, delivery leads, and anyone responsible for improving team effectiveness.
It can be completed individually or in small groups. For classroom or workshop delivery, learners can observe a fictional case study, video scenario, role play, or their own workplace team.
Important Instruction for Learners
During this exercise, learners should focus on observing behaviors, not judging personalities. The goal is not to label someone as good or bad. The goal is to understand what repeated behaviors reveal about the team culture.
Observe behavior. Identify patterns. Reflect on culture. Suggest improvement.
Learners should avoid making assumptions too quickly. For example, if people are silent in meetings, it may not automatically mean they are disengaged. It may mean they do not feel safe, they are unsure of expectations, they respect hierarchy, or they believe speaking up will not make a difference.
Activity Scenario
Read the following workplace scenario carefully. Observe the team behaviors and answer the reflection questions that follow.
Scenario: The Silent Retrospective
A software delivery team has been working together for six months. The team follows Agile ceremonies such as daily stand-ups, sprint planning, sprint reviews, and retrospectives. On paper, the team appears organized because meetings happen regularly and sprint boards are updated.
However, the team lead notices a few patterns. During daily stand-ups, most team members give short status updates such as “working on it,” “almost done,” or “no blockers.” Later in the sprint, blockers appear that were not mentioned earlier.
During retrospectives, the team usually says, “Everything is fine,” or “We need better communication.” Very few specific improvement points are discussed. Junior members rarely speak unless directly asked.
When defects are found, developers and testers sometimes become defensive. Developers say the requirement was unclear, testers say they received the build late, and business analysts say the team should have asked questions earlier.
The product owner is very busy and often joins meetings late. Team members hesitate to challenge unclear acceptance criteria because they do not want to slow down the sprint.
The team lead wants to understand whether the issue is only process-related or whether there are deeper cultural issues affecting transparency, collaboration, ownership, and psychological safety.
Part 1: Observe Visible Culture
Visible culture includes behaviors, routines, communication patterns, meeting habits, and actions that can be directly observed. Based on the scenario, identify the visible cultural signs.
| Observation Area | What Did You Notice? | Healthy or Unhealthy Sign? | Why? |
|---|---|---|---|
| Daily stand-up behavior | |||
| Blocker reporting | |||
| Retrospective participation | |||
| Junior member participation | |||
| Defect discussion behavior | |||
| Product owner interaction | |||
| Requirement clarification |
Part 2: Identify Possible Invisible Culture
Invisible culture includes beliefs, assumptions, fears, expectations, and unwritten rules that may be influencing visible behavior. For each visible behavior, identify possible invisible causes.
| Visible Behavior | Possible Invisible Belief or Assumption | How This Affects Team Culture |
|---|---|---|
| Team members say “no blockers” but blockers appear later. | ||
| Retrospectives produce general comments only. | ||
| Junior members rarely speak. | ||
| Defect discussions become defensive. | ||
| Team members avoid challenging unclear acceptance criteria. | ||
| People focus on completing sprint work quickly. |
Part 3: Culture Diagnosis
In this section, learners should diagnose the overall team culture based on the observations. The goal is to identify whether the team culture is healthy, unhealthy, or mixed.
Guiding Questions
- Does the team appear psychologically safe? Why or why not?
- Do team members raise blockers early?
- Do people feel comfortable asking questions?
- Are defects discussed for learning or blame?
- Are Agile ceremonies meaningful or mechanical?
- Is there strong cross-role collaboration?
- Is accountability clear and healthy?
- Do team members focus on outcomes or only task completion?
| Culture Area | Observation | Diagnosis |
|---|---|---|
| Psychological safety | ||
| Trust | ||
| Respect | ||
| Accountability | ||
| Collaboration | ||
| Learning mindset | ||
| Agile culture |
Part 4: Identify Healthy Culture Signs
Even when a team has challenges, there may still be some healthy signs. Learners should identify any positive behaviors from the scenario.
Examples of possible healthy signs may include:
- The team has regular Agile ceremonies.
- The team lead is observing patterns and wants to improve culture.
- Defects are being discussed, even if defensively.
- The team has a structure for sprint planning and retrospectives.
- There is an opportunity to improve communication and ownership.
| Healthy Sign Observed | Why It Matters | How to Reinforce It |
|---|---|---|
Part 5: Identify Unhealthy Culture Signs
Learners should now identify the warning signs of unhealthy culture from the scenario. These warning signs should be based on repeated behavior patterns, not isolated incidents.
Possible unhealthy signs may include:
- Blockers are not raised early.
- Retrospectives are not producing honest discussion.
- Junior members are not actively participating.
- Defect discussions become defensive.
- Team members avoid challenging unclear requirements.
- Agile ceremonies may be happening mechanically.
- Psychological safety may be weak.
- Accountability may be unclear or fear-based.
| Unhealthy Sign Observed | Possible Root Cause | Potential Impact | Improvement Action |
|---|---|---|---|
| Blockers are raised late. | |||
| Retrospectives are silent or generic. | |||
| Defect discussions become defensive. | |||
| Junior members rarely speak. | |||
| Unclear acceptance criteria are not challenged. |
Part 6: Leadership Response Plan
After observing culture, the next step is to decide what a team lead should do. A good leadership response should improve culture without blaming the team.
Leadership Actions to Consider
- Create a safe environment for honest blocker reporting.
- Clarify that raising risks early is responsible behavior.
- Make retrospectives more specific and action-oriented.
- Invite quieter team members to contribute respectfully.
- Change defect discussions from blame-focused to learning-focused.
- Clarify acceptance criteria before sprint execution.
- Recognize behaviors such as transparency, ownership, and collaboration.
- Follow up on improvement actions from retrospectives.
| Culture Issue | Leadership Response | Expected Positive Impact |
|---|---|---|
| Late blocker reporting | Appreciate early blocker reporting and ask, “What support is needed?” | More transparency and earlier problem-solving |
| Silent retrospectives | Use specific questions and follow up on agreed actions | More honest reflection and continuous improvement |
| Defensive defect discussions | Ask root-cause and prevention questions instead of blame questions | Improved learning and quality ownership |
| Low junior participation | Invite input respectfully and protect quieter voices from interruption | Better inclusion and more diverse thinking |
| Unclear requirements | Create a team agreement that unclear acceptance criteria must be clarified before execution | Reduced rework and better sprint confidence |
Part 7: Observation Exercise for Real Workplace Use
Learners can also apply this exercise to their own team or a team they observe. They should observe one team meeting, project discussion, Agile ceremony, or collaboration session.
While observing, learners should focus on behavior patterns such as who speaks, who stays silent, how disagreement is handled, how blockers are discussed, and whether people appear safe to ask questions.
| Observation Item | What I Observed | What It May Reveal About Culture |
|---|---|---|
| Who speaks most often? | ||
| Who stays silent? | ||
| How are questions handled? | ||
| How are blockers discussed? | ||
| How is disagreement handled? | ||
| How are mistakes or defects discussed? | ||
| Is feedback specific or vague? | ||
| Is ownership clear? | ||
| Do people support each other? | ||
| Do leaders model the desired culture? |
Part 8: Culture Observation Rating
Use the rating scale below to evaluate the culture observed. This is not a formal assessment. It is a reflection tool to help identify strengths and improvement areas.
Rating scale:
- 1 = Very weak
- 2 = Needs improvement
- 3 = Moderate
- 4 = Strong
- 5 = Very strong
| Culture Area | Rating 1-5 | Evidence for Rating | Improvement Needed |
|---|---|---|---|
| Open communication | |||
| Psychological safety | |||
| Trust | |||
| Respect | |||
| Accountability | |||
| Collaboration | |||
| Learning from mistakes | |||
| Inclusion | |||
| Leadership role modeling |
Part 9: Reflection Questions
Answer the following questions after completing the observation.
- What visible behaviors did I notice most clearly?
- What invisible beliefs or assumptions might be influencing those behaviors?
- What signs of healthy culture did I observe?
- What signs of unhealthy culture did I observe?
- Did people appear comfortable speaking honestly?
- How were mistakes, blockers, or risks discussed?
- Did the leader respond in a way that built trust or reduced trust?
- Were quieter voices included?
- Was accountability clear and respectful?
- What one culture improvement action would make the biggest difference?
Part 10: Culture Improvement Action Plan
Based on the observation, learners should create a small and realistic action plan. The goal is not to fix everything at once. The goal is to choose one or two practical actions that can improve team culture.
| Culture Gap Observed | Desired Behavior | Action I Will Take | How I Will Know It Improved |
|---|---|---|---|
| People do not raise blockers early. | People raise blockers as soon as they notice them. | ||
| Retrospectives are silent. | People share honest and specific improvement points. | ||
| Defect discussions become defensive. | Defects are discussed for root cause and prevention. | ||
| Junior members do not speak. | All team members have space to contribute. | ||
| Ownership is unclear. | Every commitment has a clear owner and follow-up. |
Facilitator Notes
If this activity is conducted in a classroom or workshop, the facilitator should encourage learners to discuss observations respectfully. Learners should avoid blaming individuals in the scenario. The focus should remain on behavior patterns and culture improvement.
Suggested Discussion Prompts
- What behavior in the scenario is most concerning?
- Which behavior would you address first as a team lead?
- How can a leader make blocker reporting safer?
- How can retrospectives become more meaningful?
- How can defect discussions shift from blame to learning?
- How can leaders include quieter team members?
- How can accountability be improved without fear?
Facilitator Reminder
The purpose of the activity is to help learners practice culture observation, not to create perfect answers. Different learners may interpret the same behavior differently. Encourage discussion by asking, “What evidence supports your observation?”
Sample Completed Observation
The table below provides a sample response for learners to understand how to complete the activity.
| Observed Behavior | Possible Culture Meaning | Suggested Leadership Action |
|---|---|---|
| Team members say “no blockers,” but blockers appear later. | The team may not feel safe or responsible enough to raise blockers early. | Clarify that early blocker reporting is responsible behavior and appreciate people who raise risks early. |
| Retrospectives produce only general comments. | The team may not believe retrospectives lead to real change. | Ask specific questions and follow up on one improvement action in the next sprint. |
| Junior members rarely speak. | The team may have hierarchy-based silence or low inclusion. | Invite junior members respectfully and create space for all voices. |
| Defect discussions become defensive. | The team may associate defects with blame. | Shift defect review questions toward root cause, prevention, and shared quality ownership. |
| Unclear acceptance criteria are not challenged. | The team may value speed over clarity or may fear challenging the product owner. | Create a team agreement that unclear requirements must be clarified before execution. |
Key Learning Points
- Culture can be observed through repeated team behavior.
- Visible behaviors often reveal invisible beliefs, assumptions, and fears.
- Silence in meetings may indicate low psychological safety or low inclusion.
- Late blocker reporting may indicate fear, unclear accountability, or weak transparency.
- Defensive defect discussions may indicate blame culture.
- Healthy culture requires trust, respect, psychological safety, collaboration, and accountability.
- Leaders should respond to cultural issues with curiosity, not blame.
- Small repeated leadership actions can improve team culture over time.
Activity Debrief
After completing the exercise, learners should discuss what they discovered about culture. The most important insight is that culture is not always directly stated. It is often revealed through small repeated behaviors.
For example, if people repeatedly avoid raising blockers, the problem may not be only communication. It may be trust, fear, unclear accountability, or previous negative experiences. If retrospectives are silent, the issue may not be lack of ideas. It may be lack of psychological safety or lack of follow-up on past feedback.
A good team lead learns to look beyond the surface and ask thoughtful questions:
- What behavior am I seeing?
- What pattern is repeating?
- What might be causing this pattern?
- How is my leadership behavior influencing this culture?
- What small action can improve the culture?
Conclusion
The Culture Observation Exercise helps learners practice one of the most important leadership skills: seeing culture in action. Culture is not only what people say. It is what people repeatedly do, especially during pressure, mistakes, conflict, feedback, and uncertainty.
By observing team behavior carefully, leaders can identify strengths, risks, and improvement opportunities. They can understand whether the team culture supports trust, respect, psychological safety, accountability, inclusion, and learning.
The key lesson from this activity is: to improve culture, leaders must first learn to observe it clearly.