THE PLACE WHERE ACCOUNTABILITY GOES TO DIE

Try a quick exercise before reading on. Think back to your last work week and count how many meetings filled your calendar. Now, for each one, ask yourself: what actually changed in the world once it ended? Not a “let’s align on this,” not a tidy set of notes filed away in a folder nobody will ever reopen, not a round of nodding heads. A real change. Something someone felt, executed, and sustained through the following Friday — without needing another meeting just to remember it existed.

If the honest answer is “almost nothing,” there’s an uncomfortable truth here, and, at the same time, a liberating one: the problem isn’t a lack of effort. It’s an excess of it — misdirected, looping endlessly, dressed up as productivity.

Most of the companies I work closely with don’t suffer from people working too little. They suffer because hard work became a sophisticated substitute for hard decisions. Calling another meeting is always more comfortable than personally owning the call to kill a beloved project. Debating a metric in committee always hurts less than admitting, in front of everyone, that the target was poorly designed from the start. The more uncomfortable the choice that needs to be made, the stronger the collective urge to dilute it in conversation.

I recognize the symptoms from a distance, before I even walk into a company for the first time. Goals that became decorative slides in quarterly decks, repeated every year with different numbers and the same fate: the drawer. Leaders with calendars packed from the first minute to the last who, when asked about the last important decision they made on their own, hesitate longer than they should. Teams that arrive at Friday exhausted and, when asked what they actually delivered that week, talk about processes in motion, conversations had, alignments reached — almost never about something finished. Customers complaining about the same issue for the third time in the same quarter, hearing, for the third time, the same polite line: “we’re already working on that internally.” These aren’t isolated problems of communication, motivation, or talent. They’re the same symptom wearing different clothes: an organization that produces a lot of motion and very little resolution.

There’s an even subtler layer to this same phenomenon, one that rarely shows up in any report because it has no official name: busyness as a collective body language. In environments where deciding is risky and being wrong is costly, looking visibly busy becomes a safe way to signal commitment without ever exposing yourself. Someone who’s always in a meeting, always answering messages, always fully booked, projects the image of contributing — even when much of that motion produces nothing that survives the very week it was generated. It isn’t laziness in disguise. Ironically, it’s the opposite: an excess of diligence that, with no structure to channel it, turns into noise.

There’s an image I like to use when a fast-growing company comes to me, proud of its numbers and lost in front of its symptoms. A teenager’s body, during a growth spurt, hurts. Long bones stretch faster than tendons, muscles, and joints can keep up with — and for a while, there’s genuine, physical growing pain, because the supporting structure doesn’t grow at the same speed as the length of the bone. That’s exactly what happens to companies that double or triple their revenue, their customer base, their headcount, without their decision-making architecture, communication, and leadership growing along with them. The business gets too long for the skeleton holding it up. Every extra meeting, every new committee, every layer of approval thrown together in a hurry is a desperate attempt to brace a bone that grew too fast with a muscle that hasn’t caught up yet. The symptom isn’t the growth. It’s the imbalance between the size of the body and the strength of the structure meant to hold it.

I know of a company that tripled its revenue in eighteen months and, over that same period, kept the exact decision-making structure it had when it was a third of the size: the same three partners personally approving almost everything, the same weekly meeting ritual trying to handle a reality that no longer fit inside it. The result wasn’t immediate, visible chaos — it was something worse, because it was harder to point to. It was a creeping slowness, dressed up as caution, while smaller, more agile competitors took over, decision by decision, the ground that company could no longer decide to claim.

Consider also the case, repeated in nearly every industry, of the brilliant professional who solves alone the problems nobody else can crack. They deliver, get recognized, get promoted — and overnight, stop being paid to solve problems and start being paid to get twelve other people to solve problems they don’t always understand as deeply as they understood their own. The reflex trained over a lifetime stays the same: when a problem shows up, they solve it alone, again, late at night, exhausted, while the team waits for direction and learns, in practice, that they don’t need to think — because the boss always handles it. Nobody in that picture is incompetent. What’s missing is the honest recognition that leading people is an entirely different skill from producing technical results, and almost nobody is prepared for that shift before getting pushed into it.

There’s a recurring, almost universal confusion between two concepts that sound like synonyms and aren’t: consensus and alignment. Seeking consensus means trying to get everyone to agree before acting — a slow, exhausting process that, in practice, is almost always incomplete, because there’s always someone holding a reservation in reserve, ready to bring it up later if the outcome doesn’t go as expected. Alignment is something else: making sure everyone understands the decision that was made, even while disagreeing with it, and commits to executing it with the same energy as someone who agreed from the start. Companies stuck in the first model live meeting to meeting, trying to wring out a unanimous “yes” that may never come. Companies that master the second decide faster, fail earlier, correct more cheaply — and, crucially, know exactly who’s accountable for every choice made.

Back to the meeting, because that’s where the hardest part to swallow lives. Try this experiment, if you dare, at your company’s next important meeting: at the end, without letting people compare notes with each other, ask each person, individually and in private, what was decided. You’ll likely collect five different versions of a meeting everyone considered productive. That’s not because people weren’t paying attention. It’s because the meeting, structurally, wasn’t designed to produce a decision with an owner, a deadline, and a consequence. It was designed — without anyone consciously planning it that way — to produce the comfortable feeling that something got resolved.

