The method

A clear idea.
Made to work.

Every project starts with a real situation and works towards an agreed outcome. Technology is chosen along the way, for a specific reason.

  1. Understand

    We look at how
    the work happens today.

    You tell me about your goal, the tools you use and the points where the process gets complicated. If a product already exists, we start there: existing content, features and materials are part of the context.

    To clarify: the problem, people involved, constraints and desired outcome.

  2. Define

    We choose what
    to build first.

    I turn the need into a scope: what the project includes, what it takes to build it and how to recognise a successful result. External services and recurring costs are part of the assessment.

    To agree: the proposal, priorities, timing and costs.

  3. Build

    We put something
    concrete on the table.

    A structure, a prototype or the first working flow makes decisions easier to assess. From there I develop the project and refine the experience around how it needs to behave.

    To observe: real user journeys, content, interactions and edge cases.

  4. Test and hand over

    Delivery means
    handing it over.

    We check what was agreed and clearly distinguish what works from any remaining limitations. We prepare access, instructions and responsibilities for the next stage of use.

    To define: publication, management, maintenance and future development.

Working together

Plain language.
Clear decisions.

The first conversation

You don’t need a perfect
document to begin.

Three things are enough: what you want to achieve, what you do today and what gets in the way. If you already have materials, examples or a product, bring them into the conversation. We will clarify the rest as we work.

The next step

Tell me where
you are right now.

A practical need can help us define a sensible next step.

Tell me where we start