Intranet audit vs discovery: why internal comms teams keep building the wrong thing
It’s a familiar story. A new intranet launches. Stakeholders are aligned. The design is clean. Content has been reviewed, rationalised and migrated carefully.
But then… nothing happens.
Engagement is low. Employees still rely on email. Important updates are missed. Workarounds quickly reappear.
One organisation we worked with employed hundreds of staff who spent most of their day on the road, doing maintenance. Leadership assumed the solution was simple – create a tablet-optimized intranet and point everyone to it.
On paper, this seemed like a good solution. But our research revealed a different story: that there was one device per vehicle, not per person, forcing people to share and navigate a clunky login process.
Worse, staff had no natural opportunity to check it. These employees spent their working day behind the wheel, and it’s illegal to use a device while driving. Their only real window was when they’d parked up at the end of a shift – by which point accessing the intranet was competing with going home.
The official channel wasn’t helping people work better – it was getting in the way.
But why does this keep happening?
In many cases, the problem isn’t execution – it’s where the work started.
Most internal communications teams begin with an intranet audit – when what they actually need is discovery.
Begin by looking at what you have, you’ll optimise the present. Start with what people need, you might actually change it.
What an intranet audit tells you
An intranet audit is often the default starting point for internal comms projects.
It typically includes:
content inventories
channel and platform reviews
analytics snapshots
assessments of structure, ownership and governance
Done well, this work is valuable. It helps teams establish a baseline, reduce duplication and improve consistency.
But an audit has a built-in limitation – it’s essentially a supply-side exercise and tells you what your organisation has, not whether it works for the people who use it.
Think of it like checking what’s in your fridge. You can see what you have and what’s missing, but you don’t know who’s hungry or what they actually want.
What discovery does differently
Discovery starts from a different place.
Instead of focusing on content and channels, it shifts perspective to people and the work they do.
Discovery asks:
what are employees trying to do?
where do they get stuck?
when does communication help – or get in the way?
This is a demand-side view, grounded in user needs, tasks and barriers to effectiveness.
You can’t fix comms if you don’t know what’s broken.
Discovery reveals unmet user needs, friction in everyday work and gaps between official channels and real behaviour
That’s why discovery should underpin any internal communications strategy – not sit alongside it.
Audit vs discovery: a simple way to see the difference
Audit and discovery are often treated as interchangeable.
But they’re not, and they answer fundamentally different questions:
Audit asks: what content do we have?
Discovery asks: what do people need to do?
Where an audit maps channels and optimises supply, discovery maps the work itself and reveals where demand is going unmet.
Audits improve what exists, while discovery questions whether it should exist at all.
This distinction is what shapes outcomes.
Why audits alone lead to the wrong outcomes
When teams rely on audits without discovery, they tend to optimise the current system rather than rethink it.
That leads to familiar patterns such as legacy structures being preserved, migration taking priority over transformation and a focus on visible content rather than invisible friction.
Audits also miss what isn’t there, including:
tasks with no supporting content or channel
barriers that slow people down
workarounds employees rely on to get things done
The result? A neater, more organised intranet that still doesn’t help people do their jobs.
It’s not a step forward – it’s just organising your existing mess better.
What discovery reveals that audits can’t
Discovery gives you a clearer picture of how communication actually works across an organisation.
It surfaces barriers, unmet needs and gaps between systems. Crucially, it also reveals real behaviour and the informal networks people rely on.
In practice, this might include:
critical tasks unsupported by any channel
over-reliance on email as a workaround
shadow IT, where unofficial tools fill the gaps
repeated questions that signal systemic issues
Discovery helps you map the real digital workplace – not just the official one. That’s what you need if you want to design something that works.
How to run discovery without overcomplicating it
Discovery doesn’t have to be slow or resource-heavy.
A practical approach combines lightweight and structured methods, including:
surveys to identify patterns
interviews to explore real experiences
analytics to understand behaviour
heuristic reviews to assess channels
inbox sampling to see what people actually receive
Alongside this, there’s a more informal layer of guerilla research, which can include:
shadowing or ‘day in the life’ observation
watching how people use Teams or Slack
noting repeated questions in meetings or chats
You don’t need to be a UX researcher to run discovery, but you do need to challenge your assumptions.
Why teams skip discovery
Despite its value, discovery is often skipped.
This is mostly because an audit just feels easier – it’s faster, more tangible and easier to align with platform timelines and procurement.
There’s also pressure to move quickly, especially when stakeholders are focused on delivery.
Discovery, by contrast, can feel slower and less concrete.
But skipping it creates a false sense of progress. You move faster, but in the wrong direction.
The right sequence: discovery, then audit, then design
The goal isn’t to replace an audit with discovery, it’s about using them in the right order:
Discovery identifies needs, barriers and opportunities
Audit assesses what currently exists
Design bridges the gap between the two
This sequence allows you to prioritise effectively, identify quick wins and build a roadmap grounded in real needs – not assumptions.
Practical ways to get started
You don’t need a large programme of work to begin discovery.
Start small and:
run 10 interviews across different roles
review a week of inbox traffic
map the top five tasks employees need to complete
If you’ve already completed an audit, revisit it with a new lens and ask: What problem does this content actually solve?
That question can change how you interpret everything.
Discovery isn’t a phase – it’s a discipline
Discovery isn’t something you do once at the start of a project. It’s an ongoing practice.
It helps you stay connected to how work is changing, builds trust with employees and keeps your communications relevant over time.
Done well, it shifts the role of internal comms: from managing content to enabling work
If you only audit what you have, you’ll build more of it. If you discover what people need, you’ll build something that works for everyone.
Digital Communications at Work dives deep into discovery, and will help you to understand how it earns trust, focuses effort and helps you deliver comms that actually work.
