methodatlas
Session Builder

Plan my session

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

Method session1-3 hWorkshopKnowledge Map

Session: Knowledge Mapping

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

  1. 1

    Phase 1: Scope and domains

    20-30 min

    Finalize knowledge domains. Tune granularity so each domain is recognizable as a coherent knowledge area, not too broad and not too fine. Name critical tasks per domain briefly. Hint: "Frontend" as a domain is too broad. "React routing in app X" is actionable. Tune granularity iteratively.

    FacilitatorKnowledge Map
  2. 2

    Phase 2: Capture knowledge owners

    20-30 min

    Each person self-assesses each domain (P, S, L, blank). Then add peer assessment per person. Clarify larger discrepancies quickly. Hint: Self- and peer assessment diverge often. Record both and take the average, or clarify together.

    FacilitatorCritical Knowledge Areas
  3. 3

    Phase 3: Add artifacts and docs

    15-20 min

    For each domain, note which written artifacts exist (runbook, wiki, ADR, Notion page). Add links or paths. Flag missing documentation. Hint: Knowledge without documentation is person-bound knowledge. Record both as risks even when the person is available.

    FacilitatorTransfer Plan
  4. 4

    Phase 4: Assess criticality

    20-30 min

    Mark each domain with a traffic light: red (single point of failure, no documentation), yellow (two owners or partial documentation), green (three+ owners and documentation). Mark top risks. Hint: Three-owner rule is a guideline. For very large or safety-critical systems, require more.

    FacilitatorKnowledge Map
  5. 5

    Phase 5: Transfer plan

    15-30 min

    Create specific transfer actions for each red risk: pair working, documentation sprint, shadowing, ADR. Assign owner and date. Set re-review cadence, typically quarterly. Hint: Transfer plans without dates are wishes. Better three binding actions than ten unbound ideas.

    OwnerCritical Knowledge Areas
  6. 6

    Publish artifact

    10 min

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

    OwnerKnowledge Map
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Knowledge Mapping

Goal

Artifact: Knowledge Map

Working Question

Where is knowledge located, who is the sole holder, and which gaps or single points of failure must be closed before a critical period?

Context

Scope (team, area, product); list of relevant knowledge domains pre-collected (e.g. Auth System, Billing, Onboarding pipeline, vendor relationships); trigger (team growth, imminent departure risk, onboarding wave).

Setup

  • Format: Method session
  • Duration: 1-3 h
  • Mode: Workshop
  • Participants: A facilitator who keeps domains separated; three to twelve team members; one scribe for the knowledge map and transfer plan; optional lead for criticality scoring when needed.
  • Owner: A facilitator who keeps domains separated
  • 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 Knowledge Map. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Whiteboard or Miro board with matrix (knowledge domain x person); sticky notes for artifacts (documentation, wikis); criticality marker pens (traffic lights); list of relevant systems or tasks; timer.

Preparation

Prepare matrix with columns for domains and rows for people. Use symbols for knowledge levels (for example P = primary, S = secondary, L = learning, blank = unknown). Keep a separate criticality marker.

Agenda

  1. Phase 1: Scope and domains (20-30 min) Owner: Facilitator Action: Finalize knowledge domains. Tune granularity so each domain is recognizable as a coherent knowledge area, not too broad and not too fine. Name critical tasks per domain briefly. Hint: "Frontend" as a domain is too broad. "React routing in app X" is actionable. Tune granularity iteratively. Output: Knowledge Map

  2. Phase 2: Capture knowledge owners (20-30 min) Owner: Facilitator Action: Each person self-assesses each domain (P, S, L, blank). Then add peer assessment per person. Clarify larger discrepancies quickly. Hint: Self- and peer assessment diverge often. Record both and take the average, or clarify together. Output: Critical Knowledge Areas

  3. Phase 3: Add artifacts and docs (15-20 min) Owner: Facilitator Action: For each domain, note which written artifacts exist (runbook, wiki, ADR, Notion page). Add links or paths. Flag missing documentation. Hint: Knowledge without documentation is person-bound knowledge. Record both as risks even when the person is available. Output: Transfer Plan

  4. Phase 4: Assess criticality (20-30 min) Owner: Facilitator Action: Mark each domain with a traffic light: red (single point of failure, no documentation), yellow (two owners or partial documentation), green (three+ owners and documentation). Mark top risks. Hint: Three-owner rule is a guideline. For very large or safety-critical systems, require more. Output: Knowledge Map

  5. Phase 5: Transfer plan (15-30 min) Owner: Owner Action: Create specific transfer actions for each red risk: pair working, documentation sprint, shadowing, ADR. Assign owner and date. Set re-review cadence, typically quarterly. Hint: Transfer plans without dates are wishes. Better three binding actions than ten unbound ideas. Output: Critical Knowledge Areas

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

Closeout

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

Knowledge Map: Knowledge Mapping

Working Question

Where is knowledge located, who is the sole holder, and which gaps or single points of failure must be closed before a critical period?

Context

Scope (team, area, product); list of relevant knowledge domains pre-collected (e.g. Auth System, Billing, Onboarding pipeline, vendor relationships); trigger (team growth, imminent departure risk, onboarding wave).

Participants

  • Owner: A facilitator who keeps domains separated
  • Participants: A facilitator who keeps domains separated; three to twelve team members; one scribe for the knowledge map and transfer plan; optional lead for criticality scoring when needed.

Input

Whiteboard or Miro board with matrix (knowledge domain x person); sticky notes for artifacts (documentation, wikis); criticality marker pens (traffic lights); list of relevant systems or tasks; timer.

Template

Knowledge Mapping Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Knowledge Map:
  • Critical Knowledge Areas:
  • Transfer Plan:

Open questions

  • ...

Next step

Owner, date, success signal.

Completion Check

  • Knowledge Map 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

Knowledge Mapping Working Template

View templateCompact working template for Knowledge Mapping with context, input, output artifacts, and next step.
canvas

knowledge-mapping-working-template.md

Compact working template for Knowledge Mapping with context, input, output artifacts, and next step.

Knowledge Mapping Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Knowledge Map:
  • Critical Knowledge Areas:
  • Transfer Plan:

Open questions

  • ...

Next step

Owner, date, success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Knowledge Map.
  • Create one entry per iteration with date. Refresh every 3-6 months or when people leave. Review action status regularly.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet