The Wall Nobody Is Allowed to Touch

The consultant used a house metaphor.

"Transformation is like renovating while people are still living inside," he said. "You need to move carefully, protect what matters, and redesign the space around future needs."

Everyone liked the metaphor. It sounded humane and strategic.

Then Nhan discovered the wall.

Every organization has one. A load-bearing wall nobody is allowed to touch. It may be a senior executive's domain, a legacy process, a political compromise, a revenue line, a sacred reporting structure, or an old system that should have died years ago but now supports too many careers to be questioned directly.

In Nhan's organization, the wall was a particular approval committee.

On paper, it existed to manage risk. In practice, it was where decisions went to become slower, safer, and harder to trace. Every process redesign eventually reached that committee. Every simplification stopped at its door.

The transformation team proposed removing two approval layers.

"Good idea," said the business.

"Necessary," said operations.

"Aligned with target state," said technology.

Then someone asked, "Does this affect the committee?"

The room became careful.

Not silent. Careful. People spoke with the precision of those walking near sleeping power.

"We may need to preserve existing governance."

"Perhaps the committee can be an exception path."

"We should avoid changing decision rights in phase one."

Within thirty minutes, the process had been redesigned around the wall.

It was impressive. Like watching water find the shape of a container.

The final flow removed three small steps, added two routing rules, and left the committee intact. The slide said "streamlined governance." Everyone approved it because everyone understood what had not been said.

Nhan hated this at first.

He believed transformation meant facing the real constraint. If a wall blocked the future, the wall should be inspected, reinforced, moved, or demolished. Instead, the organization kept repainting the rooms around it.

He raised the issue with his sponsor.

"If we do not change the committee, the process will still be slow."

The sponsor nodded. "Correct."

"Then why are we calling this transformation?"

The sponsor leaned back. "Because we are transforming what can be transformed."

Nhan carried that sentence like a pebble in his shoe.

Over time, he began to see the wall everywhere. In budget cycles. In hiring approvals. In architecture exceptions. In the informal right of certain people to override agreed rules without appearing in the risk log.

People rarely defended the wall directly. They defended timing, readiness, stakeholder alignment, regulatory sensitivity, cultural context. The wall survived through softer words.

One day, during a workshop, a younger analyst suggested eliminating the committee entirely.

The room smiled gently, the way adults smile at children who have not yet learned gravity.

"That is a good long-term aspiration," someone said.

The analyst wrote it under "future state."

Future state is where organizations put truths they are not ready to visit.

Months later, the program delivered measurable improvements. Cycle time dropped a little. The customer form became shorter. The dashboard looked better. The committee remained.

Nhan had to admit the renovation helped. People moved through the house more easily. Some rooms had more light. Not every change had to be heroic.

But whenever he looked at the process map, he could still see the wall. Solid, unnamed, carrying the weight of old bargains.

The lesson was not that transformation is impossible.

The lesson was that every transformation has a protected structure. Until you know what cannot be touched, you do not understand the change you are actually allowed to make.

And once you know, you must decide what kind of person you will become.

The person who keeps pretending the wall is not there.

The person who walks around it forever.

Or the person who waits for the day someone finally asks why the house was built that way.