PROCESS

A clear route from business requirement to delivery.

The exact implementation varies by project. The working discipline should not.

FROM FIRST BRIEF TO COMPLETION

The lifecycle.

01
Requirement
What is the business trying to achieve, replace, repair or launch?
02
Context
What already exists? Which systems, providers, deadlines and stakeholders matter?
03
Information
Complete only the forms and material relevant to this project.
04
Scope
Define intended deliverables, assumptions, exclusions and dependencies.
05
Commercial agreement
Confirm the relevant price, payment and contract structure before work proceeds.
06
Access
Request only the access needed for the agreed task.
07
Production
Implement the agreed work.
08
Decisions
Surface questions that affect the project rather than guessing.
09
Review
Present the relevant work for client or agency review.
10
Changes
Separate corrections within scope from new requirements.
11
Launch / handover
Deploy to the agreed environment or hand over the agreed deliverable.
12
Verification
Check the production outcome within our control.
13
Completion
Close the defined project.
14
Support
Continue only where support, monitoring or maintenance is separately defined.

INTERACTION

The useful questions remain simple: what do we need from you now, what are we doing now, what decision is pending and what happens next?

A project is easier to manage when decisions, dependencies and next actions are explicit.

PROGRESSIVE INFORMATION

Enough information to understand the requirement and decide the next route.

Existing environment, brand, technical or infrastructure information is requested only when it affects the work.

Launch details, final access or provider information should not be demanded before there is a real need.

NEXT STEP

You do not need to complete the whole project on day one. Give us enough context to identify the next useful step.