methodatlas
Session Builder

Plan my session

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

Method session60-180 minWorkshop or asyncFault Isolation Map

Session: Fault Isolation

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

  1. 1

    Fix scope

    10-20 min

    Define occasion, objective, and boundaries of analysis. Collect off-topic themes on a parking lot. Hint: A tight scope produces better results than a complete but diffuse sweep.

    FacilitatorFault Isolation Map
  2. 2

    Collect raw material

    20-40 min

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

    FacilitatorTest Log
  3. 3

    Build structure

    30-60 min

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

    FacilitatorExcluded Hypotheses
  4. 4

    Review and condense

    20-40 min

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

    FacilitatorNarrowed Fault Area
  5. 5

    Define next steps

    15-20 min

    Document decision, experiment, test, measure, or follow-up with owner and date. Hint: An excellent artifact without a next action remains knowledge work without impact.

    OwnerFault Isolation Map
  6. 6

    Publish artifact

    10 min

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

    OwnerFault Isolation Map
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Fault Isolation

Goal

Artifact: Fault Isolation Map

Working Question

Which system area most likely causes the symptom, and which tests narrow the fault domain further?

Context

Scope, occasion, known facts, relevant constraints, existing options or events, and desired meeting outcome.

Setup

  • Format: Method session
  • Duration: 60-180 min
  • Mode: Workshop or async
  • Participants: Facilitator; domain experts from affected area; owner for outcome 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 Fault Isolation Map. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Workspace or document for isolation map; existing notes, data, decisions, and assumptions; markers for uncertainty, owner, and next steps.

Preparation

Prepare an empty Isolation Map template. Make scope and working question clearly visible at top. Mark each assumption as assumption, not fact.

Agenda

  1. Fix scope (10-20 min) Owner: Facilitator Action: Define occasion, objective, and boundaries of analysis. Collect off-topic themes on a parking lot. Hint: A tight scope produces better results than a complete but diffuse sweep. Output: Fault Isolation Map

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

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

  4. Review and condense (20-40 min) Owner: Facilitator Action: Mark gaps, weak assumptions, counterexamples, and critical paths. Check output for understandability. Hint: If nobody can explain the logic in two minutes, the artifact is not ready. Output: Narrowed Fault Area

  5. Define next steps (15-20 min) Owner: Owner Action: Document decision, experiment, test, measure, or follow-up with owner and date. Hint: An excellent artifact without a next action remains knowledge work without impact. Output: Fault Isolation Map

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

Closeout

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

Fault Isolation Map: Fault Isolation

Working Question

Which system area most likely causes the symptom, and which tests narrow the fault domain further?

Context

Scope, occasion, known facts, relevant constraints, existing options or events, and desired meeting outcome.

Participants

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

Input

Workspace or document for isolation map; existing notes, data, decisions, and assumptions; markers for uncertainty, owner, and next steps.

Template

Fault Isolation 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

  • Fault Isolation Map:
  • Test Log:
  • Excluded Hypotheses:
  • Narrowed Fault Area:

Open questions

  • ...

Next step

Owner, date, and success signal.

Completion Check

  • Fault Isolation 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

Fault Isolation Working Template

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

fault-isolation-working-template.md

Compact working template for Fault Isolation with context, input, output artifacts, and next step.

Fault Isolation 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

  • Fault Isolation Map:
  • Test Log:
  • Excluded Hypotheses:
  • Narrowed Fault Area:

Open questions

  • ...

Next step

Owner, date, and success signal.

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