The Design section begins with the Brand Vision — a foundational element often overlooked. Millions of designers move objects on screens without understanding the vision that should guide those decisions. When the vision is clear, tangible, and easy to digest, the entire team becomes wiser, and decisions become more consistent.
Design Strategy builds on this. It describes how design manifests internally and externally, how it influences the team, and how it shapes the product. The more specific the definition, the more precise - and effective - the outputs.
Design Principles then align with CX principles. They articulate the desired behaviour (action) and the emotional connection (expression or need). Without clearly defined principles, teams often give ten different answers when asked what the product stands for. Inconsistent understanding always results in inconsistent delivery.
The Brand Bible is the modern evolution of traditional brand guidelines. Instead of static PDFs, it becomes a living digital artefact - updated, versioned, and directly tied to the product. Many companies create bespoke systems; others integrate with existing platforms. The method matters less than the commitment to keeping it alive.
The Design System is often mistaken for a Figma file. In reality, it’s a logical response to a complex landscape of requirements - visual, functional, behavioural, and organisational.
A true system integrates across the business, enabling consistent, well-considered outcomes. It has never been “a design-only thing.”
The Feature List documents each feature's latest state — behaviour, dependencies, APIs, security protocols, SSO variations, and UI evolution. While dynamic and frequently updated, this list ensures alignment across teams.
The Component List, by contrast, changes less often and represents the stable foundation of the Design Operating System. Once created, it requires minimal maintenance — think of how rarely default buttons truly change.
