Need to share some of the top ideas that impressed me.
#writethedocs If you don’t have documentation, you don’t have a product. @therealpadams, I can’t agree more!
#writethedocs Great point by @therealpadams: The problem is Scrum. Think “Rugby”, where the Forward creates space, and the Backs are agile and get the ground.
#writethedocs Handy tip by @therealpadams: Backlog clearance method: get TW tasks out of the engineering team efforts into a separate user story or backlog.
#writethedocs @sarahleeyoga offers to measure your self-service ratio: # of article views divided by # of support tickets created.
#writethedocs Customer effort score: if it was too easy, it should have been self-service (=documentation). Second that, @sarahleeyoga!
#writethedocs Support uses tags for incoming issues: How to, Bugs, and Feedback. Everything tagged with “How to” should be covered either by docs or UX. That should be of real help to InfoDevs! Thanks for sharing, @sarahleeyoga
#writethedocs For sure, using support data and tickets data lets you calculate and show ROI. Talk by @sarahleeyoga
- What can I do with the API?
- What are the features (purpose) of the API?
- What’s the API architecture?
- How do I get the API up and running?
- How do I program with API?
- How can I test the code?