Drop the Content Wall

Someone asks in a meeting: "Is the database going to run out of memory again?" The engineer responsible for the database says: "Well, theoretically, given the number of unknown accessing processes and the unpredictability of query plans under concurrent load, it's difficult to assess with certainty, but if we consider the growth trend relative to current allocation..." Three minutes later nobody knows if the database is going to run out of memory again.

That is a content wall. A direct question got a paragraph of qualifications instead of an answer.

What It Actually Is

A content wall is not the same as a thorough answer. Thorough answers contain the answer. A content wall contains everything adjacent to the answer, arranged in a way that makes the answer hard to find or easy to mistake for something that was said when it wasn't.

The tell: someone finishes talking and you still don't know what they think. You know what factors are relevant. You know what considerations exist. You do not know what they believe is true.

It happens in meetings, in Slack threads, in code reviews, in incident retrospectives. Anywhere someone can be asked a question they are not sure how to answer.

Why People Do It

Usually because they don't know the answer and don't want to say so plainly.

Saying "I don't know" feels like admitting incompetence. So instead of saying "I don't know," people demonstrate knowledge of the problem space. They explain the factors that make the question hard. They enumerate the scenarios. They perform expertise while not actually answering the question. It can sound thorough enough that the asker feels they should have understood the answer from it, which means nobody has to acknowledge that nothing was actually said.

Sometimes it's genuine uncertainty delivered badly. The person has a best guess but isn't confident in it, so they surround the guess with so much qualification that the guess disappears. This is the more sympathetic version. It is still not useful.

I have done this. You hedge because you're not sure, and the hedging starts to feel like the whole answer, and you run out of time before you get to the part that would have been useful.

What It Costs

The person who asked the question now has to either ask again more specifically, or make a decision without the information they were looking for. Usually they make the decision. Usually the engineer who gave the content wall feels they answered the question. Neither of them is right.

Across a few months of this pattern, the asker stops asking. They don't trust that they'll get a direct answer, so they stop expecting one. That is bad for the person asking and bad for the person who doesn't realize they've been opted out of.

There is also a subtler cost. Content walls are sometimes a symptom of an engineer who doesn't actually have a view. They understand the forces in play. They cannot tell you which way the forces resolve. That is a gap worth knowing about. When it's hidden behind elaborate equivocation, nobody gets to address it.

What to Do Instead

Answer the question. Then add the caveats.

"Is the database going to run out of memory again?" The answer is either yes, no, or I don't know. Pick one. Then say why. "Probably not on current trajectory, but we're growing faster than I expected last quarter so I'd want to revisit this in two weeks." That is an answer with nuance. The nuance is attached to the answer, not substituted for it.

"I don't know" is also an answer. It is a more honest answer than three minutes of context that lets everyone walk away with different interpretations.

Caveats are not bad. Most real answers have them. The problem is leading with the caveat, or using the caveat to avoid ever landing on a position. State what you think is true. State your confidence level. State the thing that would change your mind. That is specificity. A content wall is the same information rearranged so that no conclusion is reachable.

The person asking almost always already knows the question is complicated. They asked anyway because they wanted your best read on it. Give them your best read.