European Court of Auditors intranet

From the beginning, the project was set up with a clear process and timeline. Given the scale of the initiative, it was important to align everyone on what we were going to do, what we were not going to do, and how we would get there.

This created a shared understanding of priorities and expectations, and helped maintain focus throughout the project. It also introduced a sense of accountability not pressure in a negative way, but a clear commitment to delivering within the defined timeframe.

Regular communication was key. We made sure stakeholders always knew what was happening, what was coming next, and how they could contribute. This helped build trust in the process and ensured feedback was timely and relevant as we moved through each phase.

A key part of the project was building a strong connection with stakeholders to support the change.

We identified the main working groups within the organization and translated them into representative personas. These were not just documentation, but active participants in the process. They acted as a constant line of communication between the project team and the wider organization.

This approach helped ensure that the new intranet was seen as an opportunity rather than a disruption. By involving stakeholders throughout the process, we created a sense of ownership and made sure the solution reflected real needs and expectations.

A key challenge of the project was the complexity of the work carried out within the institution, and how to ensure the solution covered all relevant needs.

To address this, we worked with both macro and micro journeys. Macro journeys helped us understand the broader workflows across teams, while micro journeys allowed us to break down specific tasks and interactions in detail.

This approach ensured that the design decisions were grounded in real user needs and aligned with the tasks defined together with stakeholders. It helped us move from abstract requirements to concrete solutions that directly addressed identified pain points.

Another key challenge was balancing ease of use with the level of expertise required for a daily professional tool. We approached this using lenticular design, making core tasks simple and accessible, while allowing additional complexity to appear progressively as users needed it.

This made navigation faster and more intuitive, improved readability across the intranet, and ensured that users could quickly find what they needed. At the same time, it preserved the depth required for more complex tasks, allowing the intranet to function as a reliable and effective work companion.