By: Natalie Johnson
When Danielle D. Pollard joined a complex technology initiative at Allstate, she saw an opportunity that many leaders might have missed.
The 60-person team was spread across four offices and three time zones. Its members brought considerable experience to the work, but the structure surrounding their collaboration was not allowing that expertise to translate into consistent progress.
Pollard began by listening.
She conducted individual interviews and asked a small number of carefully constructed questions. Rather than concentrating only on project plans and technical processes, she examined how information moved through the team, how people described their challenges, and where their words did not fully align with their behavior.
That diagnosis helped the team produce a working demonstration within three weeks. The project was ultimately completed three months ahead of schedule.
The turnaround reinforced a principle that has guided Pollard throughout nearly 30 years of corporate transformation work. Communication is not separate from performance. It is one of the systems that makes performance possible.
Language as Part of the Operating System
Corporate leaders often describe communication as a soft skill, placing it alongside qualities such as confidence, empathy, and likability. Pollard sees it differently.
With a background in Industrial Engineering, Lean/Six Sigma, and Agile software delivery, she was trained to examine systems through their constraints, bottlenecks, and outputs. That same discipline shaped the way she began looking at human interaction.
A team’s communication system includes far more than what is said during a meeting. It includes the questions leaders ask, the information people withhold, the language used in emails, the assumptions embedded in project documents, and the behavior that contradicts what someone claims to support.
When those signals are unclear or inconsistent, the effects become operational. Decisions slow down. Meetings expand without producing clarity. People protect themselves instead of exposing risk. Teams spend more time discussing the work than advancing it.
Pollard summarizes her philosophy directly: “Problems don’t exist in circumstances. They exist in language.”
The statement does not suggest that external conditions are irrelevant. It is a reminder that teams can only respond to those conditions through the conversations they are willing and able to have.
It Starts With Better Questions
One of the first things Pollard examines in a team is the quality of its questions.
Leaders frequently approach communication as a matter of giving clearer instructions. They prepare what they want to say, repeat expectations, and become frustrated when the same challenges continue. Pollard believes this emphasis is often misplaced.
“In communication, the sweet spot is in the questions you ask, not in what you’re saying,” she explains.
A useful question interrupts the rehearsed explanation. It requires a person to examine what is actually happening rather than repeat a familiar defense. It may reveal that two departments are working from different definitions of success, that an employee has stopped raising concerns because earlier warnings were ignored, or that a team has confused visible activity with meaningful progress.
Pollard’s interviews are designed to uncover both the spoken explanation and the conversation beneath it.
People may say they support a new process while behaving in ways that weaken it. They may insist a project is going well without being able to identify measurable evidence. They may point to another department because acknowledging their own contribution would be more difficult.
For leaders, this requires a different kind of attention. Listening is not simply remaining quiet until another person finishes speaking. It means noticing the distance between a person’s words, behavior, and demonstrated commitments.
The Work Is to Reveal, Not Rescue
Pollard’s experience as a Scrum Master helped sharpen one of the most important distinctions in her work. The role of a leader or facilitator is not always to resolve a team’s problem. Sometimes the more valuable task is to reveal it.
Scrum introduces visibility into a system. Work becomes easier to inspect. Short meetings require people to identify what matters now rather than wander through lengthy explanations. Progress, delay, ownership, and uncertainty become more visible.
That visibility can create resistance. Teams may say they want accountability while hesitating to adopt practices that would expose where accountability has weakened.
Pollard’s role in those situations is not to arrive with a predetermined answer. It is to create the conditions in which the team can see what it has not yet named clearly.
This approach also prevents leaders from becoming permanent rescuers. When a manager repeatedly solves every conflict or supplies every missing answer, the team may become dependent on intervention. Revealing the underlying pattern gives the people closest to the work an opportunity to address it themselves.
The result is not merely a better conversation. It is a more capable system.
Connecting Communication to Measurable Performance
Pollard’s W.O.L.F. framework grew from the belief that language shapes action.
The method asks people to become more conscious of the words they use, take ownership of their contribution to an outcome, construct language that moves the situation forward, and compare that language against the results it produces.
The framework is not based on speaking more forcefully or performing confidence. It is built around intentionality.
Pollard often encourages people to pause before contributing and ask a simple question: “Why am I talking?”
That pause can prevent a meeting from becoming a contest for airtime. It helps a person determine whether something needs to be said, whether it needs to be said at that moment, and whether they are the right person to say it.
The goal is communication that is intentional, intelligent, and grounded in integrity.
This has immediate implications for corporate teams. A leader who asks for greater ownership while making every consequential decision is communicating something. A company that says innovation matters but penalizes every failed experiment is communicating something. A team that repeatedly postpones difficult conversations is also making a decision, even when no one identifies it as one.
In each case, language and behavior are producing the result together.
A New Way to Diagnose Team Performance
Many teams do not lack intelligence, effort, or ambition. They are filled with talented people working inside conversations that no longer support the work.
The challenge may appear to be strategy, accountability, morale, or execution. Those issues may be real, but beneath them is often a more fundamental question. Can the team accurately describe what is happening, what is needed, and what each person is willing to own?
Pollard’s work challenges leaders to treat that question with the same seriousness they would apply to any other performance system.
She is not simply teaching professionals to speak with more confidence. She is examining how language influences decisions, exposes constraints, distributes responsibility, and turns knowledge into coordinated action.
She looks at what the team is producing, traces the outcome back through the system, and listens for the language shaping what happens next. From there, she helps people construct conversations that create greater clarity, stronger ownership, and more consistent movement, which can ultimately lead to better decisions, faster execution, and more measurable performance.
