DUNDERBLIXEM
Menu

Most AI spending speeds up the wrong work.

We help find what's actually holding your business back, then equip your people to fix it.

Bring us to your retreat Get the free playbook

The problem

Everyone's investing in AI, but few are actually seeing a return.

Too much AI deployment is aimed at things that aren't the real bottleneck for the business.

If you speed up the wrong thing, you get busier but not more profitable.

That's a recipe for tools that don't get used, or worse, unhappy employees who either actively try to sabotage the project or just quit.

A word on team building

“Great, more forced team building.”

Listen, we get it. One of the reasons why we built this is because of how bad most team-building exercises are.

There is nothing worse than being stuck in a room full of people pretending to have fun when you know that there is important work that you could be getting done. It's enough to make you want to rip your hair out. It's enough to make you dread the calendar hold for weeks.

We've been there. We have been stuck in that mental loop of ruminating on how frustrating it is that the team just put that retreat on the schedule.

Before you discount what we're saying here, just take a moment and consider: what if it were done well?

Done well, every exercise produces something your team will use the next week, and the problems on the wall are the real ones, written by the people who live with them. If your team would do better with a plain working session, that's how we'll run it.

How we run retreats

What we do differently

01

Constraint first, tools second.

Don't get sold on a specific deployment unless you know it's what's actually limiting your business. We help you find where investments will really pay off.

02

The answers come from your people.

They already know where work gets stuck. We know how to get it out of them.

03

People-first, on purpose.

We don't take projects that are only about cutting payroll. AI should make your people better, not get rid of them.

Our method

Pattern Interrupt

Our job is to help you and your people generate fresh insights and execute on them as effectively as possible.

It's inevitable: the people in a business get stuck viewing it a certain way, and blind spots develop.

A pattern interrupt is purposefully generating a fresh perspective. That leads to more effective problem solving and execution. That's what our methods are built to provide, whether you're doing it yourself with your team or we're organizing an entire retreat around it.

Aim

See what's really going on.

  1. Step 1GoalWhat are we actually trying to achieve? And what happens if it works?
  2. Step 2GroundWhat's the actual daily work? Watch it and check the data.
  3. Step 3WallGet everything that's going wrong out of heads and onto the wall.
  4. Step 4Root causesMap how it all connects and find the root causes.

Strike

Act on it, with your people.

  1. Step 5RoadmapBuild an action plan that maps what needs to be done to go from your current reality to the way you want things to be.
  2. Step 6PeopleEngage the people who will do the work, both internally and externally as needed.
  3. Step 7DeployMake the changes, starting with what matters most. Delete steps before you automate them.
  4. Step 8CheckCheck results continuously, starting at about two weeks, then at one, two, and three months.
  5. Step 9AdaptAdjust as you learn, then go after the next problem.
More on the pattern interrupt

How to work with us

We meet people where they're at. There's a range of ways we can help you, from doing it on your own to building a whole retreat around it.

Start here · Free

On your own

Are you or someone on your team excited about doing this and want to lead it yourself? Here's material that can help.

  • The Pattern Interrupt Playbook. Our full 9-step process, free. Print it, or hand it to an AI.
  • A small guided group. $497 a seat, before the new year. See the topics
Start on your own

We lead it with your team

2-week implementation sprint

Two weeks working with your team toward a specific outcome we design together.

  • Sessions and work throughout
  • Recommended At least one day on site
  • Starts with a 20-minute call

From $10,000

See the schedule

Most effective

Built around your retreat

An engagement with the retreat at the center.

  1. Before the retreatat least 1 month
  2. At the retreaton site
  3. After the retreatat least 3 months

Starting at $25,000

Plan your retreat with us

One day · $5,000

Want to start with one day?

A day with your team on how to think about AI in your business, and how to get your people on board. Book a 20-minute call and we'll go over what the day would look like for you.

Book a 20-minute call

This works at any size. An individual, a team of one, a small team, or a whole company. If you're small but still want to work with us, we're happy to.

* We also speak at events. If you need help motivating your people, getting them to think differently, and giving them ideas they can take action on, we'd be happy to talk at your event.

Free

The Pattern Interrupt Playbook

The 9-step process for finding what's really holding your business back, getting your people engaged with fixing it, and making sure you don't waste money on AI.

This is the method we use when we lead a team through it. We give the process away and charge for being the neutral outsider in the room.

You don't have to take on all nine steps at once. Hand it to an AI and it walks you through one at a time.

Inside

  1. 01Nine steps in order. Each one has how to run it, a worksheet, and a list to check yourself against.
  2. 02Steps 1 to 4: set your goals, see how the work really gets done, get every problem out in the open, and trace them back to root causes.
  3. 03Steps 5 to 9: build the roadmap, get your people behind it, make the change, check the numbers, and adapt.
  4. 04A plain guide to what AI is: the forms it comes in, what it's good at, and where the risks are.
  5. 05Two ways to use it. Print it, or hand it to an AI that walks you through one step at a time.
  6. 06Useful even if you never add AI.

