How we work

From an idea to a product in the world

If you have an idea, or something half-built that has stopped moving, the reasonable thing to ask is what the whole thing looks like. This page is that answer: the full route, in the order it actually gets walked, with nothing held back.

Then the part that is different here. We will show you the entire hill and sell you one stretch of it at a time. Why that is the whole argument is at the bottom of this page. The route comes first.

The route

Products differ. The ground they cross does not. Every product we have worked on moves through the same three disciplines in the same order, up one side and down the other.

Point at a part of the hill.

You start at brand, because it is the hardest thing to pivot later and it sets the lens every decision above it gets made through. You climb through UX to UI, where brand and experience finally have to agree with each other in a single artifact — which is usually where the consequential decision sits.

That is the Summit, and what it produces is a shape: the product settled far enough that someone can build from it, still loose enough to leave the how open, and bounded enough to be finished. A direction on its own is not a shape. It is the difference between knowing where you are going and knowing how much of it you are doing — and it is what everything below the Summit spends itself proving.

Then the same three in reverse, and this is the half most studios do not sell. The interface stops being one hero screen and becomes a system that has to hold. Real users arrive and replace the prototype. The story you told at the base finally meets a market that either hears it or does not. Going up, each discipline is a belief. Coming down, each one is tested.

UIUXBrand
AscentSummitDescent
  1. Ascent — what you believe

    Working in hypothesis. Each answer is the best judgment available before contact with reality.

    1
    Brand
    Who is this for, and where do we sit against everyone else?
    The core user, positioning, naming, identity, the system that carries them.
    • Who exactly is this for, and who is it not for?
    • What do we stand for that the alternatives can’t credibly claim?
    • What are we called, and what do the mark, colour and type have to say?
  2. 2
    UX
    What should the experience be?
    Journeys, flows, prototypes — the experience as hypothesis.
    • Which single journey has to work before the rest of the product matters?
    • What happens in the first five minutes, before anyone is convinced?
    • Should we build this or that — and what evidence would settle it?
  3. 3
    UI
    What does it actually look like?
    Hero screens and exploration — where brand and UX first have to agree.
    • What does the hero screen look like when brand and experience finally agree?
    • Which directions are worth exploring, and which one do we commit to?
    • What components does this product actually turn out to need?
  4. Summit
    Has it found its shape, and is that shape worth committing to?
    The Decision. The shape is settled — concrete enough to build from, bounded enough to finish. Everything below is execution.
  5. Descent — what turns out to be true

    The same three, now exposed. Every belief formed on the way up gets tested on the way down.

    4
    UI
    Does the system hold as it extends?
    The real components — variations, states, the set the build uses.
    • What variations and states does each component need to survive real use?
    • What must engineering be able to build from without us in the room?
    • Does the pattern still hold at the twentieth screen, or only the first?
  6. 5
    UX
    What is the experience, actually?
    Beta and early testers on the real thing, rather than a prototype.
    • What are early testers doing that we never designed for?
    • Which assumption the prototype rested on turned out to be wrong?
    • Given what beta showed, what do we change before opening it wider?
  7. 6
    Brand
    Does the market hear what we meant?
    The website, the launch, the story — the product meeting its market.
    • What should the website say, show and do?
    • What do we say when this meets the market for the first time?
    • Does the story we told at the base still describe what we built?

Six numbered stretches, and the Summit is the turn between them rather than a stage of its own — it happens inside the Climb that reaches it. Each of the six is at least one Climb: a bounded week with one Question and one Decision at the end of it. None of them can be skipped for free. What you can do is arrive part-way up, having already settled the ones below you.

A Climb on the way down is still a Climb, at the same price. What it does not have is a Summit — nothing is left to decide, so the week goes into making the decision hold, and we are available daily instead of at a fixed midweek meeting. Which side of the hill your week falls on is a position, not a different thing to buy.

Where you start

Almost nobody starts at the bottom. You start where your product already is, and the useful question is not what to do first but what is still unclimbed above you.

Just an idea
The base

Nothing is built and everything is still open. This is the cheapest place on the whole hill to change your mind, and the most expensive place to guess.

First QuestionWho exactly is this for, and who is it not for?
Built, not launched
Climbing

There is a product, or enough of one to argue about, and nobody outside the team has used it yet. Usually the decisions got made in a different order than this, and one of them is quietly holding the rest up.

First QuestionWhich decision is the work actually waiting on?
Live, and refining it
Descending

It is out, people are using it, and the work now is refinement — the system, the edges, the story it tells. What was a belief on the way up is being tested by real use, and some of it does not survive.

First QuestionWhich decision from the way up is real use now testing?

Starting above the base is normal. What it does mean is that some decisions below you were made by default rather than on purpose — and if the product is stalling, a skipped stretch is the first place to look.

See the whole hill →

How long a hill takes

A Climb is one week. One Question, one Summit, one Decision. A question too large for a week is not a longer Climb; it is several, taken one at a time, and each one still has to land on a decision by Wednesday.

Every stretch needs at least one, so crossing a whole hill has an arithmetic minimum: six stretches, one Climb each, is six weeks — and at $8,000 a week, $48,000 from nothing to a product that has met its market. That is the fastest the ground can be crossed, and it assumes every question is settled on the first run at it.

Weeks are bought one at a time. Plenty of people buy exactly one, get the decision they came for, and go and build — six is how much ground a whole hill has on it, not how many you take.

Treat it as arithmetic, not as an estimate of your hill. In practice a stretch takes as many Climbs as it takes: sometimes one settles brand, sometimes there are four decisions in it and it takes four. Nobody can tell you which in advance, and a studio that quotes you the number is quoting a guess.

So a real hill, base to base, is months rather than weeks — with gaps in it, because you will spend time building between decisions and should. What we can promise precisely is the unit: a week, a decision, and the artifacts to act on it.

Why we sell one stretch at a time

The route above is a map: where you are, and what is still unclimbed above you. Which is a different thing from a plan.

A plan for the whole hill has to be written at the moment you know least about it — before the user research, before anyone has clicked a prototype, before the market has heard the story. Every decision after the first one would be committed to in advance, on the strength of that guess. Six stages at a price each is a waterfall with better vocabulary.

There is a sharper version of the problem. Every Climb ends by naming the Question worth taking on next — and if that week is already paid for, the answer can never honestly come back not yet, or not that one. A prepaid decision is not a decision, and the decision is the thing you are buying.

Two things make buying one at a time safe rather than open-ended:

You are never committed past the Climb you are in.

What you have at the end

Every Climb leaves a Question, a Decision and the reasoning behind it, the artifacts that support or act on it, and one reflection on what was learned. It accumulates in your own workspace, and it is yours.

Which is the part that compounds. A year in, you can answer why the product is the way it is — not from memory, but from a record of what was uncertain, what was chosen, and what it ruled out. New people can read it. The second hill costs less than the first, because you have already learned to read the ground.

Book a call

Half an hour. We work out what you are trying to move forward, which decision is actually holding it up, and where that puts you on the hill. If there isn’t a Climb worth making, we’ll say so.