interesting thread! 
the suggestion for some kind of task-based material that walks users through different use cases sounds good to me, as does the suggestion that we come up with ten to twenty use cases first.
i think a fantastic place to start might be beck tench’s videos as she works through understanding a book.
i’m starting a very tiny nomenclature dive as an effort to figure out how to provide precise definitions and instructions that doesn’t run afoul of new legislation.
i’m also wondering if it’s time to start assembling content for a latin grammar which is presented through stories.
these are all very…?…text-y. would people in marketing find this useful? what about developers (API documentation?). speaking of, i’m always thinking about whether or not tinderbox might be a good “textbase” for documenting ui copy such as error messages, dialogs, banners, and other in-app ui copy.
do these use cases start to provide a path for task-based documentation?