Interview Q- How to Gather and address feedback from multiple sources

How to Gather and address feedback from multiple sources

Here are some interview questions related to gathering and addressing feedback from multiple sources, specifically tailored for a Technical Writer in the ITSM and DITA domain:

General Process Questions:

1. How do you gather feedback from different stakeholders (e.g., SMEs, developers, support teams, and end-users) for your documentation?
2. What strategies do you use to ensure that feedback is relevant, actionable, and prioritized correctly?
3. How do you handle conflicting feedback from multiple sources?
4. Can you describe a time when you had to incorporate feedback that significantly changed the structure or approach of your documentation?

DITA and ITSM-Specific Questions:

5. How do you collect and incorporate feedback into a DITA-based documentation workflow while maintaining structured authoring best practices?
6. What role does a CCMS (e.g., IXIASOFT, Astoria, Vasont, or Heretto) play in managing and tracking feedback?
7. How do you leverage ITSM tools like ServiceNow, BMC Helix, or Jira Service Management to collect feedback from users and support teams?
8. What techniques do you use to integrate feedback loops into DITA-OT publishing workflows?

Tools and Automation Questions:

9. Have you implemented any automated processes (e.g., using APIs, scripts, or plugins) to collect and manage feedback? If so, can you describe the implementation?
10. How do you track and manage documentation feedback when working in tools like FrameMaker and Oxygen XML Editor?
11. What are the best practices for using annotations, review comments, or version control in a collaborative documentation environment?

Real-World Scenario Questions:

12. Suppose a product manager requests a major change in terminology, but a senior SME insists on keeping the existing terminology. How would you handle this situation?
13. How do you ensure that feedback from end-users (e.g., ITSM tool customers) is incorporated effectively while aligning with organizational documentation standards?
14. How do you ensure that documentation updates based on feedback do not disrupt structured content reuse and single-sourcing principles?
15. Can you give an example of a time when feedback significantly improved the usability of ITSM documentation?