A logo file in a Dropbox folder is not a brand. A brand is a set of rules clear enough that a copywriter, a developer, and a booth designer can independently produce work that looks and feels like it came from the same organisation — without pinging the design team for every decision. Getting from a logo concept to that level of operational clarity requires a system, not a collection of assets. This article covers how we build that system: from the positioning workshop through to motion guidelines and production-ready asset libraries.
From positioning strategy to visual language
Brand identity work that starts with typeface selection and colour palette usually produces aesthetically coherent results that nobody feels strongly enough about to defend. Brand identity work that starts with positioning — what this organisation stands for, who it serves, what it wants to be associated with, and what it explicitly does not want to be associated with — produces a visual language with defensible rationale behind every decision.
Positioning workshops run before any visual exploration. We use structured exercises to surface the brand attributes that stakeholders agree on, the ones they disagree on, and the ones they have never explicitly named. The output is a brand brief: a short document that defines the positioning, the audience, the tonal range, and the visual references that resonate versus the ones that represent what the brand is not.
Visual exploration is constrained exploration. Rather than presenting three fully developed directions for stakeholders to choose between, we use the brand brief to define the decision criteria first. When a typeface choice is evaluated against explicit criteria — "does this feel precise without being cold? does it work at small sizes in data-heavy contexts?" — the conversation is more productive and the outcome is more defensible than "which one do people like best."
Building the identity system
A logo system includes more than a primary mark. It includes: the primary logo in full-colour, reversed, and monochrome variants; a wordmark for contexts where the symbol does not reproduce well at small sizes; a symbol mark for icon and favicon use; and clear minimum size and clear space rules. Each variant has documented use cases — not general guidance, but specific contexts where each is appropriate and where each is not.
Colour systems are defined by use role, not just palette. A primary brand colour, a secondary set for accents and data visualisation, a set of functional colours for status and feedback states, and accessible background-foreground combinations for text. Defining colour by role means that a developer implementing a new UI component can look up "what colour is an error state?" and find a specific answer rather than a palette of options.
Typography is similarly role-based: display type for headlines, body type for long-form content, UI type for interface labels and data tables, and code type for technical documentation. Each role has a size scale, a line-height specification, and a maximum line length. Guidelines that include specific pixel values and line heights are used; guidelines that describe typography in abstract terms are not.
Usage examples in guidelines are as important as rules. For every element in the system, we include a correct use example and a "do not" example that shows the most common mistake. A guideline that shows only correct usage leaves room for creative misinterpretation; a guideline that shows the mistake alongside the correct usage eliminates the most common errors before they reach production.
Motion design with a system, not just a style
Motion without rules produces an incoherent brand experience. An animated logo that uses a different easing curve on the website than in the pitch deck, a loading animation that runs at a different speed than the page transitions — these inconsistencies are invisible to most viewers but accumulate into an impression that the brand is not quite polished. Motion guidelines define the rules that prevent that drift.
We define motion tokens the same way we define colour tokens: named values for duration (fast, medium, slow), easing curves (enter, exit, emphasis), and delay patterns. A developer implementing a component can look up "entrance animation" and find a specific duration and easing curve rather than making an aesthetic judgement. Consistency across touchpoints follows from consistent values, not from reviewing every implementation individually.
Motion assets ship in formats matched to the use case. Lottie for interactive UI animations where colour and speed can be controlled programmatically; MP4 with transparency for video contexts; GIF only where modern formats are not supported. Each animation ships with a specification sheet: dimensions, duration, loop behaviour, and approved background combinations.
Asset production for teams that do not have design access every day
The test for an effective brand system is whether a team member without design training can produce on-brand work for a standard use case — a slide deck, a social post, a printed banner — without the design team reviewing every output. We design the system and asset library to pass that test, not just to document what the design team does when given a brief.
Template libraries in Figma and PowerPoint cover the highest-frequency use cases: presentation templates with branded layouts and placeholder content, social media templates at the sizes actually used, email header templates, and document covers. Templates include annotation layers that explain which elements can be modified and which cannot.
Export presets are defined and named for non-designers: "social-square-2x", "email-header-600w", "print-CMYK-300dpi". A marketing coordinator should not need to know what 300dpi means or why it matters — they should know that "print" files use the print preset and that is sufficient.
Brand guidelines are versioned and dated, with a changelog. When the guidelines update — a new colour for a product line, a revised logo for an anniversary — teams need to know what changed and when, not discover it by comparison with a file they downloaded six months ago. A versioned guidelines document with a clear changelog is the difference between an adopted brand system and a brand system that lives on a design team drive nobody else opens.
