Working with your planning team: a team leader’s guide

Leadership · ~6 minute read

A partnership, not a transaction

The relationship between a team leader and the workforce planning function is, in most contact centres, less mature than it should be. Team leaders treat the planning team as a service that produces a schedule, raises problems, and asks for absence reports. Planning teams treat team leaders as recipients of decisions made elsewhere. Both lose something. The team leaders and planners who treat the relationship as a partnership — sharing context, jointly diagnosing problems, debriefing after the difficult days — produce noticeably better schedules and quieter floors than the operations where the relationship is transactional. This article is for team leaders who want to get more out of their planning team, and who suspect, correctly, that the way to do that is to put more in.

What you should expect

A good planning team delivers a small set of things consistently. A schedule that arrives on time. If the operation has agreed to publish four weeks in advance, the schedule arrives four weeks in advance, every cycle, with no excuses. Changes communicated promptly and with a reason. When something moves, you should know within the working day, and you should know why. An answer when you ask. A two-minute question about why a break landed where it did should get a two-minute answer, not a defensive escalation. Awareness of upcoming events. The planning team should be telling you about next month’s training schedule, the impact of a planned system change, or a likely volume spike, not waiting for you to discover it.

Where any of these are persistently missing, you have a planning team that needs more support or a process problem the planning team has not solved. Both deserve a conversation. The first conversation is rarely with the planner; it is with whoever runs the planning function, and the question to ask is what they need from operations to make the relationship work better. The answer is usually about data quality, lead times, or clarity of constraints — all things the operation can give.

What to ask for

Most team leaders ask for less from their planning team than they could. Things worth asking for include: visibility of the forecast, not just the schedule — knowing what volume the next month is expected to bring lets you plan coaching and training around it; a regular short conversation, perhaps fifteen minutes a fortnight, to talk about how the team is performing and what is coming up; data on your team’s adherence, AHT, and shrinkage in a format that is useful for coaching, not just for reporting; scenario thinking, occasionally, on questions like “what would happen to next month if we lost two agents” — the planner can model this in a few minutes and you can plan retention conversations accordingly.

Most planners will respond well to these requests because they bring meaning to a job that often feels like it is producing numbers nobody reads. Ask for what you need, and ask for it constructively.

What to bring to the conversation

The relationship is two-way. Team leaders bring three things the planner cannot get elsewhere. Context about the team — who is on a development plan, who has a difficult home situation, who is about to be promoted, who is at retention risk. The planner cannot make this information up; you have to share it. Floor observations — the patterns you see in real time that the dashboard misses or aggregates away. Judgement about trade-offs — when the planner is weighing two imperfect options, you often know which one the team will absorb better and which will create friction.

The team leader who shows up to the conversation with empty hands gets a transactional relationship. The team leader who shows up with information that the planner cannot get anywhere else builds a partnership that pays off across years.

Handling disagreements

You and the planner will disagree about decisions. Sometimes you will be right; sometimes they will be. A few habits help these conversations go well. Lead with the data point, not the conclusion — “I’ve seen the last three Mondays come in higher than forecast, here’s the data” lands better than “the forecast is wrong.” Acknowledge the constraints they are working under — the schedule is a compromise across the whole operation, not just your team. Make the trade-off explicit — if you want one thing, you are usually willing to accept another; saying so makes the conversation a negotiation rather than a complaint. Document the conversation — a one-line note about what you agreed and why protects both sides when the question comes back two weeks later.

The planners who deal with team leaders like this remember them, and trade favours when the favours matter. The team leaders who do not get the transactional relationship they deserve.

The bad-day playbook

The relationship is tested on the difficult days. When a peak runs hot, when a system fails, when absence spikes unexpectedly, the temptation is to argue about whose fault it was. A few simple rules help. During the incident, no blame — pool the information, agree what to do, act. Immediately after, capture what happened, in writing, while it is still fresh. Within the week, hold a short debrief together — what worked, what did not, what we would do differently. The debrief is not about apportioning fault; it is about turning the incident into learning that improves the next month’s plan.

Operations that handle this well usually have an unwritten rule: bad days are joint property. Operations that handle it badly usually have a culture of blame that the planning function and operations have both contributed to. The team leader cannot single-handedly fix the latter, but they can refuse to add to it.

When the planning team is the problem

Sometimes the planning team is genuinely struggling — under-resourced, missing skills, badly led. The team leader is not usually in a position to fix this directly, but they are in a position to raise it constructively. The right route is usually through the operations manager, with a specific example rather than a general complaint. “The schedule has been late three weeks running and here are the consequences for my team” gets a different response than “the planning team is useless.” Specific problems trigger specific conversations; general complaints get filed under “noise.”

Conclusion

The planning team is one of the relationships in a contact centre that disproportionately rewards investment. A team leader who invests in the relationship — sharing context, asking for what they need, showing up to the difficult conversations, debriefing honestly — gets a level of planning support that team leaders without that investment never see. The investment is not large — an hour or two a week of attention — and it compounds over months and years. The team leader who runs this way has fewer schedule disputes, smoother peaks, better-coached agents, and a planning team that goes out of its way to help. The team leader who treats planning as a service gets the service they ordered.

Pair this with what workforce planning is and how a team leader’s daily decisions feed the plan.