This session is intended for all writers who are interested in knowing more about getting feedback from customers about the documentation they created with a lot of effort.

Enable the Customers to let them tell you what they Need

Customer engagement brings immediacy, simplicity, and relevance thus ensuring quality product development. Unless you know the audience, you will not be able to cater to their demands.

Design Thinking workshops have proved beyond doubt that early interactions with customers have saved a lot of time and rework in product development.

Similarly, customer engagement workshops for product documentation would also help us in writing documents that are tailored to the needs of our customers. This would also help us to understand the 3 Ws – Whom, What, and Why.

Through a case study, we would like to share:

• Our experience with a Customer Engagement workshop for our API documentation
• How the interaction with our customers helped us in developing a documentation strategy that focuses on reducing rework and reducing support tickets
• Hw to plan and prepare for a customer engagement workshop We would also like to share some tips and tricks on how to stay focused on

DOCUMENTATION

This is the major concern when customers also initiate discussions relevant to development requests during these interactions. Any such workshop needs proper closure, and we will also demonstrate some feedback closure tips.

We will show the Do’s and Don’ts of running a Customer Engagement Workshop for documentation deliverables.

Takeaways

1. How to start planning for the workshop?
2. How to organize the calls?
3. How to make the call focused on documentation aspects only?
4. How to identify action items for improvement and implement the changes? 
5. Present a case study about ” Customer Engagement Workshop for API documentation”