DUNDERBLIXEM
Menu

Most effective

Planning a retreat? Bring us in.

We'll make your next retreat more fun and a lot more useful.

Tell us about your retreatSee how it works

About a month of groundwork before, the retreat itself, and about three months after. Starting at [PRICE].

Photo placeholder

Your team, away from the office. Real, not stock.

Why a retreat

Time away from the office is the best pattern interrupt there is.

People think differently when they're out of the daily firefight. We use that time to do the work most teams never get to.

The retreat is the center of it, not the whole thing. A month of groundwork before means nobody walks in cold. Three months after means it doesn't fade by Monday.

How it works

Before, at, and after the retreat

This is an example of how it can look. Keep in mind it's flexible and can be customized for each organization, including more or less time at the retreat itself and more or less time after the retreat on the actual implementation.

Example: about 1 month

Before the retreat

  • Scope callWhat triggered this, what the retreat has to produce, who's in the room, and what happens if it works.
  • ListeningConfidential conversations across levels, frontline included.
  • Survey and numbersA short team survey, and the numbers that matter.
  • GroundWe watch the work and check the data.
  • Build the game lineupEvery lineup is custom, built around your goal. See examples

Example: two days

At the retreat

  • Day 1 morning · GoalWhat we're trying to achieve, and what's already working.
  • Day 1 afternoon · The WallEverything going wrong, out of heads and onto the wall.
  • Day 1 eveningOff the clock. Something fun. (?)
  • Day 2 morning · Root causesMap how it all connects.
  • Day 2 afternoon · Action planAn action plan from your current reality to the way you want things to be, with an owner for every step.

Example: about 3 months

After the retreat

  • Bring everyone else inEngage the people who weren't in the room.
  • DeployDelete steps before you automate them, then the first changes go live.
  • Check resultsAt day 30, 60, and 90.
  • Working sessionsRegular check-ins, remote or on site. (?)
  • AdaptAdjust as you learn, then go after the next problem.

Draft agenda (?). Dylan to adjust.

The game lineup

Fun, and insightful.

Every lineup is custom. Examples of games that can be both fun and insightful include these.

01

Follow the Work (?)

Pick one real item, like an order, a quote or a new hire, and walk it through every person who touches it. Where it waits is where the problems are.

02

The Ten Most Boring Tasks (?)

Everyone lists the ten most boring things they do each week. It's funny, it's honest, and it shows where the hours are hiding.

03

Delete, Code, Agent, or Person (?)

Every step of a process goes on a card. The team sorts each one: delete it, automate it with simple code, hand it to an agent, or keep it with a person.

What you walk away with

  1. 01The root causes, named and agreed by the people who live with them.
  2. 02A map of what's really going on: the Wall and the reality tree.
  3. 03An action plan that maps how to get from your current reality to the way you want things to be.
  4. 04Check-ins at day 30 and day 90, and a team that had fun getting there.

In person, or we come to you.

In person is best. If you don't want to take everybody somewhere, we'll come to your office. Remote teams get the same work, run online.

Starting at [PRICE]

Tell us about your retreatNot holding a retreat? See the 2-week sprint

Let's find what's really holding you back.

Bring us in