Word Is Losing. Not to Another Word Processor.
I’ve been writing in markdown for years. This blog runs on it. My notes live in it. Most of my structured thinking starts in a plain text file with a handful of ## headers and some dashes.
For a long time I thought of that as a personal quirk — something that worked for me but probably wasn’t how most people operated. Lately I’ve changed my mind. I think the shift I’ve made in my own workflow is happening across the industry, and it’s going to keep accelerating. Microsoft Word isn’t going to disappear, but the WYSIWYG paradigm it represents — format-as-you-write, everything-in-one-file, documents-that-look-like-printed-pages — is losing ground fast.
Not to a better word processor. To something structurally different.
The Formatting Tax Is Real and It’s Expensive
If you’ve spent any time in enterprise environments, you know the formatting tax. You’ve paid it.
You paste a section from one Word document into another and the font changes. A numbered list decides it wants to restart at 1 when you need it to continue from 4. The styles in the template someone sent you conflict with the styles in the document you already have, and Word “helpfully” resolves the conflict in a way that makes everything look like it was assembled by two different teams who’ve never spoken — because it was. Someone tracks changes on a document you didn’t know was in review mode and now you’re reconciling edits in a colored-comment nightmare.
These aren’t edge cases. This is Tuesday.
The formatting tax isn’t just annoying — it’s a real drag on the work. I’ve watched teams spend an hour on a document’s appearance for every two hours on its content. The tool is consuming effort that should go toward the thinking.
Word was designed for a world where the document was the output. You wrote it, you printed it, you handed it to someone. The formatting mattered because the page was the final artifact. But that’s not how most documents work anymore.
Nobody Is Printing These Documents
Think about the last ten “documents” you produced or consumed at work. How many of them got printed?
Most professional documents today are read on screens, pasted into emails, uploaded to SharePoint or Confluence or Google Drive, fed into ticketing systems, or copied into slide decks. The document as a physical artifact is largely gone. What remains is a file format designed for physical artifacts, dragging all its print-era assumptions into a screen-first world.
Page breaks that appear in the middle of your screen for no reason. Headers and footers that carry metadata nobody needs. Margins optimized for 8.5×11 paper that the document will never touch.
Word documents are, in most enterprise workflows, print-ready objects that are never printed. The format is overhead.
Markdown Has Already Won the Toolchain
Here’s what I’ve noticed: markdown is everywhere professionals actually build things.
Every developer on your team writes it daily in GitHub — issues, pull requests, READMEs, wikis. Confluence supports it. Notion runs on it. Obsidian, Bear, Logseq — the serious note-taking apps people use for real work have all moved toward markdown or a close variant. Static site generators like Jekyll (what this blog runs on) use it natively. Documentation platforms like Docs-as-Code pipelines assume it. AI tools output it by default.
This didn’t happen because of a marketing campaign. It happened because markdown solves the actual problem. Plain text is portable. It doesn’t carry hidden formatting state. It renders consistently. It survives being pasted into anything. It’s version-controllable without losing your mind. And it’s fast — the cognitive overhead of ## for a heading and - for a list item is close to zero.
Markdown won the developer toolchain first because developers had the lowest tolerance for formatting tax and the highest ability to route around it. But it’s been spreading. If you’re a security leader and you’re not already writing in markdown — your notes, your policies, your reports — you’re one tooling switch away from a noticeably lighter workflow.
AI Is the New Presentation Layer
Here’s where I think the trajectory gets really interesting.
The old Word model bundled content and presentation together. You wrote and formatted in the same tool at the same time, and the result was a fixed artifact.
What I’ve moved to — and what I see accelerating across the tools I use — is a two-layer model:
Layer one: structured content. Plain text, markdown, clear hierarchy, human-readable. This is where the thinking lives. This is the thing you write and edit.
Layer two: AI-driven rendering. You take that structured content and you tell an AI what you need — “format this as an executive briefing,” “turn this into a slide outline,” “write this up as a formal policy document,” “adapt this for a technical audience.” The AI handles the presentation for the context.
I do this constantly now. I’ll write a rough set of observations in markdown, then ask Claude to render it as a polished post, a board-level summary, or a draft email, depending on who needs to see it. The content layer stays stable. The presentation layer adapts on demand.
This is a fundamentally different model than Word, and it makes Word look like what it is: a tool that conflates writing with formatting at a time when those two things are better separated.
The implication is that you don’t need Word’s formatting capabilities anymore — because you’re not doing the formatting. You’re writing structured content and delegating the rendering.
Enterprise Inertia Is Real but Won’t Save It
I’m not predicting Word disappears next year. Enterprise software has a half-life measured in decades. Legal templates, compliance documentation, procurement forms, board packages — a lot of this still runs on .docx and will keep running on .docx because the process was built around the file format and changing the process is expensive.
But here’s how these transitions actually work: they don’t happen all at once. They happen one abandoned use case at a time.
First the developers stop writing internal docs in Word. Then the technical writers move to Docs-as-Code. Then the security team starts keeping their runbooks in a git repo. Then someone’s AI assistant starts generating the first draft of that policy document in markdown and nobody feels like converting it. Then the new hire, who has never had a reason to learn Word’s style system, just… doesn’t.
The enterprise inertia is real, but it protects the legacy use cases, not the growth edge. Every new workflow that gets built, every new tool that gets adopted, every new team member who joins with different defaults — those are the places where the old model doesn’t get reinstalled.
What This Means for How You Work
I’m not writing this to talk anyone into a migration project. But if you’re a practitioner who’s watching the same patterns I am, a few things are worth thinking about.
Your content should be portable. If your knowledge and your documents are locked inside .docx files optimized for printing, you’re going to pay a translation tax every time you need that content somewhere else. Plain structured text survives context changes. Word files don’t.
Separate writing from formatting. The instinct to make things look right while you’re writing them is understandable, but it burns attention that should go to the thinking. Write first in something that doesn’t distract you with style choices. Render later when you know what you need.
AI makes the two-layer model practical. The objection to markdown used to be that it doesn’t produce nice-looking output without effort. That objection is mostly gone now. If you can describe what you want the output to look like, an AI can produce it from your structured content.
Word was the right tool for a print-first, format-as-you-go world. That world is shrinking. The document that lives as a fixed, formatted artifact is giving way to content that needs to be read in a browser, pasted into a ticket, rendered by an AI, and sent as three different things to three different audiences — all from the same underlying text.
That’s a different problem. Markdown plus a capable AI is a better solution to that problem than Word is.
The transition is already happening. You can see it in the toolchain, if you’re paying attention.