The Value of Saying What You Don’t Know

The Value of Saying What You Don’t Know

You’re halfway through a draft when a sentence lands a little too neatly. It makes a claim you can’t quite support, but deleting it feels like losing the point. That’s often the moment to say what you know, what you suspect, and where the evidence runs out.

Confidence Is Not Clarity

A strong-sounding sentence can hide an uncertain thought. Words like “always” and “obviously” may smooth over the place where an example stops being enough to prove a broader claim. Replacing them with a more exact description can make the idea clearer without making it timid.

There’s a difference between being unsure of every word and being precise about the limits of an argument. “I haven’t found a good answer yet” tells a reader something different from “there is no answer.” The distinction matters.

Draw the Boundary

When a thought feels wobbly, separate its parts. What did you observe? What are you inferring from it? What would you need to know before treating that inference as fact? Even a quick note in the margin can show where the draft is standing on firm ground and where it is still testing an idea.

This doesn’t mean adding a disclaimer to every paragraph. It means resisting the urge to make a claim bigger simply because a bigger claim sounds finished. A small, well-supported point can give a reader more to work with than a sweeping one.

Leave the Reader a Map

If you’re still figuring something out, make that visible in a useful way. State the question that remains, explain what led you to it, and avoid implying that the question has already been settled. Readers can follow an open line of thought when they can see where it begins and what it hasn’t reached.

Before you publish, look for one sentence that claims more than the rest of the piece can carry. Narrow it until it matches what you actually know. That isn’t a retreat from the idea; it’s a more honest place to begin.