AI can write your docs. It can’t tell you when they’re done

What you’ll see

• Why “document the new feature” isn’t a task — a product change and the documentation work it creates are two different things, and the gap between them is where most of the value is lost
• What context a request has to carry — the information that used to live in someone’s head, why AI can’t invent it, and what happens to the output when it’s missing
• How much of that context AI can now gather itself — what changes when an assistant can go and check what already exists instead of waiting to be told
• What “done” means when nobody wrote it by hand — a definition of done built on what the user has to be able to do, which is the only version that survives contact with generated text

Who should attend

This session is for anyone who answers for documentation without producing all of it themselves.

• Product Managers — documentation arrived with the feature, and you’re the one deciding what a release means for your users
• Technical Writers — your job has shifted from producing pages to deciding what gets produced and accepting what other people and AI wrote
• Support and CS Leads — you see the cost of unclear documentation before anyone else does, and you’re rarely asked what should have been written
• Engineering Leads — your team ships the change, and nobody has agreed what has to exist afterwards or who calls it finished

What you get for registering

• Free enrollment in our new email course — 6 Steps to Documentation You Don’t Write: six lessons on running documentation you don’t produce yourself. Built on conversations with 60+ product and documentation teams, and not published anywhere else yet
• Live Q&A with Ian — bring your own situation
• Recording access — rewatch and share with your team