Skip to content
Nominal FR Let's talk about your project

Programme management & project management.

A transformation project rarely fails on the technology. It fails on scoping, on decisions that are never taken, and on the buy-in of the teams. Nominal scopes, steers and delivers, until the change is adopted.

The programme schedule
Data migration overruns, and everything behind it slips.
01 / Issues

What is at stake.

  • Loose scopingAn objective everyone understands differently, a scope that grows along the way.
  • Decisions that dragDecisions escalate, wait for a committee, and the schedule slips in silence.
  • The business absentA project driven by IT or by a supplier, without the people who will use it.
  • The day afterThe system is delivered, but the teams keep their old habits.
02 / Services

Five ways to step in.

  1. 2.1
    Project scopingObjectives, scope, budget, risks, organisation. A document that leadership signs and the team understands.
  2. 2.2
    PMO & governanceThe forums, the roles, the reporting. Who decides what, at what pace, on the basis of what information.
  3. 2.3
    Programme managementOverall steering: milestones, dependencies, budget, suppliers and decisions, alongside the sponsor.
  4. 2.4
    Change managementCommunication, training, relays within the teams. Measuring adoption, not just delivery.
  5. 2.5
    Independent project reviewA project going off track: assessment within days, causes, options, recovery plan.
03 / Approach

The approach, step by step.

  1. A

    Scope

    Why, what, for whom, with what resources.

  2. B

    Plan

    Work packages, milestones, dependencies, resources.

  3. C

    Steer

    Progress, risks and decisions, every week.

  4. D

    Deploy

    Testing, training, go-live in waves.

  5. E

    Close

    Review, measured adoption, handover to operations.

04 / Deliverables

Documents that get used.

Programme governance

Sample
  1. MonthlySteering committeeLeadership, sponsor, programme management. Arbitrates budget, scope and priorities.
  2. WeeklyProject committeeWorkstream leads. Tracks milestones, risks and dependencies.
  3. DailyTeam check-inFifteen minutes standing. What is moving, what is blocked, who unblocks.

Each decision has its forum, and each forum has its reason for being. The rest is dealt with outside meetings.

Risk register

Sample
RiskProb.ImpactOwner
Key users unavailable during the testing phaseBusiness lead
Data migration taking longer than plannedIS lead
Supplier late on the interfaceProgramme management
A team's resistance to the new processTeam lead

Each risk has an owner and a mitigation. The one that crosses the threshold turns amber and goes up to the committee.

Three-horizon plan

Sample
Straight away
  • A single person approves
  • Team check-in on Monday, 20 min
  • Emergencies in a single channel
Three months
  • Roles written down and shared
  • Four figures tracked every week
  • The request process simplified
One year
  • A deputy trained
  • Tools reset
  • Steering holds without me

What is done now, what comes next, and what must hold in a year.

Samples, with no real client or figure.

05 / Key moments
06 / Expected results

How you know it worked.

Decisions are taken on time and at the right level. The committee sees risks before they become problems. And six months after go-live, the teams would not want to go back.

Other areas

What often goes with it.

Next step

Scope, steer and deliver transformation projects, through to adoption. Let's talk.

Let's talk about your project