Self-Determination

Definition

Self-determination is the practice of letting the people doing the work define, and continually redefine, their own procedures, rather than having procedures designed for them by engineers or managers and then handed down. The book's claim is stronger than "empowerment is nice": it's that ownership of the how is itself what makes people capable, and that transplanting the resulting practices elsewhere without transplanting the underlying autonomy reliably fails.

In the Book

The chapter's anchor case is NUMMI, the Toyota-managed joint venture that reopened GM's failed Fremont plant in 1984 with 85% of the same unionized workforce and, within two years, more than doubled productivity, sharply raised quality, and cut absenteeism from chronic to about 3% — without changing who was doing the work, only how work was organized. Toyota didn't transfer Japanese practices wholesale; it transferred the principle that capable workers, organized in teams of six to eight, design and coordinate their own work standards, with management's role reduced to coaching and support — a principle GM's own managers (including one who worked undercover on the NUMMI line for a month) understood intellectually but repeatedly failed to reproduce at other plants. The book pairs this with a "Business Novelette" about a fictionalized FIX-IT development group that organically built its own coding standards and tooling, thrived, and was then studied by a corporate staff group that documented the practices as a mandatory uniform process for the whole company — stripping out exactly the self-redefinition that made the practices work, so the rollout largely failed everywhere except the original group, which quietly kept adapting. GE's "Work-Out" program is offered as a rare counter-example that succeeds at scale, because it structurally forces managers to accept and immediately act on frontline proposals rather than merely soliciting them.

Why It Matters

Best-practice rollout usually assumes the value lives in the documented procedure, so copying the document should copy the result — and it usually doesn't, which this concept explains: the value was in the ongoing act of a team owning and revising its own procedure, not in any snapshot of what that procedure happened to say. It gives you a specific failure to watch for whenever an organization tries to scale a successful team's practices by writing them down and mandating them elsewhere.