User-Story Driven Docs

Description

At OutSystems we make an awesome development platform, but our documentation wasn[HTML REMOVED]t that awesome. We focused on describing each button available on the user interface, and not the user intentions and goals. A clear example of this, was that we had a full documentation page for the find text feature (CTRL+F). It described in excruciating detail every option available on the UI, but didn[HTML REMOVED]t told our users how they could actually find what they needed! For us it was a nightmare to maintain the docs. Our development environment was constantly changing and we couldn[HTML REMOVED]t keep up with the changes. More importantly, we weren[HTML REMOVED]t meeting the user needs. And that was clear from pages with a single-digit page view, and from the feedback we got from our customers. Due to this approach, we also ended up having page titles that were feature-oriented, which is not the best for SEO. For instance, the doc page for the find text feature was called [HTML REMOVED]Find Tool[HTML REMOVED]. Who in their right mind would search for that on Google? In this talk I[HTML REMOVED]ll tell you the story of how we stopped trying to document the UI, and started creating user-story driven docs. We now focus on what the user wants to achieve and how to achieve it, independently of how many windows or buttons they need to go through. I[HTML REMOVED]ll cover: How you can check if you[HTML REMOVED]re documenting the UI, and why you should avoid doing it Why users stories work better for our users How focusing on user stories changed the culture of our team and allowed us to work on what really matters. I[HTML REMOVED]ll also share some unexpected outcomes, like how this lead us to work closer than ever with the development teams. Now our users get twice the cake: better features and better docs!