Are communication skills as important as technical knowledge for planners?
The honest answer is no — they’re more important
Most planners get hired for the technical skills — the spreadsheet fluency, the Erlang intuition, the forecasting method, the WFM platform — and promoted for the communication skills. That ordering tells you the answer. Technical knowledge is what makes you a planner; communication is what makes you a planner whose work gets acted on. A flawless model that nobody understands sits on a shelf. A competent model the operation believes in moves the business.
This isn’t a comfortable truth for the planners who came into the role because they were good with numbers and uncomfortable with people. But it’s consistent: the senior workforce planners and heads of planning who run successful functions all describe their day as 70–80% communication and 20–30% technical work. The technical work is necessary but it’s not where the leverage is.
Why this happens
Planning sits at the intersection of more functions than almost any other operational role. The forecast affects finance. The schedule affects HR. The headcount affects recruitment. The capacity plan affects the operations director’s annual budget. The real-time decisions affect the team leaders on the floor. Every output has a stakeholder; every stakeholder has a different vocabulary, different priorities, and different reasons to ignore the answer.
A planner who can produce a perfectly justified forecast but can’t reframe it for finance won’t get the headcount. A planner who can build a perfect schedule but can’t explain to a team leader why the rota changed will get a complaint instead of compliance. A planner who can run a real-time day flawlessly but can’t articulate to the operations director what just happened will get blamed for problems they actually prevented. The maths produces the answer; the communication makes the answer count.
The five audiences and what they actually need
Finance. Wants the number translated into a cost, the trade-off translated into a margin impact, and the forecast presented as a range with named drivers. A planner who hands finance a model output and expects them to read it loses. A planner who hands finance three sentences with one number and one trade-off wins. See contact centre finance and forecasting with ranges.
The operations director. Wants the outcome and the risk, not the methodology. “The forecast says X, the risk is Y, here’s what I recommend” lands better than “we ran Holt-Winters with seasonality and decomposition by call reason and the WAPE is 4.2%.” The first invites a decision; the second invites a glazed-over nod.
Team leaders. Want to know how the plan affects their team and what changes for the agents they manage. The TL conversation is concrete and operational: “Two early shifts move from Tuesdays to Wednesdays starting the 14th; here’s the reason; here’s how I’ll handle the swap conversation.”
Agents. Don’t hear from planners often, and when they do it’s usually about a change they didn’t ask for. The communication that lands is the one that explains why and acknowledges that the change costs them something. The communication that destroys credibility is the one that pretends nothing has changed or that the change is for their own good.
HR and recruitment. Want lead time and confidence. “We need 12 hires starting in October” delivered in July is useful; the same line delivered in September is a complaint dressed as a request. The planner who builds the relationship with recruitment ahead of need has a much faster path to the headcount than the one who only shows up when there’s a problem.
The specific failures that destroy planning credibility
Five communication failures recur in planning functions and each one quietly costs the team credibility over months.
Speaking technical to a non-technical audience. The MAPE, the Erlang assumption, the smoothing parameter. The audience nods and forgets. Worse, they remember being made to feel slow. The planner who explains in their audience’s language is the one who gets heard.
Leading with the model, not the recommendation. A 15-minute walkthrough of the methodology followed by “and so we recommend X” loses most audiences. The recommendation comes first. The methodology is available for the audience that asks.
Defending instead of explaining. When the forecast misses, the planner’s instinct is often to defend the model. The credibility move is to explain what happened, what the model missed, and what changes next time. Defensiveness reads as denial.
Hiding behind “the system says.” The WFM platform produced a number; the planner can’t explain it. This pattern signals that the planner doesn’t actually own the answer. Owning the answer — including being prepared to override the system — is what makes a planner credible.
Surprising people. Bad news, communicated late, lands worse than the same bad news communicated early. The single biggest communication discipline in planning is to surface variances early, even when there’s nothing to do about them yet, because by the time the consequence lands the audience has already absorbed the heads-up.
The three habits that build credibility back
Write the answer down. A one-page summary — recommendation, trade-off, risk — that goes out before the meeting, not during it. Audiences read at their own pace and arrive prepared. The conversation becomes about the decision, not the explanation.
Translate before you speak. Before any stakeholder conversation, write the technical answer and then rewrite it in the audience’s words. “The model says 64 FTE” becomes “to deliver the SL we agreed, we need six more agents than we have approved.” The information is identical; the receptivity is not.
Build the relationships ahead of the asks. The thirty-minute coffee with the head of recruitment in March turns into a fast headcount approval in September. The monthly check-in with finance turns into a sympathetic ear when the forecast is wrong. The standing one-to-one with the operations director turns into the freedom to raise problems early. Communication isn’t just what happens in the meeting; it’s the relationship that determines whether the meeting goes well.
What this means for hiring and developing planners
The implication for operations that build planning teams is uncomfortable. The standard hiring profile — strong Excel, knows Erlang, has used a WFM platform — selects for the table-stakes skills and misses the determinant ones. The candidate who can explain a complex idea in plain words, listen to a stakeholder before recommending, and write a one-page summary that lands the decision is genuinely rarer and more valuable than the candidate who knows three forecasting methods.
The development implication is the same. Operations that invest in their planners’ technical skills (training on WFM platforms, courses on forecasting) and ignore the communication side produce technically-competent functions that don’t move outcomes. Operations that invest in both produce planners who get heard. See the skills that move you up and building planning function credibility.
The honest counter-argument
The reverse case is worth stating. A great communicator with weak technical skills will get heard, then be wrong, then lose credibility faster than a quiet planner with strong technical skills. Communication amplifies whatever you’re saying; if what you’re saying is wrong, communication makes it worse. The technical foundations have to be solid. The argument here isn’t that communication replaces technical knowledge; it’s that, with technical knowledge in place, communication is what determines whether the work matters.
Conclusion
Technical knowledge gets you the planner job; communication determines what happens once you have it. The planners who run successful functions describe their work as mostly communication, mostly translation between functions, mostly written narrative that frames the numbers for an audience that won’t read the model. The technical work matters — it has to be right — but it’s the precondition, not the differentiator. Operations that recognise this hire and develop planners differently, and reap the benefit of a planning function that gets acted on rather than tolerated.
Pair this with building planning function credibility, working with your planning team, and the skills that move you up.