Our approach.
A delivery method for programs where people, process and technology change together.
Get in touchPrinciples
Establish the actual position.
Before planning, we establish where the program stands on scope, schedule, risk and the people affected. Programs get into trouble when the reported position and the actual position diverge.
Make decisions traceable.
Each significant decision is recorded with who made it, the reasoning, and the information available at the time, so it can be reviewed and defended later.
Plan for the people.
Most delivery problems surface when people have to work differently. Readiness, training and support are scheduled from the start.
Report for decisions.
Reporting states the program's position and the decisions leadership needs to make.
Method
Diagnose
Map the current state: processes, stakeholders, risks, issues and decisions already made.
Structure
Set governance and decision rights, baseline the schedule, establish the risk and issue register, and agree how progress is reported.
Prepare
Capture and validate requirements, test with the people who will use the system, and build training around roles.
Transition
Confirm readiness, conduct a pre-mortem, and go live with support in place.
Close and hand over
Record lessons learned and hand the capability to the people who will run it.
Engagement models
Program health check
A fixed-scope review of a program's position, with the three priority actions.
Embedded support
Governance, reporting and change management delivered within your program team.
Transition support
Readiness, training and handover planning for a system or capability entering service.
Purpose-built tools
Where a program has a problem no product addresses, we design and build the software to solve it.
Our method draws on Project Management Institute standards and the Prosci ADKAR model of organisational change.