methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method sessionHalf dayWorkshopCoD-Tabelle

Session: Cost of Delay

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with 3-8. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward CoD-Tabelle. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Clarify value types

    20 min

    For each initiative, define which value types are relevant: revenue, cost savings, risk mitigation, opportunity cost, compliance penalty. Record mixed cases as a linear combination. Hint: If no one can name a value type, the initiative is too early for CoD and should go back to discovery.

    FacilitatorCoD-Tabelle
  2. 2

    Phase 2: Estimate CoD per initiative

    60 min

    Estimate CoD per time unit for each initiative, either in euros or relatively (Fibonacci). Use a reference initiative explicitly for scaling. Use a range (min-max) instead of a single-point estimate when disagreement remains. Hint: Avoid false precision. CoD is an order of magnitude, not an exact cent value. But require ranges narrower than tenfold.

    FacilitatorPriorisierungssequenz
  3. 3

    Phase 3: Classify profiles

    30 min

    Set urgency profile per initiative: Urgent (CoD rises immediately), Standard (linear), Fixed-Date (jump at deadline), Intangible (long flat period, then increase). Profile affects sequence. Hint: Fixed-Date profiles often mis-rank the sequence when a date is not firm. Validate external dates.

    FacilitatorCoD-Tabelle
  4. 4

    Phase 4: Duration and CD3

    40 min

    Determine rough effort duration per initiative (weeks or T-shirt sizes). Calculate CD3 = CoD divided by duration and sort descending. Hint: Prioritize critical-path assumptions over FTE effort for duration. Otherwise duration and CD3 are distorted.

    FacilitatorPriorisierungssequenz
  5. 5

    Phase 5: Validate and commit sequence

    30 min

    Validate the sequence against external dates, dependencies, and strategic topics. A deliberately different order is allowed, but must be documented with rationale. Hint: If the sequence is completely re-sorted, either the CoD estimate is weak or there are factors not captured in CoD. State both explicitly.

    OwnerCoD-Tabelle
  6. 6

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerCoD-Tabelle
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: Cost of Delay

Goal

Artifact: CoD-Tabelle

Working Question

How much does each week cost us when this initiative is not delivered, and in which order should we maximize avoided loss?

Context

Per initiative: assumed business value, risk, time window, known external dates; current bottlenecks; list of already-rated initiatives for calibration.

Setup

  • Format: Method session
  • Duration: Half day
  • Mode: Workshop
  • Participants: A facilitator with business-economics background (portfolio lead or finance business partner); 3-6 stakeholders representing value assumptions (sales, product, compliance); one engineering representative for effort duration; a decider for disputed assessments.
  • Owner: A facilitator with business-economics background (portfolio lead or finance business partner)
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward CoD-Tabelle. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Table (initiative, value type, CoD per week or month, effort duration, CoD3 profile, CD3, owner); profile template for Urgent/Standard/Fixed-Date/Intangible; whiteboard for discussion; clear time-window assumptions.

Preparation

Share the table. Define a CoD per time unit scale (for example Euro per week or relative Fibonacci points). Explain profile classification (Urgent, Standard, Fixed-Date, Intangible). Choose one reference initiative as an anchor.

Agenda

  1. Phase 1: Clarify value types (20 min) Owner: Facilitator Action: For each initiative, define which value types are relevant: revenue, cost savings, risk mitigation, opportunity cost, compliance penalty. Record mixed cases as a linear combination. Hint: If no one can name a value type, the initiative is too early for CoD and should go back to discovery. Output: CoD-Tabelle

  2. Phase 2: Estimate CoD per initiative (60 min) Owner: Facilitator Action: Estimate CoD per time unit for each initiative, either in euros or relatively (Fibonacci). Use a reference initiative explicitly for scaling. Use a range (min-max) instead of a single-point estimate when disagreement remains. Hint: Avoid false precision. CoD is an order of magnitude, not an exact cent value. But require ranges narrower than tenfold. Output: Priorisierungssequenz

  3. Phase 3: Classify profiles (30 min) Owner: Facilitator Action: Set urgency profile per initiative: Urgent (CoD rises immediately), Standard (linear), Fixed-Date (jump at deadline), Intangible (long flat period, then increase). Profile affects sequence. Hint: Fixed-Date profiles often mis-rank the sequence when a date is not firm. Validate external dates. Output: CoD-Tabelle

  4. Phase 4: Duration and CD3 (40 min) Owner: Facilitator Action: Determine rough effort duration per initiative (weeks or T-shirt sizes). Calculate CD3 = CoD divided by duration and sort descending. Hint: Prioritize critical-path assumptions over FTE effort for duration. Otherwise duration and CD3 are distorted. Output: Priorisierungssequenz

  5. Phase 5: Validate and commit sequence (30 min) Owner: Owner Action: Validate the sequence against external dates, dependencies, and strategic topics. A deliberately different order is allowed, but must be documented with rationale. Hint: If the sequence is completely re-sorted, either the CoD estimate is weak or there are factors not captured in CoD. State both explicitly. Output: CoD-Tabelle

  6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: CoD-Tabelle

Closeout

  • Update result artifact: CoD-Tabelle
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

CoD-Tabelle: Cost of Delay

Working Question

How much does each week cost us when this initiative is not delivered, and in which order should we maximize avoided loss?

Context

Per initiative: assumed business value, risk, time window, known external dates; current bottlenecks; list of already-rated initiatives for calibration.

Participants

  • Owner: A facilitator with business-economics background (portfolio lead or finance business partner)
  • Participants: A facilitator with business-economics background (portfolio lead or finance business partner); 3-6 stakeholders representing value assumptions (sales, product, compliance); one engineering representative for effort duration; a decider for disputed assessments.

Input

Table (initiative, value type, CoD per week or month, effort duration, CoD3 profile, CD3, owner); profile template for Urgent/Standard/Fixed-Date/Intangible; whiteboard for discussion; clear time-window assumptions.

Template

Cost of Delay Working Template

Goal

Evaluates the economic value per unit of time of an initiative.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • CoD table:
  • Prioritization sequence:

Assumptions and open questions

  • ...

Decision / next step

Owner, date, and success signal.

Completion Check

  • CoD-Tabelle is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

Cost of Delay Working Template

View templateCompact working template for Cost of Delay with context, input, output artifacts, and next step.
markdown

cost-of-delay-working-template.md

Compact working template for Cost of Delay with context, input, output artifacts, and next step.

Cost of Delay Working Template

Goal

Evaluates the economic value per unit of time of an initiative.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • CoD table:
  • Prioritization sequence:

Assumptions and open questions

  • ...

Decision / next step

Owner, date, and success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits CoD-Tabelle.
  • Add one new entry per portfolio review with date. Keep old CoD values and sequence visible. Corrections appear as edit logs, not overwrites, to preserve learning on estimation quality.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet