Story 10x Summary: Explain Change People Can See and Assess

Key Ideas

1. Give the audience a context that makes the proposal understandable

Margolis’s first step is See It: Context for Change. His exercises ask readers to examine technological, economic and cultural forces. For a practical work conversation, the task is to identify the relevant change in circumstances before explaining your preferred response. A list of impressive trends will not help if the listener cannot connect them with the decision in front of them.

In the original theatre case, Mina begins by showing how the rehearsal timetable has changed. Three groups now share equipment on overlapping evenings, while the booking process still depends on separate messages. This account gives the audience a reason to examine coordination. It does not require portraying the previous system as foolish; that system may have suited a simpler timetable. The proposal becomes a response to a describable situation rather than a judgment about the people who built the old arrangement.

Before pitching your idea, write a short account of what changed, who encounters it and what can now be attempted. Check whether the audience accepts that account. This matters because a disputed premise will remain disputed even after you add more detail about your solution. If a group says the timetable is not the main source of clashes, ask for the examples behind that view. Revise the context when the evidence warrants it. A shared starting point is something you establish through an accurate conversation, not an opening paragraph that obliges everyone to accept your interpretation.

2. Make the human dilemma specific enough to recognize

Feel It: Emotional Dilemma is the second step in Margolis’s sequence. The author exercises direct attention to what a character wants and what gets in the way. This guide applies the idea by examining a choice from the affected person’s perspective. The aim is to make the stakes intelligible without deciding in advance how everyone must feel about them.

Mina’s practice story follows a stage manager who needs a projector for an evening rehearsal. A private message suggests it is available, but another group may be using it. The manager wants to confirm the rehearsal plan without appearing to demand priority over colleagues. This is more useful than describing the audience as people who dislike technology. The difficulty includes relationships and uncertainty about authority, which a calendar feature alone may not resolve.

For your proposal, select one ordinary moment where the problem is experienced. Describe the person’s objective, the conflicting considerations and the question they cannot answer. If the account concerns a real person, ask them to correct it. This matters because empathy becomes thin when the presenter supplies a convenient motive for everyone else. Someone might value the existing flexibility for reasons your solution overlooks. Include that information in the design conversation. Avoid turning the case into an invented claim about customer behavior. A clearly labeled hypothetical scene can help explain a possibility, while a real account needs confirmation before it is used as evidence for how people actually work.

3. Match each piece of evidence to the claim it can support

Believe It: Evidence of Truth brings support into Margolis’s narrative sequence. His exercises list several possible sources, including user research, demonstrations and pilot projects. This guide adds a practical discipline: state what each item establishes and what it leaves open. An illustration of a feature, evidence of a problem and evidence of an outcome answer different questions.

In the fictional example, Mina can show a record of booking clashes to establish that the coordination problem occurs. A demonstration can show that the proposed calendar records a reservation and displays availability. Neither item proves that every theatre group will keep the calendar current. A trial with real users can examine that question, provided the team agrees what to observe and records the work involved in maintaining it.

Write the important claims in your pitch and place the relevant evidence beside each one. Mark a forecast as a forecast and a demonstration as a demonstration. This matters because a coherent narrative can encourage listeners to supply a stronger conclusion than the material supports. Make the boundary explicit before requesting a decision. If the evidence is incomplete, ask what limited experiment would be justified now and what result would argue against continuing. Good support can include an inconvenient finding. A credible story of progress should remain capable of changing when a test disappoints, rather than turning every outcome into further proof that the original vision was inevitable.

4. Explain change without assigning the audience an embarrassing role

In the author interview, Margolis describes how a new story can make people invested in an existing one feel judged. His own public note about the book emphasizes reducing resistance rather than casting a conventional morality tale. The application here is to examine the roles your wording gives the audience. An explanation can accidentally make agreement sound like an admission of past incompetence.

Mina’s first draft describes a move from chaotic amateurs to professional scheduling. That phrase insults people who maintained workable arrangements with limited resources. She revises it to describe the increased overlap between productions and the new coordination it requires. The revision can still state the problem clearly. It simply stops claiming that the people who used the earlier process are the source of everything wrong.

Look for adjectives that divide your proposal into enlightened supporters and difficult opponents. Replace those labels with the observable situation and the concern being expressed. This matters because an audience may have useful reasons for caution that disappear when framed as resistance. A group protecting access for last-minute rehearsals is raising a design requirement, not necessarily refusing all change. Do not pretend every disagreement is a wording problem, either. Costs, authority and priorities may remain contested after the story is improved. Ask what is actually in dispute and address that issue. Respectful framing creates room to examine a disagreement; it does not remove the need to resolve it.

5. Invite participation in a future whose work is still unfinished

Margolis’s interview describes inviting people into an unfolding journey rather than presenting a conclusion that leaves them no role. This is useful for a change proposal because approval is only one part of the work. The people affected may need to supply missing knowledge, negotiate a responsibility or test an assumption. A future-facing story becomes more credible when those contributions are visible.

Mina closes the fictional proposal by asking two groups to help test the calendar during a limited period. The trial will examine whether bookings remain current, what happens to informal equipment swaps and who resolves a conflict. She distinguishes what she is requesting today from what would require a later decision. The audience can contribute to the next chapter without endorsing every feature or accepting a prediction about final results.

End your pitch by naming the decision you need, the work it authorizes and the questions still open. Ask who needs a role in answering them. This matters because a stirring account of the future can conceal a very ordinary disagreement about who will do the extra work. A specific invitation also allows someone to decline or propose another test. Keep that choice meaningful. If the decision is already final, explain the remaining implementation questions honestly instead of performing consultation. Treat the response as information about both the story and the proposal. A skeptical audience member who identifies a missing condition may help make the plan more viable, even if their contribution interrupts a perfectly polished ending.