“I Don’t Want To Lose My Friendship,” an Autostraddle advice column (Feb. 24, 2026) sits squarely in the gray area between loyalty and self-preservation. It follows someone wrestling with a twenty-year bond that’s fraying: old patterns that once fit now feel harmful, and the reader wants to protect what’s left of the friendship without sacrificing their own needs.
Who this helps
– Someone trying to keep a long friendship alive while setting clearer boundaries. – Someone who needs direct, usable tactics for talking, testing change, and stepping back when required.
What the column offers
Clear, practical coaching: how to describe behavior without blaming, how to run time-limited experiments, how to watch for genuine repair versus empty gestures. And if you want company while you think this through, there are Los Angeles literary events on Feb. 23–24, 2026—places to reflect, connect, and practice new ways of relating.
Why the problem often feels so hard
Three patterns show up again and again:
– Imbalanced effort: one friend does most of the emotional labor. – Life-stage drift: jobs, partners, kids, or geography change what people can give. – Value divergence: years apart can produce different priorities or public stances that feel incompatible.
Those shifts can make an old friendship feel like a mismatch rather than a safe harbor. The column avoids vague platitudes and instead names behaviors, suggests concrete tests, and insists on measurable follow-through.
How to prepare before you talk
Don’t wing it. Prepare so your conversation stays grounded and clear.
– Clarify the grievance. Is the issue political, ethical, relational, or about repeated boundary-crossing? Specificity reduces misreading. – Collect examples. Note dates, actions, and how each moment affected you. Facts keep the talk from sliding into generalized blame. – Pick the right moment. Choose a calm, private time—not a noisy party, not a late-night text, and not when either of you is exhausted.
Practical moves you can try
– Propose one testable boundary. Timebox it (weeks, not years) and make it specific: for example, “For the next six weeks I’m pausing one-on-one hangs unless we can talk about X respectfully.” – Ask for reciprocal action. Say exactly what you need and what you’ll look for as evidence of change: small, tangible signs matter. – Treat it like an experiment. Track whether promises are kept, whether tension drops, and whether the friendship still feels generative. – Dial down contact rather than cutting off. Less frequent interactions often reveal whether distance eases the problem or simply postpones the decision.
How to speak so repair is possible
Start from observation, not accusation. Something like, “When X happens, I feel Y” gives the other person room to respond without being cornered. Ask questions, test your assumptions, and really listen. If a direct conversation escalates, pause. Try a different format—mediation, a written letter, or a temporary pause—rather than doubling down on confrontation.
When a break is actually the kindest option
Sometimes time-limited distance is the most honest choice. Treat it like data-gathering, not punishment.
– Be explicit about the terms: who’s initiating the break, what behaviors you’re pausing, which communication channels you’re reducing, how long it will last, and what benchmarks you’ll use to reassess. – Look for sustained repair, not one-off apologies. Change shows up in repeated behaviors. – If contact resumes, reset expectations with concrete commitments. If it doesn’t, accept that closure can be a healthy, considered outcome—not a moral failure.
Balancing kindness and boundaries
A long history doesn’t obligate you to tolerate ongoing harm. People’s habits and trauma can explain behavior, but explanation without accountability rarely leads to real change. Compassion is vital, but not at the cost of your wellbeing.
Who this helps
– Someone trying to keep a long friendship alive while setting clearer boundaries. – Someone who needs direct, usable tactics for talking, testing change, and stepping back when required.0