When I Didn’t Know How to Answer “What’s Wrong?”

The question asked for a cause, but what I felt was cumulative.

“What’s wrong?” arrived with good intentions. It assumed there was a clear problem, a specific explanation waiting to be named.

I paused longer than the question expected. Not because I didn’t know, but because nothing I knew could be offered cleanly.

Any answer I considered felt either too narrow or too abstract.

When a Question Can’t Hold the Answer

The question implied immediacy — something recent, identifiable, and solvable.

What I was experiencing didn’t have that shape. It was built from repetition, from patterns noticed over time rather than a single breaking point.

Trying to answer forced the experience into a form it didn’t belong in.

Some questions are too small for the answers they invite.

I learned to respond with placeholders. “Nothing specific.” “Just tired.” “It’s hard to explain.”

Those answers weren’t evasive — they were protective. They avoided misrepresenting something that didn’t fit the question.

This recurring mismatch lives inside The Language Gap, where common questions fail to meet lived experience.

Not having an answer changed how the question felt over time. It started to sound like a test I kept failing.

I became more careful about when I let the question be asked at all.

That careful distance echoed another loss I would later recognize in Grief for the Expected Life.

I didn’t know how to answer because the question couldn’t hold what I felt.