Do you struggle to make your documentation better? Are you overwhelmed by the feedback that you receive but somehow never manage to figure out how to make it better? Do you want to know more about how to deliver great documentation that pleases your customers?
If you answered “yes” to any of these questions, this session is for you!
Information architecture is a field that helps us, the technical communicators, organize structure large sets of information logically. Information architecture helps you to better structure and organize the guides you are writing, no matter if they are large or small documents.
If you are serious about technical writing, you should also know the main information architecture principles. They will help you deliver the best possible documentation for your readers.
Which are these core principles to follow? And how does a field that is applied so widely by user experience (UX) designers and librarians can be leveraged by you?
- Information architecture and how it applies to documentation development (in particular, the focus is on software documentation)
- 4 information architecture principles that make your documentation better:
- User research and analysis
- Deliverables and delivery channels
- Delivery models
- Data modeling
Jordan Stanchev is a User Assistance Development Architect at SAP.
In this role, he has lead numerous projects related to information architecture, metadata, taxonomies, and writing using DITA XML for more than 1000 authors of the company.
He is also one of the founders of tekom Bulgaria.