Resilience Solutions

Experience, Design & Creative

Design experiences people understand, trust and choose.

Research, service design, interface systems and accessible design for enterprise products and customer-facing experiences.

Discuss a design or experience initiativeNot sure this is the right fit?

The problems this solves

What usually brings people here

If one of these sounds like your situation, this is the right page.

  • Our internal tools are the reason work is slow.

    Enterprise interfaces designed around database structure rather than around the task, so people need training to do things that should be obvious.

  • Every team builds interfaces differently.

    No shared component system, so patterns diverge, accessibility is inconsistent and every product rebuilds the same elements.

  • We do not know why users abandon the journey.

    Analytics show where people leave but not why, and no research practice exists to answer it.

  • Accessibility is raised as a blocker late in delivery.

    Conformance is treated as a test rather than as a design constraint, so remediation means redesign.

Capabilities

What we actually do

  • User research

    Interviews, contextual enquiry and usability testing that answer why, not just where.

  • Service design and journey mapping

    End-to-end journeys across channels, systems and the people who operate them.

  • Information architecture

    Structure, naming and navigation designed around how people actually look for things.

  • Interface design and design systems

    Tokenized, documented component systems that make consistency the default.

  • Accessibility and inclusive design

    WCAG 2.2 AA as a design constraint from the first wireframe.

  • UX writing and content design

    Interface language that reduces the need for instruction.

  • Prototyping and validation

    Testable prototypes that resolve the expensive questions before build.

  • Enterprise UX modernization

    Bringing consumer-grade usability to the internal systems people use all day.

  • Creative and technical visualization

    Brand systems, product storytelling, motion, 2D/3D animation and immersive experiences.

The sequence

Design as evidence, not taste

The marked stage is what separates design from decoration: something tested with people outside the team before it is committed to a build.

  1. 01

    Research

    What people are actually trying to do, observed rather than assumed.

  2. 02

    Define

    The problem worth solving, written so it can be disagreed with.

  3. 03

    Design

    Flows, interface and content, in the system that will build it.

  4. 04gate

    Validate

    Tested with people outside the team before it is committed.

  5. 05

    Build-ready

    Components, states and behavior a developer can implement without guessing.

  6. 06

    Measure

    What changed for the user, fed back into the next round.

Comes out the other end: An interface a developer can build without guessing, and a reason to believe it works.

How we approach it

Principles we hold to

  • Research before wireframes

    We establish why people abandon a journey before redesigning it. Analytics show where; only research shows why.

  • Design the system, not the screen

    Tokens and components come first so consistency and accessibility are the default rather than a review finding.

  • Accessibility as a design constraint

    Heading structure, focus order, contrast and keyboard operability are decided during design. Discovering them in an audit means redesigning, not adjusting.

  • Validate with a testable prototype

    The expensive questions get answered before build, on something people can actually use.

Outcomes

What you should end up with

  • Interfaces that reduce training requirements rather than create them.
  • A design system that makes consistency and accessibility the default.
  • Design decisions supported by research rather than by preference.
  • Accessibility conformance achieved by design rather than by remediation.

Where this usually starts

A short working session on your situation — what you are trying to change, what is in the way, and whether this is the capability that addresses it.

Discuss a design or experience initiative

Evidence

What changes, and how you would know

Two different things belong here. One is the structural change this capability makes, which we can describe today. The other is a client outcome, which publishes only when a client has approved it in writing with a timeframe and a baseline.

Client outcomes for Experience, Design & Creative

Proof pending approval

A published outcome here will carry the client's written approval, the timeframe it was measured over and the baseline it was measured against. Until all three exist, this section says so rather than showing a figure you could not check.

Discuss a similar challenge

Where this capability leads

Every connection below is recorded in the content itself, and each one says why it is here.

Explore where this capability fits

Answer four questions about your goal, sector, environment and constraint, and see how this capability sits alongside the others in a path — with the reasoning shown.

Start from a goal

Open the solution finder

Questions

Frequently asked

What is a design system and when is one worth building?
A design system is a documented set of tokens, components and usage rules shared across products. It is worth building when more than one team is producing interfaces, because the alternative is each team independently solving the same problems and diverging. For a single small product it is usually overhead.
Why is accessibility cheaper to design in than to fix later?
Because most accessibility failures are structural — heading hierarchy, focus order, color contrast, form labeling, keyboard operability. Those are decisions made during design and build. Discovering them in an audit means changing the structure, which usually means redesigning rather than adjusting.

Discuss a design or experience initiative

Tell us what you are trying to change. Someone who does this work reads every request and connects you with the right capability team.

Discuss a design or experience initiative
See all capabilities