Contents
In a typical technical communication development process, we rely on reviewers to ensure our content meets legal, corporate, and user requirements. New requirements are often identified at the end of the development process, which requires last minute revisions and causes product delays. In a requirements-driven process, the requirements are identified first, and they drive the content's creation, design, and maintenance. In this session, we will
Takeaways
* How to develop a requirements-driven development process
* How to use intelligent content to develop and maintain documentation
* How to use requirement-based intelligent content to enhance the user experience
Prior knowledge
* knowledge of a technical documentation creation and maintenance process and common challenges/issues
* curiosity about improving efficiency/automation