Case study · 01
Enterprise Uganda
A new website for Enterprise Uganda, shaped around clear structure, a flexible WordPress CMS and a handover the team could use confidently.
- Year
- 2026
- Role
- Information architecture, UX/UI, WordPress development, CMS setup, training
- Stack
- WordPress · Institution · BDS · Uganda
- Live
- enterprise.co.ug
01 · The brief
What the client needed.
Enterprise Uganda needed a clearer digital home for its programmes, partner directory, news and impact reporting, with a CMS the internal team could manage confidently.
02 · Discovery & IA
Structure, audience and sitemap.
The early work here was mostly about structure. The site needed to serve people looking for programmes, partnerships, updates and institutional information without feeling dense. I used the discovery phase to simplify the navigation, separate core content types, and make sure the team would have a structure they could keep extending after launch.
Sitemap · enterprise.co.ug
06 routes · 06 programmes
- ·Programmes follows one CMS-driven template, shared across all six entries (hero, mandate, outcomes, downloads, contact).
- ·Resources holds long-form downloads (toolkits, reports) shared across programmes via a tag-based content model.
03 · Wireframes & UX
From wireframes to prototype.
The wireframes were used to test how people would move between institutional information and programme content without losing context. I also used this stage to work through how repeatable pages should behave, so the CMS would not be held together by one-off layouts.
Programmes hub wireframe
Hi-fi · /programmes
- 01Sticky nav with mega-menu under Programmes
- 02Programme intent: who it's for, what it produces
- 03Programme card grid, filterable by audience
- 04Resources rail pulled from shared CMS collection
04 · Outcome
What changed after launch.
The final result was a more structured institutional site, with publishing handed back to the team through documentation, walkthroughs and a CMS setup they could keep using with confidence.
