Listen (and Understand) Before You Fix

Issues and concerns carry judgment, risk, and history that a spreadsheet or model can't capture.

Technical professionals are trained to solve problems. So when a colleague or stakeholder raises an issue, the first instinct is to fix it. That instinct, however well-intentioned, gets in the way of understanding what's actually wrong.

Concerns Are Data, Not Interruptions

A stated concern is information about what the other person values, fears, or doesn't yet trust. Treat it as a data point, not a distraction from the agenda. When you interrupt with a solution, you tell the speaker their concern wasn't worth finishing.

Ask Before You Answer

Resist the pull to respond immediately. Ask a clarifying question instead: "What's driving that concern?" or "What would resolve this for you?" These questions do two things. They surface the real issue underneath the stated one. They signal that you're listening to understand, not just to reply.

Name What You Heard

Paraphrase the concern back in your own words before you move to a solution. This confirms you understood correctly, and it slows the conversation down enough for the other person to add anything they left out. People rarely trust a solution to a problem they don't believe you heard.

The Tip: Understand Before You Fix

Issues and concerns are rarely just technical. They carry judgment, risk, and history that a spreadsheet or model can't capture. Listen long enough to understand what's underneath before you offer a fix.

---

JD Solomon champions practical communication skills that help technical professionals convey complex ideas clearly and confidently. Learn more at www.jdsolomonsolutions.com and www.communicatingwithfinesse.com.