The Revolution Will Be Negotiated: How Real Change Happens in Organizations

Consulting firms are expert at entering organizations with a clear mandate: something must change, the door is open, and the designer's job is to disrupt. This model works because the organization has already made the hardest decision — to admit that the current way is insufficient.

In-house designers rarely get that opening. Change must be earned through accumulated trust, negotiated incrementally, and re-explained to new stakeholders every quarter. The revolution, if it comes, comes slowly. And that is not a failure — it is how durable change actually works.

Why Radical Change Fails (Even When It Is Correct)

Organizations are not opposed to change as an abstract principle. They are opposed to changes that threaten what already works — the systems, relationships, and routines that keep people's jobs functioning.

A service designer who arrives with a compelling vision and an uncomfortable diagnosis can be entirely correct and still achieve nothing. Being right is not enough if the people who need to act on the diagnosis do not trust the person delivering it, cannot see how the proposed change fits their constraints, or feel that their existing work is being criticized rather than built upon.

"No matter how sharp the insight or how elegant the solution, nothing moves unless everyone involved can live with the consequences."

This is the condition that consulting engagements frequently bypass — because the client has already committed to the change before the consultant arrives. In-house, that commitment has to be built from scratch, continuously.

The Shape of Incremental Revolution

Negotiated change moves through specific conditions. Understanding those conditions is more useful than lamenting the pace.

First, trust must precede influence. The specialist who has owned a process for a decade is not an obstacle to change. They are a necessary ally. Until they trust that the journey work is helping them — not auditing them, not replacing them, not creating parallel documentation that will compete with their tools — they will not engage with it meaningfully.

Second, constraints are information, not obstructions. When a platform migration absorbs all engineering capacity for two quarters, that is not a blocker to be pushed past. It is context that shapes where the journey work should focus. The in-house designer who can read organizational constraints as data rather than obstacles becomes significantly more effective than one who treats them as problems.

Third, small agreements build the foundation for large ones. A shared vocabulary agreed in a kick-off meeting creates the conditions for a shared vision agreed in a quarterly review. A single insight validated with customers creates the conditions for a research program. A single Big Solution delivered and measured creates the conditions for a journey management practice.

What "Good Enough for Now" Actually Means

There is a phrase that feels like a compromise but is actually a strategic orientation: "good enough for now is better than perfect but impossible."

This is not an excuse for low standards. It is a recognition that perfect solutions that never get implemented have zero impact, while imperfect solutions that get implemented and measured create learning. In organizations that move in quarterly cycles, shipping something testable is more valuable than refining something that misses the window.

The in-house designer's credibility is built on results that organizations can point to — experience scores that improved, teams that aligned around a shared direction, solutions that shipped and worked. That credibility compounds over time. It is what eventually allows the quieter, more persistent kind of revolution to succeed.

The designer who learns to work within constraints, not above them, is the one who gets to keep changing things. The one who insists on the perfect approach, on the right budget, on the complete mandate, is usually shown the door before the work is finished.