Case study
Designing a scalable digital system
inside an institution
This case documents the design of a digital system embedded within a large international institution, operating across multiple regions, programmes and organisational layers.
This was a structural intervention inside an institution: aligning governance, program taxonomy, URL systems and template logic across regions and stakeholders before interface or implementation decisions were made.
When structure is outpaced by growth
The platform had expanded organically as new academic programmes, regions and initiatives were added over time. Each addition solved an immediate need, but gradually eroded structural coherence.
The result was a fragmented ecosystem: overlapping regional websites, duplicated content and inconsistent navigation. Search visibility suffered, and decision making became increasingly difficult to coordinate.
Why institutional platforms struggle at scale
Multiple audiences without a shared model
Prospective students, academic staff, institutional partners and regional teams interacted with the platform with different intents, without a common structural framework to reconcile them.
Governance as the limiting factor
The core issue was not usability or aesthetics, but governance: how decisions about content, priorities and structure were made across regions and departments.
Designing the system before the interface
Information architecture as a shared decision framework
A common information architecture was designed to represent academic programmes consistently, while allowing legitimate regional variation without duplication or internal competition.
Search behaviour as structural validation
Search behaviour was treated as a validation layer. By aligning structure with how prospective students articulate intent, SEO became a consequence of clarity rather than a corrective exercise.
Design systems as governance tools
Design systems encoded structural rules and editorial hierarchy, supporting long-term maintainability and coordinated decision making rather than enforcing visual uniformity.
The decisions described here are guided by a clear set of working principles that define how structure, governance and longevity are addressed across projects.
What changed
Once the system was in place, content decisions became clearer, internal competition in search results decreased, and new programmes could be integrated without structural rewrites.
Technical execution
Information model and taxonomy
I translated institutional complexity into a scalable information framework. This involved auditing thousands of entry points to design a unified taxonomy that serves both users and search engines.
Search architecture and structured data
The build focused on structural SEO: mapping search intent to the core navigation and implementing Schema.org (JSON-LD) to ensure that the institution's authority is correctly interpreted by global crawlers. The resulting system enforces governance rules at the code level, preventing structural decay.
Structure inside institutions
This project was not about delivering a website. It was about designing a structure capable of holding institutional complexity over time.
Other projects explore what happens when that structure does not yet exist.