A practical checklist for publishing Intranet content during transformation

Publishing intranet content is a core part of most transformation programs. New systems, new processes and new ways of working all require employees to find information, understand what is changing and take action with confidence.

Done well, intranet content supports employee self-service, reduces support requests and helps people navigate change successfully.

The challenge is rarely intent.

Project teams are often working under significant delivery pressure. Content gets created quickly, published wherever there is space and rarely considered as part of the broader information ecosystem.

The result becomes familiar.

Guidance overlaps. Old content remains live. Duplicate information appears in search results. Ownership becomes unclear and content gradually loses trust.

This checklist is designed to help transformation teams create content that supports change today and remains valuable once the project has finished.

1. Treat publishing as a design decision, not an admin task

Publishing is not simply uploading a page or attaching a document.

Every publishing decision affects:

• Where employees expect to find information.

• What appears in search results.

• How easy content is to understand.

• Who will maintain it in the future.

• Whether employees trust what they find.

If the decision will still matter after go-live, it deserves design consideration.

This is one of the principles behind content design. Publishing should be informed by user needs, existing content and long-term ownership, not just project timelines.

2. Start with what already exists

One of the fastest ways to create confusion is to publish new content without understanding the current environment.

Before creating anything new, understand:

• What guidance already exists.

• Where employees currently go for help.

• What content is duplicated.

• What content is outdated.

• What content is genuinely helping users.

Conducting a content audit before publishing helps avoid creating multiple sources of truth. If you’re short on resources, look outside the project team. Is there a team coordinator or assistant who has capacity to compile an audit for you?

If existing content is not being reviewed, retired or updated, new content may simply add to the very problem the project is trying to solve.

3. Design around real tasks, not project structures

Employees rarely think about transformation programs the way project teams do.

They are not looking for program workstreams, project streams or implementation phases.

They are trying to complete tasks.

Simple questions can help guide content decisions:

• What is the employee trying to do?

• What information is needed at that moment?

• Where would they expect to find it?

• What action should they take next?

Rather than asking, "Where should we publish project content?" ask, "What is the employee trying to achieve?"

In many cases, the right answer is updating an existing operational page rather than creating an entirely new project site.

This approach strengthens employee self-service and reduces the effort required to find information.

4. Choose formats that reduce effort

One of Steve Krug's most famous usability principles is simple:

"Don't make me think."

The same principle applies to intranet content.

In most situations:

• Use web pages rather than documents.

• Write for scanning rather than detailed reading.

• Put critical information first.

• Minimise unnecessary clicks.

PDFs often create friction. They are harder to scan, harder to maintain and harder to govern over time.

Where documents are necessary, they should support web content rather than replace it.

Organisations using SharePoint and Microsoft 365 also have opportunities to replace many traditional documents with more dynamic and maintainable solutions.

5. Integrate content into the future state

One of the most valuable questions a project team can ask is:

"Where should this content live when the project becomes business as usual?"

The answer should directly influence publishing decisions.

In practice, this often means:

• Updating existing pages

• Embedding guidance into operational content

• Extending current navigation structures

• Avoiding temporary project-only destinations

This reduces duplication and supports a more sustainable digital workplace.

6. Agree ownership before go-live

Every page and document should have:

• A named owner

• A clear purpose

• A review cycle

• An agreed maintenance approach

If nobody is prepared to own the content after go-live, that should raise questions about whether it should be published at all.

Ownership is a critical part of effective content governance.

Without ownership, content eventually becomes outdated, duplicated or abandoned.

7. Work in partnership, not in isolation

Transformation teams play an important role in identifying content needs, understanding impacts and helping employees navigate change.

However, they are rarely the people who will own content long-term.

Successful projects involve ongoing collaboration with business-as-usual teams.

This includes making joint decisions about:

• Page structure

• Content placement

• Retirement of legacy content

• Ownership arrangements

• Governance expectations

This approach reduces rework and helps protect the long-term quality of intranet content.

8. Think about search from day one

Many employees search before they navigate.

That means every new page, document and heading influences the search experience.

Poor publishing decisions can create duplicate search results, conflicting information and unnecessary noise.

When publishing content, consider:

• What employees are likely to search for

• What should appear in search results

• Whether similar content already exists

• How long the information is likely to remain relevant

Good searchability starts with good content decisions.

Final thought

Transformation projects succeed when people can understand what is changing and confidently take action.

That doesn't come from publishing quickly and moving on.

It comes from creating content that supports real tasks, integrates with existing employee experiences and remains sustainable after project teams leave.

The goal is not to publish more content. The goal is to leave the intranet clearer, easier to navigate and more useful than you found it.

When organisations combine content design, employee self-service, content governance and effective technology adoption and change management, transformation content becomes an asset rather than technical debt.