Before sharing a reflection, write 3 sentences specifying what support you want — "hear how this sounds" or "spot what I'm missing," not "solve this for me"
Before sharing a reflection, write three sentences clarifying what type of support you want—not a solution, but a specific form of assistance like 'hearing how this sounds' or 'identifying what I might be missing.'
Why This Is a Rule
When you share a reflection with someone — a partner, friend, mentor, or colleague — you have a specific need that you may not have articulated even to yourself. You might want validation ("Tell me this makes sense"), perspective ("What am I not seeing?"), emotional support ("Just acknowledge this is hard"), or analytical help ("Help me find the flaw in my reasoning"). Without specifying which, the listener defaults to their natural mode — often solution-giving — which may not match your need.
The three-sentence pre-share clarification serves two functions. First, it forces you to know what you want before you ask for it. The act of writing "I want someone to hear how this sounds out loud" reveals whether you want feedback, validation, or just a witness. Second, it gives the listener clear instructions that prevent the common mismatch where you want empathy and they offer solutions, or you want analysis and they offer reassurance.
The "not a solution" clarification is essential because solution-giving is the default response to someone sharing a problem. "Have you tried..." is the listener's automatic pattern. Specifying the support type overrides this default: "I'm not looking for solutions — I want to hear whether my reasoning sounds coherent when I say it out loud" gives the listener permission to do something other than fix.
When This Fires
- Before sharing any vulnerable or important reflection with another person (or AI)
- When past sharing conversations produced unhelpful responses — likely a specification gap
- When you feel reluctant to share because you're afraid of getting advice you didn't ask for
- Complements Share completed reflective writing with AI and ask "What assumptions am I making that I haven't examined?" — surface premises treated as facts (AI-assisted reflection) with the human-sharing equivalent of clear prompt design
Common Failure Mode
Unspecified sharing: pouring out a reflection and hoping the listener intuits what you need. They guess wrong, give unsolicited advice, and you feel unheard. Both parties leave frustrated — you because the support didn't match your need, them because their help wasn't appreciated.
The Protocol
(1) Before sharing, write (or say) three sentences: "I've been reflecting on [topic]. What I need from sharing this is [specific support type]. I'm NOT looking for [common default you want to prevent]." (2) Support types to choose from: Witness ("I just need someone to hear this"), Mirror ("Tell me what you hear — does my reasoning hold up?"), Blind spot check ("What am I not seeing or not considering?"), Emotional validation ("Acknowledge that this is hard"), Analytical partnership ("Help me find the weak points in my thinking"). (3) Share these three sentences before the reflection content. This frames the conversation so the listener knows their role. (4) If the listener drifts into unsolicited advice despite the framing, gently redirect: "I appreciate that — right now I'm looking for [specified type] more than solutions." (5) This applies equally to AI: "I'm going to share a reflection. I want you to identify unexamined assumptions (Share completed reflective writing with AI and ask "What assumptions am I making that I haven't examined?" — surface premises treated as facts), not to solve the problem or offer advice."