Friday and we have another Readings issue on content. Today’s issue includes taxonomy standards, IA for phone, DITA2.0. ROI of documentation, Confluence for UX documentation, headless and not brainless CMS, and Minimum Viable Content!
We wanted to look at: how many support calls an organisation needs to have resolved by users reading the Help content instead of calling Support, before it starts to see a return on the cost of creating the Help.
The problem-solving information our Technical Authors create can also attract prospects to your website. It helps convert your trial users into paying clients. It can also reduce your support team’s workload.