The Four Values

A hospital buys a state-of-the-art handoff system. Every field validated, every workflow mapped. Six months later, a patient nearly gets the wrong dose — the details were in the system, but the day nurse never actually talked to the night nurse. In the incident review someone writes the sentence this whole lesson hangs on: "The tool didn't fail. The conversation did."

By the end of this video, you'll know the Manifesto's four values well enough to explain each one with an example — and, more importantly, you'll understand the one sentence at the end of the Manifesto that most people skip and almost everyone gets wrong.

Last lesson: seventeen practitioners, Snowbird, 2001, sixty-eight words. Those words are structured as four "this over that" statements. We'll take them one at a time, in our own words — the exact original text is on the resource page right below this video, reproduced in full, and it's worth reading unfiltered.

First: people and how they work together matter more than the processes and tools they use. That's the hospital story. Tools and processes are amplifiers — of whatever communication actually exists. When something goes wrong, the instinct is to buy a better tool or add a process step. The first value says: look first at whether the right people are actually talking.

Second: a working solution counts for more than exhaustive documentation about it. A marketing team can spend three weeks polishing a forty-page campaign strategy — or ship a rough landing page in three days and learn from real clicks what the document could only guess at. The working thing is the progress; the paperwork is support.

You might think this means agile teams don't document. That's understandable — it's probably the single most common agile myth. Actually, the value says comprehensive documentation loses to working solutions when they compete for your time. Good agile teams document plenty — just enough, kept current, serving the work. A one-page setup guide that saves the next person a day? That's the second value working for you, not against you.

Third: collaborating with your customer beats negotiating against them. Picture two agencies. One locks the client behind a signed contract and bills every change through change-order warfare. The other brings the client into a working session every week and co-designs as understanding grows. Contracts still exist — they matter — but the third value says the relationship that produces value is collaboration, not clause enforcement.

Fourth: responding to change beats clinging to the plan. Think of a GPS. You set a destination and get a route — that's a plan, and it's useful. But when a road closes, the GPS doesn't insist you drive into the barrier because the route said so. It reroutes, destination unchanged. Plans are instruments for reaching goals, not contracts with the past. Keep that GPS in mind — it returns in Lesson 4 as a full decision tool.

Now the line that changes everything. After the four values, the Manifesto adds — and here I'm paraphrasing; read the original on the resource page — that the items on the right do have value; the items on the left are valued more.

Read "over" as a weighting, not a rejection. Processes, documentation, contracts, plans — all still matter. Agile doesn't delete the right-hand side; it decides the tiebreaks. When working software competes with finishing the spec, when rerouting competes with defending the plan — the left side wins. Miss this sentence and you get the caricature: no plans, no docs, chaos with standups. Teams that live the caricature give agile its bad name — we'll study exactly that failure later in the course.

Three things to keep. One: the four values in plain words — people over process, working solutions over exhaustive documentation, collaboration over contract combat, responding over clinging. Two: "over" means weighted more, never instead of. Three: when you hear "agile means no documentation," you now know better — and you can say why.

Values are a compass — they point, but they don't give directions. For that, the same seventeen authors wrote twelve principles. Nobody can remember twelve of anything, so next lesson we'll compress them into four ideas you'll actually keep.