Pattern Snapshot: Advice Avalanche
- What it looks like: You mention a small problem. He responds with ten solutions before you finish.
- Where you see it: Casual conversations, personal updates, any mention of a difficulty.
- What drives it:
How to Spot It
- You mention one frustration. He offers five approaches before you finish.
- He keeps adding ideas after you acknowledge the first ones.
- He never pauses to ask if you want advice.
- The solutions get bigger. A minor work problem turns into a life overhaul.
- He looks energized. You feel buried.
- Your clarifications do not slow him down.
- The conversation is now about fixing your problem, not about you.
What It Means
He is not trying to take over. He is trying to be useful.
- Need for Relevance: Solving your problem proves he has something to offer. That matters to him.
- Fixer Mode: This is Fixer Mode at full speed. A problem calls for a solution. That is his reflex.
- Conversation style: For him, solving problems together is a form of connection. He is not aware it can feel like a lecture.
- Genuine care: The flood comes from wanting to help. The execution is the problem, not the intent.
What You Can Do
- Say what you need before you start. “I want to vent about something. I am not looking for solutions yet.” He will adjust.
- Acknowledge one idea, then redirect. Say: “That’s a good point. Right now I mostly need you to hear me.” That is not a rejection. That is a direction.
- Name it lightly. “I think I just triggered an advice avalanche.” He will probably laugh. It opens the door.
- Ask for one idea, not all of them. “What is the one thing you would do?” Limits help.
The avalanche comes from the same place as Experience Shield: accumulated knowledge looking for a place to land. Both patterns improve when you give him a clear role. Tell him what kind of help you want.
At Work
A junior shares an early code draft. He sends back twelve comments and a rewritten version. She says thank you. She does not share the next draft.
The team loses sight of work in progress. Problems grow before they surface.
Give him a clear scope before he starts. Say: “Review the logic in this section only. Flag anything that blocks the build.” That limits the feedback to something useful.
More for the workplace: Men Over 50 at Work