Walk into almost any growing company that's noticed it has an "alignment problem" and you will find the same instinct in operation: schedule a meeting. A weekly leadership sync. A cross-functional standup. A monthly strategy review. A new all-hands rhythm because the old one wasn't doing the job. Within eighteen months, the senior team's calendars look like Tetris boards and people are quietly asking when they're supposed to do the actual work.
The meetings aren't useless. But they're treating the symptom. Alignment that requires a meeting to maintain isn't alignment at all — it's synchronised understanding that starts degrading the second the meeting ends. By Wednesday, the version of the strategy in five different heads has already diverged. By Friday, two teams are working on something the Monday meeting was supposed to have prevented.
What alignment actually means
Alignment doesn't mean "everyone heard the same words at the same time." That's communication. Alignment means the work happening across the organisation is directed at the same outcomes — provably, continuously, and without anyone having to be told again.
When alignment exists as a property of the work, the engineer building the API integration knows which key result it serves, who else is working toward the same goal, and what the current state of that goal is. She knows this not because she was in the all-hands. She knows it because the system she opens every morning tells her, and tells her colleague the same thing, and tells her manager the same thing on top of that.
When that system doesn't exist, alignment requires meetings to sustain it. And here's the brutal part: the meeting that aligns a team is evidence that the system failed to. The more meetings your alignment depends on, the worse your alignment infrastructure is.
The three things alignment-by-meeting costs you
The direct costs of alignment meetings are easy to see — calendar time, prep, the carefully formatted update deck. They're not the expensive ones. The expensive costs are the ones that don't show up on a calendar.
The first is the attention tax. A fifty-person company with two hours of weekly alignment meetings per person is burning a hundred person-hours a week — the equivalent of two and a half full-time employees doing nothing but maintaining shared understanding. That's a real expense. It just isn't on a P&L line.
The second is the degradation interval. Alignment created in a meeting begins decaying immediately. By the time the next meeting arrives, a week of decisions, pivots and priority shifts have introduced drift. The faster the company is moving, the faster the alignment degrades, and the more meetings get added to compensate. The result is a negative feedback loop: the more turbulent the strategy, the more meeting time required to hold it together, and the less time available for actual work. Companies in this loop usually conclude they need better meetings, when what they need is a different load-bearing structure.
The third cost is the one nobody discusses. When the weekly leadership sync becomes the place alignment happens, decisions stop happening there. The agenda fills up with "where are we?" and never reaches "what do we decide?" The strategy meeting becomes a status meeting wearing a strategy meeting's name tag. Over time, the company loses the muscle of making decisions in a room of more than three people — because the room of more than three people is busy maintaining shared understanding instead.
What alignment looks like when it's a system property
It looks like this. Every work item in the system is linked to the outcome it's supposed to move. When a new piece of work is created, the first question the system asks — and won't let you skip — is which goal does this serve? If the answer is "none," the work is flagged. Not blocked. Visible as unanchored. Someone has to make a call about it, and the call is logged.
Every person in the company can see, without asking, whether what they're working on is aligned to what the organisation has agreed to prioritise. The answer doesn't come from a meeting. It comes from the surface they're already in. When something drifts — when work that should be moving a strategic priority is in fact moving something else, or when a strategic priority has no active work behind it — the system surfaces it on the day it happens, not in the quarterly review that's still six weeks away.
This is what removes meetings from the alignment job description. Not better meetings. Different infrastructure.
What meetings should actually be for
The point isn't to eliminate meetings. The point is to stop using meetings to do work that infrastructure should be doing.
Status meetings become unnecessary. The system is the status. Reading it out loud to each other for forty-five minutes is theatre.
Alignment meetings become unnecessary. The system is the alignment layer. The remaining meeting is for the cases the system can't decide automatically — judgment calls, strategic pivots, escalations that need a human to weigh in.
Strategy reviews become shorter and dramatically higher-value. Instead of spending the first thirty minutes reconstructing what happened, the meeting opens with a live system view: which goals have active work, which are stalled, which decisions are pending. The conversation that follows is thirty minutes of actual judgment, not thirty minutes of catching up on facts that were already in the system.
The Vindaris view
We build the system layer because the communication layer has a proven ceiling. You can communicate your way to alignment in a twenty-person company because everyone is in the same room every day. You cannot communicate your way to alignment in a hundred-person company. At that size, alignment has to be embedded in the work items, the goal connections, the ownership model, and the capacity graph — or it doesn't hold, no matter how many meetings you add.
The meeting that used to create alignment becomes the meeting that uses it. That's the whole shift.