Skip to main content
AriaHelpDesk
Capability area

Branding & Experience Design

Identity and interface design: what your organisation looks like, how it behaves, and the systems that keep both coherent across everything you make.

Overview

Design problems are usually not design problems. A confusing interface is generally a flow that was never mapped. An inconsistent brand is usually an identity that was never extended past the logo. Redesigning the surface without addressing that moves the problem rather than solving it.

So the work here starts with a decision or a piece of research, and then builds systems rather than artefacts: components, tokens and documented rules, so consistency is the default rather than an act of vigilance.

Who this is for

  • Companies whose materials look like they came from several different firms
  • Products with high support volume around one specific step
  • Businesses whose identity predates what they now sell
What's inside

The groups that make up Branding & Experience Design

Each one links through to scope, typical deliverables and how the work runs.

Questions

Common questions about Branding & Experience Design

The things people ask before they get in touch. If yours is not here, ask us directly.

Do we need a full rebrand?

Usually not. Most inconsistency comes from an identity that was never extended into photography, illustration and motion, rather than from an identity that is wrong. That is a much smaller and cheaper piece of work, and we will say when we think that is the case.

How many users do you need to test a design with?

Five to eight per round finds the large majority of significant usability problems. More rounds with fewer people beats one round with many, because you want to test the fix as well as find the fault.

Our website looks dated. Is that the problem?

Sometimes, but more often the problem is structure and copy. A dated site that says something specific outperforms a current-looking one that could describe anyone.

  • Multi-market delivery

    Teams that have shipped across regions, languages and regulatory regimes.

  • Built for review

    Security, accessibility and privacy handled during the build, not bolted on at audit.

  • Measured, not assumed

    Every engagement agrees its success metric before work starts.