I've spent over a decade moving between software development and technical writing, and the workflow that's changed the most in the last two years isn't how I write — it's how I turn scattered, undocumented knowledge into something structured before I write a single line of user-facing content.
The hard part of documentation was never sentence construction. It's extracting a coherent model from an engineer's head, a half-updated wiki, and three Slack threads, and turning that into something a user can follow without guessing. That extraction step is slow, and it's where most documentation projects stall.
What I've found genuinely useful is treating an LLM as a structured interview partner during that extraction phase — not as an autocomplete for prose.
It's not "ask AI to write the docs." Docs written that way read like they were written for no one in particular, because they were. The value is entirely in step 2 — using the model to interrogate a messy corpus faster than I could alone — and step 4, where judgment about the actual reader still has to come from a human.
Developer-facing documentation lives or dies on precision: an inaccurate parameter description or a skipped edge case costs a user real debugging time. An LLM-assisted workflow doesn't lower that bar — if anything, using the model to cross-check a draft against source code or an OpenAPI spec catches inconsistencies a purely manual pass might miss on a tight deadline. The discipline that made technical writing rigorous before AI — versioning, testing docs against real user tasks, treating documentation like a product — is exactly what keeps an AI-assisted workflow honest.