The Prettiest Document Is Now the Least Useful One

I just spent an hour building an HTML page so ugly it would embarrass a 1997 GeoCities site. Five years ago, I would have built a deck with custom fonts and branded slide masters.

The shift isn't about taste. It's about survival. Every document you create now has two audiences, and only one of them cares about your color palette.

The Audience You Didn't Budget For

Here's the number that changed my workflow: Slack is rebuilding its product roadmap on the assumption that by next year, more agents will use its platform than humans.

Read that again. Not "agents as a feature." Agents as the primary user.

I was reviewing a client's investor materials last month—beautiful deck, $15K of design work, the kind of presentation that makes you look credible in a conference room. Their VC forwarded it to an AI agent for preliminary analysis. The agent's summary confidently cited figures that didn't appear anywhere in the document. It had hallucinated numbers because it couldn't parse the layered text boxes and background images.

The board deck they labored over for weeks became telephone game the moment it hit an LLM.

Meanwhile, the scrappy startup that sent a Markdown memo? Quoted accurately. Shared faster. Actually read—by both the human and the machine acting on the human's behalf.

We've Watched This Movie Before

This is the SEO story, compressed into eighteen months instead of a decade.

Remember when Flash sites dominated agency portfolios? Immersive experiences, cinematic transitions, the kind of work that won awards. Then Google's crawler became a reader you had to satisfy. Overnight, those gorgeous sites went invisible. The pages that won were structured, boring, and machine-legible.

Nobody set out to build for the crawler. But the crawler quietly redefined "good."

The companies that figured this out early—that recognized the robot in the room as a first-class audience—built SEO into their DNA. The ones that dismissed it as a technical concern kept making beautiful things nobody could find.

Now we're doing it again. Except this time the crawler doesn't just index your content. It summarizes it. Answers questions about it. Makes decisions based on it. And if your formatting confuses the parser, the agent doesn't penalize your search ranking—it just invents a more convenient answer.

The Formats That Survive This Transition

I'm watching three design patterns emerge from teams that take agent-readability seriously:

Plain HTML is back. Not as a retro aesthetic choice—as infrastructure. Anthropic's own engineering team now argues that HTML is the optimal format for handing information to an AI. Semantic tags, clean hierarchies, no mystery about what matters. It's the format the open web was built on, before we piled seventeen layers of polish on top of it.

Markdown is the new executive memo. John Gruber designed it in 2004 to be readable as plain text and renderable as HTML. Turns out that's also the perfect profile for agent consumption. I'm seeing it replace PowerPoint in contexts where it would have been unthinkable two years ago—board updates, strategic plans, documentation that needs to be both authoritative and parseable.

Structured data is the new design system. Startups like Ando are building collaboration tools from scratch with a core assumption: humans and agents working side by side, not sequentially. That changes everything about how you structure information. The "designed for skimming" layout principles that worked for busy executives now have to work for LLMs with context windows.

The irony? The humble formats are winning again. The ones that prioritized structure over style, machine-readability over visual hierarchy, semantic meaning over pixel-perfect layout.

What This Costs You Right Now

Let me make this uncomfortably specific.

That 40-slide pitch deck you're circulating? Every time someone forwards it to Claude or ChatGPT asking "what's the key risk here," you're rolling dice on whether the agent parses it correctly or confabulates something plausible-sounding.

The RFP response your team spent three weeks formatting? If the buyer's procurement agent can't extract your pricing structure cleanly, you don't get a follow-up question. You get skipped.

The internal strategy memo that looks gorgeous as a PDF? When your CEO's AI assistant tries to pull the three key initiatives for a board prep call, it might cite the photo captions instead of your actual recommendations.

This isn't theoretical. I'm watching deals slow down, miscommunications compound, and credibility erode—not because the thinking was wrong, but because the formatting made the thinking illegible to half the audience.

The Question Nobody Wants to Sit With

Here's the tension I can't resolve, and I don't think you can either:

When more than half your document's readers are machines, does the polished deck become a liability?

I'm not saying burn your brand guidelines. I'm not arguing that design doesn't matter. I spent fifteen years perfecting the executive presentation—I know what a good deck does in a room full of skeptical humans.

But I also know what I've started doing differently. I'm defaulting to structured text where I used to default to slides. I'm building semantic HTML where I used to build one-sheets. I'm choosing agent-legible over human-impressive for any document that's going to get forwarded, summarized, or analyzed.

And the uncomfortable part? It works better. Not just for the agents—for the humans too. Turns out when you strip away the formatting crutches and force clarity of structure, your thinking gets sharper.

The prettiest asset is now your least readable one—to the reader that increasingly matters.

What to Do Monday Morning

Here's the specific action, not the rhetorical flourish:

Pick one document type you produce regularly—investor updates, client reports, internal strategy memos, whatever—and produce the next one in Markdown or plain HTML instead of your usual format. Don't announce it. Don't apologize for it. Just ship it and watch what happens.

Track two things: How long it takes to produce. How often people reference it accurately in follow-up conversations.

Then ask yourself: What's the first format you stop making?

Because I've already decided mine. That beautiful deck template I spent years refining? It's now the exception, not the default. The web page that makes my designer weep is the new power move.

Your most carefully designed document might be the one nobody—human or machine—can actually read.