Overview
Redesigned the front page, search and personalisation for the Storting's EPiServer-based intranet, working through structured workshops on navigation, search relevance and analytics.
Who This Is For
Parliaments, government bodies and public institutions, typically 200 to 5,000 staff, with an intranet that has grown organically. This case is most useful if:
- the front page is crowded with shortcuts, portals and notices
- search returns too many broad matches
- personalisation has to work across very different staff roles
- analytics are in place but KPIs have not been defined
The Challenge
The Storting's EPiServer-based intranet had grown organically. The front page was crowded with shortcuts, personalised portals and notices, search surfaced too many broad matches on topic tags, and the personalised "My Page" area had to work across very different staff roles.
Analytics ran on Piwik with premium modules, but the KPIs had not yet been defined in a way that matched what the platform could measure.
Our Approach
Over May and June 2017 we ran structured workshops with the Storting's own product owner and IT stakeholders.
- Front-page structure: shortcuts, personalised portals, messages and a calendar-style events view.
- Search relevance: working with Intellisearch's Norwegian synonym search and breadcrumb navigation to fix over-broad topic-tag matches.
- People directory: a simple staff listing combined with longer biography blocks for larger profiles.
- Systems context: how the intranet's information architecture should relate to EPHORTE, the case-management system already in use.
- Measurement: where Hotjar session recording, used only on the public stortinget.no, fitted alongside Piwik.
Impact
Stakeholders in the room. The process put the Storting's own people at the centre rather than imposing a specification from outside.
Real structural questions. How search, personalisation and org-chart navigation should relate to each other, worked through on a live public-sector platform.
An intranet that has grown organically rarely needs more features. It needs someone to decide how the existing ones relate.
Delivered while employed at Making Waves (later NoA Ignite). Any public information referenced here is used for identification and does not imply endorsement.
Topics
Delivered Norwegian-to-English translation and QA review of SpareBank 1 Markets' website content, covering their research, corporate finance and capital markets service lines.
Built a data-driven content and channel strategy for Econa, Norway's professional association for economists and business graduates, building on an already-delivered website redesign to reduce member churn.
Built a CRM-connected advertising sales platform for a leading Nordic digital marketplace. Connected audience data, targeting options, advertising formats, pricing and sales contacts into a single self-service portal for advertisers and media agencies, replacing a fragmented sales experience with a repeatable path from research to qualified inquiry.
CMS Architecture for AI-Driven Enterprises
Choosing and Configuring the Right Content Platform for Intelligent Operations

Dries Buytaert: The cost of running multiple CMS platforms
Dries Buytaert argues that running multiple CMS platforms creates hidden operational costs through duplicated integrations, security policies, expertise, and governance. He proposes standardizing on Drupal while using different operating models—SaaS (Acquia Source) for speed and PaaS (Acquia Cloud) for control—to preserve flexibility while reducing fragmentation.
Content-to-Pipeline Check
See how far your content connects to sales, and how much of what sales learns comes back.