Creating an Office to Eliminate Offices

The Transformation Management Office was created to reduce bureaucracy.

That sentence should have warned everyone.

The announcement described a lean central team that would remove blockers, accelerate execution, and help business units move faster. It would not become another layer. It would enable, not control. It would coordinate, not govern. It would be practical, agile, and close to the work.

On day one, the office created an intake form.

This was reasonable. Work needed to be visible.

On day five, it created a prioritization template.

Also reasonable. Capacity was limited.

By day twelve, there was a weekly reporting pack, a dependency tracker, a risk taxonomy, a decision log, a benefits register, a communications calendar, and a naming convention for initiatives that made every project sound like a small military operation.

None of this was irrational. That was the problem.

Bureaucracy rarely begins as stupidity. It begins as protection against confusion.

Nhan joined the office as a liaison. He spent his mornings helping teams fill out templates designed to help them stop filling out unnecessary templates. He spent his afternoons in meetings about how to reduce meetings. The irony was visible, but not actionable.

Business units complained.

"We used to need approval from three places. Now we need approval from three places plus the transformation office."

The office objected. "We do not approve. We align."

This was technically true. Alignment took forty minutes longer than approval and produced fewer signatures.

The TMO became very good at visibility. It knew every initiative, every dependency, every status color, every owner. It could answer leadership questions quickly. It could produce a heatmap by Friday. It could tell you which projects were blocked, though not always unblock them.

Leaders loved the visibility.

Teams feared it.

Once work becomes visible enough, it becomes performative. Project managers learned to phrase problems in ways that sounded mature. Risks became "watch items." Delays became "timeline pressure." Lack of ownership became "cross-functional dependency."

The office had not created fear. It had created a stage.

One afternoon, Nhan reviewed a report that said "bureaucracy reduction initiative: on track." The initiative had four workstreams, two governance forums, and a fourteen-page update deck.

He stared at the phrase for a while.

Later that week, the head of the office asked for ideas to simplify the process.

Nhan suggested killing half the templates.

The room was interested.

"Which half?"

That was where the conversation became difficult. Every template had a defender. The intake form protected capacity. The risk log protected leadership. The benefits tracker protected finance. The decision log protected memory. The weekly pack protected attention.

By the end of the meeting, the team had agreed to create a template rationalization task force.

Nhan wrote the action item himself.

There are moments when an organization becomes a mirror and politely asks you to look.

The office did not fail because it was useless. It solved real problems. It gave senior leaders one place to look. It helped some initiatives survive the fog. It made chaos legible.

But legibility has a cost.

To make work visible, the office asked work to describe itself. To make work comparable, it asked work to fit categories. To make work governable, it asked work to slow down long enough to be reported.

The office created to remove layers became a layer because the organization still wanted what layers provide: reassurance.

Nhan learned to respect the paradox.

If you create an office to eliminate offices, the first thing it will do is prove why offices exist.

And then, if you are lucky, it may eliminate a few of them before becoming one itself.