Intranet adoption: A change management plan that drives use
A new intranet becomes useful when employees know where it fits into their day and feel comfortable using it. Intranet adoption starts with that connection: helping people finish everyday tasks with less searching, fewer repeated questions, and more confidence that they have the right information.
For internal communications, HR, and digital workplace managers, launch day is an important milestone. What comes next is helping those first visits become useful habits.
This guide walks you through a practical plan for communications, training, employee champions, and learning what works after launch.
In this article:
- What should your intranet adoption plan achieve?
- How do you build a communications plan employees will notice?
- What training helps employees use the intranet in daily work?
- How do you recruit and support an intranet champions network?
- Which launch strategy fits your workforce?
- How do you measure intranet adoption after launch?
- How do you turn feedback into sustained use?
What should your intranet adoption plan achieve? {#define-adoption-goals}
Start with the things that make work harder today, rather than the features you want people to explore. Perhaps colleagues struggle to find current policies, miss updates for their location, or ask HR questions because they do not know a useful guide already exists.
Choose a few everyday tasks you would like to make easier:
| Everyday difficulty | What you want to help employees do | What to look at |
|---|---|---|
| Employees find outdated policy copies | Find the approved policy on the intranet | Task-test success and questions about policy versions |
| Team updates disappear in email threads | Check the team update page at an agreed cadence | Return visits and employee feedback |
| HR repeatedly answers the same question | Find a useful answer in the relevant HR guide, with help still available | Guide usefulness ratings and related support questions |
Adoption is about getting something useful done, not simply logging in. A monthly policy lookup may be the right pattern for one role, while another role needs daily operational updates.
Think about your employee groups: their roles, locations, working patterns, languages, and access needs. Desk-based staff, field teams, and shift workers may need different messages and training. If someone cannot reach the portal on an approved device during working hours, another reminder will not solve the problem.
Choose one person to coordinate the adoption plan, then agree how others will help:
- Internal communications: Look after the message calendar and the move between channels.
- HR: Check people-related content and include intranet guidance in onboarding.
- Digital workplace or IT: Take care of access, technical support, and analytics setup.
- Managers: Make time for training and show where the intranet fits into team tasks.
- Content owners: Keep priority pages accurate and current.
Before launch, capture your starting point using existing support data, a short survey, or a few employee task tests. Agree when you will review progress and what improvement would look like for each task.
How do you build a communications plan employees will notice? {#build-communications-plan}
Give employees a reason to try a different way of doing something familiar. “We have a new intranet” announces a platform. “Find the current leave policy without asking which copy is correct” explains how it can help.
Build a calendar around three stages:
- Prelaunch: Explain the problem being addressed, what will change, and when access begins.
- Launch: Share clear access instructions, one useful task, and where to get help.
- Post-launch: Offer useful reminders, answer recurring questions, and share improvements made from feedback.
For each message, note who it is for, how it helps, who will send it, where and when it will appear, and what you are inviting people to do. A frontline team might need a supervisor briefing during a shift handover. An office-based team might find a manager’s message in an existing chat channel more convenient.
Start with channels employees already follow. Keep the main message consistent, but choose examples that fit each group’s work.
Give managers a short briefing kit containing:
- Why the change matters to their team.
- What is changing and what is staying.
- A brief demonstration of a relevant task.
- Where to send access problems and content questions.
- When older routes will stop being updated.
For example, a launch message could say:
Starting Monday, you can find the current leave policy in the intranet’s HR section. Take a moment to find the policy for your location. Having trouble signing in? The service desk can help through the usual help channel.
Make the move away from older channels clear too. Agree dates, identify where the current version will live, and replace outdated copies with links or notices where possible. People should not have to guess which version to trust.
What training helps employees use the intranet in daily work? {#plan-task-based-training}
Help people do something useful during training, rather than asking them to remember a tour of every feature. A few short learning paths built around everyday tasks are a practical starting point.
| Audience | Useful training tasks |
|---|---|
| Employees | Sign in, find a policy, locate a contact, and find relevant updates |
| Managers | Find team resources, share authoritative links, and direct employees to help |
| Content owners | Publish and update pages, check access permissions, and review aging content |
| Champions | Demonstrate common tasks, gather feedback, and direct unresolved issues to the right person |
Keep the teaching pattern simple: show the task, give people a chance to try it, then point them to instructions they can return to later. Leave space for questions and for anyone who needs a little more practice.
Offer several ways to learn:
- Short live sessions with time for questions.
- Captioned recordings and text-based instructions.
- Searchable task guides with clear labels.
- Drop-in help across shifts and time zones.
Check that materials work with assistive technology and the devices employees actually use. Account for language needs, and arrange approved device access for staff without individual workstations. Remember that an office-hours webinar or a personal phone will not be an option for everyone.
Schedule training close to each group’s access date so they can put it into practice straight away. Include the same core tasks in onboarding, and update guides when questions show that a step needs a clearer explanation.
How do you recruit and support an intranet champions network? {#run-champions-network}
Champions give employees someone nearby to ask for help. They can also spot things a central project team might miss, such as a confusing label or a sign-in problem affecting one shift.
Look for approachable colleagues across departments, locations, shifts, and levels of digital confidence. People who understand local routines can be just as valuable as enthusiastic early adopters.
Keep the role clear and manageable. Champions can:
- Demonstrate useful tasks in their team’s context.
- Answer basic questions using shared guidance.
- Note recurring frustrations and suggestions.
- Pass unresolved issues to the right person.
Give champions clear boundaries: they are not expected to replace the service desk or solve every content problem. Agree time commitments with their managers so helping colleagues fits within normal working hours.
Before launch, offer early access, task guides, a shared space for questions, and a simple list of who to contact. Make it clear who handles sign-in failures, incorrect policies, navigation issues, and feature requests.
During launch, hold short, frequent check-ins. Ask what colleagues are finding difficult, which questions keep coming up, and what would make helping them easier. Meet less often as demand settles, while keeping a regular feedback route open.
Recognize specific contributions, such as spotting a broken access path or improving an instruction. Revisit the network as teams change, and invite new people where coverage is missing.
Which launch strategy fits your workforce? {#choose-launch-strategy}
Choose a rollout approach that fits employee access, the shape of your organization, and the support your team can offer. There is no need to make one big announcement if a smaller start gives people a better experience.
| Approach | When it can fit | Main trade-off |
|---|---|---|
| Representative pilot | You need to test assumptions before wider release | Creates room to learn, but an unrepresentative group can hide barriers |
| Phased rollout by team or location | Groups have different needs or support capacity is limited | Spreads support demand, but extends the overlap with older channels |
| Organization-wide launch | Access and core content are ready across the workforce | Creates a shared starting point, but concentrates support demand |
For a pilot, invite employees with different devices, schedules, and levels of digital confidence. Agree what you need to see before expanding, such as people completing priority tasks and critical access problems being resolved.
Before any launch, check that:
- Priority content is accurate, easy to find, and assigned to an owner.
- Employees can sign in from approved devices.
- Permissions protect restricted information without blocking intended users.
- Training materials match the current portal.
- Champions and support teams know their responsibilities.
- Help is available outside the intranet for people who cannot access it.
Give launch activities a practical purpose. Invite employees to find their location’s leave policy or a frequently needed contact, so their first visit helps them do something relevant.
While old and new channels overlap, explain where people should go for the current information. Plan launch-week support around working patterns, including shift changes, and make it easy to report confusing content as well as technical problems.
How do you measure intranet adoption after launch? {#measure-intranet-adoption}
The first announcement may bring people in, but it is worth checking what happens after that first visit. Look at a few measures together to understand where employees are finding value and where they need help.
| Dimension | What to examine | What it tells you |
|---|---|---|
| Reach | Unique active users divided by eligible employees in a defined period | Whether the intended audience is accessing the portal |
| Repeat use | Return visits across relevant time periods | Whether use continues after the initial launch |
| Task completion | Success finding selected information or completing a task | Whether employees can do what they came to do |
| Reported usefulness | Brief surveys and task-specific feedback | Whether employees believe the portal helps their work |
Agree what counts as an “active user” and use that definition consistently. Also distinguish employees who should have access from those whose accounts are already enabled. That way, people still waiting for access do not disappear from the picture.
Page views are a clue, not the whole story. Repeated visits to a policy page might reflect regular use, or they might mean people are struggling to find a clear answer.
Check priority tasks through available analytics, short surveys, or by watching employees try them. Your platform may not record task completion automatically. If you need event tracking, define and test it before relying on the results.
Look for places where a little help or a content change may be needed:
- Search terms returning no results.
- Repeated searches for the same topic.
- Recurring support questions.
- Difficulty finding priority content during testing.
Compare results with your prelaunch starting point, and read them together. Fewer HR questions are encouraging when people are finding answers, not when they have stopped asking because they are stuck.
Look at trends by employee group where privacy safeguards permit. Use aggregate reporting, avoid small groups that could identify individuals, and explain what data is collected and why. The aim is to improve support and content, not monitor individual employees.
Review results weekly during the early launch period. Move to monthly reviews once patterns settle, and agree who will follow up on each significant issue and what they will do next.
How do you turn feedback into sustained use? {#iterate-after-launch}
Make it easy for employees to tell you what is working and what is not, then show them that someone is listening. Combine a visible feedback channel, short pulse surveys, champion conversations, and task testing. Keep another way to ask for help available for people who cannot sign in.
Before choosing a fix, take a moment to understand what is getting in the way:
| Barrier | Example | Possible response |
|---|---|---|
| Awareness | Employees do not know a guide exists | Send a task-focused message through an established channel |
| Access | A shift team cannot sign in | Resolve the account or device issue |
| Skills | Employees do not know how to narrow a search | Update the task guide and demonstrate the steps |
| Content | A policy contradicts another page | Ask the content owner to resolve the conflicting information |
| Navigation | Employees look in the wrong section | Test clearer labels or a different content location |
| Relevance | Updates do not address a group’s needs | Review content priorities with that group |
Prioritize changes by how much they help employees, how often the problem occurs, and the effort involved. Give access and security issues the attention their severity requires, even when only a few people report them. For each agreed action, choose someone to take it forward and a date to check progress.
Try changes with the people affected. If you revise a navigation label, ask them to repeat the original task and see whether it is easier. If you improve a guide, look at related questions and usefulness feedback.
Share short “You said, we changed” updates explaining what you improved and how it helps. When you cannot take up a suggestion, explain why and offer an alternative where possible.
Use these suggested checkpoints to keep the conversation going:
- Day 30: Review access barriers, missing priority content, and immediate training needs.
- Day 60: Look at return visits, recurring questions, and differences between employee groups.
- Day 90: Review progress on your chosen tasks and adjust communications, training, and champion coverage.
Make these reviews part of normal HR, internal communications, and digital workplace planning. Keep adapting as people join, policies change, and teams find new ways to work.
Ready to start?
You do not need a large document to get going. Start with a one-page adoption plan that brings together:
- The employee problems and tasks you want to make easier.
- Employee groups and access needs.
- A lead to coordinate the work and named people to help.
- Communications and training activities.
- Champion coverage and ways to get support.
- The launch approach and readiness checks.
- Starting measurements and review dates.
Choose a few tasks that would make a noticeable difference, then build on what employees find useful.
If you are planning a Drupal-based employee portal, consider Open Intranet, an Open Source system built by Droptica. Explore it with your employees’ tasks, access requirements, and content ownership needs in mind. Software provides the foundation; clear communications, a little practice, and helpful people make it part of everyday work.
Bring your one-page adoption plan to a conversation with the Open Intranet team. We can talk through what your employees need and how to help them get started.
