Winning Without Persuading Summary: Esther Choy on Story Discovery

Key Ideas

1. Pursue the task while leaving room to change your understanding

Choy's T² principle connects an immediate transaction with a broader transformation. The distinction matters because an interaction can appear efficient while leaving everyone with the same mistaken picture. A leader may obtain a quick yes and still have learned nothing about whether the work can be done.

Our fictional case concerns Anika, who leads a service-design team, and Mateo, who handles customer handovers. Anika wants agreement on a new handover process by Friday. That deadline is legitimate. It does not establish that the process she has drafted solves the right problem. Her opening should make both the decision and the room for input clear.

For this guide's application, she writes two questions before the meeting. What must be settled today? What could another person's experience teach me that would alter my proposal? The first prevents a conversation from drifting away from its purpose. The second prevents the purpose from becoming an excuse to ignore new information.

Anika also identifies what she cannot offer. The team cannot change a contractual requirement during this discussion. It can decide when to collect the information needed to meet that requirement. Naming the distinction makes participation more honest. The desired result is neither an open-ended conversation nor automatic acceptance of the draft. It is a workable decision made with a better understanding of the situation. Changed understanding may be modest; the framework should not encourage claims of profound transformation after an ordinary meeting.

2. Invite an account of experience rather than another abstract opinion

Story discovery gives a conversation something more specific to examine than a contest between confident conclusions. A person's account of what happened can reveal a sequence, a constraint or a turning point that a broad judgment conceals. It remains an account to understand and, where necessary, check.

Mateo says the proposed handover will create more rework. Anika initially hears resistance to change. In our example, she asks him to describe a recent handover that became difficult and the point where the process stopped helping. The question concerns work he knows; it does not demand a personal disclosure or imply that he must entertain the room.

His answer might reveal that a client decision regularly arrives after the internal deadline for recording it. Anika can ask which information was available, what happened next and whether the same pattern occurred elsewhere. She should avoid adding the cause before Mateo has explained it. A vivid incident can identify a useful question without establishing the frequency of the problem.

Choy's comments on question design in Clare McDermott's Content Marketing Institute article show how a more thoughtfully framed invitation can draw out an important obstacle. Our workplace question follows that broad principle without reproducing a book exercise. Ask for enough detail to understand the work, then distinguish the person's experience from your interpretation. When the topic is sensitive, offer a private or written route and accept a decision not to share.

3. Make a pause useful to the person answering

In her CBRE interview, Choy explains pauses as room to process information and participate. A leader who immediately answers their own question removes that room. Silence is useful here because it changes the pace of the exchange, not because it forces someone to reveal more.

After asking about the difficult handover, Anika can stop editing her slides and let Mateo think. If he hesitates, she need not interpret the hesitation as lack of knowledge. He may be deciding which example is relevant, recalling its sequence or considering what can appropriately be discussed in the group.

Our suggested practice is to ask one question, give it space and then check what the person would find useful. Mateo may want to look at the handover note or return with an example after the meeting. A pause should create an option to contribute, including the option to do so later. It should not become a test in which the manager stares at someone until they speak.

When Mateo finishes, Anika can briefly summarize the part she understood and invite correction. She should not claim to read his feelings from a facial expression. If he corrects the summary, that is useful information about the account, not a failure of the conversation. The practical change is small but consequential: the listener is no longer using every available moment to rehearse a response, and the speaker has a chance to determine whether the point has been understood accurately.

4. Offer several ways to contribute instead of demanding boldness

Choy describes three levels of speaking up in the CBRE conversation: clarifying or summarizing; adding or subtracting; and challenging or changing. The distinctions help a leader avoid treating a direct public challenge as the only valuable contribution. They do not make any workplace automatically safe.

In our example, a newer colleague can begin by checking whether the new deadline applies to every client. That clarification may reveal a difference Anika's proposal overlooked. Mateo can then suggest adding an exception for information the customer controls, or removing a duplicated approval. A more fundamental challenge would ask whether the handover should happen at a different stage altogether.

For a reader facilitating a discussion, the application is to say what kind of input is needed and what is open to change. Ask for clarification before inviting alternatives, and avoid treating a short question as evidence that someone has nothing substantive to contribute. Equally, do not require people to work through these levels in a fixed sequence. An urgent risk may need direct attention immediately.

The leader's response matters as much as the invitation. If Anika praises speaking up but embarrasses the first person who identifies a flaw, the next invitation will be less credible. She can acknowledge a useful contribution, examine it and explain the resulting decision even when she does not adopt the suggestion. Participation has value when it can affect understanding, rather than when it merely gives a meeting the appearance of inclusion.

5. Alternate explanation and facilitation, then make the decision legible

Choy's October 2026 article distinguishes telling a story from facilitating other people's stories, and argues that leaders need both capacities. A prepared explanation can orient a group; facilitation can reveal what the explanation missed. Choosing between them depends on what the conversation needs at that moment.

Anika can begin with the handover problem, the deadline and the boundary she cannot change. She then asks for experiences that bear on the proposed solution. If the discussion becomes confusing, she can summarize what is agreed and identify the remaining question. She does not need to choose between delivering a monologue and abandoning the group to an unstructured discussion.

In this guide's application, she keeps three kinds of information separate: what someone experienced, what the group thinks that experience means, and what decision follows. Mateo's account may warrant a trial exception. It may also reveal a need to check the records before changing the whole process. The decision should reflect that difference.

At the end, Anika explains the version the team will try, who owns the next action and when they will inspect the result. She checks with Mateo before repeating his account outside the room and gives credit for the contribution appropriately. This closing step is our addition, not a claimed book worksheet. It prevents a satisfying discussion from becoming another unresolved meeting and shows participants what their contributions actually changed. Listening and decision-making belong in the same process, with neither used as an excuse to avoid the other.