What is the Five Ideals of DevOps health check?

The Five Ideals come from Gene Kim's 2019 novel The Unicorn Project, the follow-up to The Phoenix Project. They describe what developers need to do their best work: code they can change locally without breaking someone else's, focus and flow, improvement of daily work, psychological safety, and customer focus. Each ideal becomes one statement your team rates from Strongly disagree to Strongly agree. The low scores show where developers are blocked by complexity, slowed by technical debt or unsure whether it's safe to raise a problem. Use the results to pick one ideal to work on before the next check.

Dimensions

The Five Ideals

The five guiding principles from The Unicorn Project that shape high-performing DevOps cultures.

  • Local and Simple

    We can make local code changes in a simple way without impacting others.

    • Strongly disagree
    • Neutral
    • Strongly agree
  • Focus and Flow

    Our work environment is engaging and even joyful. We have small batching, single piece flow with continual feedback.

    • Strongly disagree
    • Neutral
    • Strongly agree
  • Improvement of Daily Work

    We have limited technical debt and our architecture lets us work efficiently, deliver value faster, and benefit the business.

    • Strongly disagree
    • Neutral
    • Strongly agree
  • Psychological Safety

    Our team members feel safe to talk about problems openly and to address issues without fear.

    • Strongly disagree
    • Neutral
    • Strongly agree
  • Customer Focus

    We value the context (systems that deliver the core product) to the customer as essential and resource them appropriately, but also understand the core (what customers are willing and able to pay for).

    • Strongly disagree
    • Neutral
    • Strongly agree

When to use this health check

  • When your team wants to check its DevOps culture against the Five Ideals from The Unicorn Project.
  • Before a retrospective or quarterly review, to find where work gets stuck between idea and customer.
  • When a team is moving to DevOps ways of working and needs a shared starting point.
  • When technical debt, slow delivery or low morale point to a problem bigger than one sprint.

Tips & tricks

  • Share a short summary of the Five Ideals before the check so everyone rates from the same understanding.
  • Keep answers anonymous. The Psychological Safety score only means something if people feel safe giving it honestly.
  • Compare results over time to see whether work on daily improvement is actually reducing friction.
  • For each low score, agree one small experiment the team can try before the next check.

Frequently asked questions

What are the Five Ideals of DevOps?
They come from Gene Kim's novel The Unicorn Project: Locality and Simplicity; Focus, Flow and Joy; Improvement of Daily Work; Psychological Safety; and Customer Focus. Together they describe the conditions developers need to do their best work.
Who should take part in this health check?
Everyone who builds and runs the software: developers, testers, operations, product owners and engineering leads. Each of them sees a different part of how work flows.
How often should we run it?
Quarterly works for most teams, or alongside a bigger retrospective. That leaves time for changes to architecture or process to show up in the scores.
How do you run a Five Ideals health check?
Send the five statements to the team and let everyone answer privately on a five-point agree scale. When it closes, start with the lowest-rated ideal or the one where answers are most spread, and agree one experiment to try.
How are the Five Ideals different from the Three Ways of DevOps?
The Three Ways (flow, feedback, and continual learning and experimentation) come from The Phoenix Project, which Gene Kim co-wrote, and describe how work moves through a system. The Five Ideals, from The Unicorn Project, focus on the developer's day-to-day experience, such as code locality, joy in the work and psychological safety.