This article was developed with AI assistance.
A website can use the new palette while the product still uses the old one. The release video can describe a feature differently from the interface. Each piece may have been approved, just against a different version of the brand or product.
A managed Creative-as-a-Service model can support long-running brand consistency when someone maintains context, briefs contributors and reviews their work. At Designity, the dedicated Creative Director is responsible for creative direction, specialist selection and brand alignment, while a Creative Project Manager coordinates workflow and delivery. That is a concrete ownership model for keeping related assets aligned, not a guarantee that inconsistencies disappear. An in-house team, agency or freelancer group can use the same practices.
For a software team working with outside creatives, the practical goal is simple: make the current decision easy to find, and make changes visible to everyone affected.
Give contributors a small, current starting point
A large brand guide has useful background. Someone adapting an illustration for a release page also needs to know which rules apply today.
Create a short starting document that points to the current design library, product terminology, approved assets and named reviewers. Link to the maintained sources rather than copying their contents into another document that can go stale.
Include examples of an acceptable adaptation and a change that needs review. “Use the approved palette” leaves room for disagreement; “this accent is allowed in campaign illustrations, but not as a replacement for interface status colors” is easier to act on.
Assign a maintainer and a backup. If the creative lead changes, the references and the reasons behind important decisions should remain available.
Separate shared rules from room to experiment
Consistency does not require every surface to look identical. A product settings screen and a launch video do different jobs.
| Keep aligned | Allow to vary within agreed limits |
|---|---|
| Product names and factual claims | How much detail each audience needs |
| Logo use and core identity | Layout and campaign composition |
| Interface meaning, such as error and success states | Decorative treatments outside the interface |
| Approved typography and color rules | Format-specific hierarchy and emphasis |
| Review responsibilities | The production tool used to make the asset |
Treat this as a starting point for discussion, not a universal brand specification. Your team still needs to decide where those boundaries belong.
Accessibility also needs its own check. A color combination can follow the brand palette and still make text hard to read. W3C's guidance on minimum text contrast explains the relevant thresholds and exceptions. Brand approval alone does not establish accessibility.
Keep a decision log for changes that cross surfaces
The useful record is more than “new blue approved.” It explains what changed, why, and where the change should apply.
Use one entry per decision with these fields:
- Change: what is different, with a link to the approved reference.
- Reason: the problem it solves or the constraint behind it.
- Affected surfaces: product, website, help content, email or other assets.
- Owner: who resolves questions and who implements the change.
- Timing: when it takes effect and which older assets can remain.
For example, if a feature gets a new name, record whether the old name must disappear everywhere at once or remain in help content during a transition. A designer cannot infer that migration plan from the latest logo file.
This gives new contributors somewhere to look before repeating an old debate. It also helps a team distinguish an intentional exception from a mistake.
Review the relationship between assets
Checking each asset separately can miss contradictions between them. Before a release, put the relevant page, product screen and announcement beside one another.
Review three questions:
- Do they describe the same product behavior and use the same terms?
- Do shared visual elements have the same meaning, even where the layout differs?
- Are differences intentional, documented and suitable for the channel?
In a Designity-led workflow, the Creative Director’s brand review can sit alongside a product owner’s check of behavior and claims. Engineering should assess implementation details. For example, a release-page illustration may follow the visual identity but still show a feature that has changed. The creative lead needs the current product decision before approving it. Make that split explicit rather than expecting one person to approve everything.
For assets maintained in GitHub, CODEOWNERS can route review requests to the responsible people or teams. Requiring their approval before merging needs the appropriate repository settings; the file alone does not enforce it. For work outside a repository, use an equally clear review assignment in the tool where that work lives.
Use AI for assistance, with checks tied to the task
AI can help organize feedback, suggest brief drafts or produce variations. Those uses can save effort, but each needs a different check.
A summary can omit a disagreement. A generated variation can change wording or introduce a visual detail that was never approved. A polished answer can be based on an outdated reference.
Give the tool the current, permitted materials and a bounded task. For a brief draft, ask it to separate confirmed decisions from unresolved questions. Have a person compare the result with the source before passing it to a contributor. Keep confidential material out of tools unless your organization has approved that use.
For mechanical checks such as text contrast, use a suitable checker rather than treating a model's visual opinion as a pass. Human review should focus on product accuracy, accessibility, brand judgment and whether the output fits its context.
Start with one inconsistency
Pick one recurring mismatch, such as outdated product names in launch assets. Find where the current decision lives, who maintains it and how contributors learn that it changed.
Fixing that path is a useful first step whether your creative team is internal, managed externally or spread across independent specialists. More people reading the same old PDF will not resolve a decision that was never recorded.
Where does your team keep decisions that affect both product design and marketing assets?
Top comments (0)