This might be the most underrated mechanism in organizational life: meetings frequently function as a place where accountability walks in concentrated in one or two people and walks out diluted among everyone present — just enough that, when the result doesn’t show up, no one can be individually held to it, because, after all, “it was a group decision.” It’s a quiet engineering of mutual protection, never deliberately designed by anyone, and yet extraordinarily efficient at its undeclared purpose. Ironically, the more meetings a company creates to try to solve a chronic problem, the more layers of protection against accountability it builds around it — which is exactly why the chronic problem stays chronic. It doesn’t survive despite the meetings. It survives, in large part, because of them.

There’s a particular ritual that illustrates this with almost comic cruelty: the monthly meeting, always the same day, always the same people, always the same metric stuck in red for six months — where everyone reviews the chart again, repeats hypotheses already discussed last month, jots down an action item that probably won’t go anywhere, and leaves feeling like the job got done. It’s the corporate equivalent of repeatedly checking a thermometer without ever adjusting the thermostat. The ritual of revisiting the problem quietly replaced the work of actually solving it.

It’s worth putting a real price tag on this. A problem that repeats quarter after quarter doesn’t just cost the time spent discussing it all over again. It costs leadership’s credibility, which gradually starts to sound like a broken record. It costs the team’s engagement, who learn to treat the issue as recurring theater and stop taking it seriously. It quietly costs customer trust, who notice — before any satisfaction survey ever reveals it — that they’re dealing with an organization that can name its problems with precision but can’t solve them. None of that shows up on a single line of a balance sheet. Maybe that’s exactly why it keeps getting ignored for so long.

The same logic explains why conflict between departments is rarely, at its core, a personality problem — even though it’s almost always treated as one. Picture the classic scene: sales promises a deadline operations considers impossible; operations complains that sales “doesn’t understand how the floor actually works”; sales complains that operations “is holding back growth.” Both are right, within their own dashboards. Salespeople are evaluated and paid for closing deals. Operations people are evaluated and paid for hitting cost and quality targets. Nobody in that scene is the villain. There are two incentive systems running in parallel, pulling smart people in opposite directions — and calling that “lack of alignment,” as if it were a matter of goodwill, hides the fact that it’s actually a matter of design. Put the two kindest people in the world inside that same structure and they’ll still clash, because the friction isn’t born from anyone’s character. It’s born from an architecture that pays good people to disagree with each other.

Turnover follows a similar logic, just quieter. Anyone who works closely with people knows: almost nobody resigns on the day they decide to leave. The real departure usually happens months earlier, in silence — in the meeting where they stopped sharing their opinion because they realized it didn’t change anything, in the project they accepted with zero enthusiasm because they no longer expected to be heard, in the energy that got pulled back little by little until just enough was left to go through the motions. By the time the resignation letter finally lands on the manager’s desk, it usually comes as a surprise. The person, in practice, had already left a long time ago. The body just took a while to catch up with a decision the mind had already made somewhere along the way, between one unproductive meeting and the next.

Faced with all of this, the most common temptation is to try to solve complexity with more of the same kind of action: more meetings, more internal memos, more one-afternoon motivational training, more inspirational quote framed on the office wall. It works like a painkiller. It eases the symptom for a few weeks and hands the problem back, with interest, shortly after. Complex problems don’t need more action. They need a different kind of structure: absolute clarity about who decides what, deadlines that actually cost something when missed, small and frequent conversations instead of large, rare, inconclusive meetings, and leaders genuinely prepared for the relational work that leading requires — not just the technical work that got them there in the first place.

None of this is a magic formula or a five-step checklist to print out and tape to the wall. It’s a kind of organizational maturity that gets built slowly, decision after decision, with the uncomfortable courage to admit that part of today’s chaos was, unintentionally, designed by the very people now trying to fix it.

There are companies that, by cutting their recurring meetings in half and requiring every remaining one to end with a named decision, a clear owner, and a check-in date, discover something revealing: half the meetings they used to hold never needed to be meetings in the first place. Most of the time, the same problem got solved just as effectively in a ten-minute conversation between the two right people — no audience, no minutes, none of the dilution a packed room inevitably produces. This isn’t about eliminating collective dialogue. It’s about giving it back the function it lost along the way.

Organizations that manage to face this recognition without drowning in guilt tend to come out the other side lighter — not because they stopped having complex problems, but because they stopped pretending, in ever-longer meetings, that talking about the problem is the same thing as solving it.

Next time your company calls a meeting to address, once again, the same problem that’s already shown up on at least three previous agendas, it’s worth asking a simple question before walking into the room: are we here to decide something — or to politely decide, once more, to decide nothing at all? The honest answer to that question usually says more about an organization’s real health than any quarterly results deck ever could.

This was just one fragment of a broader investigation I’ve spent years building, on how human behavior, leadership, and organizational structure intersect in practice. If this resonated with you, there are hundreds of reflections like it waiting for you — on human development, organizational behavior, and healthy relationships, both at work and beyond — on the blog.

#organizationaldevelopment #leadership #organizationalculture #peoplemanagement #businessstrategy #productivity #highperformance #marcellodesouza #marcellodesouzaoficial #coachingevoce