The 4D Method

Diagnose. Design. Develop. Deliver.

A connected sequence held together by a single principle: intent must survive the journey from first question to live operation.

Advisory team reviewing a city-scale model and live operations data in a control room
Before the method

Before the method: the Four Clocks.

Infrastructure lasts for decades. Technology evolves in years. Operations change every day. Institutions adapt at their own pace. Mobility decisions become difficult when these clocks are treated as if they were synchronised.

The Four Clocks framework helps name the tension before the organisation jumps to a solution.

Advisory value

Bringing the four clocks into one decision table before prescribing the next step.

The Four Clocks describe the tension. The 4D Method is how MagicPill moves from that tension to diagnosis, design, development and delivery.

The 4D method

A method, not a process diagram.

The 4D method is not a rigid sequence of tasks. It is a way to keep evidence, direction, governance and delivery connected.

  1. Diagnose
  2. Design
  3. Develop
  4. Deliver
D1

Diagnose

Purpose

Establish the real question. Separate symptom from cause. Build a baseline of facts that all parties can accept.

Typical output

An independent assessment with a clear problem statement and defensible evidence base.

Typical artefacts

Problem statement · evidence baseline · decision context map · issue/cause separation

D2

Design

Purpose

Set direction at the level of intent: what the system, programme or institution should become, and what it should stop being.

Typical output

A direction the organisation can own, govern and communicate.

Typical artefacts

Target direction · governance principles · strategic options · decision criteria

D3

Develop

Purpose

Convert intent into the artefacts that procurement, governance and delivery actually need.

Typical output

Specifications, governance arrangements, sequencing and procurement logic aligned with the agreed direction.

Typical artefacts

Roadmap · procurement logic · specifications · governance arrangements · implementation sequence

D4

Deliver

Purpose

Stay engaged through implementation and protect intent against pressure to compromise on the wrong things.

Typical output

Senior oversight through delivery and into early operation.

Typical artefacts

Delivery oversight · decision gates · implementation assurance · early operation review · intent protection log

Where clients usually enter

The method can be joined at any phase.

Not every engagement starts at D1. The entry point depends on the maturity of the question, the evidence available and the implementation risk.

Situation
Before a decision
Response
Diagnose
Situation
After a direction is agreed
Response
Design
Situation
When a programme needs mobilisation
Response
Develop
Situation
When implementation needs protection
Response
Deliver
Independence by design

Independent by design. Connected through delivery.

MagicPill holds no supplier relationships, sells no technology and carries no incentive to favour a particular system, vendor or implementation path. Advice is shaped by the client's context, grounded in implementation experience, and held close from first conversation through to delivery.

Principle 01

Unbiased diagnosis

The diagnosis is shaped by evidence, independent of any solution the practice would later be paid to build or operate.

Principle 02

Unsiloed delivery

Senior responsibility remains close to the work from first conversation to delivery, avoiding the handover gaps that often weaken intent.

Preserve value. Improve performance. Invest with purpose.

The aim is simple: preserve intent, improve performance and make decisions easier to govern.