The pursue–withdraw cycle: when one wants to talk and the other goes quiet
It's one of the most common patterns couples get stuck in. One partner wants to talk things through now. The other needs space, goes quiet, or leaves the room. The more one pursues, the more the other withdraws — and the more the other withdraws, the harder the first pursues.
Each person sees the other as the problem. "You never want to talk." "You never let anything go."
What's happening underneath
The partner who pursues usually feels anxious when there's distance. Silence feels like being shut out, so they push harder to reconnect — which can come across as criticism or pressure.
The partner who withdraws usually feels overwhelmed by conflict. Going quiet is how they try to stop things getting worse — which can come across as not caring.
Both are trying to protect the relationship. They're just doing it in opposite ways.
See the cycle as the enemy
A big shift happens when you describe the loop out loud as something that happens to both of you:
"When you go quiet, I feel shut out and push harder. Then you feel pressured and go quieter. Then I panic and push even more."
Once it's named, you can fight the cycle together instead of fighting each other.
Softer moves for each of you
If you tend to pursue: share the worry underneath instead of the complaint. "I'm scared we're drifting apart" is easier to hear than "You never talk to me." And try giving a little space without punishing it.
If you tend to withdraw: say what you need instead of disappearing. "I do want to talk about this. I need twenty minutes to calm down first." Then come back when you said you would. More on taking breaks.
How Between helps
In your profile, each of you says how you usually react when things get tense. The guide uses this to pace the conversation: giving the quieter partner more time and gentle invitations, and reassuring the partner who wants to talk that their turn is coming.
This guide is general information, not therapy or professional advice. If you feel unsafe, see our safety page.