In short
Skip the feature wish list. Group your intranet requirements by the jobs employees, editors and admins actually do, prove each in a scripted demo with your own content, and cross-check the shortlist against the 17 criteria of Tryane's Digital Workplace Benchmark 2026.
Key takeaways
- NN/g found employees completed intranet tasks in 78 seconds on centrally managed intranets versus 123 seconds on distributed ones.
- Only Unily and Poppulo were rated 5/5 on Analytics / Insights in Tryane's Digital Workplace Benchmark 2026.
- SharePoint scored 45% on Analytics in Tryane's Digital Workplace Benchmark 2026, the lowest category score of the 12 platforms rated.
- Microsoft advises piloting one key intranet scenario and judging success on business impact, not system metrics.
- NN/g credibility guidance: require a publication date, a last-updated stamp and a named owner on every intranet page.
Group your intranet requirements by job, not by feature
Most intranet requirement documents we see start as a feature wish list: carousel, chatbot, employee app, dark mode. That list collapses the moment two vendors demo side by side, because every platform can tick every box in a scripted environment. What separates platforms is not whether a feature exists but whether it does the job your employees and your communication team actually need done. So we recommend a different structure: write every requirement against one of five jobs an intranet must support.
- Find: employees locate the policy, form or person they need in a few clicks, using navigation built on their tasks and their words.
- Publish: your comms team dates every item, stamps every page with a last-updated date and a named owner, and runs an approval step before anything goes live.
- Target: the right message reaches the right department, country or role, including deskless workers, without manual distribution lists.
- Administer: roles, multilingual capacity and authentication are managed securely inside your Microsoft 365 governance model.
- Measure: you can report who actually read what, by audience segment, across all your channels in one place.
This framing is not ours alone. Nielsen Norman Group's intranet research, based on usability testing of 57 intranets over 18 years, keeps finding that successful intranets are organised around what employees do, not around how the org chart is drawn[1]. The same discipline applies to procurement: group requirements by job, then commit to proving each job in a scripted demo with your own content. If you are a Digital Workplace or IT manager evaluating platforms on Microsoft 365, the five jobs above are the scope of this article. We take them one at a time, then cross-check the list against an external benchmark of 17 criteria.
Can employees find what they need?
Findability is the first job because every other job depends on it. NN/g's 2024 intranet guidelines are explicit: build your information architecture and navigation on the tasks employees perform on the intranet and the terms they use to describe those tasks. Organising content by department makes information hard to find, and vague category labels leave employees struggling[1]. Labels like 'Benefits, pay, and time' or 'Apps and tools' work because they describe a task, not an org unit.
The structure behind the navigation matters as much as the labels. In the same research, employees completed tasks in an average of 78 seconds on intranets with centrally managed content, against 123 seconds on distributed models, a statistically significant difference[1]. For your requirements, that translates into a governance question: who owns and edits the top-level navigation and the pages behind it? The Scottish Government's intranet team is a useful model. They ran user research, card sorting and tree testing to structure their information architecture, and their intranet ranked in the top three of fifteen studied for task-completion rates[1].
Search is the second half of the find job. NN/g found that a single search field is now the baseline, because employees bring search expectations from the public web[1]. Search success rate is also one of the KPIs worth tracking once the intranet is live, alongside reach by audience segment intranet KPIs.
Then test it in the demo. Do not accept the vendor's sample content. Bring three real tasks your employees fail at today and watch an employee, not a product specialist, complete them.
- Find the parental leave policy using only the navigation, phrased as an employee would say it.
- Find the travel expense tool using only search, starting from the words employees type.
- Find the right contact for a facilities issue in a specific office.
What should publishing requirements cover?
Publishing is where credibility is won or lost. In NN/g's reflection on two decades of award-winning intranets, credible content is one of the defining elements of the most successful intranets, and credibility has concrete, checkable ingredients[2]. Write these into your requirements rather than treating them as editorial good intentions.
- A publication date on every news item.
- A last-updated date on every page, not only on news.
- The name of the page owner, with contact information, so the source of every piece of content is known and findable.
- An approval step before content goes live, so a named editor is accountable for what employees read.
- No content duplication: write it once, link to it from many places.
- Archiving of old, unused content and removal of incorrect content.
Each of these comes straight from NN/g's credibility research, which also notes that employees doubt news articles and look for the static page behind them, so dated, owned pages are what make the intranet a trusted source[2]. For you as an IT or Digital Workplace manager, the approval step and the owner field are also governance controls: they tell you who touched what, which matters when a compliance-sensitive message goes out.
Test the whole chain in the demo by publishing your own news post. Draft it, submit it for approval, approve it, publish it, and then check the rendered page: is the date visible, is the owner named and contactable, is the old version archived? A vendor demoing with their own polished sample content will pass this test trivially. Your own draft, with your own approval workflow, is the honest version. If the publishing flow needs five clicks and a training session, your comms team will route around it, and the credibility requirements above will quietly stop being met.
Which criteria did Tryane's 2026 benchmark use?
Once your requirements are grouped by job, you need an external yardstick to cross-check them. The Digital Workplace Benchmark 2026 evaluates 12 digital workplace and intranet platforms, including SharePoint, Unily, Poppulo, Staffbase and Workvivo, against 17 criteria in five categories. The report presents each criterion as a rating out of 5, and each category as a percentage, and the two are reported separately. Here are the 17 criteria as printed in the report.
| Category | Criteria |
|---|---|
| UI/UX | Look and Feel, Customizable User Interface, Interaction with News, Interoperability with Other Environments, Mobile Experience, Supports the Daily Work, Video Integration |
| Publishing | Rich Content Creation, Preview & Publish Content |
| Targeting | Specific Audience Targeting, Highlight top Updates, Adapt Content to Profiles, Deskless Workers Exp |
| Administration | Admin Role Management, Multilingual Capacity, Ease of Authentication |
| Analytics | Analytics / Insights |
The mapping to the five jobs is direct: UI/UX and Publishing cover find and publish, Targeting covers target, Administration covers administer, and Analytics covers measure. On the measurement criterion, only Unily and Poppulo were rated 5/5 on Analytics / Insights, while SharePoint was rated 2/5 on that criterion and scored 45% on the Analytics category, the lowest category score any of the 12 platforms received. Treat these figures as Tryane's assessment based on demonstrations, expert interviews and public data, not as independent test results, and read criterion ratings and category percentages as two separate scales.
Download the full Digital Workplace Benchmark 2026 to compare all 12 platforms by category and see which ones fit the jobs you prioritised.
What should measurement requirements include?
Measurement is the job where generic requirements do the most damage, because 'reporting dashboard' is a phrase every vendor can claim. Make the requirement specific: you need readership broken down by department, country and role, viewed across all your channels, email newsletters, the SharePoint intranet, Viva Connections and Viva Engage, in one central place rather than per platform. That is what lets a comms team answer whether a message landed with frontline workers in one country, not just how many views the page collected. Native SharePoint reporting is free and already on, but it reports per site and per platform, which is exactly why comms teams end up stitching exports together in Excel.
- Readership segmented by department, country, language and role, drawn from your Microsoft 365 directory attributes.
- One cross-channel view covering email newsletters, SharePoint intranet, Viva Connections and Viva Engage.
- Trend data over time, so you can see whether adoption holds after launch rather than spike and fade.
- Reporting your comms team can produce without an analyst, because a report nobody builds is a requirement nobody meets.
Ground the adoption side in benchmarks rather than guesses: measuring unique authenticated readers instead of raw page views is what makes adoption numbers comparable over time SharePoint adoption benchmarks.
Microsoft's own planning guidance for SharePoint intranets sets the standard for how to validate the measurement requirement: pilot one key scenario and judge it on actual business impact, not system metrics[3]. Page views and click counts are system metrics. 'Help requests to HR went down' is business impact. Write that distinction into your requirements document, because it decides what you ask to see in the demo.
Script a demo that proves your requirements
A requirement you have not seen demonstrated is a claim, not a fact. Script the demo so each of the five jobs gets one task, performed on your content, with your audiences, by your people. Microsoft's pilot guidance gives you the selection criteria: pick scenarios where a prototype can be built quickly, there is a committed sponsor, there is enough up-to-date content, and there is a specific pilot audience[3]. The same criteria work for a vendor demo, and they are the backbone of a proper pilot if you take a shortlist further building a SharePoint intranet.
- Find: an employee locates a policy via navigation and search, using your navigation labels and your search index.
- Publish: a member of your comms team drafts a news item, routes it through your approval step, publishes it, and the page shows date, last-updated stamp and named owner.
- Target: the same item is targeted to one department and one country, and a test account outside that audience confirms it does not appear.
- Administer: your IT admin creates a role, checks multilingual settings and confirms authentication runs through your existing Entra ID sign-in.
- Measure: two days later, the comms lead opens the reporting view and breaks readership of that item down by department, country and role, across channels, in one place.
For each scenario, define success in business terms before the demo, using Microsoft's 'I know this is successful when' formulation[3]. For the measurement task, that line might read: 'I know this is successful when I can tell leadership what share of the target department read the announcement, without exporting anything to Excel.' If a vendor cannot complete a task live on your content, you have learned more than any feature matrix will tell you.
Most checklists we review are strong on find, publish, target and administer, and thin on measure, because measurement is where native Microsoft 365 reporting stops. If your comms team is asking for readership by department, country and role across channels, that requirement will not be met by site-level page views alone.
In short: one central dashboard, readership segmented by department, country and role, and reporting your comms team can build and defend in front of leadership.
This is the requirement Communication Insights is built for. It is an all-in-one cross-channel analytics platform that connects your email newsletters, SharePoint intranet, Viva Connections and Viva Engage into one central dashboard, so your comms team can see who actually read what, by audience segment, and report on business impact rather than system metrics. You can see how it covers the measurement requirement on Tryane's Communication Insights page. Judged against Microsoft's own standard, pilot one scenario and measure business impact, that is the difference between knowing a page was viewed and knowing the message reached the parts of the organisation it was meant for.
If you want to see this measurement requirement demonstrated live on your own channels, book a 30-minute call with Hatim.
Frequently asked questions
What are the most important intranet features to compare?
Compare platforms across five jobs: finding, publishing, targeting, administration and measurement. Tryane's Digital Workplace Benchmark 2026 structures this as 17 criteria in five categories, from Look and Feel and Mobile Experience to Specific Audience Targeting, Ease of Authentication and Analytics / Insights. Weight the categories by your own priorities before you score any vendor.
How do I test intranet navigation during a vendor demo?
Give demo participants real employee tasks phrased in employees' own words, such as finding a policy or booking leave, and watch where they fail. NN/g research found average task times of 78 seconds on centrally managed intranets versus 123 seconds on distributed ones, so also ask how content ownership is organized.
Should every intranet page show a last-updated date?
Yes. NN/g lists a date on each news item, a last-updated date on every page and a named page owner among the elements that make intranet content credible. Without them, employees doubt what they read and stop treating the intranet as a trusted source.
Which platforms scored best on analytics in Tryane's 2026 benchmark?
In Tryane's Digital Workplace Benchmark 2026, only Unily and Poppulo were rated 5/5 on the Analytics / Insights criterion. SharePoint was rated 2/5 on the same criterion and scored 45% on Analytics, the lowest category score among the 12 platforms profiled.
What should intranet measurement requirements include?
Require readership broken down by department, country and role, across all your channels rather than one platform at a time, and test the reporting in a pilot. Microsoft's SharePoint intranet planning guidance recommends judging the pilot on actual business impact, not system metrics such as page views.
How do I write demo tasks for intranet vendors?
Script tasks around your own content and your own audiences: publish a real news item, target it to a specific department, then check that the reporting shows who read it. Microsoft recommends piloting one key scenario with a committed sponsor, up-to-date content and a specific pilot audience before you scale.
Sources
Further reading
• Intranet software in 2026: how 12 platforms compare
• Intranet governance: who owns what and how to keep it
• SharePoint intranet alternatives: 11 platforms scored
• From Workplace to Viva Engage: How to Prove the Migration Did Not Lose the Frontline
If you want to see what cross-channel reporting looks like against your real data, Tryane runs a 15-minute walkthrough with no slides. Book a slot with Jérémy.
