In Part 1, I talked about who comes to our offsites, when we run them, and why a good pickleball court is almost as important as a good agenda. Now let’s get into what actually happens once everyone is in the room (or in the pool).

This is the part I had to learn the hard way. Running strategy sessions is a bit like cooking spaghetti… looks simple, but if you don’t time it right, everything gets mushy. After years of trial and error, I’ve found a rhythm that makes these sessions productive without turning into corporate torture. This is in no way an exhaustive guide, and I still intend to get better at this, but hopefully someone will find this useful.

The Agenda Book

When everyone arrives, they get an agenda book, printed out on beautiful standard office paper, and lovingly stapled in the top corner. It also comes in a fancy digital version. In fact, they usually see it a few days before the offsite so they know what’s coming. But this isn’t like getting assigned homework. I don’t ask anyone to prepare long presentations or status updates. We’re not here to listen to two hours of “how marketing is doing.”

An example of one of my agendas

Instead, the agenda is designed to focus us on the big questions. It always includes a warm-up to get people thinking, breaks every two hours (because no one does good strategy work with a full bladder), and a quick refresher on what we actually mean by “strategy.”

I’ve uploaded a template version of my Agenda Book for you in case you find it useful.

So… What Is Strategy

Here’s how I break it down in plain English (when I say “I” I mean mainly what I learned from Richard Rumelt’s excellent book “Good Strategy/Bad Strategy“:

  1. Diagnosis. What’s the challenge we’re really facing?
  2. Guiding Policy. What’s our overall approach to deal with it?
  3. Coherent Actions. What are the specific things we’ll do to carry out that policy?

Or, to put it more simply: what game do we want to play, and how do we make sure it’s one we can win? If you haven’t heard this before, watch Robert Martin’s video on “A Plan is Not a Strategy“.

I also always remind my team of our company’s purpose, who we serve, our long-term goals, and our value proposition. Without those reminders, it’s too easy to drift into a “wouldn’t it be cool if…” brainstorm that has nothing to do with what we actually do.

Lessons and Successes

Every offsite starts with a “lessons and successes” session. Everyone writes down what went really well last quarter and what didn’t. But we don’t call them failures. We call them lessons or opportunities. It’s a small linguistic trick that makes people a lot more open about sharing. Somehow, no one wants to talk about failures, but everyone is happy to share a lesson. Go figure.

The Art of Session Timing

The timing of your sessions matters just as much as what you’re talking about. Here are a few rules of thumb I’ve learned:

  • Avoid the first week of January. People are still mentally on the beach.
  • Do the most creative sessions at 10 a.m. That’s the sweet spot between being awake and not yet hungry. Your team’s biological systems may differ.
  • After lunch = process-driven work. Digestion is the enemy of innovation. You can still work while eating, but keep those conversations more about softer subjects (how to handle one on ones, time off policies, annual parties, etc.)
  • End around 4:30 p.m. It gives people time to wind down before dinner and leaves wiggle room if you run over.
  • Plan for things to go off schedule. There will be times when the group is on to something, and you (or hopefully your facilitator) can give them that space to breathe. So you need to plan this time into your agenda.
  • Always define your terms. Even the obvious ones. Trust me, “everyone knows what that means” usually translates to “everyone has a slightly different definition.” Maybe have a little glossary where you say “OKRs: Objectives and Key Results” or something, and you can have it grow.
  • Never plan your agenda in Word or Google Docs. Use a tool like Miro. Moving around digital Post-its is a lot easier than trying to force an agenda into table. You probably have groups of ideas that either need to be spread out through the offsite, or logically follow other sessions. Having this be fluid is much easier.

Exercises That Actually Work

Here are a few of the exercises we’ve used over the years that can spark insight (and sometimes recurring jokes that last for years about moths… ask me sometime).

  • Wins and Lessons from the last quarter.
  • The $500,000 Startup Challenge: “You’ve got half a million to launch a new version of our business. What do you build?”
  • Forward and Backward Visioning: Picture three years in the future, then reverse-engineer how we got there.
  • Personal Three-Year Visions: Where do you want to be, professionally and personally?
  • OKR Realignment: Are our objectives actually aligned to strategy, or just busywork in disguise?
  • Values and Behavior Mapping: How do our values show up in real life, and where do they fall short?
  • Cultural Story Mapping: What stories define us, and what new ones should we be telling?
  • Weird Rules Creation: The sillier, the better. Think: “No big decisions without snacks.” These often end up reinforcing culture more than you’d expect. (Stolen from What You Do Is Who You Are: How to Create Your Business Culture by the brilliant, but increasingly strange Ben Horowitz).

Sometimes things do get very tactical, like “how do we estimate better” or “what should the customer experience feel like at every touchpoint.” The point is to mix the big-picture, the personal, and the practical.

Facilitator or DIY?

For our big three-day Q4 offsite, I work with a professional facilitator. About six weeks before, we start planning the sessions. He drafts exercises, I give feedback, we go back and forth a couple of times, and by the time he arrives, everything is mapped out. During the offsite, he runs most of the sessions, and I step in to lead a few. If you’re going to do this properly, you have to get a professional facilitator. There is no way you can participate and facilitate at the same time. If you want the contact information of our fantastic facilitator, just contact me and I’ll introduce you.

For the one-day offsites, I handle it myself. It’s leaner, but the same principles apply. I still use Miro boards and agenda docs with links so no one has to ask, “Where’s the link again?”

Wrapping It All Up

At the end of each day, we set aside time to reflect and capture action items. On Sunday at the Q4 offsite, we do a quick survey for the facilitator, then finish with a wrap-up where we turn the best ideas into concrete action items or OKRs.

After that, it’s back to the pool, pickleball, or Mario Kart, and whiskey. Sometimes all combined.

Final Thoughts

The trick to a great offsite is balancing focus with fun. If it’s all play, you come back with nothing but a hangover and embarrassing photos of some executive who should not have eaten that gummy (or one that accidentally ate a moth!) If it’s all work, you come back exhausted and not wanting to go back to work. The sweet spot is somewhere in the middle: a weekend of clear strategy, honest reflection, and bragging rights to the late-night Nintendo battles. But the true indicator that you’ve pulled it off is that your team are excited to get back to work on Monday.

That balance is what keeps our team aligned, resilient, and ready for whatever the next quarter throws at us.

Previous ArticleNext Article
I help companies turn their technical ideas into reality.

CEO @Sourcetoad and @OnDeck

Founder of Thankscrate and Data and Sons

Author of Herding Cats and Coders

Fan of judo, squash, whiskey, aggressive inline, and temperamental British sports cars.

Leave a Reply

The Internet Doesn’t Have Enough Love In It (And How We Can Fix It Easily)

I’ve been thinking about all the wrong things when it comes to AI writing code.

Everyone else seems to be too. Job displacement. Security vulnerabilities. The ten-times-faster developer who now bills the same and delivers four times as much. These are real conversations worth having, just not the one I want to have right now.

The one I want to have is about teaching a six-year-old multiplication.

Here’s what I mean. Imagine you’ve been sitting with your kid every night for two weeks trying to explain multiplication. You’ve tried drawing rows of dots. You’ve tried songs (don’t judge me). You’ve tried the “just think of it as groups of things” approach that works for literally every other math concept but, mysteriously, not for your kid. Then one night, something clicks. You found the explanation, YOUR explanation, the one that worked for your actual kid with your actual kid’s brain, and it finally, beautifully, clicks.

Now imagine you could spend a Saturday morning turning that into a small web app. Not a startup. Not a SaaS platform. No login. No backend. No one’s going to hack it (there’s nothing to hack). Just a little thing that walks through multiplication the exact way you figured out it works, step by step, the way you’d explain it. You send it to the WhatsApp group for your kid’s class. Some of those other parents, also quietly losing their minds over multiplication, try it. And it helps.

You just made the world a tiny bit better. That’s it. That’s the whole thing.

Claude Code exists now, and a handful of other tools like it, and the reason I think this matters isn’t productivity. It’s access. The barrier between “I have an idea for something that could help people” and “I have a thing that helps people” used to require knowing how to code, or hiring someone who does, or talking a developer friend into your project over enough beers that their guilt exceeded their better judgment. Now it’s a Saturday morning and a good description of what you want to build.

The internet already has beautiful things in it that were built out of love. Free coding education for kids. Open-source video editors. Someone’s incredibly detailed home-brewing app with no monetization plan whatsoever. Artists making interactive experiences because they wanted to see if they could. These things exist because someone cared more about making the thing than making money from the thing. I think that ratio is about to shift dramatically in favor of the people who just want to make something good.

I’m not saying we should all stop paying for Salesforce (we should probably keep paying for Salesforce, there’s a reason that thing costs what it costs). I’m saying the category of software that was previously not worth building because it wasn’t commercial enough to justify the cost, that category just got a lot more interesting.

What’s in that category? Things like:

  • An app that helps beginning judo students understand the concepts behind a throw, not just the mechanics, because judo is where I learned confidence and discipline and I want other kids to find that
  • A private family memory vault (not Instagram, not Facebook, not anything with an algorithm deciding what matters), just a place where the people who love my son can send photos and stories somewhere safe, for him to open when he’s older (Maybe I’ll turn this into something?)
  • A system that reminds companies to send their employees gifts on the days that actually matter to them, because I know from running a company that it fills the cup of the person giving just as much as the person receiving (Thankscrate, if you’re curious, and yes, that one is turning into something real, but that is genuinely not why I built it)

None of those were commercial ideas first. They were just things I cared about.

I think the most interesting software that gets built in the next few years won’t come from developers moving faster. It’ll come from people who previously had no path from “I care about this” to “I built something about this,” and now they do. Parents. Coaches. Teachers. The person in your office who could explain that one complicated process better than anyone and has always secretly wanted to turn it into something.

The stakes are low. The bar to launch is low. The cost is low. The only thing required is that you actually give a damn about what you’re building.

So… What do you give a damn about?

Go build it. I still sometimes have to count on my fingers, but I’m told the app helps.