TL;DR
- Page views are a vanity metric. Execs don’t care how many people loaded the homepage.
- Good intranet ROI reporting answers three questions: is it faster, is it used, and are people informed?
- Pick 6 to 8 metrics. Report monthly. One page. That’s the whole discipline.
- Search success rate and self-service deflection are the two metrics that move the budget.
- Most intranet projects get killed because nobody sets baselines in month one.
- We’ll give you a one-page KPI dashboard template and an instrumentation plan.
Here’s a question. If your sponsor asked you tomorrow to prove your intranet was worth the money - not in feelings, in numbers - could you?
For a lot of teams, the honest answer is no. Or ‘sort of, give me a week’. That’s the gap this post is about. Intranet ROI reporting isn’t hard, but it does need discipline: a small set of the right metrics, measured monthly, in a format an executive can read in ninety seconds.
Why page views stopped mattering
Page views are the intranet equivalent of counting how many people walked past a shop. Interesting. Not useful. A homepage view tells you nothing about whether anyone found what they needed, did anything with it, or came back.
Think of it like a library. The question isn’t how many people walked through the door. It’s how many left with the right book, how many found it without asking a librarian, and how much shelf space is holding decade-old content nobody touches.
The bottom line? Vanity metrics make nice dashboards and lose budget arguments.
The three questions every exec is actually asking
Strip away the jargon, and intranet sponsors want to know three things. At WebVine, we frame digital workplace success around three pillars — Productivity, Communication, and Engagement. Some organisations lean harder into one pillar than the others depending on what they need from their intranet, but the point is the same: are we helping people get work done faster (Productivity), are we keeping people informed with clear, effective communication (Communication), and are people actively participating, not just visiting, the experience (Engagement)?
Every metric worth reporting maps to one of those three. If a metric doesn’t, it’s probably a vanity number in a trench coat.
- Productivity: search success rate, onboarding time-to-productivity, task completion time, self-service deflection.
- Engagement: active engagement, frontline reach, repeat visits, contributions (reactions/comments), content freshness.
- Communication: comms reach (incl. frontline), comms action rate, reduction in broadcast email volume, acknowledgement/compliance completion on priority messages.
Instrument once, report forever
The reason most teams can’t report ROI isn’t that the data doesn’t exist. It’s that nobody set it up in month one. Search analytics weren’t turned on. Page templates didn’t include a ‘last reviewed’ field. The service desk categories don’t line up with intranet topics, so deflection is impossible to measure.
Spoiler: you don’t need a fancy product. You need five or six well-placed hooks - SharePoint analytics, Viva Insights, a ‘was this helpful?‘ widget, a clean taxonomy on the service desk, and a monthly pull from each.
Instrument once. Report forever. Foundations first.
The one-page rule
If your ROI report is longer than one page, nobody reads it. If it’s shorter than six metrics, nobody trusts it. Six to eight metrics, one-page, same format every month. That’s the sweet spot.
Consistency matters more than cleverness. An exec who sees the same four columns every month starts to feel the trend without thinking. Change the layout, and they’re reading it cold every time.
Mini-template: monthly intranet KPI dashboard
Drop this into a one-page report. Same metrics, same format, every month.
| Metric | Why it matters | Target | Current |
| Search success rate | People find what they need without asking. The single best proxy for intranet usefulness. | Above 80% | [your number] |
| Self-service deflection | Queries resolved via the intranet instead of escalating to HR, IT, or payroll. | 20% month-on-month lift | [your number] |
| Content freshness % | Share of pages reviewed in the last 12 months. Stale content erodes trust fast. | Above 85% | [your number] |
| Active engagement | Weekly active users who did something – searched, reacted, commented – not just loaded a page. | 60% of workforce weekly | [your number] |
| Frontline reach | % of deskless or frontline staff reached monthly via mobile or Viva Connections. | Above 70% monthly | [your number] |
| Comms action rate | Click-throughs or acknowledgements on priority comms, not just impressions. | Above 40% | [your number] |
| Onboarding time-to-productivity | Days from start date to first completed core task. Intranet should shorten this. | Down 15% year-on-year | [your number] |
| Support-ticket deflection | Tickets closed with ‘self-service link’ or avoided entirely via intranet content. | 10% of eligible tickets | [your number] |
Most orgs miss this
Baselines. Nobody captures them in month one, and then six months later when an executive asks ‘is this better?‘, the honest answer is ‘we think so’. That’s the sound of a project losing its budget.
Set the baseline the week you launch. Even a rough number is better than none. You can refine the measurement later - you can’t recreate a baseline you never captured.
3 questions worth asking
If you answered yes to any of these, let’s have a chat.
- If your CFO asked tomorrow what your intranet saved the business last quarter, would you have a number?
- Do you know your search success rate - or are you still reporting page views?
- Can you tell, month on month, whether your content is getting fresher or staying stale?
So… what now?
Pick six metrics. Capture the baseline this month. Report the same format every month for a quarter. That’s the whole discipline - and it’s the difference between an intranet that gets funded next year and one that quietly gets absorbed into ‘digital workplace’. Practical beats perfect. Start this month.
FAQs
What’s a realistic search success rate?
Above 80% is a solid target for a mature intranet. Most organisations that have never measured it are surprised to find they’re sitting around 55 to 65%. The gap between those numbers is where the frustration lives.
How do we measure self-service deflection without a fancy tool?
Tag the top 20 service desk categories, check how many of those topics have intranet content, and track ticket volume month on month against intranet visits to those pages. Rough but directional - and directional beats nothing.
Should we report weekly or monthly?
Monthly for execs. Weekly for the product team running the intranet. Different audiences, different cadences. Don’t send the weekly view upstairs.
What about satisfaction scores and surveys?
Useful, but annual. Surveys capture sentiment; the monthly KPIs capture behaviour. You want both, but don’t rely on surveys alone - people tell you they love the intranet and then ring the service desk anyway.
Our frontline staff don’t use the intranet much. Should we drop frontline reach?
No - that’s exactly why it belongs on the dashboard. A low number is a signal, not a reason to hide the metric. Viva Connections on mobile is designed for this, and the number will move if you invest.
How long until we can show real ROI?
Three months of clean data is enough for a trend. Six months gives you a story. Twelve months gives you a business case for the next round of investment.
Who is WebVine?
WebVine helps help Australian organisations turn SharePoint, Microsoft 365 and Copilot into tools people trust, use and value. WebVine are also the team behind Injio.
Sources
Unlocking value from teamwork: how social technologies improve productivity — McKinsey Global Institute.
Knowledge workers spend 1.8 hours every day searching for information — Harvard Business Review / Bloomfire summary.
Magic Quadrant for Intranet Packaged Solutions — Gartner. Vendor and capability landscape; useful for benchmarking what ‘good’ looks like.
Microsoft Viva and SharePoint analytics documentation — Microsoft Learn.
Intranet usability and information architecture studies — Nielsen Norman Group.
Service desk benchmarking and self-service deflection — HDI.