Manu's Vault

Team Snippets and Directional Metrics

3 min readStatus:Seedling

Team Snippets and Directional Metrics

Two lightweight mechanisms that together replace most status meetings and create shared situational awareness in engineering organisations: Team Snippets (structured asynchronous narrative updates) and Directional Metrics (a stable shared dashboard of leading indicators).

Team Snippets

  • Format: Short, structured written update from each team on a weekly or bi-weekly cadence
  • Three questions: What did we do? What are we doing next? What’s blocked?
  • Delivery: Shared asynchronously — posted to a shared channel or wiki, not read aloud in a meeting
  • Length discipline: 5–10 bullet points per question; longer than one page is a failure mode
  • Benefits:
    • Forces teams to articulate priorities in plain language
    • Creates a searchable, persistent record of what teams were working on and why
    • Allows any stakeholder to stay informed without attending every meeting
  • Failure mode: Snippets become status essays — so long that nobody reads them

Directional Metrics

  • Format: A small shared dashboard (5–10 metrics) visible to the whole engineering organisation
  • Composition: DORA-Four-Metrics (deployment frequency, lead time, change failure rate, MTTR) plus 1–3 product health metrics
  • “Directional” principle: You are looking for trend and direction, not precise point-in-time measurement
  • Stability rule: Don’t change the dashboard frequently — stable metrics make trends meaningful
  • Visibility: Exposed to the full engineering org, not just leadership — creates team-level accountability
  • Failure mode: Metrics changed too often; vanity metrics displacing leading indicators

Why Both Are Needed

  • Snippets provide narrative and context: what’s happening, why decisions were made, what’s blocked
  • Directional metrics provide signal and accountability: are we moving in the right direction?
  • Neither alone is sufficient — metrics without narrative obscure root causes; narrative without metrics hides systemic drift from Four-States-of-a-Team target states

Scaling Across Org Layers

LayerSnippetsDirectional Metrics
Team of teams (line mgmt)Per-team snippetsPer-team dashboard
Org of orgs (middle mgmt)Snippet rollupsOrg-level dashboard
Multi-org (exec)Executive summariesQuarterly trend analysis

Snippets and directional metrics are the communication layer that sits above Sprint-Process-Criteria: sprint health is the per-team diagnostic; snippets and metrics are the cross-org communication system.

Sources

  • Larson, Will (2019). An Elegant Puzzle: Systems of Engineering Management. Stripe Press. ISBN: 978-1-7322651-8-9.
    • Chapter 7.1 (Appendix): primary source for snippets format and directional metrics design
  • Larson, Will (2019). “Snippets: Lightweight, Searchable Status Updates.” Irrational Exuberance (lethain.com).
    • Practitioner elaboration on snippet design principles and common failure modes
  • Forsgren, Nicole, Jez Humble, and Gene Kim (2018). Accelerate: The Science of Lean Software and DevOps. IT Revolution Press. ISBN: 978-1-942788-33-1.
    • Empirical grounding for the four DORA metrics used as the core of directional dashboards
  • Reinertsen, Donald G. (2009). The Principles of Product Development Flow: Second Generation Lean Product Development. Celeritas Publishing. ISBN: 978-1-935401-00-1.
    • Theory of WIP visibility and information radiators; informs why visible metrics change team behaviour
  • Sutherland, Jeff and J.J. Sutherland (2014). Scrum: The Art of Doing Twice the Work in Half the Time. Crown Business. ISBN: 978-0-385-34645-0.
    • Three-question sprint review format predates and informs the snippets structure

Note

This note was researched and drafted with AI. How these notes are written →

Graph View

Backlinks