Skip to content

How I work

Understand. Design. Build. Deliver.

The same four phases apply whether the system is an ERP, an operational platform or an AI workflow. Timing depends on the work.

Four phases

One line from problem to handover.

  1. 01

    Phase 1

    Understand

    I start by naming the operational problem, who it affects and why it matters now. I talk to the people doing the work and look at the tools and data they use today. Operational reality becomes clear, testable requirements. We decide what to build first and what can wait.

    • Business Problem
    • Discovery
    • Requirements
    • Product Strategy
  2. 02

    Phase 2

    Design

    I design the data, integrations and workflows before code begins. Screens are shaped around the tasks people repeat every day.

    • Architecture
    • UI/UX
  3. 03

    Phase 3

    Build

    The application, integrations and business logic are built and tested. Where it helps, AI is added with a human review step.

    • Development
    • AI Integration
  4. 04

    Phase 4

    Deliver

    The system is released with care for existing data and continuity. The team receives a system they can run, with documentation and handover.

    • Deployment
    • Delivery

Behind the method

Two questions, one system.

Can it work?

Architecture tests the data, integrations, operating constraints and implementation path.

Will it work for people?

Product and UI/UX decisions follow the real tasks, reviews and handovers of daily operations.

Prepare for discovery

What to prepare before a solution architecture consultation.

Bring one operational problem, your current steps and tools, the people involved and the decisions still open. Mark unknowns: you can describe the problem before you have a complete specification.

Copy this preparation worksheet.

Fill in what you know. Write “unknown” beside anything that needs checking.

Problem
The difficulty you want to examine, in everyday language.
Trigger
The event that starts the task, such as a request arriving.
Current steps and tools
What happens now and where each record is kept.
People and next owner
Who does the work, who receives it and who makes the next decision.
Information needed
What each person needs before they can proceed.
Missing-information path
Who follows up, where the task waits and how it returns for review.
Constraints
Known limits on access, budget, timing or changing existing tools.
Open decisions
What your team has yet to decide and what evidence would help.

Fictional example: a purchase request waiting for a quote.

Illustrative scenario, not a client case study or a tested software design.

A request arrives by email. An administrator copies it into a spreadsheet. The manager cannot approve it because the supplier quote is missing. The administrator follows up, then returns the request for review.

Keep an open-decision log.

  • Does the handoff need a clearer owner? Ask the administrator and manager how requests are assigned and followed up.
  • Can the tools exchange records? Ask the tool owner about versions, interfaces and access restrictions.
  • Is a software change worth scoping? Confirm requirements and remaining gaps with the process owner and technical team.

These questions do not establish that an integration is available or that new software is the right choice.

Use a written description or a redacted sample. Leave passwords and private customer records out of an initial message. Implementation scope, cost, milestones and support need an engagement-specific agreement.

General discovery principles: GOV.UK discovery guide and user research in discovery. The worksheet and fictional example are my preparation guidance.

Discuss one workflow and your open decisions

Questions about how I work?

Start a consultation
RITEGROUP logoEPIC logoHisably logo4 Horizons Group logoRZ Foods logo