Skip to content
    Delivery & qualityChapter 16

    Squad Health Check Compared with DORA, SPACE, and DevEx

    How to combine facilitated team reflection with delivery, reliability, productivity, and developer-experience evidence.

    Original guideworking15 minevolving · reviewed Aug 12, 2026
    Chapter outline

    Brief

    The essential idea

    Spotify's Squad Health Check is a lightweight way for a team to discuss its condition using traffic-light ratings, locally relevant dimensions, and trends over time. Its primary value is a safer, structured conversation that turns perceptions into a retrospective and an improvement backlog, not a universal measure of engineering performance.

    DORA supplies an objective baseline for delivery speed and stability. SPACE combines subjective and objective signals across several dimensions, while DevEx focuses attention on tooling friction, feedback loops, and the working environment. Together they cover evidence that a self-assessment alone cannot provide.

    A useful operating model is Squad Health Check for dialogue, DORA for flow and reliability, and a small number of SPACE or DevEx signals for likely causes. The measures should guide system improvement rather than compare individuals or rank teams without shared context.

    Decision lens

    Key takeaways

    Squad Health Check is a facilitation layer, not a replacement for technical delivery metrics.

    DORA provides a scalable quantitative baseline for delivery and stability.

    SPACE and DevEx expose human load, friction, satisfaction, and feedback-loop problems behind delivery outcomes.

    Customized health questions make cross-team aggregation difficult and require careful interpretation.

    A survey without completed follow-up actions quickly loses trust and diagnostic value.

    Metrics should describe the work system and never become a scorecard for individual engineers.

    Workplace experiment

    Apply it at work

    1. 1

      Agree on a small common health-check question set and interpretation scale.

    2. 2

      Establish a DORA baseline and choose one or two relevant SPACE or DevEx signals.

    3. 3

      Run the health check every two to four weeks and select no more than two improvement actions each cycle.

    4. 4

      Compare later perceptions with objective flow data, then standardize practices that improve both.

    Choose one action, define the observable effect, and keep the first test small enough to reverse.

    Evidence

    Sources and further reading

    Additional sources

    Channel, aggregator, and commentary links confirm the work; they are not the primary source.

    Previous chapterDesigning Team Structure Around Business RequirementsNext chapterProject and Product Management