I'm interested in literature, technical writing and sport. Content Manager at https://nitter.cf/t.co/tEcN2zGwj0 🌟
Joined May 2018
- Tweets760
- Following397
- Followers603
- Likes876
Ann Green retweeted
“We need AI in our docs” means three different things to three people in the room: autocomplete, a chatbot, or an agent that publishes on its own.
We mapped it into 5 levels of autonomy, from editor to autopilot. Almost no one is at L4 yet.
👉 tinyurl.com/54cf7ebu
#AIdocs
Ann Green retweeted
Your docs chatbot gives wrong answers? A bigger model won’t fix it.
We tested 14 setups on 50 real support questions. Often the model never got the article with the answer, and no model can answer from an article it never saw.
What we found→ tinyurl.com/5yrvpp7j
#AIdocs
Ann Green retweeted
Your AI support bot has a 78% deflection rate. Great.
But how many problems did it actually solve?
A conversation ending ≠ a problem solved.
Here’s how to measure what really matters → tinyurl.com/5n6w8mjk
#TechnicalWriting #AI #TechComm #AIdocs #documentationsystem
Ann Green retweeted
A Standard-plan user asks your AI assistant about SSO. It answers from the Enterprise docs. The text matched, the plan didn’t.
Embeddings capture what the text means, not who it’s for.
Metadata fills that gap → tinyurl.com/5hdtxaed
#TechnicalWriting #RAG #TechComm #AIdocs
AI makes docs faster to write and harder to keep consistent. Thursday’s demo shows the fix 👇nitter.cf/ClickHelpNews/status/2…
AI writes the same instruction a little differently every time. Snippets make sure it’s written once.
On Oct 15, we’ll use an AI assistant + MCP to turn repeated text in a ClickHelp project into reusable snippets.
18:00 CEST / 12:00 PM EDT
Register: tinyurl.com/3zzu5e8p
Ann Green retweeted
Your support address changes. It lives in 4 manuals and 2 languages. One copy gets missed, and a user calls the wrong number.
How to publish several manuals from one source→ tinyurl.com/drxsdjj2
#TechnicalWriting #SingleSourcing #TechComm #Documentation
Ann Green retweeted
Second product, same argument: one docs site or separate ones? Both setups fail the same way. The real question is what must stay separate for readers and what must stay shared for the team.
Read the article → tinyurl.com/4dp4ss36
#TechComm #Documentation
Ann Green retweeted
Your docs say "SSO configuration." Your reader types "can't log in with my work account."
Same problem, no shared keywords. AnswerGenius now searches by meaning, so it still finds the right topic.
More features in our September release → tinyurl.com/mtrkmnzt
#Techcomm #AI
Ann Green retweeted
Who Are You Actually Writing For?
Explaining "what is a subnet" to a CCIE engineer loses them in one line. Skipping VPC basics loses a junior. This article covers how to profile readers you'll never meet.
Read → tinyurl.com/mkrumkty
#TechnicalWriting #TechComm #Documentation
Ann Green retweeted
Documentation generation with AI takes under a minute. Reads perfectly. Also wrong — because the ticket it drew from was outdated before the writer even opened it.
Where should tech writers sit in the SDLC? 🧵👇
Read → tinyurl.com/39c2tf87
#TechnicalWriting #AIWriting #SDLC
Ann Green retweeted
Your changelog and your release notes should never read the same. One's for developers. One's for users. Most teams write both the same way — which is why nobody reads either.
Read more → tinyurl.com/4y8mec2y
#TechnicalWriting #ReleaseNotes #DevOps #TechComm #CICD
Ann Green retweeted
Two dictionaries picked "slop" as their 2025 word of the year. Documentation has its own version: a portal that doubled in size while support tickets stayed flat.
Writing got cheap. Scoping went with it.
Read → tinyurl.com/4zmhuf4x
#TechnicalWriting #DocumentationStrategy #AI
Ann Green retweeted
Ask MT to translate the same term twice, and there's no guarantee it comes back the same way. That's how one feature name ends up with three names across your docs.
We asked @alconost what actually fixes it.
Read here→ tinyurl.com/yxamm92s
#Localization #TechDocs #AI
Ann Green retweeted
Docs-as-code brings technical documentation into the same workflow as software development: Git, pull requests, versioning, CI, automated validation, and continuous publishing.
In this article: popular docs-as-code tools → tinyurl.com/2uuzse7j
#TechnicalWriting #DocsAsCode
Ann Green retweeted
Same warning copied into 40 topics. Product changes, and now you're hunting down 40 places to fix it.
Snippets fix this: write the block once, insert it everywhere, update the source when things change.
Read more → tinyurl.com/3ee2a2bj
#TechWriting #DocumentationManagement
Ann Green retweeted
AI agents are only as useful as the data they can reach.
MCP changes that — one server, any compatible client.
We built a working MCP server in Python in under 30 lines.
Step-by-step guide 👉 tinyurl.com/yc87rbxn
#mcpserver #python #TechComm
Ann Green retweeted
DITA promises structure. CCMS promises scale. But most tech writing teams just need their docs to stop being a mess — and neither requires XML.
When does structured authoring actually pay off (and when it doesn't)?
Read tinyurl.com/3xacfphz
#TechnicalWriting #TechComm #dita
Ann Green retweeted
PRD, MRD, BRD, Tech Spec, User Stories — same company, five different names, zero agreement on what they mean.
New article: a clear map of what each doc actually is, who writes it, and when you need it (and when you don't).
Full guide👉 tinyurl.com/mtc2f3pe
#TechComm #Docs
