A two-day strategic planning offsite has four parts, and only one of them happens in the room. Two weeks of pre-work. Three to five decisions agreed in writing before anyone builds an agenda. About fifteen working hours across two days, structured around those decisions instead of around presentations. Then thirty days of follow-through. Teams that skip part one and part four get two good days and a quarter that looks exactly like the last one.
Below is the agenda I actually run, block by block, with the pre-work that has to land before it and the decisions that usually end up on the list. Take it and run it yourself, or have someone run it. Either way the structure is the same.
First: is this annual planning, or a strategy reset?
They are different rooms and they fail for different reasons.
Annual planning starts from last year's plan. The question is how much more, by when, with what resources. The numbers move. The shape of the business does not. That is a real meeting and it usually belongs with the finance calendar.
A strategy reset starts from a decision the company has not been able to make. Not a number, a decision. Three signals:
- The same decision keeps coming back and never closes. It gets discussed every quarter, everyone has a position, and nothing is written down that anyone could act on.
- The plan has missed for two or three quarters and every explanation is about execution. When the explanation is always execution, the problem is usually further up: the plan is asking the company to do more things than it can do well.
- The team is quietly arguing about something structural. Where the business is really working, who owns which segment, which product gets the engineers. The argument never gets settled in a room with everyone in it.
Any one of those is enough. If you recognise two, you are not behind on planning. You are carrying a decision. The agenda below is built for that, whatever the decision turns out to be.
The two weeks before: the pre-work that decides the outcome
What goes wrong in these rooms usually went wrong two weeks earlier. Nobody wrote down what had to be decided, so the agenda filled up with topics, the hard conversation landed late on day two, and everyone flew home with photographs of a whiteboard. Three pieces of pre-work prevent all of it.
1. The decision list, agreed in writing (two weeks out)
Two weeks out, before anyone opens a calendar, the CEO and whoever is running the session write down the three to five decisions this offsite exists to make. One page. Per line: the decision itself, the person who owns it today, the cost of carrying it another quarter, and the wording that will count as decided. I call it the Decision Contract, and the method behind it is its own piece.
Topics do not belong on it. "Pricing" is a topic. "Raise list price in Q1, yes or no, and by how much" is a decision, and the test is whether the sentence can be true or false by March. Three to five of them, not nine. A leadership team can close five real decisions in two days. Nine is how you end up with a deck instead of a plan.
2. One conversation with every seat in the room (ten days out)
Forty-five minutes to an hour with each person, confidential, before the agenda is written. Three questions carry most of the weight. Which decisions does this team keep making again? What does nobody say out loud when everyone is in the room? And line by line on the list, where do you stand right now?
By the end you know where the real disagreements live and which kind each one is: a disagreement about facts, a disagreement about decision rights, or two people. Those three get handled differently in the room, and you cannot tell them apart from the outside.
3. The evidence pack, five pages, sent seventy-two hours out
Not a strategy deck. The five things the business has already told you, in numbers nobody argues with on the day:
- Retention and expansion by cohort and by segment, not blended.
- Gross margin by product or segment, with the cost lines that actually move it.
- Pipeline by source, and what share of new revenue came from the motion you say is your motion.
- Win/loss from the last two quarters, in the customers' words, not the sales team's summary.
- Where engineering time went last quarter against where the plan said it would go.
Read before, not presented in the room. If it needs a presentation to be understood, it is not ready. The rule I hold: no pre-read longer than ten pages, and nothing in the room that was not in the pre-read.
What usually ends up on the decision list
The decisions are different in every company, and the agenda does not care which ones you bring. But across these rooms the same four shapes come up, and it is worth knowing them before you write your own list.
- Where the business is actually working, and where the next four quarters go. Not where we hoped. Where retention, expansion and win rate say it is. For a growth-stage technology team this is usually the segment or motion question; for a company further along it is usually a portfolio question. Same decision, different vocabulary.
- What we stop. Focus without a stop list is a wish. The stop list is the decision, and it is the one that needs a night's sleep.
- Who decides what, from here. A great deal of what a team calls misalignment turns out to be an unanswered question about who has the call.
- The thing nobody will say. There is almost always something everyone in the room knows and nobody has put on a slide. If it does not make the list, the other three decisions will be made around it, and they will not hold.
One test before you finalise the list: could someone act differently on Monday because of this line? If not, it is a topic.
The two-day agenda, block by block
About fifteen working hours. Times are a working pattern, not a rule. What matters is the order. The disagreement goes first, while the team is fresh and the CEO is listening rather than talking. The stop decision goes before dinner on day one, because it is the one people need a night with.
| Time | Block | What has to come out of it |
|---|---|---|
| 8:30 | The decision list, read aloud | Everyone hears the three to five decisions and what "decided" looks like. Nothing else is on the agenda. |
| 9:00 | What the business taught us | Forty-five minutes on the evidence pack, questions only. No presentation longer than ten minutes. |
| 10:15 | The disagreements, first | The facilitator puts the disagreements the interviews surfaced on the wall, unattributed. The team names which are about facts, which about decision rights, which about people. |
| 12:00 | Lunch | No working session. The morning needs to settle. |
| 1:00 | Where the business is actually working | Decision one: what the next four quarters are built around, with the evidence named rather than asserted. |
| 3:00 | The focus decision, and the stop list | Decision two: what gets the resources, and what stops. Named, not implied. |
| 4:45 | Read the log back | What was decided today, in the words it will be written in. Disagreements get named, not smoothed. |
| Evening | Dinner, no agenda | People need a night with the stop decision before day two. |
| Time | Block | What has to come out of it |
|---|---|---|
| 8:30 | What did not survive the night | Thirty minutes to reopen anything that looked decided and is not. Better here than in six weeks. |
| 9:00 | The structural decisions | Decisions three to five: how the team is organised around the focus, what gets resourced, what sequence. |
| 11:00 | Decision rights | For each decision: who decides, who gets a say, who has to live with it. Written down. |
| 12:00 | Lunch | |
| 1:00 | The operating rhythm | Which existing meeting each decision plugs into, and what metric will show it moving. A decision with no rhythm is a decision that quietly expires. |
| 2:30 | Owners and dates | Every decision and every defined alternative gets one name and one date. One name, not a team. |
| 3:30 | The log, read back against the list | If the log and the decision list do not match, the room is not done. This is the test that makes the two days real. |
| 4:15 | What we tell the company on Monday | Three sentences the whole team will say the same way. Write them in the room. |
Who should be in the room
The CEO and the direct reports who own the decisions on the list. Six to ten people. Add a board member or an advisor for a single block if one decision genuinely needs them, and have them leave after it.
Seats handed out to avoid hurt feelings cost you the honest conversation, and the honest conversation is what the two days are for. If someone should be there for development reasons, give them the day-two operating-rhythm block. That is real exposure and it costs the room nothing.
What you leave with: decisions, or defined alternatives
Not every decision closes in the room, and a session that forces a false close is worse than one that does not. The honest output is one of two things for every line on the list.
A decision: what was decided, who owns it, the first action, and a date.
A defined alternative: the two or three real options, what you would need to know to choose between them, who owns finding that out, and the date they bring it back. That is not a deferral. A deferral is "let's come back to this". A defined alternative has a name and a date on it.
All of it lands in a decision log while the room is still in session: the call that was made, anything parked and the date it comes back, anything sent up a level, the owner, and the first action with its date. Every attendee has the log within two business days.
The thirty days after
The measure of an offsite is not the two days. It is the ninety after, and the thirty that set them up.
Week one: the log is out, and every owner has confirmed their first action in writing. Week two: the three sentences have been said to the company, by the CEO, in the same words the leadership team wrote. Weeks three and four: each decision has appeared at least once in the operating rhythm it was assigned to, and someone has checked the first two places a decision started to slide back. There are always two.
The failure mode is not disagreement. It is silence, a decision that nobody argues with and nobody schedules.
Where these sessions go wrong
- The agenda is built from topics. Topics produce discussion. Decisions produce decisions.
- The hard conversation is scheduled for after lunch on day two. By then the room has invested a day in agreeing, and nobody wants to be the one who reopens it.
- Too many people. Twelve is a conference. Ten is the ceiling for a room where people say what they think.
- The evidence arrives as a presentation. If the data is new to the room, the room spends its day understanding it instead of deciding with it.
- Nobody will say the quiet part. When a room talks itself into a plan its own numbers contradict, a moderator writes it up as agreed and moves on.
- No owner, or a team as the owner. A decision owned by "product and sales" is owned by nobody.
- The plan never plugs into the operating rhythm. This is the most common one and the easiest to fix, and it is why day two ends where it does.
Run it yourself, or bring someone in
You can run this agenda internally. Plenty of teams do, and it beats not doing it. The two things that are hard to do from inside: the confidential one-on-ones, and saying the true thing when the room does not want to hear it.
If you are weighing that against hiring someone, what a facilitator or planning consultant costs is published separately: the survey figures, what moves the fee, and what to ask before you sign.
The CEO in particular can rarely run their own reset. They are a party to every decision on the list and the person everyone is most careful around. The person holding the process cannot be one of the people arguing, and the arguing is the whole point. If you do bring someone in, the piece on how to run an executive offsite has the questions to ask before you hire.
I have called these sessions and I have sat through them. Founder and CEO through a Nasdaq IPO. EVP at New Relic. VP at Cox Automotive with a $250M budget. COO in a VC-backed turnaround, where two unproductive days were not something the company could absorb. These days I am the one running the room, which is the same two days from a different chair.
The templates
Two one-page PDFs, both free and neither gated. The Strategy Offsite Plan is this page on one sheet: the two-week pre-work checklist with owners, the block-by-block agenda for both days, and the thirty-day follow-through. The Decision Contract is the one you fill in first, where the three to five decisions get written down before the agenda exists. It also lives on the facilitation page.
Use them with me or with anyone. If you take one thing from this page, take that: the agenda comes after the decisions, never before.
Take the plan with you.
The pre-work checklist, the two-day agenda and the thirty days after, on one page. Plus the Decision Contract to fill in first.
Bring a filled-in contract to the discovery call and we start from the decisions, not the agenda.
Common questions
What should a strategic planning offsite agenda include?
Three to five named decisions, the evidence behind them read in advance, the disagreements surfaced in the first two hours, a stop decision before dinner on day one, decision rights, owners and dates, and a read-back of the decision log against the original list before the room empties. If an agenda contains presentations and time slots but no named decisions, it is a conference agenda.
How long should a strategy offsite be?
Two days for a strategy reset with structural decisions in it. One day if there is a single decision and the team already trusts each other. Half a day is a working session on one problem, not a reset. What does not work is two days with eight decisions, or one day that tries to be two.
What pre-work should a leadership team do before a strategic planning session?
The decision list agreed in writing two weeks out, a confidential conversation with every person who will be in the room, and a five-page evidence pack sent seventy-two hours ahead: retention and expansion by cohort, gross margin by segment, pipeline by source, win/loss in the customers' words, and where engineering time actually went.
How do you lead a strategic planning session?
Open with the decisions, not the agenda. Put the disagreements first while people are fresh. Cap presentations at ten minutes. Name decision rights before each decision, not after. Capture every decision in a log as it happens. Read the log back against the decision list before anyone leaves, and treat a mismatch as unfinished work rather than a rounding error.
Who should attend a strategic planning offsite?
The CEO and the direct reports who own the decisions on the list. Six to ten people. A board member or advisor for one block if a specific decision needs them. Nobody added for politics or optics.
What are the four types of facilitators?
In practice you will meet four, and they are good at different things. The process facilitator holds the structure and stays out of the content. The trainer teaches a method and runs the room through it. The content expert brings an answer and works the team toward it. The operator has sat in the seat the room reports to and will tell you when the plan contradicts your own numbers. The first is safest, the last is the one worth paying for when the decision is hard and the team already knows the method. Ask which one you are hiring before the contract, not after.
Should we do it in person?
Do the room in person. The pre-interviews and the thirty-day follow-through run fine on video. Two days where ten people have to say what they actually think while the boss listens do not.