Every year, companies spend serious money sending their executive teams somewhere quiet to get on the same page, and every year execution stalls anyway. The off-site produces real clarity in the room and almost nothing that survives contact with the operating month that follows. Javier Castillo, an executive advisor who works with leadership teams on exactly this problem, argues that the failure is not one of facilitation or effort. It is that alignment gets treated as an event when it behaves like infrastructure. “Alignment is a process, not an event,” he says. A retreat does what it is built to do: it pulls executives out of the noise and gives them uninterrupted time to think. Castillo calls that the design phase. The mistake is believing it is the whole build.
Why The Off-Site Loses To The Operating Model
The structural problem shows up the moment the team walks back in. “The team leaves the room, the noise comes back, the pressure returns, and the spotlight lands on every leader individually again,” Castillo says. “Nothing in the company changed while they were gone.” That last clause is the whole argument. Two days of consensus are competing against a compensation system, a reporting cadence, and a set of individual accountabilities that were all designed before the retreat and remain untouched by it. When agreements made off-site meet incentives still running the business, the incentives win. They are not stronger arguments. They are simply the thing people are measured on.
There is an earlier flaw too, one most retreat designs quietly assume away. The format presumes everyone arrives with a shared mindset, when building that mindset is the real work. “You don’t get a team mentality by skipping the individual one,” Castillo says. Each leader carries a private read on the priorities, a personal definition of success, and unspoken conditions for buy-in. Alignment has to work through those person by person, understanding each leader’s biases and preferences, before anything collective can be molded from them. Skip that and the group is agreeing on vocabulary rather than on direction.
The Misalignment That Looks Like Harmony
The most expensive version of this problem sits inside teams convinced they have solved it. “The team that believes it’s aligned usually has consensus on the words and no consensus on the meaning,” Castillo says. Everyone nods at customer-centric or growth focus and leaves with a different picture of what it requires them to stop doing. The tells are small and easy to rationalize: functions optimizing locally in ways that undercut each other, decisions relitigated in side conversations after the meeting ends, leaders publicly backing a plan while privately protecting their turf inside it. Often that is not obtuseness. Naming the real cost of the plan out loud makes a leader look like the detractor, so nodding along is the safer move. “They mistake harmony with lack of courageous conflict, right up until execution stalls and nobody can explain why.”
What goes unpriced is sacrifice. “You want to bet on innovation, that comes with a cost. You say engagement matters, that comes with a cost too,” Castillo says. Teams agree to the priority and skip the harder conversation about what they will give up for it, which is why the agreement feels solid without ever being tested. Then a real decision lands, resources tighten, and the shared priority bends toward whatever protects the number. That is normally the first moment anyone notices the alignment was never there. And when the pattern repeats, the cause is rarely ignorance of the trade-off. The incentives underneath are still rewarding the opposite of what was agreed. Someone hits a target the old way and gets rewarded, while the leader who held the line on the stated priority reads as slower or less decisive. Castillo is blunt about where that leaves accountability: that is the system at work, and the people who built it are the only ones with the authority to change it.
The diagnostic he uses on arrival follows from this. First, he checks whether a strategy exists at all, since much of what gets called strategy is a goal with a number attached. Grow 10x names the destination, not the how. Where a genuine strategy is in place, he tests understanding across the team rather than within it. Every function can explain what the strategy means for its own patch, and that part often sounds fine. Ask a sales leader what the strategy demands of operations, or finance what it demands of product, and the answers go vague fast. “A strategy problem shows up as confusion about the destination itself and how to get there. An alignment problem shows up as a team that each understands their own piece perfectly and has almost no picture of how the pieces connect.”
Building Systems That Outlast The People In Them
AI decision tools raise the stakes rather than resolving them. The hard part of a C-suite decision is not simply finding the solution, Castillo argues; it is living with what the solution costs, and that has not changed; it has only been disguised. When a person proposed a plan, the room instinctively questioned it, because someone was about to own the consequences. AI removes that reflex. People can read it as neutral because it has no visible motive, though it still carries bias baked into the data and the framing rather than into anyone’s incentives. “The danger isn’t that the bias exists, it’s that nobody in the room is wired to go looking for it.” An aligned team still treats the hard part as theirs, deciding who absorbs the impact and whether the company can live with it. A misaligned one either defers because agreeing beats being the person who slows things down, or each function extracts the piece of the output that serves its own priorities. Same tool, opposite results.
Which points to what Castillo thinks chief executive officers should be building. “Build a system that survives the people, not one that depends on them.” Alignment held in memory walks out with whoever leaves, and the team as an entity changes the moment its composition does. What must persist are the habits: how the team communicates, challenges, decides, shares information, and holds itself accountable. He knows the objection, that systemizing kills the art of leadership. His answer is that instinct is a learned mechanism made unconscious through practice, and what has been learned can often be passed on. The real resistance is quieter. “Nobody likes building something that makes them replaceable, because being needed is one of the oldest instincts we have. But the leaders worth remembering are the ones who made sure the thing they built didn’t need them to keep working.”
Follow Javier Castillo on LinkedIn for more insights on executive team alignment, organizational design, and leadership systems.
