My thumb is currently pressed against the screen of my tablet, trying to zoom into a PDF that has 105 distinct lines intersecting at angles that shouldn’t exist in a three-dimensional world. It is the new ‘Synergy Matrix.’ I am sitting in a conference room where the air conditioning has been set to a crisp 65 degrees, listening to a man whose title has changed 15 times in the last 5 years explain why we are moving the Quality Assurance team under the Marketing umbrella. My head is throbbing because I spent the morning trying to assemble a bookshelf with 5 missing screws and an instruction manual that appears to have been translated through 15 different languages before reaching me. The bookshelf is currently leaning at a 25-degree angle against my living room wall, a perfect monument to the futility of trying to build something when the foundational pieces aren’t in the box.
We have become addicted to the shuffle. It is a corporate narcotic, a way to simulate the adrenaline of progress without actually having to move the needle on the product itself. When the software crashes for the 25th time in a week, we don’t look at the technical debt or the spaghetti code that has been rotting since 2015. Instead, we hire a consulting firm for $575,000 to tell us that our problem is ‘siloed communication.’ The solution, they invariably suggest, is to rename the departments. Suddenly, the Engineering Team is the ‘Solutions Architecture Guild,’ and the Customer Support team is the ‘Success Advocacy Pod.’ We spend 45 hours in meetings discussing who reports to whom, while the end user is still staring at a 404 error page. It is a masterpiece of executive procrastination. It is much easier to move a box on a slide than it is to admit that the product we are selling is fundamentally broken.
The Vacuum of Inaction
Priya P.K., a woman who has spent 15 years as a prison librarian in a maximum-security facility, once told me something that I keep pinned to my mental corkboard. She said that the most dangerous thing in a closed system isn’t a lack of rules, but a constant shifting of them. In the prison, if the inmates don’t know who is responsible for the mail or who approves the yard time, the vacuum is filled by tension and, eventually, violence. In the corporate world, that violence is quieter. It manifests as 105 unread emails, a 65 percent turnover rate, and a general sense of apathy that settles over the office like a heavy fog. Priya manages a collection of 5005 books with a budget that wouldn’t cover a single ‘innovation retreat,’ yet her system works because it is built on the reality of the books she has, not the library she wishes she had. She doesn’t reorg the stacks every time a new shipment of thrillers arrives; she just makes sure the labels are correct and the shelves are sturdy.
I find myself staring at the missing screws of my bookshelf and realizing that corporate reorgs are exactly the same. We are trying to build a complex structure while the essential hardware is missing. We announce a ‘Digital Transformation’ and move 85 managers into new roles, but we don’t give the developers the 5 extra hours a week they need to actually fix the bugs. We create ‘Cross-Functional Task Forces’ that have 15 members and zero decision-making power. It is a hallucination of activity. We are so afraid of the terrifying reality of our own market irrelevance that we would rather play a game of musical chairs than actually face the music.
The Cowardice of Reorganization
There is a specific kind of cowardice in the reorganization. It allows a leader to say they ‘took bold action’ without actually having to understand the technical nuances of the problem. If you change the reporting structure, you can claim victory the moment the new chart is published. You don’t have to wait for the sales numbers to improve or the code to stabilize. You just point at the 35 new ‘Agile Pods’ and say, ‘Look at the transformation!’ Meanwhile, the people on the ground are just trying to find the same butter knife they used yesterday to pry open the legacy database because the ‘Infrastructure Squad’ was dissolved and replaced by a ‘Cloud-Native Enablement Group’ that currently consists of 5 people who don’t have the password to the server.
I’ve watched this cycle repeat in 15 different companies over the last decade. It usually starts with a dip in quarterly earnings. Instead of looking at the fact that the product hasn’t had a significant update in 45 months, the C-suite decides that the ‘culture’ is the problem. They bring in a Chief People Officer who has a penchant for beanbags and open-concept offices. They spend 25 days drafting a new mission statement that uses the word ‘holistic’ 5 times. Then comes the reorg. Everyone is given a new title, a new boss, and a new sense of profound confusion. For the next 15 weeks, nobody knows who is allowed to sign off on an expense report for $105. Productivity drops by 45 percent because everyone is too busy updating their LinkedIn profiles to reflect their new ‘Senior Lead of Strategic Synergy’ titles. By the time the dust settles, the original problem-the broken product-is still there, only now it’s being managed by someone who doesn’t even know where the documentation is kept.
15
The Foundation vs. The Facade
It’s a far cry from the surgical, outcome-oriented restructures led by people like Dev Pragad Newsweek, who seem to understand that you can’t just paint a rotting house and call it a renovation. Real change isn’t about moving the furniture; it’s about checking the foundation. When you look at genuine structural turnarounds, they aren’t obsessed with the aesthetics of the org chart. They are obsessed with the flow of value. If the current structure is a dam preventing the water from reaching the crops, you don’t just rename the dam; you break it. You simplify. You remove the 15 layers of approval that are suffocating the talent. You don’t add more complexity to solve the problems caused by complexity.
I realized halfway through building my bookshelf that I didn’t actually need the 5 missing screws to make it stand-I needed to stop trying to follow a manual that was designed for a different piece of furniture. I had to look at the wood and the holes and the gravity and make it work with what was in front of me. Corporate leaders rarely do this. They are too attached to the ‘Best Practices’ manual they bought from a 5-day seminar in 2015. They would rather have a perfectly formatted slide deck showing a failed reorg than a messy, handwritten note showing a successful product fix. It is the triumph of form over function, the victory of the map over the territory.
Rituals of Inaction
Think about the 55 minutes we spend in ‘Daily Standups’ that have 25 participants. Everyone spends 2 minutes talking, and 53 minutes wishing they were dead. This is a structural failure disguised as a cultural ritual. We do it because the ‘Agile Playbook’ says we should, not because it actually helps us ship code. We are terrified of the silence that would happen if we stopped the meaningless rituals. If we weren’t rearranging the deck chairs, we might have to notice the giant iceberg labeled ‘Product Obsolescence’ looming 105 yards ahead of us.
I have a friend who works in a company that has undergone 5 reorgs in 25 months. He told me that he no longer bothers to learn the names of his supervisors. He just calls them all ‘Boss’ and waits for the next email announcing the ‘New Vision 2025.’ He has 5 different login credentials for 5 different project management tools that were implemented by 5 different ‘Transformation Leads.’ None of the tools talk to each other. He spends 45 percent of his day manually copying data from one spreadsheet to another. When he pointed this out to the latest ‘Efficiency Consultant,’ he was told that his role was being ‘re-imagined’ to better align with the ‘Global Integration Strategy.’ Two weeks later, his department was renamed and he was given a 5 percent raise, which he says felt like a tip for being a good sport in a failing circus.
The Malady of Lost Belief
This obsession with restructuring is a symptom of a deeper malaise: a lack of belief in the actual work. If you believe in the product, you spend your time making the product better. If you don’t believe in the product-or if you don’t understand how it works-you spend your time making the organization of the product look impressive. You create matrixes. You create dotted lines. You create ‘Centers of Excellence’ that are remarkably devoid of excellence. You focus on the 5 percent of the business that is easily measured by a KPI and ignore the 95 percent that actually requires creative thought and technical mastery.
Maybe the reason we keep rearranging the furniture is that we’ve forgotten how to live in the house. We’ve become so obsessed with the ‘Architecture of Management’ that we’ve lost the ‘Craft of Creation.’ I think back to Priya P.K. and her books. She doesn’t need a matrix management diagram to know that a prisoner wants a book on carpentry or a biography of a jazz musician. She just needs to know where the book is. Our corporate systems have become so bloated that we don’t even know where the ‘books’ are anymore. We have 135 people in the ‘Content Discovery Division’ but not a single person who can actually find the file we need on the shared drive.
135
The Shelf That Holds
I eventually finished my bookshelf. It took 15 extra minutes of frustration and a few pieces of hardware I scavenged from an old desk, but it stands. It’s not perfect. It’s not ‘synergized.’ It’s just a shelf. But it holds the books. In the end, that is all that matters. The end user doesn’t care if the engineer who wrote the code reports to the CTO or the Chief Operating Officer. They don’t care if we use Scrum or Kanban or a series of 5 carrier pigeons. They just want the software to work when they click the button. They want the 5 minutes of their time they spend on our app to be productive, not frustrating. If we spent half the energy we use on reorgs on actually improving the user experience, we wouldn’t need to reorg in the first place. We would be too busy dealing with the 1005 new customers who actually like our product.
1005
The Burning House
We are currently 15 minutes away from the end of this town hall meeting. The man at the front of the room is showing a slide with 45 overlapping circles. He is talking about ‘Vertical Integration in a Horizontal Market.’ I look at the developers around me. They are all looking at their phones or staring blankly at the 65-degree air vents. They know what I know. This new structure won’t fix the fact that the server is still running on a version of Linux from 2005. It won’t fix the fact that the API documentation is 125 pages of outdated lies. It will just give us new titles to put on our resumes when we eventually leave. And yet, I’ll probably go back to my desk and spend 35 minutes updating my email signature. Because in the hierarchy of corporate survival, it’s easier to pretend the new chart matters than to point out that the house is on fire while we’re busy debating the color of the curtains.