_edited.jpg)
What communication strategy actually does
Communication strategy is the thinking that helps work hold together.
It defines what the communication is trying to achieve, who it is for, how it should be structured, and what needs to remain consistent as the work develops. Without that layer, even strong design can become reactive, fragmented or difficult to sustain.
This kind of work often involves
-
Clarifying the communication objective
-
Shaping structures that support clarity across multiple outputs
-
Building systems that help teams work more consistently
-
Identifying what should remain fixed and what should stay flexible
-
Connecting strategy to practical delivery
-
Creating frameworks that can adapt as projects evolve
Visual systems sit within this, not separately from it. A strong system is one of the ways strategy becomes usable. It helps protect the core idea, the brand, the narrative or the communication goal while allowing the work to scale more efficiently.
What communication strategy actually does
Communication strategy is the thinking that helps work hold together.
It defines what the communication is trying to achieve, who it is for, how it should be structured, and what needs to remain consistent as the work develops. Without that layer, even strong design can become reactive, fragmented or difficult to sustain.
This kind of work often involves
Clarifying the communication objective
~
Shaping structures that support clarity across multiple outputs
~
Building systems that help teams work more consistently
~
Identifying what should remain fixed and what should stay flexible
~
Connecting strategy to practical deliver
~
Creating frameworks that can adapt as projects evolve
Visual systems sit within this, not separately from it. A strong system is one of the ways strategy becomes usable. It helps protect the core idea, the brand, the narrative or the communication goal while allowing the work to scale more efficiently.
Shaping Communication Strategy for Scale and Impact
The Clarity Triangle
Why it matters
As work expands, communication often becomes harder to manage well.
Different teams produce content in different ways. Standards slip. Messaging drifts. Useful assets are duplicated or lost. Production becomes overly manual. The work may still be strong in parts, but the overall communication becomes less efficient, less consistent and less effective.
This matters because poor structure does not only affect appearance. It affects:
-
How quickly teams can work
-
How clearly information is communicated
-
How consistent the output feels across touchpointsHow easily communication can be maintained or updated
-
How much confidence the work creates internally and externally
Good strategy gives the work direction. Good systems help that direction survive real conditions.
Why it matters
A lot of important work loses impact because the information is hard to follow.
That does not mean the thinking is weak. It usually means the communication is doing too much at once, or not enough of the right things. Pages become crowded. Relationships between ideas get buried. Comparisons become difficult. Technical language overwhelms the wider message. Stakeholders leave with partial understanding rather than real confidence.
This matters because important decisions are often made under pressure, with limited time and mixed levels of expertise in the room.
When information is designed well:
Technical work becomes easier to review
~
Options become easier to compare
~
Teams can align more quickly
~
Public-facing communication becomes more accessible
~
The message lands with greater confidence and credibility
Good information design supports understanding. Great information design supports action.
How I approach it
My process usually begins by looking at the wider communication context rather than jumping straight into outputs.
-
What is the work trying to achieve?
-
Who needs to use it, understand it or contribute to it?
-
Where is the process breaking down?
-
What needs more structure, and what needs more flexibility?
-
What would help this communication stay coherent over time?
From there, I shape a strategic response that can support both clarity and delivery.
That might involve:
-
Defining the communication framework for a complex project or programme
-
Building a visual system that can hold together across formats and teams
-
Creating template structures that reduce friction and improve consistency
-
Introducing automation where repetitive production is slowing things down
-
Developing guidance, toolkits or internal resources that improve capability
-
Creating approaches that can be tested, refined and expanded over time
This is where agile thinking becomes useful. Rather than creating something rigid and final too early, I tend to build frameworks that can respond to real-world use, changing needs and evolving delivery pressures. The aim is to create systems that are strong enough to guide the work, but flexible enough to stay useful.
How I approach it
My process usually begins before any visual decisions are made.
First, I look for the structure inside the content. What is the core message? What is the user trying to understand, compare or decide? What is essential, and what can be simplified, grouped or reframed?
From there, I shape the communication around usability.
That might mean:
Creating hierarchy so the reader knows where to look first
~
Restructuring content so it flows more logically
~
Breaking complexity into clearer parts
~
Designing systems that allow comparison at a glance
~
Using visuals to reveal relationships that would otherwise stay hidden
~
Creating formats that work in the real context they will be used in
Sometimes that output is static. Sometimes it is interactive. Sometimes it is a one-off infographic. Sometimes it becomes a scalable template or automation system that can support a whole programme of work.
The format changes. The principle stays the same: make complexity easier to understand and more useful to the people who need it.
Strategy, Systems and Scalable Communication
Strong communication is not only about how something looks. It is about how clearly it is directed, how well it is structured, and how effectively it can hold together as projects grow in size, speed and complexity.
This is where strategy becomes essential.
I work on the thinking that sits behind communication systems, helping shape the objectives, structure and frameworks that make work more coherent, consistent and scalable. Sometimes that means defining how a programme of work should be organised and communicated. Sometimes it means building the systems, tools or templates that help that strategy function in practice. Sometimes it means introducing more agile ways of working so communication can evolve without losing clarity or intent.
The goal is not to standardise everything. It is to create stronger foundations so communication can move faster, stay aligned and maintain quality over time.
Where this adds value
This type of work is especially valuable when:
projects involve multiple teams, disciplines or contributors
~
communication needs to scale across many outputs
~
quality and consistency are hard to maintain
~
workflows are too manual or inefficient
~
teams need clearer structures to support better communication
~
strategy exists, but is not yet translating into repeatable delivery
It often applies to:
Reports and publications systems
Internal communication hubs
Visual guidance platforms
Presentation systems
Technical note frameworks
Playbooks and repeatable communication products
Automated document workflows
Brand and asset toolkits
In practice, this is often where strategic thinking has the greatest operational effect.
Creating structure without losing the point
A lot of communication strategy sounds right in theory but falls apart in delivery.
It becomes too vague to guide decisions, too rigid to adapt, or too disconnected from the realities of how teams actually work. That is why I see systems and agile delivery as part of the same conversation, not separate ones. Strategy needs a form it can live inside.
When the framework is clear, the work becomes easier to build, easier to maintain and easier to scale.
The best systems do not flatten creativity or over-control the work. They protect what matters most.
They help teams move faster without losing clarity. They improve consistency without removing flexibility. They reduce friction without weakening the original objective.
If communication needs to grow, repeat or operate across multiple people and outputs, then the structure behind it matters.
That is where strategy, systems and agile thinking start to create real value.
_edited.png)