Here is the context. The average knowledge worker sits in 23 hours of meetings per week. More than half of those meetings are considered unproductive by the people who attend them. The number one complaint is not that there were too many people, or too many slides, or even too much pad thai. It's that nobody knew what the meeting was for.
That's not a scheduling problem. That's a story problem.
Meetings don't fail because of the people in the room. They fail because of the story that isn't.
Which brings us to Dave. Dave is smart. Dave is present. Dave has a standing desk and a Moleskine that has never once held a useful next action. Dave designs things — mostly his own suffering — and has attended the same meeting in different conference rooms for most of his professional life. You know Dave. You may, on certain Tuesdays, be Dave.
The Four Anti-C's: What Actually Happens
Before we give Dave the tools, let's name what actually happened in that room. Four things, in sequence, like clockwork. Dave didn't cause them. Nobody did. They're what naturally emerges when you gather humans without a story to hold them.
- Chaos. Nobody agreed on what the meeting was actually about. The agenda said "alignment." Three people thought it was a status update. Two thought it was a decision. One thought it was optional. (It was not optional, Craig.)
- Confusion. Context was assumed, not established. Half the room didn't have the background. The other half had the wrong one. Everyone was nodding at different things with equal conviction.
- Coercion. Without a shared story, the loudest voice wins — not the best idea, but the most forceful delivery. The meeting became a power map. Despair took notes.
- Capitulation. By minute forty, Dave agreed to whatever would end it. Not because it was right. Because it was over. Consensus by exhaustion is still consensus on paper. It just doesn't hold past the parking lot.
Every Chaos is a missing Core. Every Confusion is a missing Context. Every Coercion is a missing shared Conflict. Every Capitulation is what you get instead of Collaborate. Which brings us to the framework — and why Context comes first.
The 4C Framework: Four Moves, Starting With Context
The 4C Framework is storylab's distillation of 3,000 years of narrative structure — Context, Core, Conflict, Collaborate. Every story that works, works because it orients before it activates. It sets the scene before it raises the stakes. It answers where are we before it asks where are we going together.
Which is why Context is not the third move. It's the first thing anyone in the room actually needs.
What does everyone need to know?
Context is the shared reality — the full picture that lets people orient before they're asked to act. It's the history, the stakes, the gap between what we said and what actually happened. Context kills assumptions before they kill the meeting.
What are we actually protecting?
The core is the theme beneath the agenda — not the project name, but the essential truth underneath it. Why does this meeting exist? What is the dream, the hope, the thing worth showing up for?
What breaks if we don't decide?
Conflict isn't the villain — it's the tension that makes the story worth telling. What's the gap between where we are and where we need to be? What is actually at stake? Without stakes, there's no urgency. Without urgency, nobody decides anything.
What is our shared story going forward?
Collaborate is the activation — not just a decision, but a shared commitment to what comes next. Who owns what? What's the accountability we carry out of this room? What story are we co-authoring together from here?
Then ask: what's our shared story forward?
How Dave's Meeting Could Have Gone
Same room. Same leftover pad thai smell. Same twelve people with the same unspoken questions. Four sentences — in the right order — and it's a completely different story.
Context: "Here's what led to this: the timeline, the signals we missed, the gap between what we promised and what actually happened with the Morrow account." Now everyone is in the same story. The meeting has shared ground.
Core: "We're here because we almost lost that account and we need to decide how we prevent the next one." Now everyone knows what they're protecting. The meeting has a heart.
Conflict: "If we leave without a decision today, three more accounts are in the same risk window." Now there are stakes. The meeting has a spine.
Collaborate: "One decision, one owner, one deadline — and we're writing that story together right now. Who's in? What do we each carry out of this room?" Now there's shared accountability. The meeting doesn't just end — it becomes the beginning of something everyone co-owns.
That's not a script. That's a story structure. Four sentences that replace forty-seven minutes of Chaos, Confusion, Coercion, and Capitulation with something that actually moves an organization forward. Even Despair would have had a better day.
Before your next meeting, write four sentences — in this order. Context: what does everyone need to know before we can decide anything? Core: what are we actually here to protect? Conflict: what breaks if we don't resolve this today? Collaborate: what is our shared story going forward — who owns what, and what accountability do we each carry out of this room?
You don't need a facilitator. You don't need a retreat. You need four sentences and the courage to say them out loud before the pad thai arrives.
The 4C Framework is one of storylab's core narrative design tools — taught at Parsons, used in the field, and given away here.
See all the storylab frameworks →