How to spot a topic that always gets deflected

Some topics never get a straight answer. You raise a concern and the conversation shifts to something else. You ask a direct question and get a response about a different subject entirely. You bring up the same issue for the fifth time and realize, looking back, that it has never once been addressed on its own terms.

Deflection is easier to feel than to prove. In the moment, the conversation flows naturally enough that the redirect doesn't register as avoidance. It's only when you look at the record across multiple attempts that the pattern becomes clear: this topic is consistently evaded.

Here's how to use your message history to identify and document it.

The search-and-read method

Pick the topic you suspect is being deflected. Identify the keyword or phrase you use when raising it - "rent," "that night," "your mother," "the agreement," whatever term is specific enough to find the relevant messages.

Search your message history for that term. Most messaging platforms have a search function. If you're working with exported messages, a text search in your document or spreadsheet works.

Now read each result in context. Don't just read your message - read the response. And the message after that. Follow each thread for three to five exchanges past the point where you raised the topic.

For each instance, note:

1. How you raised it. Direct question? Casual mention? Reference to a previous conversation about it?
2. The initial response. Was the topic acknowledged? Partially addressed? Ignored entirely?
3. Where the conversation went. Did it stay on the topic, or did it move to something else? If it moved, what did it move to?
4. Whether the topic was resolved. By the end of the exchange, was the original concern addressed?

Do this for every instance in your search results. Five, ten, fifteen instances - however many your history contains.

What deflection looks like in messages

Deflection takes several forms in text. Knowing what to look for makes it easier to identify in a review.

Topic change. You raise subject A. The response is about subject B. There's no acknowledgment that subject A was raised. The conversation proceeds on subject B as if your message was about something else.

Example:

You: "Can we figure out the utilities split this month?" Them: "I had such a long day. My manager was being impossible again."

Counter-complaint. You raise a concern. The response raises a different concern about you. The original topic is displaced by a discussion of your behavior.

Example:

You: "You said you'd call the landlord last week. Did that happen?" Them: "You always act like I don't do anything. What about the time you forgot to pay the internet bill?"

Vague agreement with no follow-through. The topic is nominally acknowledged but not engaged with. A response like "yeah, we should figure that out" or "I know, I'll handle it" that closes the conversation without actually addressing the substance. When you search for the topic again, you find another vague agreement, and another, with nothing resolved between them.

Emotional escalation. You raise a topic calmly. The response escalates the emotional register - anger, hurt, accusation - in a way that makes continuing the discussion feel unsafe or futile. The topic gets dropped not because it was resolved but because pursuing it became too costly.

Delay and drop. "Can we talk about this later?" followed by later never arriving. When you raise it again, you get another delay. The topic exists in a permanent future tense.

Building the deflection record

Once you've reviewed every instance where the topic was raised, compile your findings. A simple format:

Read that table from top to bottom. Six attempts across two months. Zero resolutions. Five different deflection strategies. The pattern is visible in a way that it never was in the flow of individual conversations.

What consistent deflection tells you

Deflection is a behavior, and like all behaviors, it carries information. A topic that is consistently avoided - across multiple attempts, using multiple deflection strategies - is a topic that the other person is not willing to engage with under the current conditions.

This is a factual observation, not a judgment about their reasons. They might be avoiding it because they're uncomfortable. They might not realize they're doing it. They might be doing it deliberately. The record doesn't tell you why. It tells you that it's happening, how often, and what forms it takes.

That information is useful regardless of your interpretation. It tells you that raising the topic the same way is producing the same result. It gives you a documented record if you need to demonstrate the pattern to someone else. And it clarifies what you're dealing with - not a topic that hasn't come up, but a topic that has come up repeatedly and been deflected each time.

When you have enough

You have enough documentation when the pattern is clear to any reasonable person reading the record. If someone unfamiliar with your situation could look at your deflection log and say "this topic is being avoided," the record is sufficient. What you do with that clarity is a separate question. The documentation gives you the evidence. The decision is yours.