I found myself staring at the projected slide, the kind of corporate graphic design that uses gradients and little stylized stick figures meant to represent ‘cross-functional synergy.’

Another one. I swear I hadn’t even updated my Slack profile picture since the last deck dropped 18 months ago. That sickly fluorescent light in Conference Room B always makes the stale coffee smell sharper, and it bathes everyone-from the newly minted VP to the guy who’s just trying to retire-in a universal shade of corporate dread. We were, yet again, breaking down silos. The same silos we had rigorously constructed, labeled, and color-coded during the ‘Agile Transformation’ only 73 weeks prior.

My throat tightened slightly.

The Sincerity Deficit

I remember Peter Y., a voice stress analyst I consulted with years ago, told me the most revealing corporate communications are often non-verbal. The subtle tremor in the CEO’s voice when they introduce the ‘bold new matrix structure,’ the way the presenter avoids eye contact when they insist this will ‘increase collaboration by 43%.’ Peter claimed he could measure the cognitive dissonance of the room by how many people checked their phones simultaneously.

If authenticity were a metric, this room would be registering 0.3 on the sincerity scale.

It’s easier to spend $373 million implementing new reporting lines than it is to admit that the core strategy devised two years ago was flawed from its inception.

I’ve been the person advocating for change. I know how easy it is to look at a stagnant problem-a product line that hasn’t moved, a competitor that suddenly leapfrogged us-and conclude that the structure is the problem. It’s a clean diagnosis. It allows you to fire the architecture instead of the architect.

I did that once. My team was drowning in legacy system debt, and instead of demanding the C-suite allocate the required $1.23 million to fix the infrastructure, I tried to ‘re-prioritize’ the teams into a different configuration. It was like rearranging the furniture on a sinking ship. I criticized the ritual, and then, I did the ritual anyway. That hypocrisy still stings.

The Real Engine: Informal Networks

What these constant churns really destroy isn’t just morale-though that certainly takes a hit-it’s the informal network. The shadow structure. The person in Finance who knows how to shortcut the approval process, the engineer in R&D who actually understands the undocumented workaround from 2003, the assistant who knows exactly which email subject line gets the CMO’s attention.

These networks, built on trust and repeated interactions, are the actual engines of the business. A re-org comes along, rips up the entire seating chart, and suddenly, you lose operational efficiency because everyone is spending four months figuring out who is responsible for the paperclips again.

The Value of Enduring Structure

We talk a lot about ‘breaking silos,’ which is just the corporate jargon for ‘we haven’t created a clear enough shared purpose.’ But the irony is that these constant reorganizations create deeper silos, not between departments, but between the individual and the organization itself.

It reminds me of the few things in this world built to endure. When you look at high-quality, specialized crafts-the kind of artistry and tradition represented by the detailed work found at the

Limoges Box Boutique-you realize that real excellence isn’t achieved by tearing down and rebuilding the workshop every year.

That commitment to stability feels entirely alien in the modern corporate environment. We reward motion over momentum.

Structure Rot

I threw out a three-year-old jar of mustard last week. It looked fine, sealed, sitting there on the shelf, but it was expired. Useless. That’s what many corporate structures become: sealed, preserved, looking official on paper, but internally expired.

A re-org is just transferring that expired mustard to a different shelf in a new fridge. It doesn’t solve the core issue of rot; it just delays the inevitable and contaminates the new environment with uncertainty.

I sat through the rest of the presentation. They called this new structure the ‘Vortex Model,’ emphasizing rotational flow and adaptability. They promised improved knowledge sharing metrics within 23 days.

But my mind was stuck on the fact that the person who designed the entire customer support structure we are now scrapping is the same person who is presenting the need for the new one. The redundancy is staggering, yet somehow acceptable. We are all just pretending the memory of the last failed attempt doesn’t exist.

They always finish these presentations by asking for questions, but everyone knows the implicit answer: “No, because any question I ask about accountability or logic will mark me as a barrier to progress.” We clap politely, shuffle out, and begin the silent, exhausting work of trying to reverse-engineer who, exactly, approves our vacation requests now.