Skip to content

How I work

First I understand how it works. Then I write code.

Whether it's a website, a business tool or a campaign, every project goes through the same five phases. Not as a ritual: each one removes a doubt before it gets expensive.

Five phases, in this order.

  1. 1Phase 1 / 5

    Understand

    What happens

    I ask how the work happens today: who does it, with which tools, where it gets stuck. For a €1,200-a-month campaign I spent two weeks just understanding how the client sold. They weren't wasted weeks.

    What comes out

    The problem in one sentence, the priorities, what stays out.

  2. 2Phase 2 / 5

    Design

    What happens

    Before screens, I draw the flow: who comes in, what they can do, which data matters, where a person has to decide. Like Tolkien's maps: the world first, then the story.

    What comes out

    Flows, roles and a first version to discuss.

  3. 3Phase 3 / 5

    Build

    What happens

    I build in pieces you can see and try straight away, not months of silence and then a delivery. I pick technology for the problem: often Astro and Cloudflare, sometimes Shopify, sometimes a well-made spreadsheet is enough.

    What comes out

    Working pieces to try, one at a time.

  4. 4Phase 4 / 5

    Measure

    What happens

    Before going live I check access, edge cases, speed and above all tracking. If you don't measure properly, you can't improve properly: an unchecked event always lies.

    What comes out

    A release where the numbers add up.

  5. 5Phase 5 / 5

    Improve

    What happens

    After release I watch how it's really used: questions, errors, habits. Sometimes the most useful improvement is removing things: on one store I won back a second of load time by deleting three apps nobody used.

    What comes out

    Next steps, decided on data rather than hunches.

Six questions I always ask.

Not a form to fill in. It's what I need to know so I don't build the wrong thing.

Goal
Which result should become easier to achieve?
People
Who will use the system and what decisions must they make?
Data
Where does it come from, where does it live and who can change it?
Constraints
Time, budget, tools already in use, privacy.
Measure
How will we know the change actually helped?
Risk
What cannot stop, get lost or become opaque?

Three things I don't negotiate.

A test beats an opinion

Mine included. I used to guess the winning ad wrong six times out of ten: since then, we try first and decide after.

Technology you can explain

If I can't explain what an automation does and how to stop it, it shouldn't be running in your company.

Clarity, even when it's awkward

Organising hikes taught me that saying the weather is turning early is kinder than finding out at the top. Quotes and deadlines work the same way.

Which phase do we start from?

Usually the first. Tell me how your work happens today and where it gets stuck: I reply myself, within two working days.