HOW WE WORK
A clear brief.
A connected way forward.
Understand the challenge. Agree the scope. Coordinate delivery. Prepare the handover.
The details change with the engagement. The purpose stays the same: make the next decision, responsibility and output clear.
FROM THE FIRST QUESTION TO HANDOVER
THE ENGAGEMENT, STEP BY STEP 01 / APPROACH
01 / UNDERSTAND
Start with the right problem.
Establish the problem, audience and starting point before deciding which activities belong in the engagement.
ILLUSTRATIVE REVIEWABLE OUTPUT
The business question, audience, current evidence and unresolved assumptions.
A sample format, not a claim about a completed client engagement.
02 / DEFINE
Agree what the work includes.
Turn the brief into a scope with deliverables, responsibilities and success measures. Make the boundaries as clear as the ambition.
ILLUSTRATIVE REVIEWABLE OUTPUT
Deliverables, exclusions, acceptance criteria, owners, dependencies and review points.
A sample format, not a claim about a completed client engagement.
03 / DELIVER
Keep the workstreams connected.
Coordinate delivery through the agreed review and approval points, so business direction, communication and development stay aligned.
ILLUSTRATIVE REVIEWABLE OUTPUT
The output under review, consolidated feedback, decisions and any written change agreement.
A sample format, not a claim about a completed client engagement.
04 / ENABLE
Leave the business ready.
Prepare the agreed handover, guidance and adoption support so the work can be used beyond the delivery milestone.
ILLUSTRATIVE REVIEWABLE OUTPUT
The agreed files, documentation and guidance, plus owners and the boundary of continuing support.
A sample format, not a claim about a completed client engagement.
MAKE THE EXPECTATIONS EXPLICIT 02 / ALIGNMENT
A useful scope
includes the boundaries.
These points are agreed for the specific engagement. They are not a promise that every service includes the same deliverables or ongoing support.
- Deliverables & exclusionsWhat is included, what is outside scope and how completion will be assessed.
- Ownership & approvalsWho provides inputs, who reviews the work and who gives approval.
- Dependencies & changesWhat the timing depends on and how requested changes will be documented and agreed.
- Handover & supportWhich files, documentation and enablement are included—and what happens after handover.
BEFORE WE BEGIN
Practical questions.
Clearer expectations.
01 Can we engage one discipline? +
Yes. The scope can focus on one discipline or connect several. Start with the business challenge; the combination follows the need, not a fixed package.
02 What determines the timeline? +
The agreed deliverables, dependencies, required inputs and review points. Specific timing is confirmed in the engagement scope rather than assumed from a generic package.
03 What if requirements change? +
Document the requested change and its implications for scope, fees and timing. Changed work begins only after the authorized parties agree in writing.
04 What is included after delivery? +
The handover, documentation, guidance and support that have been agreed for the engagement. Continuing support should be defined explicitly; it is not implied by every project.
YOUR NEXT STEP IMC EXPAND
Start with
the right brief.
You do not need a finished specification. Share what needs to change, who it affects and what is already in place.
Deliverables, responsibilities and timing are agreed around your scope.