Articles about Documentation
The Politics of Design Systems: Keeping Stakeholders and UX Teams Invested Through the Process
Design systems require significant organizational effort. Its champions can follow these practical tips to gain buy-in and create a clear vision for its future. [Read More]
What to Write: Communicating Based on User Need
Corporate writers explain six reasons why people read documentation, and how the writer's style of writing changes based the user's need and motivation. [Read More]
Collaboration with the Front Line: Designing for Support
Observation, gamestorming, co-creation exercises, and storyboards let a customer support team help design a chat interface, and taught the UX team the value of collaboration. [Read More]
Writing Tutorials That Actually Help Users: Communication for Learning
An effective tutorial supports user modifications and guides them through errors so that, using your UI, they can achieve their goals. [Read More]
Role Reversal: Testing for Ease of Learning and Recall
When testing a software package, include traditional roles found in a pyramidal training model but also a reversed, "train the trainer" round. [Read More]
Help! Where Is It When You Need It?
Provide form instructions on a separate web page and place a “Help” link at the beginning to help users who prefer or require “up front” instructions to complete the form. [Read More]
Capturing User Requirements in Health and Social Care: Applying UML for unambiguous communication
An approach to the Unified Modeling Language that captured what is possibly the most comprehensive set of aging healthcare requirements documented in Australia, and possibly worldwide. [Read More]
