The Invisible Throne of the Chief of Making Things Complicated

The Invisible Throne of the Chief of Making Things Complicated

When simplicity becomes a radical act.

Navigating the digital landscape of a modern enterprise feels like wading through a pool of lukewarm molasses, and I am currently stuck at the hip. My finger is hovering over the ‘Submit’ button on a Jira ticket that has 13 mandatory fields, including one that asks for the ‘Impacted Stakeholder Synergy Score,’ a metric I am convinced was invented by someone who hates joy. I’ve spent 43 minutes trying to change a single hex code on a landing page. Ten years ago, I would have just emailed the designer, we would have chatted for 3 minutes, and the change would be live. Now, I am part of a process. I am a cog in a machine that has been over-engineered to the point of structural failure.

I’m Robin F.T., and as a corporate trainer, my job is ostensibly to help people communicate better. But how do you teach communication in an environment where the systems are designed to stifle it? I just spent 23 minutes-I timed it on my watch-trying to end a conversation with a middle manager named Gerald. He was too busy explaining the new 13-step ‘Feedback Loop Protocol.’ It occurred to me that Gerald is a primary candidate for a title that doesn’t exist on paper but dominates our reality: The Chief of Making Things Complicated (CMTC).

The Labyrinth of Justification

Every organization has one. Sometimes they are an entire department. These are the people who look at a straight line and see an opportunity to build a labyrinth. They don’t do it out of malice; they do it out of a desperate, clawing need to justify their existence. In the corporate world, simplicity is a threat. If a process is simple, it doesn’t need a director, a sub-committee, and a $330,003 budget for a ‘Strategic Implementation Framework.’ Complexity, however, requires oversight. It requires meetings. It requires 53-slide decks that use words like ‘orthogonal’ and ‘bimodal’ to describe things that are essentially just common sense.

Complexity is the ultimate byproduct of careerism. When someone gets promoted into a role that shouldn’t exist, their first instinct is to mark their territory with red tape. They invent new roles with titles like ‘Engagement Orchestrator’ or ‘Cross-Functional Gatekeeper.’ These roles don’t actually produce anything. They are the barnacles on the hull of the ship, and as the ship slows down, the leadership’s response is usually to hire more barnacles to study why the ship is moving so slowly.

[Complexity is the tax we pay for the lack of institutional trust.]

The Entropy of Approval

Tweet Life Cycle

13 Days

To Post Approval

VS

Labor Cost

$5,003

For One GIF

I remember working with a tech firm in 2013 that was obsessed with ‘agility.’ By the time I left, they had created a ‘Brand Council’ consisting of 33 people who had to approve every single social media post. A tweet-140 characters of ephemeral nonsense-had to pass through a legal review, a brand consistency check, a DEI audit, and a final sign-off from the VP of Public Relations. This is the entropy of the modern workplace. Left to their own devices, organizations do not become more efficient; they become more dense. They accumulate layers of ‘safety’ and ‘alignment’ until the actual work becomes a secondary concern to the preservation of the process.

We see this everywhere. What used to be a simple request to the design team is now a multi-step saga. You need a project brief that follows a specific 23-page template. You need to attend a ‘Discovery Session’ where 13 people who have nothing to do with the project give their ‘input.’ Then, you wait for the ‘Sprint Planning’ meeting, which only happens every second Tuesday of the month. If you miss that window, your 3-minute task is delayed by 23 days. It is a miracle anything ever gets done. In fact, most things don’t get done; they just get ‘socialized’ until they disappear.

The School Zone Bus

“As a trainer, I often find myself apologizing for the tools I am forced to teach. I’ll stand in front of a room of 13 exhausted developers and try to explain why they need to use the new time-tracking software that requires them to categorize their bathroom breaks into ‘Productive’ or ‘Administrative’ buckets. I can see the light dying in their eyes… They want to build things. But the CMTC doesn’t want things built; they want things tracked, measured, and filed in a way that makes their quarterly report look impressive to the other CMTCs.”

There is a profound psychological toll to this. When you spend your day fighting the system rather than using it, you experience a specific kind of fatigue. It’s not the ‘good’ tired you feel after a day of hard, creative work. It’s a gray, soul-crushing exhaustion. It’s the feeling of being a Ferrari stuck in a school zone behind a bus that stops every 13 feet. We are living in an era where the tools meant to liberate us have become our cages. The digital space should be where we escape the friction of the physical world, yet we have recreated the DMV inside our web browsers.

Simplicity: The Ultimate Luxury

This is why I find myself gravitating toward platforms that still value the user’s time. In an age of bureaucratic bloat, simplicity is the ultimate luxury. When I am done with a day of navigating the Jira mines, I want an experience that understands that my cognitive load is at capacity. I want the digital equivalent of a cold glass of water. This is the core appeal of streamlined hubs like ems89, where the noise of the corporate machine is silenced in favor of a direct, functional experience.

The Burden of Too Much

I’ve made mistakes in my career too. In 2003, I was part of a team that tried to implement a ‘Comprehensive Knowledge Management System’ at a mid-sized law firm. We spent $100,003 on software that no one used because it required 13 steps just to save a PDF. I learned the hard way that if a system requires a manual longer than 13 pages, it is not a tool; it is a burden. I was a junior CMTC back then, high on the idea that more data was always better. I was wrong. Less is not just more; less is the only way to survive.

📚

13-Page Manual

Burden

✅

One Direct Action

Efficiency

We need a ‘Chief of Deleting Things.’ Someone whose only job is to walk through the office (or the virtual workspace) and ask, ‘Why does this exist?’ and ‘What happens if we stop doing it?’ If the answer is ‘nothing’ or ‘Gerald will be sad,’ then the process should be killed immediately. We need to stop rewarding people for the complexity they create and start rewarding them for the friction they remove. We need to treat bureaucracy like a disease that requires a ruthless, aggressive cure.

[The most powerful word in any language is ‘No,’ followed closely by ‘Delete.’]

Finding Agency in the DMV

As I finally click ‘Submit’ on this ticket, 53 minutes after I started, I realize I’ve forgotten to attach the ‘Strategic Alignment Memo.’ The system flashes a red error message. It tells me my session will expire in 3 minutes if I don’t refresh. I think back to my 23-minute conversation with Gerald. He had a piece of spinach in his teeth the whole time, and I didn’t tell him. I realize now that I didn’t tell him because I wanted him to suffer a little bit for making me listen to his ‘Feedback Loop Protocol.’ It was a petty, small-minded revenge, but in a world governed by the Chief of Making Things Complicated, petty revenge is sometimes the only agency we have left.

I am going to close my laptop now. I am going to walk outside and look at a tree. A tree doesn’t have a Brand Council. A tree doesn’t use Jira. It just grows, slowly and simply, without a single meeting about its ‘Annual Leaf-Drop Strategy.’

There is a lesson there, if only we were simple enough to learn it. I will probably spend the next 13 minutes thinking about that tree, and it will be the most productive part of my day.

We need to stop rewarding complexity.

The friction is optional. Choose simplicity.