The Three Stories Every Change Program Needs

Every change program runs on three stories, and companies usually publish only the first one. The other two get improvised in meeting rooms by people who were handed a strategy deck and asked to make it real.

Fernando Palacios founded Storytellers in 2006, the first storytelling company in Brazil. For Libbs in 2014, the team built Plenance, a fictional brand universe created around a cholesterol treatment and documented in a storybook catalogued as version 16, the kind of record it takes to keep a world consistent across everyone who has to use it.

The Story Most Companies Write

The first story is the corporate one: why the company is changing, what the market did, where the organization is going. It gets written well, presented at a town hall, and posted on the intranet, and it is the only one most programs ever produce.

It fails alone for a structural reason. The corporate story is told from the altitude of the executive team, and its protagonist is the organization. A person in a regional office can agree with every word of it and still have no idea what to do differently on Tuesday.

So two other stories get invented on the spot. A team leader improvises one to explain the change to six people, and each individual builds a private one about what this means for their own career. Both circulate faster than the official version.

The Direct Answer: Three Stories, Three Protagonists

Write all three deliberately, with the same obstacle at the center and a different protagonist in each. The company story has the organization as protagonist and the market as obstacle. The team story has the team as protagonist and the daily routine as obstacle. The personal story has the individual as protagonist and their own habit as obstacle.

The three have to agree on the facts and differ in scale. When they agree, an employee can climb from their own situation up to the company's logic and back down, which is the movement that makes a change program feel coherent.

The second and third stories are the ones that decide the outcome, because they are the ones told most often. The full architecture for programs built this way sits in storytelling for change management.

How the Palacios Method Keeps the Three in Sync

The Palacios Method runs on Narrative Intelligence and Strategic Entertainment, with the 8 Steps as its working engine. The 8 Steps hold at every scale: what the protagonist wants, what stands in the way, what changes, what it costs, what happens next. Running the same sequence three times with three protagonists produces three stories that fit together by construction.

Strategic Entertainment covers what keeps each version alive in the retelling. Tension, character and stakes get drawn from the level being addressed, so the team story uses the team's real week and the personal story uses a decision the individual actually faces.

The Plenance work shows the discipline behind consistency. A fictional universe built around a treatment and written down in a versioned storybook means everyone who touched the material worked from the same world, with the same rules. A change program needs that same single source, in plainer form. The full architecture sits in the method.

Writing the Three Stories

1. The company story. Protagonist: the organization. Write what the market did, what it costs to keep operating the current way, and what the company is now committing to. Keep it to a page, and put a date and a number in it so it can be checked later.

2. The team story. Protagonist: a specific team. Written by the team leader, using the same obstacle translated into their week: which meeting changes, which handoff disappears, which decision moves closer to them. This is the version that runs most often, so it deserves the most support.

3. The personal story. Protagonist: one person. What this individual will be able to do a year from now that they cannot do today, and what they have to give up to get there. Managers deliver this one in conversations, which means the program has to prepare them for it.

Programs that stop after the first version leave the other two to chance. The mechanics of putting story to work across a transformation are in how to use story in change management.

Frequently Asked Questions

Who Writes the Team and Personal Versions?

Team leaders and managers write them, and the program gives them the obstacle, the structure and two worked examples. Centrally written team stories arrive in the wrong vocabulary and get read aloud with visible distance, which does more damage than a rough version in the leader's own words.

What if the Three Stories Contradict Each Other?

Treat that as the most useful signal the program will get. A contradiction means the change costs something at team or personal level that the corporate version never admitted, and the fix belongs in the corporate story, where the cost gets named out loud.

Your Next Step

Take your current change program and check which of the three stories exists in writing. If only the first one does, ask two team leaders to draft their version this week and read them side by side against the company story. The gaps between the three are your implementation risk, listed in advance. The way these stories travel across the company is covered in internal communications.

To build the three stories with the method, explore the services or get in touch with Fernando Palacios.

A calibrated method built from 20 years of real rooms, real audiences, and real results. The Palacios Method stack ensures the narrative lands. Not vibe typing. VibeStorytelling.