Hogeschool Utrecht

A unified digital foundation

The challenge

Hogeschool Utrecht partnered with Anderson MacGyver for strategic IT advisory and brought in YaWorks as expert delivery partner to define and realize the infrastructure architecture vision.

Hogeschool Utrecht (HU) is one of the leading universities of applied sciences in the Netherlands. Like many institutions in the education sector, HU is undergoing a fundamental digital transformation. With the rise of hybrid learning, regional partnerships, and practice-based research, the role of digital infrastructure is more critical than ever.


At the same time, HU faced a complex challenge shared by many large organizations: how to modernize its IT infrastructure in a way that supports innovation, while maintaining operational continuity, control, and cost-efficiency. As government funding tightens and budgets come under increasing pressure, controlling infrastructure costs has become more important than ever.With diverse teams, growing technical complexity, and evolving demands, it became increasingly important to align all infrastructure domains under a shared strategic vision that not only enables transformation but ensures secure, sustainable financial management.

The initial question

HU approached YaWorks with the request to define a five-year infrastructure architecture vision. This vision needed to connect strategic goals with technical foundations and provide clear guidance for domains such as cloud, identity & access, connectivity and the workplace.
HU’s original question focused on developing a comprehensive infrastructure architecture that could support the university’s broader digital strategy. However, early conversations revealed that the deeper challenge lay in the need for collective ownership. Previous architecture visions lacked adoption from IT teams. With that learning in mind, the HU assigned us to create an architecture vision in co-creation with HU's execution teams to create support, buy-inn and shared responsibility along the way.

The challenge behind the question


As the project progressed, it became clear that teams often worked with their own vision and focus within their respective domains. This created strong expertise locally, but also highlighted the need for a shared perspective across the entire infrastructure.
The architecture vision addressed this by bringing those perspectives together into a common framework. In addition, the project laid the foundation for an operating model that balances consistency with flexibility, providing central standards and principles while leaving room for teams to act within their own context. Together, this creates both alignment across domains and the ability to make targeted decisions within them.


Aligning teams through co-creation and clear deliverables

The approach

YaWorks applied a transparent and collaborative work method designed to keep all stakeholders aligned throughout the project. Drafts were shared early, feedback loops were short, and all deliverables were developed in close partnership with team members involved. This created ownership, trust, and momentum from the start.


To manage scope and complexity, we structured the engagement around six key deliverables: the infrastructure vision, four domain architectures (hosting, digital identities, connectivity, and workplace), and a consolidated roadmap. Each deliverable followed the same structured process and was developed in close collaboration with the relevant domain experts including management, architects, product owners, and engineers.


Each domain followed a four-workshop cycle:
1. Kick-off & as-is analysis: We launched the project, clarified expectations, and gathered input on the current state. We outlined how we would collaborate and what review and involvement was expected.
2. Strategic direction: In this workshop, we validated the processed findings from the first session and co-developed the initial strategic directions for the domain.
3. Architecture design: We refined the strategic direction, introduced first drafts of architecture principles and the modular service architecture, and jointly identified initiatives needed to realize the vision.
4. Final validation: We walked through the complete architecture, including all refinements, for final feedback and agreement.

Every workshop began by validating the processed output of the previous one, ensuring continuity and alignment. In parallel, we kept close contact with each team to address questions or tensions as they emerged, often resolving issues together in focused working sessions. This structure enabled deep involvement while keeping the project predictable and efficient.


The YaWorks factor


HU emphasized the way of working as one of the key reasons the project succeeded. YaWorks was not just brought in to deliver documents, we were there to bridge the gap between vision and reality. By embedding change and adoption directly into the process, we ensured that the architecture would not only land, but last.


We worked side by side with both strategic stakeholders and operational teams. From management to product owners, architects and engineers, we brought together different worlds that often remain disconnected in infrastructure projects. Through structured collaboration, shared ownership, and a high level of transparency, we helped all parties understand and participate in the architecture development, strategic choices, and roadmap to create one shared vision.


Our ability to translate between strategy and execution in a way that resonates with everyone from engineers to leadership is what made the difference. Teams didn’t just receive a new architecture. They were part of building it. Because they were actively involved throughout, they now recognize it as their own.
That sense of ownership is what transformed the architecture from an abstract plan into a living framework. One that is understood, supported, and ready to be put into action. What stood out to HU was not just the quality of the architecture, but the collaborative journey that made it truly sustainable.

Key outcomes


  • Cost efficiency: A unified hybrid hosting landscape and FinOps practice will simplify operations, reduce complexity, and enable future cost savings.
  • Improved security & compliance: Embedding structural improvements to strengthen security and raise SURF compliance levels including governance, access control, and data classification across all domains. This is supported by a dual security model that keeps HU’s academic environment open, yet protected.
  • Greater agility: Standardized building blocks and service models will allow teams faster access to technology, enabling quicker experimentation and innovation in education and research.
  • Student and staff flexibility: A modern workplace architecture enabling support for hybrid learning, remote access to exams and applications, and seamless digital experiences across locations.
  • Future-proof identity: Integration of EduID into HU’s identity ecosystem will enable students to retain one digital identity across institutions and throughout their learning journey.
HU now has a prioritized roadmap and multiple strategic scenarios that guide execution over the coming years. The architecture delivers the foundation, coherence, and direction needed to realize these outcomes.

YaWorks & Hogeschool Utrecht

How was the collaboration
Maarten Vervoorn
Maarten Vervoorn

HU about The Collaboration

"YaWorks was able to combine our overall strategy with execution within the teams, in a way that resonates with everyone from engineers to leadership. That is what made the difference in this project. Teams didn’t just receive a new architecture from an external ‘specialist’. No, they were part of building it. Because of this actively involvement throughout the project, they now recognize it as their own. With this ownership I expect we will be better equipped to implement this new architecture in the coming years."