Describe What, Not How: The Story of the Two Chefs
Write amazing accptance criteria tests
Let me tell you a story.
There were once two chefs tasked with preparing a meal for a grand feast. The first chef, eager to impress, handed his apprentice a step-by-step scroll: “Chop the onions this thin, heat the pan to just this temperature, add everything in this order…” He explained every dash and sprinkle. His apprentice, overwhelmed, spent more time deciphering instructions than cooking. The meal, though technically precise, lacked flavor and joy.
The second chef took a different approach. She told her apprentice, “Tonight, we must serve a soup that warms the soul on a cold night, that smells like coming home.” She described the experience she wanted the diners to have, the outcome - not the process.
The apprentice chose his own path, using what he knew and could discover, tasting as he went. He focused on the warmth, the comfort, the delight. His soup was a triumph. The guests were moved. No one asked how it was made.
The Lesson
When we write acceptance criteria - or any instructions - there’s a desire to dictate every step. But in doing so, we risk the creativity, losing sight of our purpose, and tripping over complexity. Focus on what you want to achieve - the outcome, the experience, the why. Trust the team to discover the how. Describe what soup to serve, not how to stir the pot.
That’s the recipe for long term QA success.