Your team is already living a story.
Bad Story helps teams surface the interpretations, patterns, and relational loops shaping how they work together - and practice a different way forward.
The thing on the agenda is rarely the thing in the room.
Teams arrive at an offsite with a stated problem: alignment, communication, a strategy that isn't landing, a team that's grown too fast. Those problems are real. They're also usually downstream.
Underneath them is a layer nobody scheduled. What people have concluded about each other. What the last two years taught them to expect. Which risks are worth taking. Whose voice actually counts. What happens to a person who says the difficult thing out loud.
That layer is running whether or not anyone names it. Bad Story names it.
A bad story usually isn't a false one.
It may be incomplete. Outdated. Overgeneralized. Formed under pressure, or built from one painful experience that has not been revisited since. It may have been completely accurate at the time and simply stopped being accurate.
A bad story is one that has gained enough authority to shape behavior without being examined.
The work isn't correcting anyone's thinking. It's noticing when an interpretation quietly became a fact.
Where it comes from changes what to do about it.
Story Within
Formation
The stories each person carries in: history, identity, assumptions, fear, habit, expectation, the strengths that have worked before and the ones that stopped working. Most of it operates below the level of a decision.
What am I bringing to this moment that's shaping what I think it means?
Story Between
Relationship
What two people have taught each other to expect. Trust, conflict, repair, belonging, status, and the accumulated record of how it has gone before.
What have we taught each other to expect from this relationship?
Story Around
Culture
What the environment has taught people to expect. Leadership behavior, systems, rituals, what gets rewarded and what quietly gets punished, and everything the organization has already demonstrated.
What has this place taught us to expect?
The story creates the evidence that proves the story.
A loop is what happens when an interpretation shapes behavior, and that behavior produces exactly the evidence that confirms the original interpretation. It isn't anyone's fault, and it's remarkably hard to see from the inside, because every step in it feels reasonable.
The one that costs you
- Leadership asks for feedback.
- The room stays quiet.
- Silence is read as agreement.
- The decision goes ahead.
- The team concludes the question was never real.
- Fewer people speak next time.
The one that compounds
- Someone admits a mistake.
- The leader responds with curiosity.
- The team learns mistakes are survivable.
- More people say the hard thing early.
- Problems surface before they are expensive.
- Trust compounds.
The goal isn't to escape loops. It's to know which one you're building.
Two to three days, built around your team.
Before anyone arrives, we learn the story. We talk with leaders. We talk with the team. We come to understand the tensions, transitions and opportunities shaping this particular moment. Only then do we design the days.
Facilitated sessions and unfacilitated hours. Conversations that don't happen on a normal Tuesday. Time outdoors. Shared meals that aren't a break from the work. Individual reflection alongside the group work. Evenings that matter as much as the mornings. Lodging, venue, food and pacing handled, so the team's only job is to be present.
Don't give us a slot on your agenda. Give us the agenda.
We aren't trying to fill every minute. We're trying to create the conditions for conversations that are difficult to have inside the normal rhythm of work.
Some conversations don't happen inside the room that created them.
Distance changes what you can see.
Teams spend most of their time inside the environment that produced their current patterns. The same rooms, the same threads, the same pressures, the same hour between two other meetings. Sometimes a team has to physically leave the story it is living in long enough to notice it.
Bad Story is most useful when the old story no longer explains the new reality.
- A leadership team has recently formed, or recently changed shape
- The organization is growing faster than its habits
- A strategy shift isn't landing the way it was intended
- Trust has been strained and nobody has said so directly
- A difficult season ended but the residue didn't
- A strong team wants to be deliberate rather than lucky
You don't need to be dysfunctional to need a different conversation.
How much of your team’s actual story is making it into the room?
Every leadership team runs on interpretations as much as facts. The Storied Team Diagnostic is a short reflection on where your team’s story is rich, and where it may be getting thin.
Awareness isn't the deliverable.
- A named story the team can talk about without it detonating
- Language for where a story is coming from - within, between, or around
- One loop mapped honestly, including each person's part in it
- A set of next signals: specific things people will do differently, with names on them
- A shared reference point that outlives the offsite by more than a week
Tell us what your team is navigating.
No pitch deck and no discovery funnel. A short conversation about what's actually happening, after which we'll tell you honestly whether this is the right thing - including when it isn't.