Skip to main content

HOW WE WORK

A clear process for problems that rarely are.

Six phases that structure the work without making it rigid. Not every project runs every activity — the process adapts to the problem.

Process phases

  1. 01

    Discover

    Understand the business, users, context and constraints.

    Possible activities

    • Stakeholder interviews
    • UX research
    • Analytics review
    • Benchmarking
    • Heuristic review
    • Customer journey
    • Product audit

    Possible deliverables

    • Findings
    • Problem framing
    • Opportunity areas
    • Research summary
  2. 02

    Define

    Turn information into a clear direction.

    Possible activities

    • Problem definition
    • Prioritization
    • Product goals
    • User flows
    • Information architecture
    • Feature scope
    • MVP definition
    • Roadmap

    Possible deliverables

    • Product direction
    • Flow map
    • Prioritized backlog
    • Scope definition
  3. 03

    Design

    Turn strategy into experience.

    Possible activities

    • Wireframes
    • UX design
    • UI design
    • Interaction design
    • Prototyping
    • Responsive behaviour
    • Component design

    Possible deliverables

    • Wireframes
    • Final interface
    • Interactive prototypes
    • Component library
  4. 04

    Validate

    Test before investing further.

    Possible activities

    • Prototype testing
    • Usability testing
    • Stakeholder validation
    • Accessibility review
    • Design QA

    Possible deliverables

    • Test results
    • Fix list
    • Accessibility report
  5. 05

    Deliver

    Make sure the solution reaches implementation correctly.

    Possible activities

    • Design specs
    • Developer handoff
    • Design tokens
    • Component documentation
    • Responsive specs
    • Interaction specs
    • Accessibility guidance

    Possible deliverables

    • Design documentation
    • Tokens
    • Implementation guide
  6. 06

    Improve

    Measure what happens after launch.

    Possible activities

    • Analytics
    • Funnel review
    • User behaviour
    • CRO
    • Iterative design
    • Continuous optimization

    Possible deliverables

    • Metric readout
    • Improvement hypotheses
    • Iteration plan

MODULARITY

The process adapts to the problem.

Not every project starts at the same point. The methodology is modular: we enter where it makes sense and continue from there.

Possible entry points

  • Research
  • Audit
  • Redesign
  • Design System
  • MVP
  • CRO

COLLABORATION

We work with your team, not around it.

We integrate with existing teams and adapt to how they already work.

Compliance and regulated areas join the process where applicable.

  • Product
  • Engineering
  • Marketing
  • Business
  • Data
  • Customer Experience
  • Compliance

PARTNERSHIP

What we need from you

Work moves faster when we have access to the right context.

  • Access to product and business context
  • Access to relevant stakeholders
  • Fast feedback at decision points
  • Clear business priorities
  • Known technical constraints
  • Available usage data

RHYTHM

Simple, direct communication.

Less noise, more clarity about where the project stands.

Clear milestones
Every phase has a goal and a visible end.
Regular check-ins
Status points at an agreed cadence.
Transparent decisions
What was decided, why, and what stays open.
Shared documentation
Everything decided stays accessible to the team.
Visible progress
The state of the work can be checked at any time.

WAYS OF WORKING

Three ways to work together

  • Project

    For challenges with a defined beginning and end, with agreed scope and deliverables.

    View services
  • Sprint

    For specific problems that need a fast, focused response, such as an MVP Sprint or a UX Health Check.

    UX Health Check
  • Partnership

    For ongoing support and product evolution over time, as a product partner.

    Start a Project

Have a challenge worth solving?

Let's talk.