Responsibility where
the work needs it.

From the first delivery plan to the operational handover, I help make complex software implementations workable.

Plan and deliver an implementation

You have software to introduce and a lot that needs to come together: customer requirements, technical dependencies, internal teams and a launch to prepare for.

Discuss this situation

What I take on

I bring those pieces into one workable delivery plan. I coordinate requirements, milestones, decisions and risks, keep stakeholders aligned, and follow the work through testing and rollout.

The work may include

  • Implementation plan and delivery milestones
  • Clear ownership, dependencies and decision tracking
  • Stakeholder coordination and launch readiness
From enterprise pilot to global launch

A 12-month pilot, nine client workstreams and six internal teams.

Read the example

Get a difficult rollout back on track

Progress has slowed, expectations differ, or the same issues keep coming back. The team needs a clear account of what is blocking delivery and who can move it forward.

Discuss this situation

What I take on

I work through the requirements, technical constraints and stakeholder expectations with the people involved. I bring decisions into the open, establish ownership, and coordinate the follow-through needed to restore progress.

The work may include

  • A shared view of blockers, priorities and risks
  • Agreed decisions, owners and next steps
  • Practical progress tracking and escalation coordination
Closing the gap during an enterprise pilot

Client expectations, product capability and a fixed launch window brought into one conversation.

Read the example

Prepare people for the handover

The software is approaching launch, but the people who will use and support it need more than a demonstration. Handover needs to be part of the implementation.

Discuss this situation

What I take on

I plan user and administrator training around the work people actually need to do. I develop supporting materials and knowledge-transfer activities, and coordinate operational readiness with the teams taking over.

The work may include

  • User and administrator training
  • Practical documentation and knowledge transfer
  • Handover activities and operational readiness
From requirements to independent operation

A 36-month implementation, through training and handover to the client’s operations team.

Read the example

Build practices the team can use

Customers are already using the software, but delivery knowledge is scattered and too much depends on a few experienced people. The team needs working practices it can use day to day.

Discuss this situation

What I take on

I help organize how work is documented, handed over and shared. That can include knowledge bases, reusable templates, training materials, coaching and a regular way for colleagues to learn from one another.

The work may include

  • Practical delivery and support processes
  • Knowledge bases, templates and training materials
  • Coaching and knowledge-sharing practices
Making experience reusable

Reusable delivery frameworks and a weekly peer knowledge-sharing program led over one year.

Read the example

Scope around
the situation.

Some work needs a defined project and a clear handover. Other work needs someone embedded with the team over a longer period.

We agree the responsibilities, boundaries and working arrangement around what you need. You don’t need to arrive with a complete brief.

What needs to
move forward?

Tell me what you’re implementing, where things stand, and where you need someone to take responsibility.

Let’s discuss your situation