Plans Don't Commit Us, Commitments Commit Us

Definition

A commitment is a promise made by a person to get something done, carrying with it the responsibility to speak up and adapt when circumstances threaten that promise. A plan is nothing more than "a convenient place to write those commitments down." The book insists on keeping this distinction sharp because conflating the two lets people treat the paperwork as the obligation — and once a plan (rather than a person's promise) is what supposedly binds the team, anyone can escape responsibility for a miss by noting they never personally signed off on that plan.

In the Book

Chapter 4 makes this argument directly in the context of why Scrum gives the Product Owner — not a separate "plan owner" — responsibility for the commitment to the business: "Most of us have been in meetings where a team member says that they didn't sign off on the deadlines they were committed to, so the fallout for not meeting the deadline isn't that person's fault. This happens because many inexperienced project managers make the mistake of thinking that once a task is written into a plan, the team is automatically committed to it." The book contrasts this with a command-and-control project, where a single project manager owns the schedule and everyone else feels license to say "it's that guy's problem" when trouble hits. On a Scrum team, nobody owns "the plan" as a separate artifact — the Product Owner makes and keeps the actual promise to the company, and the Scrum Master's job is to help the whole team feel like they collectively own that promise, not merely a document describing it.

Why It Matters

This separates two things that get routinely confused in any planning process: the artifact (the Gantt chart, the roadmap, the sprint backlog) and the human promise it's meant to represent. Wherever a team is arguing about whose fault a miss is by pointing to what the document said or didn't say, the underlying problem is usually that the plan was allowed to substitute for a real, personally-owned commitment — a distinction that applies just as much to a corporate roadmap or a personal to-do list as it does to a sprint.