Track · PM Careers & Leadership5 min read
A Polished Announcement Is Not Internal Communications
Comsint argues internal communication starts before drafting: teams differ in whether they want direction or co-creation, and managers need context, not just talking points.

Context
Comsint published an essay arguing effective internal communication starts with understanding team expectations before drafting announcements
A study by Jia Hu and Timothy Judge found leader-team performance links depended partly on teams' expectations about authority
The essay prescribes five things managers must know before any announcement, including what is decided and what remains open
Email open rates and town hall attendance measure reach, not communication effectiveness
A well-written company announcement can still leave employees frustrated, because effective internal communication starts before the first draft — with understanding how each team expects leadership to engage them. That is the core argument of a new essay from Comsint, the internal communications firm, published via citybiz under the title "Effective Internal Communications Starts With Knowing Your Teams."
The piece opens with a scenario product and communications leaders will recognize. Leadership announces a new AI platform, having selected the technology and built a rollout plan. Some employees welcome it. Others ask whether it changes their jobs, whether leadership understands their daily challenges, and why nobody asked for input before choosing a platform they must now use.
Everyone received the same message. Not everyone heard it the same way. The difference is not enthusiasm for technology. It is what employees expect from leadership and the role they believe they should play in decisions affecting their work.
What does the author say teams actually need?
Comsint's argument splits teams into two expectation patterns, and the distinction carries real planning consequences:
- Some teams want clear direction. They expect a leader to decide, explain and define next steps. Open-ended discussion may leave them doubting anyone has a plan.
- Other teams expect to help shape the approach. A detailed announcement delivered after every choice is made can feel like an invitation to comply with something they should have co-developed.
Neither expectation measures commitment or capability, the author stresses. It signals the working relationship the team expects.
Learning those expectations requires conversations, employee feedback and the managers who work with teams daily. An organizational chart will not tell you everything. Do not assume everyone in a department shares the same preferences.
How do you keep facts consistent and conversations relevant?
Organizations need one consistent explanation of what is happening and why — the same facts about decisions, commitments and expectations across the company. That consistency still leaves managers room to make the conversation relevant locally.
The essay's example: a hospital introducing a new scheduling process. Some employees want to know exactly how it works, who is responsible and how conflicts get resolved. Others want to identify problems and shape the process before it takes effect. A strong plan anticipates both. It gives managers clear information and identifies where employees can contribute.
That discipline cuts both ways. If a decision is final, say so and explain the reasoning. If employees can influence implementation, be specific about what remains open. People deserve to know whether they are being asked to understand a decision, help carry it out or help make it.
Inviting feedback also creates an obligation to respond, the author writes. Employees should hear what leadership learned, what changed as a result and why some suggestions could not be adopted.
What should managers know before an announcement?
Managers carry much of the burden. They field the practical questions: What does this mean for us? How will we manage the additional work? Does leadership understand the problem this creates?
Talking points are a starting point, not the deliverable. Before an announcement, managers should understand:
- What has been decided and what remains open
- Why the organization chose this approach
- What employees will need to do
- What support will be available
- How to raise questions and report problems
They also need permission to acknowledge uncertainty. A manager who can say "We haven't resolved that yet, and here is how I'll get an answer" has something useful to offer — and that promise becomes credible when the answer comes back. For communicators, manager preparation belongs in the schedule from the beginning, planned with the same care as the announcement itself.
Why do broad assurances fall flat?
Leadership messages often explain why a change is necessary. Employees also need to understand how they are supposed to make it work. If an initiative requires training, time or new responsibilities, address those needs directly. If resources are unresolved, say so and give a date for the next update.
Confidence grows when people see a workable path forward. Assurances about teamwork and commitment carry limited value when employees are still figuring out who covers a shift or how they learn a new system.
The essay cites research support: a study by Jia Hu and Timothy Judge found that the relationship between leader characteristics and team performance depended partly on teams' expectations about authority, with employee identification with the leader and confidence in the team as important mechanisms. The study examined leadership, not communications campaigns, but the author treats it as a useful basis for thinking about how leaders explain decisions and engage teams.
What should you measure after the announcement?
Email open rates and town hall attendance show whether communications reached people. They do not show effectiveness, the author argues. The harder questions: Do employees understand the decision? Do they know what it means for their work? Do they believe they have the support to carry it out? Were they clear about where they could contribute, and did their questions get answers?
Answers will vary across teams, and that variation is useful. It reveals where managers need support, where an explanation fell short or where an operational problem needs leadership attention. At Comsint, these questions should guide an internal communications assessment, connecting communication quality to the work employees are being asked to do.
The closing principle is blunt: a message can be accurate, polished and widely distributed while still leaving people without what they need. As AI rollouts multiply and change management becomes core product work, the teams that succeed will be those whose leaders close that gap — by knowing their teams, making expectations explicit and staying engaged after the announcement goes out.
via citybiz.co (Source)
More from Marcus Bennett
Show full bio
Market editor covering regulation, policy and their impact on product management at Roadmap File.
56 articles