Scenario 1: Team Member Arrives Late to Meetings
Scenario 1: Team Member Arrives Late to Meetings
How an effective Team Lead handles repeated lateness in IT delivery meetings with structure, empathy, and clarity.
Scenario Overview
In IT delivery environments, meetings are the heartbeat of communication. Daily stand-ups, sprint planning, sprint reviews, retrospectives, client calls, and internal syncs all carry a clear purpose — alignment, decision-making, problem-solving, and progress tracking. When a team member consistently arrives late, it is not just a small habit issue. It quietly damages team rhythm, trust, productivity, and even client confidence.
As a Team Lead, how you handle this situation reveals your leadership style. A harsh response damages morale. Ignoring it encourages indiscipline. The right approach is calm, structured, empathetic, and firm. This scenario teaches you exactly how to balance both sides.
Typical Real-World Situation
Understanding the Scenario in Depth
Lateness in meetings is rarely about the clock. It is usually about underlying behaviors, habits, priorities, or unspoken challenges. Before reacting, a leader must observe patterns and seek context. The same behavior can have very different reasons across individuals.
Think of a meeting like a train
If one passenger is late, the entire train waits. Multiply that by 8 team members, and you waste collective time, energy, and momentum.
Why This Issue Cannot Be Ignored
| Impact Area | Consequence If Ignored |
|---|---|
| Team Productivity | Updates get repeated, decisions delayed, momentum lost. |
| Team Morale | Punctual members feel their time is not respected. |
| Team Discipline | Others copy the behavior, creating a cultural problem. |
| Client Perception | If lateness happens in client calls, it damages credibility. |
| Leadership Image | The Team Lead appears weak, inconsistent, or unaware. |
| Delivery Risk | Missed dependencies in stand-ups can delay sprint goals. |
Leader’s Core Objectives
What the Leader Must Achieve
- Identify the real cause behind the lateness.
- Address the issue without humiliating the team member.
- Restore discipline and respect for shared time.
- Set clear expectations for future meetings.
- Maintain a healthy and motivated team environment.
- Demonstrate fair and consistent leadership to others.
Step-by-Step Leadership Approach
Observe Before Reacting
Leaders speak with data, not emotions.
Track the pattern for a few days. Is it daily? Only on certain meeting types? This gives you facts before you start the conversation.
Avoid Public Confrontation
Never criticize behavior in front of the team.
Public callouts damage psychological safety. Handle behavioral issues privately to preserve dignity and trust.
Schedule a Private One-on-One
Frame it as a check-in, not a warning.
The intention should be conversation, not confrontation. A calm tone increases openness.
Use the SBI Feedback Model
Situation – Behavior – Impact.
Deliver feedback that is specific, factual, and respectful — without making it personal.
Listen With Empathy
The cause is often hidden under the behavior.
There may be a workload conflict, personal issue, or scheduling clash. Listening reveals the real solution.
Reset Expectations Clearly
Polite, but firm.
Reinforce the team's punctuality standards and define what is expected going forward.
Offer Support, If Needed
Lead by enabling, not just instructing.
Help with rescheduling, reducing meeting load, or adjusting timing if the issue is genuine.
Monitor and Acknowledge Improvement
Recognition reinforces the right behavior.
Track behavior over 1–2 weeks. Acknowledge improvement positively — even a small word matters.
Applying the SBI Feedback Model
Behavior: "…you joined around 10–15 minutes late on most days."
Impact: "…this caused the team to repeat updates and delayed our task planning."
Sample Conversation – Standard Approach
Leader: Hi [Name], thanks for joining. I wanted to have a quick chat — nothing serious.
I’ve noticed that over the past week, you’ve been joining the daily stand-ups around
10–15 minutes late. For example, on Monday, Tuesday, and Thursday, you came in after
the team had already shared updates.
When this happens, we end up repeating discussions, and it delays our task planning
for the day.
I wanted to check in with you — is there something specific causing this?
Any scheduling conflict, workload pressure, or anything personal I should be aware of?
(Pause and listen…)
Thanks for sharing that. I understand.
Let’s work together to fix this. Going forward, can we agree that you’ll join the
stand-up on time every day?
If there’s anything blocking that — like overlapping meetings or workload —
let me know and we’ll adjust.
I appreciate your openness, and I’m confident this will improve from tomorrow.Sample Conversation – When the Member Reacts Defensively
Team Member: It’s just a few minutes. I don’t think it’s a big deal.
Leader: I understand it may feel small, but in a team setting, even 10 minutes
affects everyone’s flow. We have 8 people waiting, and we end up repeating updates.
I’m not bringing this up to blame you — I’m bringing it up because I value
your contribution, and I want the team to function smoothly.
Let’s find a way to make this work for both of us.
Is there something I can do to help you be on time?Sample Conversation – When There Is a Genuine Reason
Team Member: Actually, I have a client call from another project that ends at 9:30,
and our stand-up is at 9:30 sharp. I’m always rushing.
Leader: Thanks for telling me — that explains it.
Let’s see if we can shift our stand-up by 15 minutes, or I can speak to the other
project lead. We’ll find a solution. Appreciate you being transparent.Weak vs Effective Leadership Response
| Weak Leadership Response | Effective Leadership Response |
|---|---|
| "Why are you always late? It’s annoying." | "I noticed you joined late on a few days — is something blocking you?" |
| Calls out the member in front of everyone. | Schedules a private one-on-one. |
| Reacts emotionally and assumes intent. | Speaks calmly, with data and empathy. |
| Ignores it because it feels small. | Addresses it early before it becomes culture. |
| Demands compliance with no support. | Sets expectations and offers help. |
Good vs Bad Communication Examples
Failure vs Success Outcomes
If Handled Poorly
- Team member feels humiliated.
- Trust with leader weakens.
- Behavior continues silently.
- Other members lose respect for the leader.
- Team culture becomes tense and reactive.
If Handled Well
- Team member feels respected and understood.
- Behavior improves quickly.
- Trust between leader and team grows.
- Team discipline becomes self-driven.
- Leader is seen as fair and emotionally intelligent.
Leadership Principles Demonstrated
| Principle | Application in This Scenario |
|---|---|
| Emotional Intelligence | Stays calm, avoids blame, listens actively. |
| Specificity | Uses exact dates and behaviors, not vague accusations. |
| Empathy | Understands the human side before judging. |
| Accountability | Sets clear expectations going forward. |
| Supportive Leadership | Offers help instead of only demanding change. |
| Consistency | Applies the same standards fairly across the team. |
| Psychological Safety | Speaks privately, never publicly humiliates. |
Possible Root Causes to Explore
Investigate Before Concluding
- Poor time management or personal habits.
- Back-to-back or overlapping meetings.
- Heavy workload and burnout.
- Late working hours impacting morning routines.
- Personal or family challenges.
- Disengagement or lack of motivation.
- Health-related concerns.
- Unclear meeting importance or expectations.
Action Plan After the Conversation
Follow-Up Steps for the Leader
- Document the discussion informally for personal tracking.
- Reconfirm meeting timings to the whole team if needed.
- Encourage calendar reminders 5 minutes before meetings.
- Reschedule overlapping meetings if conflicts are genuine.
- Observe behavior for 1–2 weeks before next intervention.
- Recognize improvement privately or in 1:1s.
What a Leader Should NEVER Do
- Do not call out the person in front of the team.
- Do not use sarcasm or passive-aggressive comments.
- Do not assume the reason without asking.
- Do not ignore repeated lateness — silence equals approval.
- Do not compare the member with others publicly.
- Do not escalate to management without giving a chance to improve.
Coaching Tip for Team Leads
Reflection Activity for Learners
Imagine you are the Team Lead. Reflect on the following questions and write down your answers:
- How would you observe the pattern before initiating a conversation?
- How would you start the one-on-one without making the team member defensive?
- What words would you avoid using? Why?
- What if the team member becomes emotional or upset during the conversation?
- How would you set expectations without sounding authoritative?
- What follow-up actions would you take in the next two weeks?
Key Takeaways
Leadership Insight
Handling lateness is one of the smallest yet most revealing tests of leadership. How you respond shapes your team’s culture, discipline, and trust in you as a leader. Approach it with structure, empathy, and clarity — and you will build a team that respects time, respects each other, and respects your leadership.