By Andreas Pettersson, Founder, Leaders ADAPT
You know the company can win. You also know you're the one dragging eight people up the hill, and the post mortems keep finding the same things. So someone suggests an executive retreat, and you picture a lodge, a team building afternoon, and a Monday where nothing changed.
That version is a vacation with name tags. The decisions per day test is a retreat scoring rule: count the decisions that left the room with one named owner and a date, divide by the number of days, and if the result is below three the retreat was a vacation. Three a day is the floor I hold my own retreats to, and the one I'd hold a facilitator to before paying the invoice.
Here's what the retreat is for, the two day executive retreat agenda I run with outputs per block, the cadence, and how to score it.
Quick answer: An executive retreat is a one to three day off site meeting of a company's leadership team, held quarterly or twice a year, to review the last period, set three to five priorities for the next one, and assign one owner to each. A retreat that works ends with written commitments and dates; one that produces only discussion, bonding or a long list has not met its purpose.
What is the purpose of an executive retreat?
Three purposes. Most retreats confuse them.
Decide. The things the weekly leadership meeting can't hold: the three year picture, which product line to stop, whether the structure still fits, who owns next quarter's priorities. These need time, distance from email, and a room with titles off.
Realign. The leadership offsite is where the team hears the same story at the same time. Across 199 people who came to Leaders ADAPT for coaching, advisory or a discovery call between 2024 and 2026, 22% raised leadership team alignment and accountability; among executives the share was 34% (What CEOs Bring to Coaching, 2026). The CEO rarely names alignment first. The team does.
Rebuild trust. Dinner, the walk, the argument that gets finished instead of parked. Real, but a by product. Design for it and you get a team building event. Design for decisions and trust shows up anyway.
The purpose is never to inform. Two presentation blocks on the agenda and you've booked a conference for eight.
Retreat vs offsite vs team building: which one are you planning?
The words get used loosely, and the mix up costs a day. A leadership team offsite and an executive retreat are cousins; team building is a different species.
| Format | Who | Length | Primary output | When it's the right call |
|---|---|---|---|---|
| Executive retreat | leadership team, 5 to 10 people | 2 to 3 days, off site, overnight | annual direction, 3 to 5 priorities with owners, structural decisions | annual planning, a plateau, a new CEO, a merger |
| Leadership offsite (quarterly) | leadership team | 1 full day, off site, no overnight | the look back, 3 to 5 quarterly priorities, written commitments | every 90 days as part of the operating rhythm |
| Team building event | any team | half day to 1 day | shared experience, stronger relationships | a new team, after a conflict or heavy hiring; never a substitute for the two above |
| Company kickoff | the whole company | half day | everyone hears the plan the leadership team made | after the retreat, never instead of it |
An executive offsite and an executive retreat differ mainly in length and the overnight. The quarterly offsite is a one day working session. The retreat is the longer, usually annual, version with a night in between, because some decisions need sleep before the commit.
How long should an executive retreat be, and how often?
The cadence I prescribe in The 5-Minute Leader is a full day minimum every 90 days, genuinely off site in a different location, no laptops except the presenter's, no urgent calls. The attendance test comes with it: if nobody else can handle the company for one day, you don't have a scheduling problem, you have a delegation problem. The delegation assessment tells you how big.
Once a year, stretch the quarterly offsite into the two day retreat. Why quarterly: monthly gives too little data to see a pattern, annual allows too much drift. A quarter is long enough to accomplish something and short enough to adapt.
On length, here's what I learned running retreats for my own CEO mastermind, two days every six months. The main feedback after one of them was more bonding time and fewer sessions. I'd packed the days.
So now I protect the social time the way I protect the decision blocks. Guest speakers get about two and a half hours each on separate days, and the roundtable slots go to the four or five people who most need feedback; everyone else comes prepared knowing they might not get one. We get far more done in person, because the agenda has less in it.
When a team says it can't afford two days away: Microsoft's 2025 Work Trend Index found 52% of leaders say work feels chaotic and fragmented, with interruptions about every two minutes (Microsoft, 2025), and Asana's Anatomy of Work Index puts the average knowledge worker's loss to unnecessary meetings at about 103 hours a year (Asana). You're not losing two days. You're buying the only two uninterrupted ones this quarter.
What should the executive retreat agenda be?
Here's the two day executive retreat agenda I run, with the output each block must produce. Day one is strategy, broad to narrow. Day two is execution, and it moves. Offsite facilitation on both days is an outsider's job; with my own team I'm a participant.
| Block | Day and time | What happens | Output |
|---|---|---|---|
| Rules | Day 1, 8:30 to 9:00 | Titles off, "yes and" until lunch, phones in a box, the decisions per day target said aloud | a room that knows how it'll be scored |
| Look back | Day 1, 9:00 to 10:30 | What we committed to, what shipped, what didn't, why. Honest, against the habit of pretending targets were hit | three lessons, written |
| North Star | Day 1, 10:30 to 12:15 | Where the company must be in three years: one sentence, three numbers. Standing, post its, a co facilitator on the energy | a draft North Star |
| Lunch off site | Day 1, 12:15 to 13:45 | Leave the venue. The morning is recorded and turned into a straw man strategy draft during the break | a one page draft on return |
| Narrow | Day 1, 13:45 to 16:00 | From the draft to three strategic pillars, at least one cross departmental | three pillars, named |
| Decide | Day 1, 16:00 to 17:30 | Three to five priorities for the year ahead, one owner each, and the no list | decisions with owners (count them) |
| Dinner | Day 1 evening | No agenda. The parked arguments finish here | nothing to write down, on purpose |
| Walk shop | Day 2, 8:30 to 12:00 | The leadership group visits a site, a floor or a customer, or walks a route, in pairs, each pair working one real problem from the lists | one proposed decision per pair |
| Live IDS | Day 2, 13:00 to 15:00 | Identify, discuss, solve on the two biggest current issues, facilitator acting as a team member, not a lecturer | two decisions, one owner each |
| Commit | Day 2, 15:00 to 16:30 | Each leader states priority, owner, number and date aloud and in writing. Scorecard metrics set | the plan on one page, commitments signed |
| Score | Day 2, 16:30 to 17:00 | Count the decisions with owners and dates. Divide by two | the decisions per day number |
Day two moves because day one sat. The walk shop isn't a gimmick. Interactions land less stale when people move and talk rather than sit, and if you walk your own facilities, the staff see the whole leadership group show up together, a team pride exercise you'd struggle to buy.
The straw man draft during lunch means the afternoon starts from a page, not a blank wall. Record the morning, run a prepared prompt against the transcript, review the draft fresh. About 80 percent right is enough.
Nothing on a slide. No death by PowerPoint. Post its, whiteboards, standing exercises, and a facilitator who narrows the group toward decisions after lunch.
Cut what the room isn't ready for. On one offsite a stakeholder pushed to add AI to the agenda. A co facilitator suggested tabling it because the organization wasn't ready, and I agreed on the spot, even though it's my strongest line. The retreat serves the room.
How do you plan an executive retreat?
Six weeks is enough, in this order.
- Fix the purpose in one sentence and write the expected decisions at the bottom of the invitation: "By Friday 17:00 we will have chosen next year's three priorities and their owners." If you can't write that sentence, you're planning a team building event.
- Choose the facilitator before the venue. Offsite facilitation by an outsider lets you be a participant; you cannot be both. The strategic planning facilitator guide covers who to hire and what it costs.
- Pre interview every leader, privately: what should we stop, what are we pretending is fine, what would you do in my chair. Nothing said gets attributed in the room.
- One page of numbers, last four quarters, a week ahead. No deck.
- Pick a venue that forces the behavior. Within two hours' drive, a room where tables can go to the wall, somewhere to walk on day two, a dinner table that seats everyone. This page doesn't rank venues or quote room rates; the venue sites do, and none mention outputs.
- Book the follow through first. The weekly leadership meeting slot, the first monthly scorecard date, and the next quarterly offsite go on the calendar before anyone packs a bag. A retreat without a rhythm behind it is a long weekend.
How do you measure a retreat worked?
Score it twice: on the drive home and at day 90.
On the drive home: decisions per day. Count every decision that left the room with one named owner and a date, and divide by the number of days. Three or more per day and the retreat did its job. Below three and you had a pleasant time.
Strategy is a choice. If you're not choosing, you're not strategizing, and a retreat that produced a mood instead of choices is the most expensive kind of not choosing. Two rules keep the number honest: a decision with two owners has none and doesn't count; "we'll explore" is a decision not to decide, fine if it goes on the no list.
At day 90: the look back block of the next offsite. What did we commit to, what did we accomplish, what worked, what failed and why. That conversation is only honest if the commitments were written and public at the retreat.
McKinsey's survey of 1,259 executives found top executives spend about 70% of their time on decision making (McKinsey Quarterly, 2019). A retreat is the one place that time is spent together, in writing, dated.
The failed retreat is the one where everyone tells the CEO how, and nobody writes down who. The owner column is the whole page.
Executive retreat FAQ
What is an executive retreat?
An executive retreat is an off site meeting of a company's leadership team, usually one to three days with at least one overnight, held to make decisions the regular meeting rhythm cannot hold: the multi year direction, the priorities for the next period and their owners, structural changes, and what the company will stop doing. It differs from a team building event in that its primary output is written decisions rather than shared experience.
How long should an executive retreat be?
Two days with one overnight is the common length for an annual executive retreat; one full day is the standard for a quarterly leadership offsite. Three days suits a new CEO's first retreat or a post merger integration. Longer than three days produces fatigue and fewer decisions per day. The length should follow the number of decisions required, not the venue's minimum stay.
Should you hire a facilitator for an executive retreat?
An outside facilitator is advisable whenever the CEO wants to participate fully, when the team is misaligned, when the agenda includes the CEO's own role, or when the company is installing a new operating system such as EOS, Scaling Up or OKRs. A chief of staff or COO can run a routine quarterly offsite once the agenda is a template. The CEO cannot act as both participant and facilitator without one of the roles suffering.
What should the output of an executive retreat be?
A one page plan listing the three to five priorities for the next period, one owner and one measurable number per priority, the dates each will be reviewed, and the list of what the company will stop doing. Each leader's commitments should be stated aloud and recorded. A slide summary alone is a weak output because few teams reopen it; the one page plan feeds the monthly scorecard and the next offsite's look back.
How often should a leadership team hold an offsite?
Every 90 days for a full day leadership offsite, with one of the four each year extended to a two day executive retreat for annual planning. Quarterly spacing gives enough data to see patterns without the drift that annual only planning permits. Teams in a crisis compress the rhythm rather than cancel it, because a crisis is when a shared set of priorities matters most.
Count the decisions, not the days
An executive retreat is judged by one number, and it isn't the hotel rating. Count the decisions that left with an owner and a date, divide by the days, and tell the team the score before the last dinner. Teams that know they'll be scored decide differently by 10 a.m.
If the number keeps coming in low, the retreat isn't the problem. The leadership team has no rhythm to carry decisions out of the room and no Alignment Check on the priorities between retreats. That's leadership team coaching work, and it's cheaper than another lodge.
When your retreats produce agreement and your quarters produce surprises
This is what 1:1 CEO advisory at Leaders ADAPT does about it, mechanism first. A 30 minute discovery call, where I ask for your last retreat's output and we score it together. Then 90 days of weekly sessions on three components.
The operating rhythm: a weekly leadership meeting, a monthly scorecard, and a quarterly offsite you attend as a participant. The commit discipline: every priority with one owner, one number and one date, read back to the team. And a third component I run in the two weeks before a retreat that tells me which decision the team will try to avoid, which I'll show you on the call rather than describe here. I was a tech CEO for 10 years, ran Arcules as one of Canon's youngest CEOs, and took a 10 day vacation with zero calls once this rhythm was in place, so I know a retreat from a vacation from both sides.
Tomorrow morning, open the notes from your last executive retreat and count the decisions that had one owner and a date, then divide by the days. Under three is the first conversation to have: 1:1 CEO coaching with Andreas.


