Our approach

The Forlanto Delivery Framework

One front door, five stages and five gates, designed to remove the root causes that stall change.

Designed from the root causes up

Most delivery frameworks start with a process diagram. Ours started with a question: why does good change stall? Across telecoms, healthcare and the public sector, the same eight causes appear again and again.

The Forlanto Delivery Framework is built to remove each of them, and it scales from a single project to a full portfolio. We tailor it to your organisation, your regulators and your suppliers.

Eight root causes we design out
Root cause 1Too many front doors

One front door and one short request form for every idea.

Root cause 2Priority by volume, not value

Weighted value scoring, applied the same way to every request.

Root cause 3Capacity ignored

A capacity line drawn every planning cycle, so work starts only when people are free.

Root cause 4Unclear ownership

A named sponsor and owner for every initiative and dependency.

Root cause 5Gates without teeth

Gates with clear criteria and the authority to say not yet.

Root cause 6Plans owned by one party

One work breakdown built and signed by internal teams and suppliers together.

Root cause 7Quality and compliance arrive late

Quality, validation and compliance planned into the work from the start.

Root cause 8Benefits never tracked

Benefits tracked after go-live against the original case.

Five stages, five gates
1

Idea and Assessment

  • Request through one front door
  • Value and strategic fit scored
  • Effort and risk profiled separately
Who leads

Sponsor and portfolio office

Key outputs

Request form, prioritisation scorecard, demand register

Gate 1Is it worth pursuing?
2

Initiation and Design

  • Requirements and options
  • High-level design
  • Cost, people and time sized
Who leads

Business owner and design lead

Key outputs

Requirements, high-level design, initiation document

Gate 2Do we fund it?
3

Delivery Readiness

  • One jointly owned work breakdown
  • Dependencies owned and dated
  • Resources and contracts secured
Who leads

Programme or project manager

Key outputs

Delivery plan, RAID log, resource plan

Gate 3Are we ready to build?
4

Agile Delivery

  • Planning increments and sprints
  • Weekly plain-language reporting
  • Testing and validation built in
Who leads

Delivery lead and teams

Key outputs

PI objectives, sprint outputs, test evidence

Gate 4Are we ready to go live?
5

Deployment and Benefits

  • Planned cut-over and early-life support
  • Training and adoption
  • Benefits measured and lessons shared
Who leads

Business owner and service owner

Key outputs

Go-live plan, handover, benefits and closure report

Gate 5Did we get the benefits?
Watch the framework
Case study: from idea to benefitsPublic sector case study | 3:58 | Narrated

Let's connect

Tell us what you need to deliver. We reply within one working day to arrange a short, no-obligation conversation.

Start a conversation