Template · C32

Map roadmap dependencies

Question addressed

Which prerequisites can block the roadmap?

Direct answer

Each dependency links an upstream and downstream object to a type, date, owner, status and fallback option.

Decision supported

01Secure, decouple or rephase critical dependencies.

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 prerequisites can block the roadmap?

02Decision prepared

Secure, decouple or rephase critical dependencies.

03Deliverable to use

Dependency map

Dataset · SQ-10

Turn a list of prerequisites into a governable set of dependencies

A useful dependency states its type, its required date, its owner, a fallback and the impact of a delay.

Working context

Illustrative data set for the launch of a new B2B offer.

  1. 01Identify

    Name the upstream deliverable actually needed, not just the team concerned.

  2. 02Type

    Distinguish finish-to-start, start-to-start, external constraint and resource availability.

  3. 03Quantify

    Estimate the lead time, float, impact and decision deadline.

  4. 04Secure

    Assign an owner and a fallback to the critical links.

Original element

Dependency register of the launch

The register shows that legal validation, despite its short duration, carries the greatest delay impact.

UpstreamDownstreamTypeRequired dateOwnerFallbackDelay impact
Offer approvalMessagingFinish → start12/09Product marketingRestricted version4 d
MessagingCreativeFinish → start18/09BrandMinimal kit6 d
PricingSales trainingFinish → start20/09FinanceProvisional range3 d
LegalLanding pageExternal constraint24/09LegalForm without evidence8 d
TrackingMedia activationFinish → start27/09Marketing opsPilot budget5 d
CreativeMedia activationStart → start25/09AcquisitionStatic formats2 d
CSV · 7 columnsDownload the dependency register
Decision interpretation

01The Legal → landing page dependency must receive an escalation date before 24/09.

02The “pilot budget” fallback reduces the impact of a tracking delay, but limits the reading of performance.

03A dependency without a fallback must be visible in the risk register.

Fictitious data. Delay impacts must be recalculated from the real roadmap.

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

Dependency map

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