How we work

Good work starts with a clear understanding.

The path from a problem to a useful solution should be understandable. Start by making the need clear, then choose an approach that fits.

The outline below is a way to explain the decisions a piece of work may involve. The exact sequence, scope, pace, deliverables, and engagement terms depend on the situation and are agreed separately.

A considered sequence

From context to next steps.

Not every project follows an identical path. These stages offer a shared way to think through the work without assuming a fixed methodology or delivery commitment.

  1. 01

    Understand the context

    Begin with the problem, the people affected, the current situation, and the constraints. The first step is to understand what is happening before assuming what should be built.

    • Who is this for?
    • What is difficult today?
    • What constraints already exist?
  2. 02

    Clarify the need

    Make the desired change more specific. Identify what matters most, what is known, what remains uncertain, and what should sit outside the initial scope.

    • What would be meaningfully better?
    • What must the solution account for?
    • What should wait or remain out of scope?
  3. 03

    Shape an appropriate approach

    Consider possible directions and their trade-offs before settling on a solution. The right shape may be a new product, a focused software tool, an integration, an improvement to an existing system, or a decision not to add technology.

    • What is the simplest useful approach?
    • Which risks need attention?
    • What decisions are needed before work begins?
  4. 04

    Build with the context in view

    If implementation is the right next step, keep the agreed need and constraints visible as the work takes shape. Where appropriate, work can be reviewed in understandable increments so questions and decisions are surfaced early.

    • Does the work still address the original need?
    • Are assumptions changing?
    • Are important trade-offs understood?
  5. 05

    Review against the need

    Look at the result in the context it is meant to serve. Review behaviour, usability, and relevant technical considerations against criteria agreed for the work; identify gaps and next decisions honestly.

    • What has been addressed?
    • What still needs attention?
    • What has been learned?
  6. 06

    Agree what happens next

    Discuss the practical next step: handover, further improvement, or another phase of work. Ownership, access, documentation, support, and ongoing responsibilities should be explicitly agreed for the particular engagement.

    • What needs to be handed over?
    • Who is responsible for each part?
    • Is further work useful or necessary?

Clear expectations

Agree the details, not assumptions.

Before a specific engagement begins, its scope, responsibilities, timing, review points, and commercial terms need to be understood and agreed. Questions about source code, intellectual property, accounts, documentation, handover, support, and ongoing maintenance should be addressed explicitly rather than inferred from a general process description.

The aim is to make decisions visible: what is included, what is not, what depends on another decision, and how a change in context may affect the approach.

Where to begin

Bring the problem you are trying to solve.

You do not need a complete specification to start a conversation. A description of the current situation, what you would like to improve, and any important constraints is a useful starting point.