Redirect the path

Keep the necessary function but send it through a safer person, channel, or route.

Your teenage son tells you nothing, but you have noticed the pattern: every hard conversation about school ends with you interrogating him at the dinner table in front of his sister, he shuts down, grades slip further, and the next interrogation gets tenser. The conversations are necessary. The route they travel is destroying them.

Redirect the path keeps a necessary function alive but sends it through a safer person, channel, or route. The cue: cutting the connection outright would lose something you actually need, so removal is off the table. Run it in three steps. Name the function precisely (staying informed about school, offering help). Choose a route that preserves the function while shedding the harm: one-on-one in the car instead of an audience at dinner, or a weekly text check-in he controls. Then verify the function survived the move: are you still learning what you need to know? When it works, the payload keeps flowing, but the collateral damage, the public shame feeding the shutdown loop, stops. Don't redirect when the function itself is the problem; rerouting a genuinely harmful flow just relocates the damage, and that situation calls for cutting the path instead.