Guide · C83

Size marketing-roadmap buffers

Question addressed

Which protection should be added without turning every estimate into hidden slack?

Direct answer

Buffers pool the uncertainty of critical tasks and separate project protection, feeding-path protection and prohibited local reserves.

Decision supported

01Set the size, location and consumption thresholds of each buffer.

02The rule, the evidence and the next review date stay visible.

How to use this

Move from the question to the deliverable.

01Starting point

Which protection should be added without turning every estimate into hidden slack?

02Decision prepared

Set the size, location and consumption thresholds of each buffer.

03Deliverable to use

Buffer calculation by aggregated uncertainty

Calculation · SQ-83

Pool 22 days of uncertainty into 9 days of protection

Adding up every local margin inflates the roadmap and protects each task at the expense of the overall deadline. A buffer aggregates the uncertainty of the critical path without hiding it.

Working context

Fictional launch roadmap: six critical tasks, likely and prudent estimates, target date in 54 days.

  1. 01Remove local margins

    Separate likely duration from uncertainty at task level.

  2. 02Isolate the chains

    Distinguish the critical path from feeding chains.

  3. 03Aggregate

    Take the square root of the sum of squared uncertainties.

  4. 04Steer

    Link buffer consumption and real progress to three decision zones.

Original element

A 9-day project buffer and two feeding buffers

The 22 days of individual margins are not added together. Pooling them protects the deadline with nine visible days.

Calculation methodBuffer = √Σ(prudent duration − likely duration)²
Critical taskLikelyPrudentUncertaintySquareProtection
Positioning6 d9 d3 d9Project
Offer8 d12 d4 d16Project
Tracking7 d11 d4 d16Project
Creative10 d15 d5 d25Project
Enablement6 d9 d3 d9Project
Acceptance5 d8 d3 d9Project
Total42 d64 d84√84 = 9.2 d
Decision interpretation

01The likely duration of the path is 42 days; a visible 9-day buffer brings the internal target to 51 days.

02Consuming more than 6 days before 50% progress triggers a rephasing.

03The method avoids treating the three remaining days up to the external date as an implicit margin.

Fictional case. The formula assumes partially independent uncertainties; correlated risks must be added explicitly.

Coherence controls

Minimum conditions before validation.

01No loop

The status, the evidence and the owner must be available for review.

02Realistic milestones

The status, the evidence and the owner must be available for review.

03Owners present

The status, the evidence and the owner must be available for review.

04Explicit buffers

The status, the evidence and the owner must be available for review.

Usable deliverable

Output produced

Buffer calculation by aggregated uncertainty

Explore the decision further with an interactive control, or start from a structured template to produce your deliverable.