Structuring the information architecture for a unified design guidelines portal, consolidating 40+ years of product knowledge across 5 disciplines into a single source of truth — built on Zeroheight, designed for everyone in the Creative & Design department.
Logitech's design guidelines were scattered across slide decks, Google Docs, web pages, and tribal knowledge — over 300 documents spanning brand, creative, packaging, product hardware, digital software, and cross-platform experiences. Teams recreated assets instead of reusing them, engineers implemented inconsistently, and finding the right guideline required knowing who to ask.
A research-driven information architecture for the Logitech Design System portal, built on Zeroheight. Through stakeholder interviews, content audits, card sorting, tree testing, and iterative prototyping, we created a navigation structure that organised 5 disciplines into 8 intuitive sections — making 40+ years of product knowledge discoverable, searchable, and maintainable.
300+ files migrated and structured into a single, searchable platform. A three-tier guidelines framework (Fixed, Flexible, Free) that balances brand consistency with creative freedom. Unified navigation serving designers, engineers, product teams, and external partners across the entire Creative & Design department.
Logitech's Creative & Design department spans multiple disciplines, each with decades of accumulated knowledge. The LDS project aimed to unify all of it into one coherent, navigable system.
The project ran with 5 core members — I worked alongside the rest of the team on the Information Architecture, contributing strongly without being the sole lead. Around the core sat 14 advising and consulting points spanning UX, Web, CMF, Software, Brand and the Global UX function, plus 2 project sponsors including Logitech’s CDO. The design org sits across 4 time zones — 90% of stakeholder interviews were remote, against a content corpus of 300+ legacy guideline docs spread across slide decks, Google Docs, web pages, and tribal knowledge.
I owned the parts where AI tooling could compound a single designer’s reach: 99% of the Zoom interview processing — transcription, insight extraction, cross-interview pattern surfacing — ran through Companion. Most of the 300+ document analysis went through Gemini, helping the team decide where each piece of content belonged in the new IA. And we built a “brain of the LDS” on LogiQ (Logitech’s internal LLM), seeded with brand voice guidelines and tone-of-voice rules so copy decisions across the system stayed coherent. Final calls on taxonomy, hierarchy, and content strategy were shared with the core team — the AI bought back weeks of manual processing time that would have otherwise pushed delivery out of the strategic window.
The project began with understanding the landscape. We conducted interviews with Points of Contact (PoCs) across every discipline — designers, engineers, product managers — to map how teams actually find, use, and share guidelines.
Users consistently expressed a strong preference for centralised, searchable web content over scattered slide decks. Search functionality was identified as the single most critical feature for the portal's success.
With research insights in hand, we audited the existing content landscape. Over 300 documents spanning decades of product development knowledge were catalogued, categorised, and assessed for relevance and migration priority.
Guidelines were classified as Fixed (non-negotiable standards), Flexible (limited options within bounds), or Free (complete creative freedom). This framework ensured brand consistency while preserving room for innovation.
Working alongside the Design Lead and core team, I contributed to designing the navigation systems, logical hierarchies, and sitemaps that would make this vast body of knowledge intuitive and findable. This involved multiple rounds of collaborative testing and validation.
Research showed that organising content by narrative flow rather than by perceived importance created more intuitive paths. Core, unchanging guidelines live on the platform directly, while frequently changing supplementary content links externally — reducing maintenance burden without losing discoverability.
With the architecture defined, we built interactive prototypes on Zeroheight and conducted multiple rounds of user testing with teams across the organisation. Each round informed refinements to navigation, labelling, and content hierarchy.
The migration was executed across three distinct four-month phases, each progressively expanding the platform's scope while refining the architecture. We also established governance processes to keep the system alive and current.
Due to the proprietary nature of Logitech's design guidelines, specific content, product specifications, and internal processes cannot be disclosed. The following represents the scope of work with sensitive details redacted.
Anonymised insights from stakeholder and PoC interviews that shaped the architecture decisions. These voices represent designers, engineers, and product leads across the organisation.
The project was structured as three four-month phases, each dedicated to architecture development and content loading — progressively expanding the platform's scope while refining its structure.
The best architecture is the one you never notice.
Three hundred documents, five disciplines, forty years of knowledge — and no shared home. The work here was never visual; it was structural. The architecture decisions traced back to stakeholder interviews, and the loudest finding was the quietest one: people wanted to find, not to browse. Search beat polish.
A structure is only as durable as the process that maintains it. Ownership, review cycles, update workflows — without them the portal drifts back to the scatter it replaced. Building the architecture is the visible half. Keeping it coherent is the design no one applauds.