The Geometry of Mediocrity

The smell of stale, reheated coffee and the residual chill of the too-aggressive air conditioning clung to my clothes as I walked out, the sound of the closing door muffling the final, meaningless platitudes being exchanged inside. My internal clock registered exactly 46 minutes of productive time lost, plus the hours the designer spent integrating 12 contradictory suggestions into a single, doomed artifact.

We had just concluded the fifth official review of the landing page refresh. Fifth. The presentation deck was now swollen to 236 slides, weighed down by endless ‘context’ sections and appendix slides detailing every historical design decision made since 2016. The designer, a brilliant woman who deserves better than us, presented the exact same page structure she had presented four weeks ago. The only difference? The Call To Action button had been tweaked to a slightly deeper shade of oceanic blue. Marketing had demanded “more conviction,” while Legal insisted it must remain “approachable and not overly coercive.” The resulting color was, inevitably, neither convincing nor approachable. It was the color of institutional compromise.

The Geometry of Mediocrity: Consensus over Genius

This is the geometry of mediocrity: a figure formed not by genius, but by consensus. Everyone wants to talk about collaboration as if the sheer act of inviting 16 people to the table guarantees a better outcome. But when everyone has a voice and nobody has a final veto, the fundamental purpose shifts. It stops being about building the best possible project and starts being about minimizing the political risk. The goal becomes clear: get so many fingerprints on the murder weapon that the blame can never be traced back to a single decision-maker.

We talk about being inclusive, but beneath the veneer of inclusivity lies the deeply human fear of ownership. If the project fails, the senior leader can say, “Well, we incorporated input from Marketing, Sales, Product, Legal, and Finance.” The mediocrity is justified by the process. It is a brilliant strategy for survival but a terrible strategy for design.

The Thread Tension Calibrator

I remember David K.L., the thread tension calibrator. I met him years ago when touring a specialized textile manufacturer. He didn’t design the patterns, and he didn’t pick the yarn colors. His entire, highly technical job was to ensure that when two threads crossed-say, at the 6th repeat in a complex weave structure-the tension was calibrated perfectly. Too tight, and the entire structure snaps under stress. Too loose, and the fabric distorts, creating a slack, dull result that fails the moment it needs to perform. He wasn’t praised for being the artist; he was revered for maintaining the tension.

We try to weave in every thread, accommodating every single voice until the resulting fabric (the project) is just a loose, dull sack. We lose the singular, focused vision. We lose the conviction. It is the cost of minimizing liability, paid for by maximizing complexity.

Visionary Authority vs. Bureaucratic Safety

This is why true, uncompromising excellence often comes from highly centralized, visionary authority, not from committees. It is the difference between a project hammered into shape by 16 contradicting executives and a piece of work that relies entirely on an unwavering aesthetic standard, focused on delicate and precise artistic integrity. You see this best in fields where precision dictates value, like the meticulous craftsmanship upheld by the

Limoges Box Boutique. Their work succeeds because someone, somewhere, dictates the tension and refuses to compromise it for the dozen different opinions that corporate structures inevitably cough up.

The Trap of Shared Liability

And yet, I must confess, I fall into this trap constantly. I’m writing this entire critique, yet just last week, I sent out a draft document for “soft feedback” to six different people. I knew exactly what the document needed to say, but I wanted the safety of shared liability. I wanted their validation more than I wanted the best, most focused outcome. That is the honest truth about the feedback loop-it feeds our need for certainty and feeds our cowardice, not the project’s ultimate quality. We seek feedback to be told we’re not wrong, rather than to be told how to be right.

It feels like untangling Christmas lights in July-all that effort, all that frustration, just to confirm they still work, only to put them back in the dark.

The Tally of Drag

We spent $676 last month on unnecessary tools just to facilitate the endless revisions, which is a minuscule amount compared to the organizational drag of having a core feature stuck in purgatory for two months, unable to generate the revenue it was designed for. The financial cost, the opportunity cost, and the spiritual cost are all tied up in this 16-step dance of indecision. The spiritual cost is the worst, because it tells your best people, like the designer, that precision and clarity are less valued than political maneuvering and bureaucratic safety. They learn to design projects that are designed to survive the review process, not thrive in the market.

The Administrative Confusion

I remember one project where we were testing 46 different shades of blue for a button, solely because four key stakeholders couldn’t agree on “the right feeling.” Four opinions. Forty-six options. That is not design; that is the technical application of administrative confusion. It creates a vacuum of responsibility. When the feature finally launched and performed poorly, everyone shrugged. “We followed the process. We incorporated all feedback.” No one owned the success, and no one owned the failure. The failure simply belonged to the process, a convenient, inanimate scapegoat.

This cycle continues until someone-usually someone outside the immediate process-demands a clear framework, or until the sheer inertia of the pending deadline forces a decision, which is almost always the worst possible moment to make a critical call. The design that wins is usually not the best one, but the one that generates the least resistance by being the least interesting. It pleases no one but offends no one.

Accountability Defined

If the entire point of the project is to create something definitive, something sharp and valuable, why are we prioritizing the process of feedback over the quality of the output? If the design is everyone’s fault, whose design is it, really?