Engagement Over Installation

Definition

"Installation" is Block's term for treating organizational change as an engineering problem: articulate a vision, set standards, define measures, follow the steps — as if a blueprint executed correctly guarantees the outcome. This works for mechanical systems but fails for living ones, because implementation "does not actually begin until the people who do the work decide whether they are going to make real changes or simply go through the motions." The alternative, engagement, treats bringing people into the decision — not just informing them of it — as the actual mechanism of change, not a courtesy layered on top of it.

In the Book

Block opens Chapter 16 by naming the gap between "knowing what to do" (the product of discovery) and "finding the right way to do it" (implementation), arguing consultants historically over-invest in analysis and under-invest in the difficulty of translating answers into action. He attacks a specific belief he calls "deciding doesn't get it done": the assumption that once a leader's mind is made up, action follows — "no single person runs a business, no one person makes or delivers a product, and no one general ever fought a war." Managers, he observes, already understand this limit on their own authority better than consultants give them credit for; it's consultants who keep expecting decisiveness alone to produce results. Block explicitly ties this back to two earlier ideas in the book: the positive deviance approach (Chapter 12) and whole-system discovery both work because they refuse to install a pre-built answer, instead building change out of the "intangible" — relationships, personal commitment — alongside the tangible methods and structures. The chapter's prescription is concrete: design meetings for participation rather than presentation, put real choice on the table early rather than packaging a finished solution for speed, and encourage difficult, public disagreement early rather than letting it surface after commitments are already made.

Why It Matters

This names a specific and common implementation failure: a leadership decision, however well-reasoned, that produces compliance theater rather than behavior change, because the people executing it were informed rather than involved. It generalizes to any effort to change how a group of people works — policy rollouts, technology adoption, cultural initiatives — where the temptation is always to treat the plan as the hard part and the rollout as mechanical, when the rollout is where the real, unengineerable work actually happens.