The agent sold my house for the price I wanted within the time frame I requested. What more need I say?
I said this, and meant it literally, and posted it as a review. It was the complete account. The agent had been given a task. The task had been performed to the specified standard within the specified conditions. Nothing had gone wrong. Nothing required qualification. The review described the event accurately and stopped.
Most reviews do not stop.
I am sparing with reviews. Not because I am indifferent to the experiences I have or the products I use, but because the ordinary does not require documentation. The coffee that was adequate coffee. The delivery that arrived when it was supposed to. The hotel room that contained a bed and a bathroom and a temperature control that worked. These things met their specifications. Meeting specifications is not an event. It is the absence of an event. The appropriate response to the absence of an event is silence.
I reserve comments for the extraordinary—the thing that exceeded what was reasonable to expect, or failed so comprehensively that the failure itself became information useful to someone else. These are the conditions under which a review performs its original function, which is the reduction of uncertainty. The person who has not yet bought the thing, stayed in the place, used the service—they face uncertainty. The review addresses that uncertainty by supplying the experience of someone who has already been through it. When the experience is ordinary, the uncertainty is already addressed by the specifications. The review adds nothing because the specifications already said it.
The review of the real estate agent was not ordinary, which is why it warranted documentation. The agent had performed a specific, complex, high-stakes task to the exact standard I required. That is not common. That is worth noting. The note was: the agent sold my house for the price I wanted within the time frame I requested. The note was complete. The question at the end—what more need I say?—was not rhetorical. It was diagnostic. It asked whether additional language would add information or merely add length.
Additional language would have added length.
The modern review does not ask this question. It adds length regardless of whether length is warranted, because the systems that receive and display reviews do not primarily value accuracy. They value volume. A short review, however precise, registers as less substantial than a long one, however padded. The platform’s ranking mechanisms weight engagement signals—length, helpfulness votes, verified purchase status—in ways that reward the production of content rather than the transmission of information.
The review that says exactly what needs to be said and stops is, within these systems, a thin contribution. The review that says what needs to be said and then continues for several paragraphs, discussing the packaging, the delivery experience, the customer service interaction, the emotional context of the purchase, and the reviewer’s general relationship with products of this category—that review is substantial. It feeds the system. It ranks well. It generates helpfulness votes from people who have not yet bought the thing and are looking for reassurance rather than information.
The purpose of the review has shifted. It was designed to reduce uncertainty. It now produces content. These are different functions. Reducing uncertainty requires stopping when the uncertainty has been reduced. Producing content requires continuing.
There is a particular shape to the reviews that extends beyond necessity, and it is consistent enough to be recognisable across categories.
The review begins with the product or service—what it is, what the reviewer expected, whether those expectations were met. This is the functional core. This is the part that addresses uncertainty. In a review that stops when it should stop, this is where the review ends.
In a review that does not stop, this is where the review continues.
What follows the functional core is a series of additions, each one extending the account without adding information that would change any reasonable person’s decision. The reviewer notes that the packaging was attractive, though packaging is not the product. The reviewer describes the delivery experience, though the delivery is not the product. The reviewer observes that they bought the item as a gift, or during a difficult period, or having tried several alternatives, though none of this affects the performance of the thing itself. The reviewer concludes with a general endorsement—would highly recommend—which restates, at lower resolution, the information the functional core has already supplied.
The additions feel like generosity. They feel like the reviewer taking care, being thorough, giving the potential buyer everything they might want to know. What they give, in most cases, is an extended experience of one person’s relationship with a purchase. This is not the same as information. It is the texture of information—the form of it, the weight of it, the social performance of having engaged seriously with the act of reviewing. The performance is widely accepted as equivalent to the thing it performs.
I understand why it happens. The act of reviewing invites a particular kind of attention—a looking back at the experience with the purpose of accounting for it, which naturally generates more material than the accounting requires. The reviewer sits down to describe what happened and finds that several things happened, and each of them has a texture, and the texture seems worth conveying, and before long the review contains everything the reviewer noticed rather than the subset of what they noticed that addresses the reader’s uncertainty.
The invitation to review also carries an implicit expectation of a certain length. A review of two sentences looks, on the screen, like insufficient effort. A review of three paragraphs looks considered. The platform’s interface reinforces this—the text field is generous, the character count is high, the prompt often asks several questions rather than one. The structure of the invitation suggests that more is more, and the reviewer, wanting to be helpful, produces more.
But more is not more when the uncertainty was already resolved. More is more only up to the point where the additional material changes what a reasonable person would decide. After that point, more is just more.
The question what more need I say? is useful because it forces the specific examination that the review system does not perform automatically. It asks: what remains uncertain for the person who will read this? If the answer is nothing—if the functional core has addressed everything that was uncertain and stopped at that point—then the review is complete. If the answer is something—if there is a material question that the current account leaves open—then the review should continue until that question is addressed and then stop.
This is not a standard the modern review system applies. The system does not ask whether uncertainty remains. It asks whether content has been produced. Content is measurable. Uncertainty reduction is not. The system measures what it can measure and rewards the production of that thing. The reviewer who produces three paragraphs is rewarded with a higher helpfulness ranking than the reviewer who produces two sentences, regardless of which account more precisely addressed the reader’s uncertainty.
The result is a corpus of reviews that is, in aggregate, longer than it needs to be and less precise than it could be. The information is present, distributed through the length of accounts that carry it alongside material that does not carry anything. The reader must extract the information from the padding. The extraction is the reader’s task, not the reviewer’s—because the reviewer was not asked to minimise the reader’s extraction effort. The reviewer was asked to produce content.
The review of the real estate agent produced, as far as I could tell, mild surprise. The surprise was at the length—or rather the absence of it. People have come to expect that a review, especially of a significant transaction, will contain a substantial account. A house sale is not a bottle of shampoo. The stakes are high. The process is complex. There is much that could be said about it. The expectation was that I would say much.
What I said was: the agent sold my house for the price I wanted within the time frame I requested.
This was not brevity for its own sake. It was not a demonstration of restraint or an implicit critique of those who write at length. It was a description of what had occurred, complete at the point where the description was complete. The agent had been given two criteria—price and time. Both had been met. The account of the meeting of both criteria is the account of the service. The service had no other dimensions that were relevant to the uncertainty of a person deciding whether to use this agent.
There was nothing else to say. I said nothing else.
The question at the end of the review—what more need I say?—is the question the review system should ask of every submission before it accepts the submission as complete. It does not ask this question. It accepts whatever is submitted, weights it by length and engagement, and distributes it according to those weights. The question is left to the reviewer, and most reviewers do not ask it, because asking it risks producing something that looks, on the screen, like not enough.
Not enough and sufficient are different things. The review system does not distinguish between them. The reader, if they are paying attention, can make the distinction themselves—the account that stops because it is complete versus the account that continues because the system rewards continuation.
The account that stops because it is complete is the rarer one. It is also the more useful one. It gives the reader the information and stops, which is the most efficient possible transfer of what the reader needs.
I sent two sentences. They said what needed to be said. They stopped.
What more need I say?
