Quiet Work, High Stakes (#11)
On urgency, invisibility, and the work that holds everything together
I don’t like reading documentation.
I skim. I search for keywords. I let AI summarize it for me. If I’m paying for support, I open a ticket instead. I do all the things a good technical writer isn’t supposed to admit.
This is not a piece with five quick wins. It’s not a checklist. It’s an orientation for anyone who’s ever wondered why this work matters, even when it goes unread.
But here’s the punchline: I still write documentation every week for teams who insist their users will read it. Some users do engage with the content when it’s first published. More often, though, they refer to it only when something breaks — or when sales engineers need to sound like they understand OAuth.
Most people don’t seek out documentation. They hope they’ll never need it. But when the demo freezes, the dashboard errors, or the question goes beyond what the chatbot can handle, the documentation suddenly matters.
Documentation doesn’t launch with fanfare. It doesn’t drive conversions or headline a roadmap.
But when something breaks, it’s the fallback. It's the quiet system someone hopes was prepared in advance, ready to carry the weight when nothing else can.
We tend to overlook what’s been prepared in advance, until we’re the ones depending on it.
The Oil They Forgot to Bring
There’s a parable in the Gospel of Matthew.
Ten virgins go out to meet the bridegroom, each carrying a lamp. Five are wise. They bring extra oil. Five are foolish. They bring only what’s in the lamp.
The bridegroom is delayed. At midnight, a cry goes out: “Here is the bridegroom! Come out to meet him.” The wise trim their lamps. The foolish realize theirs are going out. They ask to borrow oil, but there isn’t enough to share. So they leave to buy more.
While they’re gone, the bridegroom arrives. The door is shut. By the time the others return and ask to be let in, it’s too late.
It’s not a story about effort. It’s a story about preparation, about having the foresight to be ready before the moment arrives.
Many of us treat documentation the way the foolish virgins treated a backup oil supply. We believe that things will go smoothly. Inevitably, something breaks: the dashboard errors out, a client asks a tough question mid-demo, the chatbot fails.
In that moment, documentation becomes essential.
It's neither flashy nor central. It's just complete, quietly doing its job when everything else falters.
Why No One Reads the Manual
But preparation only matters if people reach for it. And most don’t — at least not right away.
When something breaks or a deadline’s closing in, they’re not calmly browsing a well-organized knowledge base. They’re Googling error codes, pasting stack traces into ChatGPT, or pinging the first support person who’s still online.
It’s not laziness. It’s urgency.
Recent research backs this up. In a 2024 behavioral study, Yang et al. found that people were significantly more likely to trust algorithmic recommendations — even unverified ones — when placed under time pressure. Cognitive load didn’t shift behavior. Urgency did.
Another study observed user behavior following the launch of ChatGPT. Within six months, Stack Overflow saw a 25% drop in activity. Users stopped asking public questions. They turned to AI for fast, private answers without friction, wait, or debate.
In those moments, immediacy beats accuracy.
That’s the environment we’re writing into. Documentation isn’t competing with other documents. It’s competing with convenience. If it’s not fast, scannable, and trusted, it’s ignored.
And even when documentation clears the bar — fast, scannable, trustworthy — it may never reach the user it was written for.
Because increasingly, it isn’t just for end-users. It’s for the systems and teams that support them.
What Documentation Really Does
We talk about documentation like it’s educational material. But it functions more like infrastructure: invisible when it works, disruptive when it doesn’t.
It’s referenced, not read. Parsed, not pondered.
And the parsing isn’t always human.
A lot of technical content today gets skimmed by support teams, chunked into retrieval databases, fed into LLMs, or quoted in Slack mid-escalation.
One customer success lead put it this way:
“Your documentation saves the day for me. I’m in client Slack threads all the time. I just search the doc, copy the right chunk, and paste it in. The client thinks I’m a wizard."
That’s the tell. What was written for the end-user becomes internal enablement, AI input, and crisis communications, all at once.
The real audience might be:
A support rep in escalation mode
A sales engineer five minutes before a call
A machine deciding whether it can generate a helpful answer
This isn’t another “AI is taking over” narrative. It’s subtler than that.
AI isn’t replacing the need for documentation. It’s becoming dependent on it.
Tools like Gemini transcribe meetings and generate summaries using knowledge base integrations. Perplexity runs instant deep dives across product documentation. What gets written isn’t just consumed, it’s repackaged, rerouted, and reused.
If the documentation isn’t clear, the bot won’t be either. If it’s missing, the human sounds unprepared. Either way, the words still get used.
Which raises the question: if documentation works best when it disappears, why write it at all?
Writing Toward the Crisis
The better the documentation, the less likely it is to be noticed.
No one says, “Thanks for the config guide that didn’t waste my time.” But they forward it. They paste it into Slack. They solve the problem and move on.
What happens when the article’s missing or out of date? That’s when the messages come in, because no one reads documentation until they’re under pressure.
Urgency, not complexity, drives behavior.People don’t browse. They scramble. They search, they skim, they ask AI.In that moment, clarity matters more than authorship.
Unlike most writing, documentation isn’t performative. It’s a hedge against disaster.
It’s the config someone finds at 1:00 a.m., the answer that stops a third email thread, or the quiet proof that someone thought this through before it broke.
You won’t always get a “Thank you.” You won’t always get read.
But when the moment finally comes, documentation is the oil someone was wise enough to bring.