What ChangeShop was/is¶

ChangeShop is an experiential workshop developed by Gerald and Daniel Weinberg. You do not study change in ChangeShop. You bring a real problem and work on it, live, with other people, and discover things about it that desk analysis would never surface.

The structure¶

Participants rotate through three roles while working on real issues.

The client brings an actual problem. Not a sanitised case study, but something live: a security programme that is stalling, a control nobody will adopt, a risk that keeps getting accepted without being addressed. The client comes in thinking they want solutions.

The consultants attempt to help. They ask questions, offer perspectives, propose interventions. They also run into walls they did not expect: constraints that were not mentioned, assumptions that turn out to be load-bearing, emotional reactions that derail the logical thread.

The observers watch the interaction itself, not just the content. They notice who deflects when, when energy shifts, when the stated problem and the actual problem come apart. This role is often the most instructive, because the dynamics that undermine change in the real organisation show up in the room with impressive fidelity.

What happens in practice¶

Three things tend to become clear within hours.

The problem is not what the client thought it was. The initial problem statement is almost always incomplete, misattributed, or several steps upstream of the actual issue. “We need better tooling” frequently resolves into “we do not trust each other’s decisions.” “Staff are not following the process” frequently resolves into “the process was designed without the people who have to use it.”

The client is part of the problem. Not as blame, but as observation. The way a problem is framed, the constraints the client has already ruled out, the solutions they have already rejected: these are data about the system, and the client is in it.

The organisation is structured to resist the solution. Organisations are homeostatic systems. They resist change to remain stable. Processes slow down approvals. Priorities shift at critical moments. What looks like obstruction is often the system doing what systems do: preserving the current state.

The key insight¶

You cannot implement change from the outside. You can only alter the conditions under which change becomes possible.

This is not a counsel of patience. It is a practical observation about leverage. Pushing harder against a homeostatic system usually makes it resist harder. Finding the conditions that allow the system to change its own state is a different kind of work, and it is what ChangeShop teaches.