![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
I'm working on a doc plan for a new project, and instead of diving in and creating a document outline, I'm writing:
A description of who the intended audience for the documentation is, and what they need.
A description of the purpose of each intended documentation deliverable, what it needs to include to help users succeed, and what it shouldn't include.
And a list of open questions that I need answered by the product manager and/or the development team before I can have confidence in the first two items.
I appear to have absorbed something from all the content strategy conferences I got sent to last year.
Let's see if this provokes more fruitful discussion than a typical doc plan review.
A description of who the intended audience for the documentation is, and what they need.
A description of the purpose of each intended documentation deliverable, what it needs to include to help users succeed, and what it shouldn't include.
And a list of open questions that I need answered by the product manager and/or the development team before I can have confidence in the first two items.
I appear to have absorbed something from all the content strategy conferences I got sent to last year.
Let's see if this provokes more fruitful discussion than a typical doc plan review.
