One powerful way to apply a design thinking mindset to internal communications is to shift from a publishing machine to an iterating system. Iteration as a best practice for internal communications is the most consequential change an internal communications team can make. Especially when feeling overwhelmed or "too busy to overhaul anything," stuck in "order-taking" mode, or trying to more clearly demonstrate their strategic value to the business.
It's the answer to questions like
- how do we get our workload in order?
- how do we prove our value?
- how do we say with certainty the things we are doing are the right things?
- how do we claim the actual impact of what we do, when so many other variables are part of the situation?
- hello? Is this thing on?
Design thinking is a methodology built for product development. It was designed around physical objects and digital experiences — things you can prototype, put in front of users, watch them interact with, and revise. Applying it directly to internal communications requires some translation, but the discipline underneath the methodology transfers almost perfectly. And most internal communications teams are not practicing it.
The discipline is this: treat every communication as a hypothesis (a prototype you're testing) rather than something that is done.
- Before it goes out, be clear about what you expect it to accomplish.
- After it goes out, find out whether it did.
- Let what you learn change what you do next.
That loop — intent, signal, adjustment — is what separates an internal communications team that is strategically improving from one that is producing.
Most teams are producing. They are good at it. They are often exhausted by it. And because production is what they have learned to measure, it is what they optimize for, quarter after quarter, without much evidence that the volume of output is doing what they need it to do.
No blame here - this is not a character failure. It is a rational response to a measurement vacuum. When no one has established what good looks like beyond content out the door, volume becomes the proxy for value. The team looks busy; the calendar is full; the intranet is updated. Whether any of it changed anything is a question that tends not to get asked. Did an employee understand something they did not understand before? Do managers now feel equipped to have a conversation they would otherwise have avoided? Is this change initiative gaining traction it would not have had otherwise?
What Publishing Mode in Internal Communications Looks Like
An internal communications team in publishing mode has a predictable rhythm. Content is requested, briefed, produced, approved, distributed, and filed. The next request enters the queue. The team's value is demonstrated by throughput: how many emails went out, how many articles were published, how many all-hands events were supported, how many channels were fed.
In publishing mode, every communication is implicitly treated as final. Once it has been sent, the work is done. There is no designed mechanism for finding out whether it landed: no feedback loop, no measurement against a stated intent, no conversation with the employees who received it. The team moves on.
The consequence is that the team learns very slowly, if at all. The all-hands format that employees find too long and too one-directional runs the same way for three years because no one has asked employees what they want from it. The newsletter sections named after internal departments go unread by employees who cannot connect department names to anything relevant in their daily work. The cascade that leaders believe is reaching frontline workers stops two levels down because managers do not have the context or tools to carry it further and no feedback mechanism exists to surface that gap.
Meanwhile, the team produces more and more and more. The calendar stays full. And the distance between what the internal communications function is capable of producing and what it is actually accomplishing quietly widens.
Volume becomes the proxy for value when no one has established what good looks like beyond content out the door.
What Design Thinking Iteration in Communications Looks Like in Practice
The move from publishing mode to a more iterative approach does not require a methodology overhaul or a new measurement framework before anyone can start. You don't even have to use a multisyllabic word like "iteration." It starts with a simpler change: adding the question after.
For example: once a communication has gone out, something — however lightweight — is designed to find out whether it worked. A short pulse survey after an all-hands. A manager roundtable two weeks after a major announcement, to learn what questions employees were actually asking. Analytics on what content employees are clicking versus scrolling past. A handful of informal conversations with employees in different roles and locations about what they understood from a recent communication and what remained unclear.
The signal does not have to be sophisticated to be useful. What it has to be is intentional. Someone has to decide, before the communication goes out, what signal they will look for afterward, and someone has to be responsible for acting on what that signal shows.
Here is what that looks like in three examples, each from organizations we've helped make this shift.
When You're Already On to Something, You Just Had to Ask
One large enterprise had an extensive internal communications ecosystem: newsletters, a digital intranet, town halls, manager cascade, all-staff emails, a social platform. In assessments across every level of the organization, one communication vehicle was named unprompted by employees more than any other. It was a simple, regular update called "We Did It" — a consistent, easy-to-digest format that celebrated client wins and made visible the work the organization was doing in the world. Employees in every focus group mentioned it. They looked forward to it. They shared it.
Every other channel was struggling. The intranet had search problems. The all-staff emails were too long. The manager cascade was unreliable. The social platform had low adoption. But "We Did It" worked, and employees had been saying so, in their own way, for as long as it had existed.
The insight was available. What was missing was the practice of treating it as a signal: asking why this one worked when others did not, identifying the specific qualities that made it land (transparent, consistent cadence, easy to digest, globally visible), and applying those qualities deliberately to other communications. The organization had stumbled into something effective. A product mindset would have studied it - and that curiosity would have lead to insights that could improve other activities and tactics.
When Simply Asking Reveals the Parts are There, You Just Need to Adjust Them
A second organization ran an all-hands meeting in roughly the same format every quarter: prepared remarks from the CEO, a financial update, a few slides from department heads, thirty minutes for questions. Clockwork. And the reliability of it cranking out each quarter was the measure of success. One adjustment: asking. After one all-hands, a simple post-event survey was sent. The responses were consistent: employees wanted the prepared remarks shorter, wanted more time for questions, and wanted to hear from peers as well as leaders.
The next all-hands was restructured. Prepared remarks were cut by a third. A peer recognition segment was added. The Q&A block was extended, with a mix of live and pre-collected questions which produced more substantive give and take. Post-event satisfaction scores went up. More employees said they left with something actionable.
None of this required a significant investment. It required asking, then adjusting.
When asking helps reset from "bureaucratic brain" to "audience brain" and leads to a measurable improvement
A third organization had a company newsletter organized around internal departments: an HR section, a Finance section, an Operations section, an IT section. Employees read their own section and skipped the rest. The newsletter was producing content - a lot of it. lt was genuinely a win to have leaders engaged enough to participate in contributing content. But it was not producing organizational awareness.
The sections were renamed to reflect the organization's strategic priorities rather than its reporting structure. The HR section became the section about how the organization takes care of its people. The Finance section became the section about what the organization is building toward. The names were not there to please any department head. Instead, they were there to answer the question an employee brings to any piece of content: why does this matter to me?
Readership of sections other than the employee's own immediate area increased. More importantly, the organization had demonstrated, in a small and concrete way, that it was possible to change how communications were organized based on what employees actually needed from them.
The Three Moves that Create a Value Loop for Internal Comms
Across organizations that have made this shift, three practices appear consistently. They are not complex. But they don't just happen unless you are intentional.
1.
State the Intent.
Before a communication goes out, be explicit about what it is meant to accomplish.
Not just: what it will say. But also: what it will change. An employee who reads this will understand X. A manager who receives this will be equipped to do Y. A team that sees this will feel Z about the organization's direction.
The intent does not have to be elaborate. But it has to exist, and it has to be specific enough that you can later find out whether it was achieved.
2.
Design for signal.
Decide, before the communication goes out, what you will look for afterward. What will tell you it worked? What will tell you it did not?
The signal can be formal (a survey, analytics data, a structured debrief) or informal (conversations with employees, a question in the next manager roundtable, feedback from the team that will be asked to cascade the message).
The mechanism matters less than the intention: you are not done when the content goes out.
3.
Let the signal change something.
This is where most teams stop short. Signals are gathered (sometimes!) but the loop does not close because no one is responsible for acting on what it shows. The all-hands survey results sit in a folder. The analytics data shows low readership on a particular section and no one investigates why.
The gap between what was intended and what happened is noted and forgotten. Closing the loop means assigning someone to review the signal, draw a conclusion, and carry that conclusion into the next iteration of the communication. Not perfectly. Not comprehensively. Just consistently.
Your Constraints Are Real So: Start Small
Design thinking as a formal methodology assumes a degree of time and structural permission that most internal comms teams do not have. The fire drill is real. The request queue is real. The expectation that the team will produce a certain volume of content, on a certain cadence, regardless of whether anyone is measuring its effect, is also real. But you can start today.
In the absence of having the blessing to entirely reset/rethink your approach from top to bottom (we help with that too!), this is why we suggest that internal comms teams start with something smaller and more achievable than a wholesale redesign of their entire approach: pick one communication and run the loop. One all-hands, one newsletter, one cascade. State the intent before it goes out. Design one mechanism for signal after it goes out. Act on what the signal shows.
That one loop, run honestly, tends to produce two things. First, a finding. They have something specific that can be improved, and evidence that improving it matters. Second, a change in how the team relates to its own work. Once you have asked whether something worked and changed something based on the answer, the question becomes harder to stop asking. The publishing reflex does not disappear, but it gets interrupted.
Over time, this grows and compounds. Teams that practice this learn faster than teams that do not. They get better at anticipating what will and will not land. They develop the institutional knowledge that comes from actually tracking whether their work is doing what they designed it to do. And they build the credibility with leadership that comes from being able to say, in specific terms, what is working and why.
A Note for Executives
If your internal communications team is producing a lot and you are not sure what it is accomplishing, that is worth examining. Without blame. The team is most likely working exactly as the system has trained it to work. Volume is what the system has learned to reward, because volume is what has been visible and countable.
The shift toward an iterative approach requires one thing from leadership that it cannot generate on its own: permission to measure differently. Permission to spend some of the time currently used for production on the question of whether what was produced last time worked. Permission to change formats and approaches based on what employees say they need, even when that means doing something differently than it has always been done.
That permission, granted explicitly and sustained over time, is what allows the publishing reflex to give way to something more useful. It does not require a large investment. It requires a clear signal that the organization values communication that works over communication that is simply present.
FAQs
Q: What are internal communications best practices for measuring effectiveness?
The most effective internal communications teams measure against stated intent rather than volume produced. Before any communication goes out, they document what it is meant to accomplish: what an employee will understand, what a manager will be equipped to do, what behavior the communication is designed to support. After it goes out, they gather signals through surveys, analytics, manager feedback, or informal employee conversations and act on what those signals reveal. Volume metrics (emails sent, articles published, events held) are easy to count but tell you nothing about whether the communication worked.
Q: How do you improve internal communications without overhauling the entire program?
Start with one communication and run a single loop: state the intent before it goes out, design one mechanism to gather signal afterward, and change something based on what the signal shows. This can be as simple as a short post-event survey after an all-hands, or informal conversations with employees two weeks after a major announcement. The goal is not a perfect measurement system. Instead focus on cultivating the habit of asking whether communications are working and letting the answer change the next iteration.
Q: Why do internal communications teams focus on volume rather than impact?
Volume is a rational response to a measurement vacuum. When no better measure exists for what good looks like, the team optimizes for what is countable: content produced, emails sent, events supported. This is not a character failure. It is what happens when a function has not been given clear outcome metrics. The shift toward impact measurement requires two things: a practice of stating intent before communications go out, and organizational permission to spend time on signal-gathering rather than sheer production for the sake of it.
Q: What is the difference between a publishing mindset and a product mindset in internal communications?
A publishing mindset treats every communication as final once it has been sent. The work is done when the content goes out. A product mindset treats every communication as a hypothesis: it was designed to accomplish something specific, and whether it accomplished that thing is a question that gets asked and answered. The practical difference is a feedback loop: a designed mechanism for learning whether the communication worked and carrying that learning into the next iteration.
Q: How can internal communications teams demonstrate their value to leadership?
The most credible way is to be specific: show what a communication was designed to accomplish, show what happened as a result, and show what changed based on what you learned. This requires the iterative practice described above: stating intent, gathering signal, acting on findings. Teams that can do this in concrete terms earn a different kind of credibility than teams that report on volume. They can speak to what their work produced, not just what they produced.
Where Internal Comms Teams Can Start
If you are an internal communications practitioner looking for an entry point, a newsletter rename or an all-hands pulse are both low-risk starting places. Look for something small enough to run without organizational approval, but concrete enough to produce a finding you can point to.
If you are a leader wondering whether your internal comms function is operating in publishing mode, the most direct diagnostic is a simple question: ask the team to show you the last time a communication did not work the way they intended, what they learned from it, and what they changed as a result. The quality of the answer will tell you more about how the function is working than any content audit.
If the broader question — whether your internal communications program has the architecture it needs to produce coherent, audience-centered communication at scale — is on your mind, we’d be happy to discuss.
And if an objective assessment of where your program stands would be useful, that is what our ICIQ™ diagnostic is built to provide.