Running an offsite is one of those things that sounds straightforward until you actually try to do it. Then you realize it’s more like attempting to teach a cat how to swim.. like, it’s possible, but the trial and error is going to leave you with scars and trauma for you and the cat. The truth is, I didn’t learn how to run these from some leadership book. In fact, there aren’t many practical resources out there on this topic. Zack Urlocker (famous to me from MySQL) has a great article on the subject, and the HBR book “How to Plan a Team Offsite That Actually Works” is pretty good, and I’ve read and can partly “Retreats That Work“. But compared to other tactical or strategic business topics, there is suprisingly little stuff out there on how to plan and run what I think is one of the most important processes in a functioning executive team. So most of what I know has been pieced together by experimenting, failing, adjusting, and occasionally stumbling onto something that worked.

Over the years, I’ve realized that the best offsites aren’t just about staring at spreadsheets in a new zip code. They need to hit a few big goals if they’re going to be worth all the planning headaches.

  1. First, they give us strategic focus. It’s the one time everyone can step out of the chaos of Slack notifications and email fires and actually think about the future of the company. No one is allowed to answer a support ticket from a kayak.
  2. Second, they create leadership alignment. If you’ve ever tried to get a group of executives pointing in the same direction, you know it’s a bit like herding caffeinated cats (second cat reference already). Offsites are where we stop doing the daily functional stuff and agree on what we’re actually chasing this quarter or even the year.
  3. And finally, they build team cohesion. This doesn’t mean trust falls or awkward icebreakers where you have to say your “spirit animal.” It means real connection. Cooking dinner together, laughing at terrible pickleball form, or having spouses bond over yoga and day drinking. That’s the glue that makes the work stick.

Strategy and alignment and synergy and other business words are important. But if you don’t also have a little fun, then honestly, what’s the point?

Who Gets Invited?

One of the first questions people ask me is who actually gets to come. The answer is simple: just the people who report directly to me. That means my VPs and my C-levels. Keeping the group small matters. Too many people and it stops being a strategy session and starts to feel like you’re at an HOA meeting with whiskey. That’s actually the only way I would attend an HOA meeting, but that’s besides the point.

The Rhythm of Our Offsites

Over time, we’ve settled into a pattern that works for us.

  • We hold one-day offsites each quarter, right at the beginning of the quarter, to reset and align.
  • At the beginning of Q4, we host a three-day offsite. This one is much more involved, both in planning and in structure.

That Q4 gathering has become the cornerstone of our leadership rhythm. It’s where we not only map out the next year but also strengthen the relationships that help us make better decisions together.

The Big Airbnb Weekend

An example AirBNB we’ll rent

The three-day offsite is a little different. Actually, a lot different. Instead of cramming into a conference room for eight hours, we rent a big Airbnb within driving distance. It has to have something that makes it feel special. Maybe it’s a weird swimming pool, a pickleball court, a river with kayaks, or a beach nearby. Basically, something that makes it feel less like a board meeting and more like an executive retreat with paddleboarding skills designed to test our key-person insurance. A lot of these places are pretty weird. Getting a place where 5 couples can comfortably stay in a single house means either super luxurious mansions, or strange homes that have winding corridors, mapping our the evolutionary path of the renovations that made it a desirable property for events like ours.

We also come prepared. That means swimsuits, a fully stocked bar, and a Nintendo Switch for late-night Mario Kart battles. For the record, those races have only ended in tears two or three times, which I consider an acceptable casualty rate.

Spouses and partners join us for the whole weekend, from Friday through Sunday. Friday night we cook a big meal together. Saturday night we all go out to dinner. In between, the partners, who jokingly call themselves “the tech wives” even though the group definitely includes men, do their own thing. They go to yoga, they day drink, they sometimes prepare lunch for us, and in return we make sure to take them out for dinners. They get a vacation, and we get the benefit of stronger connections across the group.

A Tech Wife Grilling

It might sound unusual to mix work and family life, but it has been incredibly useful. When the people at home know and trust the people at work, it changes the dynamic completely. It creates more openness, more support, and a lot more resilience when things inevitably get tough.

Timing Is Everything

When you schedule an offsite matters almost as much as where you hold it. For example, I’ve found the sweet spot for our first offsite of the year is the third week of January.

  • If you schedule it the first week of January, no one is really in the office yet. Everyone is still half in vacation mode.
  • If you push it to the last week of January, the new year’s energy has already started to fade.

So the third week is usually just right.

For our one-day offsites, I like Mondays. That’s already the day we hold our management meetings, which means I have two hours of my executives’ time on the calendar anyway. It’s easier to rearrange schedules if we’re already starting from that block.

The Q4 offsite follows a set pattern too. We begin Friday morning at 9 a.m. and wrap up Sunday afternoon. Since we usually rent the Airbnb through Monday, people often stick around a little longer. Sometimes kids show up and end up swimming in the pool or playing pickleball, which is honestly a pretty great way to close things out.

Wrapping Up Part 1

That’s the foundation: who comes, when we meet, and how we structure the year. These basics took a few years of trial and error to figure out, but once we found the rhythm, it became much easier to plan and run these without burning out.

In Part 2, I’ll share what actually happens inside the offsite, including how I structure agendas, the kinds of exercises we run, and why you should never try to build your offsite plan in a Word document.

There is now a Part 2!

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.