Problem to solve

How might we reorganize our documentation to better answer the questions that developer have when evaluating and integrating with Stytch?

Customer research & pain points

In order to better understand the specific questions developers need answers to when evaluating Stytch, I conducted research with customers and ICP participants to develop key wayfinding painpoints and map out key moments in the Stytch user journey that our documentation needed to serve.

Strategy & milestones

To solve for these key wayfinding pain-points I isolated milestones we could ship iteratively while we overhauled the entire system. I up-leveled general find-ability with minor UX improvements like a new search experience, in-page linking, page breadcrumbs, and light nav design updates. I then was able to do design iterations on larger components like updated navigation groupings, new UI for top-level switching between sections, and an entirely new "Docs Home" section to create net new content to answer key evaluation questions.

‍

How might we answer developers questions, quickly? A new "Docs Home" experience

Developers know what they're looking for when evaluating a product, as well as building with one. With all of these improvements, the most major one was my designs for a new landing experience when a developer lands on our documentation that provides more guidance of why Stytch can solve their authentication and fraud needs. Since documentation is the most important marketing material developers use, this landing experience had to sell all key components of Stytch in common patterns developers are used to.

‍

‍

‍

Impact & learnings

We received great qualitative feedback from customers and we saw significant increases in navigation across all core verticals,. We saw upticks in navigation to the developer quickstarts, which are the most important pieces for developers to get a sense of how easily they can get up and running with Stytch.

‍

‍

‍