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 their own 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
- Cadence: Updated weekly or bi-weekly alongside snippets
- Stability rule: Don’t change the dashboard frequently — stable metrics make trends meaningful; changing metrics resets the trend signal
- Visibility: Exposed to the full engineering org, not just leadership — this creates team-level accountability and shared context
- Failure mode: Metrics changed too often; precision over-optimised; 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 actually 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
| Layer | Snippets | Directional Metrics |
|---|---|---|
| Team of teams (line mgmt) | Per-team snippets | Per-team dashboard |
| Org of orgs (middle mgmt) | Snippet rollups | Org-level dashboard |
| Multi-org (exec) | Executive summaries | Quarterly trend analysis |
Connection to Sprint Health
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.
Related Concepts
- DORA-Four-Metrics
- Four-States-of-a-Team
- Sprint-Process-Criteria
- Larson-2019-An-Elegant-Puzzle
- Presenting-to-Senior-Leadership
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). Retrieved 2026-03-11. https://lethain.com/snippets-for-communicating-team-health/
- 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 in product development systems; informs why visible metrics (not just private ones) 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.
- Foundational source on asynchronous written communication patterns in iterative team settings; three-question sprint review format predates and informs the snippets structure
Note
This content was drafted with assistance from AI tools for research, organization, and initial content generation. All final content has been reviewed, fact-checked, and edited by the author to ensure accuracy and alignment with the author’s intentions and perspective.