Questions people actually ask

Where do we start?

Start with what you're trying to achieve, not with a tool. Get specific: what would be meaningfully better six months from now, and what number would show it? If nobody can name that number, it's too early to buy anything.

Next, look at how the work actually gets done today. It's often different from how leaders think it gets done, so ask the people doing it. Write down everything that's going wrong, then look for the few root causes behind most of it.

Only then ask where AI fits. Sometimes it's the answer. Often the first fix is simpler: a deleted step, a clearer handoff, or an owner for something nobody owned. Pick one workflow, make the change, measure it for a month, and let that result decide what comes next.

Do we have to play games?

No. Some teams love them, and some people dread them. Both can be right. A change can fail because nobody got people talking honestly with each other. A day of exercises can also get in the way of work that someone already knows needs doing.

We use a game when it produces something your team needs, like a map of what's going wrong. If your team would do better with a plain working session, we'll run it that way. The one thing we always keep is hearing from the people who do the work.

Do we have to fix our data first?

It depends, and it's worth getting right.

You don't need perfect data across the whole business before you start. Trying to clean everything first is one of the most common ways AI projects stall for a year. What you need is trustworthy data for the first thing you're trying to improve. A small, clean, well-understood set of data usually beats a huge messy one.

Trustworthy means more than tidy. A few questions to ask about the data your first change will touch:

  • Does it mean what you think it means? "Closed" might mean won in one system and gave up in another. Definitions that drift between teams quietly break everything built on top of them.
  • Which version is the real one? Ask three people where the authoritative customer list lives. If you get three answers, that's the first problem to solve.
  • Does it reflect what actually happens? If half the team works around the system, the system records the workaround, not the work.
  • Is it complete and current? Gaps and stale records look fine until something acts on them.
  • How does it come in? A lot of so-called AI errors are really intake problems: free-text boxes, missing required fields, and three different date formats.
  • Who owns it? Every set of data an AI system depends on needs a named person who keeps it right.

AI makes data problems louder, not quieter. A person notices when a number looks off. An automated system acts on it, at scale, with confidence. So check the data your first change depends on, fix how it comes in, write down what each field means, and keep a person reviewing results until you trust them.

Getting your data in order is part of the work, not a gate you have to pass before you can begin.

What happens to our people?

Start with them. People who help shape a change tend to use it. People who have a change done to them tend to work around it, sabotage it, or leave.

Much of the resistance to AI isn't really about the technology. It's about relevance, identity, and job security, and it deserves an honest conversation, not a pep talk. In practice that means:

  • Talk to the people who do the work before deciding anything.
  • Be straight about what the change means for their jobs.
  • Decide ahead of time what happens to the time it frees up.
  • Find the people who are already excited, and let them lead and teach others.

If a plan only works by cutting people, we're not the right fit. We don't take projects that are only about replacing people or cutting payroll.

Can't we just do this ourselves?

Often, yes, especially if you have someone who cares about this and has the time to lead it. That's why the playbook is free. It's the same nine steps we lead teams through.

What's hard to do alone is see your own blind spots. Inside a business, everyone's view is shaped by the daily firefight, and rank changes what people are willing to say in the room. An outside facilitator's job isn't to hand you answers. It's to create the conditions for honest input and fresh perspective, and to keep the process moving when it would otherwise stall.

If you try it yourself and get stuck, that's a good moment to bring someone in.

What happens if it works?

Ask this before you start, not after. Three questions:

  • Who runs it day to day?
  • Who improves it when it breaks or the business changes?
  • What does your team do with the time it gives back?

Hours saved only count if they go somewhere: more customers served, faster turnaround, work that kept getting dropped, or simply less overtime and stress. If nobody decides, the time tends to disappear into more busywork, and the return never shows up.

Plan for how the work itself changes, too: what people stop doing, what they start doing, and how you'll support them through it.

Do you build the AI too?

Sometimes. A lot of AI deployment can and should be led by your own team, especially once the right people are equipped. Some of it needs a little outside help.

Bigger or more involved deployments, especially ones that touch sensitive data, compliance, or core systems, may require pulling in additional implementation experts. We can help with that if and when it's needed, including finding the right people and working alongside them.

How do we vet an AI consultant, including you?

A few questions go a long way:

  • Can they show you something they built that's running today, and can you talk to that customer?
  • What will they ask your people, and can they explain their recommendations out loud, not just in a document?
  • What exactly will their discovery or audit produce, and how does it get you closer to a result?
  • How will success be measured, and who owns the result after they leave?
  • Will you own everything they build, including the prompts, settings, and code, or will you need them for every change?
  • What happened on a project that didn't go well?

Be wary of quick audits that conclude you need exactly what they sell, and of roadmaps that came straight out of a chatbot. Ask us every one of these questions too.

Is this only for big companies?

No. It works at any size: an individual, a team of one, a small team, or a whole company.

Smaller teams often move faster, because there are fewer handoffs and less politics. The size of the engagement changes. The thinking doesn't.

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

Bring us inOr lead it yourself. Get the playbook.