methodatlas
Session Builder

Plan my session

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

Method session1-3 days for initial setup, ongoing maintenanceWorkshop or asyncGolden Path Guide

Session: Golden Path

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

  1. 1

    Section 1: Sharpen use case

    30-60 min

    Define the use case in one sentence: what is the target outcome of the path (for example REST backend in Go with Postgres and central SSO authentication). Explicitly list what is out of scope. Hint: If the use case is too broad ("any service"), the Golden Path becomes generic documentation. Better define three narrow paths than one for everything.

    FacilitatorGolden Path Guide
  2. 2

    Section 2: Describe the path

    2-6 h

    Build a step-by-step guide from repository setup to production deployment. Include one concrete command, template link, or click path per step. Estimate time per step. Hint: If steps exceed one paragraph, automation is missing. Templates and scripts should replace narrative text. A path should stay below twelve steps.

    FacilitatorTemplates
  3. 3

    Section 3: Templates and automation

    4-16 h

    Link or create existing templates (Cookiecutter, GitHub templates, Terraform modules). Evaluate Backstage software templates or similar tooling. Provide CI pipeline templates. Hint: Documentation without templates becomes stale quickly. Teams that only copy commands and config from a wiki page lose consistency within four weeks.

    FacilitatorQuality Checks
  4. 4

    Section 4: Standards and checks

    1-2 h

    Document mandatory quality and security checks: linting, tests, SAST, SBOM, logging conventions. Specify which checks are automated (CI) and which are manual. Define acceptance criteria for being "on the path." Hint: If mandatory checks exist only as plain text, they will be bypassed. Automation in CI is required for all security and compliance-relevant points.

    FacilitatorGolden Path Guide
  5. 5

    Section 5: Exceptions and FAQ

    1-2 h

    Section "if your use case deviates": when is deviation legitimate, how should it be documented (ADR), and who decides. Add common questions from pilot teams to FAQ. Hint: Without an opt-out path, Golden Path feels authoritarian and is bypassed informally. A visible exception process lowers resistance and reveals drift.

    FacilitatorTemplates
  6. 6

    Section 6: Pilot and adoption

    2-4 weeks

    Run path with one to two pilot teams. Observe where friction appears and improve documentation iteratively. Communicate publicly only after successful pilot. Hint: Publishing without a pilot produces docs that fail at first use. Pilot team feedback must be incorporated into v1.0.

    OwnerQuality Checks
  7. 7

    Publish artifact

    10 min

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

    OwnerGolden Path Guide
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Golden Path

Goal

Artifact: Golden Path Guide

Working Question

Which path takes a team from zero to a production-ready state for the defined use case in under one day without breaking standards?

Context

Precisely scoped use case (for example "new backend service with public API"); existing best-practice examples from two to three teams; known pain points the path should solve; non-negotiable compliance and security requirements.

Setup

  • Format: Method session
  • Duration: 1-3 days for initial setup, ongoing maintenance
  • Mode: Workshop or async
  • Participants: Platform team as Golden Path owner; one technical writer or senior engineer as primary author; representatives from two to three product teams as reviewers; one architect or principal engineer as approver.
  • Owner: Platform team as Golden Path owner
  • 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 Golden Path Guide. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Repository or wiki area for Golden Path docs; diagram tool (Mermaid, Excalidraw, Lucidchart); a sample repository as template anchor; list of links to tooling (CI templates, IaC modules, service libraries); list of existing paths used by each team.

Preparation

Create doc structure with overview, prerequisites, step-by-step, templates, standards/checks, exceptions, FAQ. Link sample repository. Show owner and Slack channel for questions.

Agenda

  1. Section 1: Sharpen use case (30-60 min) Owner: Facilitator Action: Define the use case in one sentence: what is the target outcome of the path (for example REST backend in Go with Postgres and central SSO authentication). Explicitly list what is out of scope. Hint: If the use case is too broad ("any service"), the Golden Path becomes generic documentation. Better define three narrow paths than one for everything. Output: Golden Path Guide

  2. Section 2: Describe the path (2-6 h) Owner: Facilitator Action: Build a step-by-step guide from repository setup to production deployment. Include one concrete command, template link, or click path per step. Estimate time per step. Hint: If steps exceed one paragraph, automation is missing. Templates and scripts should replace narrative text. A path should stay below twelve steps. Output: Templates

  3. Section 3: Templates and automation (4-16 h) Owner: Facilitator Action: Link or create existing templates (Cookiecutter, GitHub templates, Terraform modules). Evaluate Backstage software templates or similar tooling. Provide CI pipeline templates. Hint: Documentation without templates becomes stale quickly. Teams that only copy commands and config from a wiki page lose consistency within four weeks. Output: Quality Checks

  4. Section 4: Standards and checks (1-2 h) Owner: Facilitator Action: Document mandatory quality and security checks: linting, tests, SAST, SBOM, logging conventions. Specify which checks are automated (CI) and which are manual. Define acceptance criteria for being "on the path." Hint: If mandatory checks exist only as plain text, they will be bypassed. Automation in CI is required for all security and compliance-relevant points. Output: Golden Path Guide

  5. Section 5: Exceptions and FAQ (1-2 h) Owner: Facilitator Action: Section "if your use case deviates": when is deviation legitimate, how should it be documented (ADR), and who decides. Add common questions from pilot teams to FAQ. Hint: Without an opt-out path, Golden Path feels authoritarian and is bypassed informally. A visible exception process lowers resistance and reveals drift. Output: Templates

  6. Section 6: Pilot and adoption (2-4 weeks) Owner: Owner Action: Run path with one to two pilot teams. Observe where friction appears and improve documentation iteratively. Communicate publicly only after successful pilot. Hint: Publishing without a pilot produces docs that fail at first use. Pilot team feedback must be incorporated into v1.0. Output: Quality Checks

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

Closeout

  • Update result artifact: Golden Path Guide
  • 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

Golden Path Guide: Golden Path

Working Question

Which path takes a team from zero to a production-ready state for the defined use case in under one day without breaking standards?

Context

Precisely scoped use case (for example "new backend service with public API"); existing best-practice examples from two to three teams; known pain points the path should solve; non-negotiable compliance and security requirements.

Participants

  • Owner: Platform team as Golden Path owner
  • Participants: Platform team as Golden Path owner; one technical writer or senior engineer as primary author; representatives from two to three product teams as reviewers; one architect or principal engineer as approver.

Input

Repository or wiki area for Golden Path docs; diagram tool (Mermaid, Excalidraw, Lucidchart); a sample repository as template anchor; list of links to tooling (CI templates, IaC modules, service libraries); list of existing paths used by each team.

Template

Golden Path Working Template

Goal

Describes the recommended standard path that helps teams reach a common technical goal reliably.

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

  • Golden Path Guide:
  • Templates:
  • Quality Checks:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

Completion Check

  • Golden Path Guide 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

Golden Path Working Template

View templateCompact working template for Golden Path with context, input, output artifacts, and next step.
markdown

golden-path-working-template.md

Compact working template for Golden Path with context, input, output artifacts, and next step.

Golden Path Working Template

Goal

Describes the recommended standard path that helps teams reach a common technical goal reliably.

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

  • Golden Path Guide:
  • Templates:
  • Quality Checks:

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 Golden Path Guide.
  • Use semantic versioning for the path (v1.0, v1.1, v2.0 for breaking changes). Place changelog at the top of the documentation. Keep deprecated paths linked with migration notes; do not silently replace them.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet