methodatlas
Session Builder

Plan my session

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

Method session60-120 minWorkshop or asyncTimeline

Session: Timeline

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 2-12. 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 Timeline. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Fix scope

    10-20 min

    Define trigger, goal, and boundaries of the view. Collect non-fitting topics in a parking lot. Hint: A narrow scope creates better results than a complete but diffuse sweep.

    FacilitatorTimeline
  2. 2

    Collect raw material

    20-40 min

    Gather facts, events, options, constraints, or assumptions and make them visible. Hint: Keep facts and interpretations separate. Mark uncertain points instead of smoothing them over.

    FacilitatorMilestones
  3. 3

    Build structure

    30-60 min

    Fill the timeline step by step, clarify relationships between elements, and make contradictions visible. Hint: Do not evaluate too early. Stabilize structure first, then draw conclusions.

    FacilitatorInsight Notes
  4. 4

    Check and condense

    20-40 min

    Mark gaps, weak assumptions, counterexamples, and critical paths. Check result for comprehensibility. Hint: If nobody can explain the logic in two minutes, the artifact is not finished.

    FacilitatorTimeline
  5. 5

    Define next steps

    15-20 min

    Document decision, experiment, test, measure, or follow-up with owner and date. Hint: A good artifact without next action remains knowledge work without effect.

    OwnerMilestones
  6. 6

    Publish artifact

    10 min

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

    OwnerTimeline
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Timeline

Goal

Artifact: Timeline

Working Question

Which events, decisions, and dependencies explain the trajectory, and which patterns become visible from it?

Context

Scope, trigger, known facts, relevant constraints, previous options or events, and desired result of the session.

Setup

  • Format: Method session
  • Duration: 60-120 min
  • Mode: Workshop or async
  • Participants: Facilitator; domain experts from the affected area; one owner for result and follow-up; named decider for decisions.
  • Owner: Facilitator
  • 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 Timeline. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Working board or document for timeline; existing notes, data, decisions, and assumptions; markers for uncertainty, owner, and next steps.

Preparation

Prepare an empty timeline template. Make scope and working question visible at the top. Mark every assumption as assumption, not as fact.

Agenda

  1. Fix scope (10-20 min) Owner: Facilitator Action: Define trigger, goal, and boundaries of the view. Collect non-fitting topics in a parking lot. Hint: A narrow scope creates better results than a complete but diffuse sweep. Output: Timeline

  2. Collect raw material (20-40 min) Owner: Facilitator Action: Gather facts, events, options, constraints, or assumptions and make them visible. Hint: Keep facts and interpretations separate. Mark uncertain points instead of smoothing them over. Output: Milestones

  3. Build structure (30-60 min) Owner: Facilitator Action: Fill the timeline step by step, clarify relationships between elements, and make contradictions visible. Hint: Do not evaluate too early. Stabilize structure first, then draw conclusions. Output: Insight Notes

  4. Check and condense (20-40 min) Owner: Facilitator Action: Mark gaps, weak assumptions, counterexamples, and critical paths. Check result for comprehensibility. Hint: If nobody can explain the logic in two minutes, the artifact is not finished. Output: Timeline

  5. Define next steps (15-20 min) Owner: Owner Action: Document decision, experiment, test, measure, or follow-up with owner and date. Hint: A good artifact without next action remains knowledge work without effect. Output: Milestones

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

Closeout

  • Update result artifact: Timeline
  • 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

Timeline: Timeline

Working Question

Which events, decisions, and dependencies explain the trajectory, and which patterns become visible from it?

Context

Scope, trigger, known facts, relevant constraints, previous options or events, and desired result of the session.

Participants

  • Owner: Facilitator
  • Participants: Facilitator; domain experts from the affected area; one owner for result and follow-up; named decider for decisions.

Input

Working board or document for timeline; existing notes, data, decisions, and assumptions; markers for uncertainty, owner, and next steps.

Template

Incident Timeline

Incident: ... Period: ... Sources: logs, alerts, chat, tickets

TimeEventSourceConfidenceNote
HH:MMhigh/medium/low

Observed delays

  • ...

Open gaps

  • ...

Learnings

  • ...

Completion Check

  • Timeline 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

Incident Timeline

View templateChronological template for incident reconstruction with sources and uncertainty.
markdown

incident-timeline-markdown.md

Chronological template for incident reconstruction with sources and uncertainty.

Incident Timeline

Incident: ... Period: ... Sources: logs, alerts, chat, tickets

TimeEventSourceConfidenceNote
HH:MMhigh/medium/low

Observed delays

  • ...

Open gaps

  • ...

Learnings

  • ...
Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Timeline.
  • Store artifact with date, scope, and participants. On new evidence, create a new version or change note so decision logic stays traceable.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet