The fear about AI in a writing team is that it comes for the writing. In my experience it comes for something better: the toil.
A documentation team drowns in the un-fun middle — auditing hundreds of pages for a renamed feature, reconciling five slightly-different install guides, checking whether the screenshots still match the product. This is exactly the work a machine should do. Give it the toil.
What you keep is judgment: deciding what’s worth documenting, what a reader is actually afraid of, where the real ambiguity lives. That doesn’t scale by hiring — it scales by leverage. A small team with good tools and clear taste will out-ship a large team without either.
So the question I ask about any new AI workflow isn’t “can it write?” It’s “does it give my writers back the hours they spend on things no human should have to do?” If yes, adopt it. The writing was never the bottleneck.