Chapter 2 How an Explanation Takes Shape
Silence became a refusal
During a planning meeting, Tessa suggested replacing an event registration form. The manager moved to the next item without answering. Tessa left the room believing her proposal had been rejected. When a colleague asked to see the new version, she said there was no point: the manager did not like it.
The colleague was surprised. There had been ten minutes left, and another event had a deadline that afternoon. He assumed the manager was dealing with the urgent matter first. He could not establish that explanation either. They had witnessed the same transition and supplied different reasons for it.
Tessa's account affected what happened next. She did not send the form, so other people could not inspect it. The lack of discussion then seemed to confirm the rejection. An interpretation had changed her behavior, and her behavior had reduced the available information.
She drew the Two of Swords and first saw a manager who refused to look at her work. Later she noticed that the blindfold could remind her of the information she herself lacked. Both associations were possible. The card did not select the correct one or disclose what the manager had been thinking.
Finding the step between an event and a conclusion
“He did not answer, so he opposed the proposal” leaves an inference unexamined. A rushed agenda, a missed comment, a need for more detail, and actual disagreement could all fit the observed silence. You do not have to believe all these possibilities. Their existence may be enough to show that the information does not yet support a single conclusion.
This is a practical inquiry, not a competition to imagine the largest number of motives. Listing fifteen alternatives can keep you occupied without bringing the task closer to a decision. Find one or two plausible possibilities that would materially change your understanding. Then work out how to get the necessary information.
Tessa asked who needed to approve the form and whether time could be set aside to review it. She sent the draft with two reasons for the changes. The manager replied that the next event would use the old version; the proposed form needed to be checked with the colleague responsible for reporting attendance and fees.
Tessa disliked the delay. She now had a specific arrangement to dislike, rather than a private attitude she could not verify. During the review, the data colleague pointed out that she had removed a field required for reconciliation. She had thought it unnecessary. Her proposal needed a correction.
The new information complicated a flattering story as well as a painful one. The manager had not necessarily dismissed her personally, and her idea had not automatically been an excellent proposal that others were too unimaginative to appreciate. Staying open to information includes discovering that your own work needs improvement.
A familiar explanation can arrive quickly
Tessa remembered being laughed at when she suggested a change in a previous job. The silence in the current meeting brought that experience to mind. It helped explain why rejection seemed immediate. It could not prove that the current manager was repeating the old behavior.
An explanation may have an understandable history and still be inaccurate today. You can acknowledge that history without making it the only route through every new situation. “I expected ridicule because I remembered that meeting” is a more limited claim than “People always ridicule me when I speak.”
Certain sentences may arrive particularly fast for you: you are causing trouble, you will be left to do everything, or somebody is about to withdraw. Notice the sequence in one event. What did you observe? Which sentence appeared? What did you do after it? What information became easier or harder to obtain?
You do not need a diagnostic label to examine this sequence. Tessa could see that after the agenda moved on, she stopped participating and withheld the draft. That did not make her responsible for the manager's communication. It showed one action she could change while also asking for a clearer review process.
Past experience can sometimes be highly relevant. If the same manager has repeatedly mocked suggestions in public, that history deserves a place in your judgment. The point is to describe the actual pattern and its coverage, rather than use one remembered humiliation as evidence about everyone you meet.
Questions can carry the conclusion inside them
“Why do you dislike my proposal?” appears to request information while treating the dislike as established. The answer may become an argument about tone. The missing field, approval process, and deadline remain outside the conversation.
A task question makes room for different answers. You could ask which requirements the form must satisfy or what would need to happen before it could be used. If there is an emotional issue worth discussing, it can have its own question: you felt uncertain when the meeting moved on and would appreciate a brief acknowledgment in future.
Neither question guarantees a helpful answer. Some people repeatedly avoid clarifying a decision. You can describe that behavior and limit your investment. You do not have to establish malice before deciding that a project lacks the commitment you need to continue.
Later Tessa had a proposal that really was left unattended. She followed up twice and received no review date. She stopped making extra versions and kept the existing file. Careful interpretation did not require her to excuse every silence as reasonable busyness. It required her to distinguish what had happened from what she could not know.
This distinction matters when an organization has formal responsibilities. A private reflective exercise cannot replace an approval record, a required escalation, or the applicable workplace process. Use the actual procedure when the task calls for one. Cards have no authority to assign permissions or waive requirements.
Correcting an account you have already repeated
Tessa had told several colleagues that the manager disliked the proposal. Once she learned more, changing her account felt embarrassing. She imagined the correction becoming evidence that she was oversensitive.
She used a bounded sentence: “I took the lack of response in the meeting as opposition. I now know the data team needs to check the form first.” It corrected the claim without announcing that every concern she had ever expressed was wrong. She did not need to make the manager blameless either.
Public claims may require a public correction to the relevant people. Writing a better account privately does not undo the effect of an earlier statement. The necessary scope depends on who heard it and what it changed. Tessa corrected the colleagues she had spoken to, then returned to the form.
A month later, a different proposal was explicitly declined because it did not meet the reporting requirements. She kept both events in her notes. The first silence had been ambiguous; the later refusal had stated grounds. Combining them into “Every time I feel rejected, I am just imagining it” would have erased the difference she had learned to make.
Practice Recover the missing inference
Take one conclusion you reached after a recent interaction. Write the observable event underneath it. Ask which step connected the two. If that step concerns another person's private motive, mark it as an inference unless you have relevant evidence.
Consider one plausible alternative that would change the next action. You do not have to choose it as the truth. Write one question or check that could distinguish what matters. Set a limit for the inquiry, particularly if the other person may not answer.
With the Two of Swords, look at the position of the figure, the crossed blades, and the surrounding scene. Write which information gap an association brings to mind. Then put the picture aside while you obtain the information. When an answer arrives, record what changed and what remains unknown. An exercise can end with a delayed decision, a refusal, or a corrected piece of work.