What will be delivered
Name the user journeys, system connections, outputs and documentation to be delivered. Agree the examples the client will use to check that the implementation does what they need.
The company
How we work
We establish the requirement with the people doing the work, agree the scope and make progress available for review.
Explore the delivery stagesDefine the work with the people who use it.
A project brief rarely explains everything that happens between a request and a completed result.
We speak with the people doing the work, review representative examples and identify what keeps the process moving today. The important details may sit in an email, a spreadsheet, an exception or the knowledge of one person.
That discovery gives the scope a practical basis: the intended outcome, the activities involved, the information available and the decisions needed from each party.
From the brief to ongoing operation.
Understand
Understand
Understand the task before proposing the solution.
We review representative work with the people doing it: the tools they use, the information they need and the interruptions they handle.
- Current process and intended result
- Examples of ordinary work and exceptions
- The people who use and own the process
Define
Define
Agree what will change and how to assess it.
The proposal sets out the work, deliverables, responsibilities and dependencies. We agree what the client needs to review before implementation begins.
- Included work and exclusions
- Access, decisions and client contributions
- Acceptance, timing and commercial terms
Build
Build
Review working increments as they develop.
We implement the agreed behaviour and put meaningful work in front of the client. Feedback and new requirements are assessed against the scope.
- Interfaces and operating rules
- Connections, permissions and approval policy
- Reviews of complete journeys and interrupted work
Operate
Operate
Prepare the people who will run it.
Handover includes the agreed documentation, accounts and operating guidance. We establish ownership, recovery and any continuing support.
- Release and acceptance review
- Accounts, documentation and operating ownership
- Support coverage and further development
Decisions that belong in the scope
Who can decide and approve
Identify the process owner, reviewers and release decision-maker. For AI, the client determines which actions may execute independently and which need review.
How changes are handled
A new system, use case, user group or information source can change the work. We record the effect on delivery, dependencies and commercial terms before treating it as part of the engagement.
What continues after handover
Set out account ownership, usage charges, support coverage and maintenance responsibilities. Ongoing support is available under an agreed arrangement.
Client and delivery responsibilities
Your team
Provides the business context, authorised access, representative examples and decisions on intended use.
EVSP
Carries out the commissioned work, makes dependencies visible and provides the agreed review and handover material.
Specialists
Contribute legal, technical or other professional conclusions where the assignment requires their expertise.
Bring us the current process.
A description of the work and a few representative examples can be enough to establish the first discussion.