L4 of 4 · How that software feels to everyone it touches

The Experience‑First Manifesto

Written by Harkirat Singh

We are uncovering better ways to build products
by designing, validating, and operating experiences.

Values

Values

While there is value in the items on the right, we value the items on the left more.

  1. ExperiencesoverFeatures

    Working software matters — but how it feels to operate a business with that software matters more.

  2. Customer ControloverProduct Control

    The product should adapt to a customer’s business logic, not force businesses to adapt to our application logic.

  3. ClarityoverCleverness

    Intelligent users deserve systems that respect their intent, make consequences visible, and enable recovery from mistakes.

  4. End‑to‑End JourneysoverIsolated Interfaces

    An experience spans roles, moments, failures, and outcomes — not just screens and clicks.

Principles

12 principles behind the values

  1. 01

    Experience is the product

    A product is not complete when it works — it is complete when it earns trust and confidence through use.

  2. 02

    Everyone impacted is a user

    If a person is affected by our system — customers, end‑customers, partners, administrators, agents — they are having a user experience, whether they log in or not.

  3. 03

    Respect user intelligence; design for human fallibility

    Assume users are capable and intentional.

    Design systems that prevent silent failure, surface impact, and enable correction.

  4. 04

    Business logic belongs to the business

    Customers must be able to express their rules, policies, and constraints without being limited by application assumptions.

  5. 05

    Application logic must not dictate organisational reality

    Architecture serves the experience — never the other way around.

  6. 06

    Control is a first‑class experience

    Authorisation, access, scope, and delegation are not technical details; they are core to how safe and effective a system feels.

  7. 07

    Design for recovery, not perfection

    Errors will happen. Great experiences make mistakes understandable, reversible where possible, and learning‑oriented.

  8. 08

    Prototype to learn, validate to decide

    Opinions do not scale. Evidence does.

    We validate experiences with real users before committing to build.

  9. 09

    Consistency enables confidence

    Coherent behaviour across roles, environments, and products reduces cognitive load and increases trust.

  10. 10

    Friction anywhere degrades trust everywhere

    Setup, onboarding, configuration, and failure states are as important as daily use.

  11. 11

    Experience quality is not subject to the 80/20 rule

    Mediocre experiences are remembered longer than missing features.

  12. 12

    If we cannot articulate the experience, we are not ready to build

    Ambiguous promises of “great UX” are a risk, not a strategy.

Closing

Adopting this manifesto means:

  • Accepting complexity without leaking it
  • Giving up false certainty early
  • Shifting power closer to customers
  • Measuring success by trust, not output

It is harder — and it is worth it.

It is harder — and it is worth it.