PROJECT SUMMARY
Documentation is the most important product that an API-first company can build, and at Stytch, no matter how well written our documentation was, as the company scaled and released new features, our documentation needed to grow up with us.
The Big PICture
Customer research & pain points
Conducted research with customers and ICP participants to develop understanding about main wayfinding painpoints as well as key moments in the Stytch user journey our documentation needed to serve
Strategy & milestones
With a big architecture overhaul like this one I developed core milestones we could execute on as a team in concert with one another so we could ship iterative impact quickly while chipping away at the larger people problems
"As a developer, all that matters is docs. New company? Bad docs? Don't care." - Research participant
final thoughts
Information systems that scale
Most importantly was developing an architecture and system that would allow us to ship new products and grow as a product while being able to have clean and clear documentation at scale
How might we answer developers questions, quickly?
Developers know what they're looking for when evaluating a product, as well as building with one. We had to make sure to be able to answer all the questions a developer might have at any point in the user journey all in one intuitive wayfinding system. We implemented a more powerful search, in-page outline, breadcrumbs, and switcher, all with this in mind.
"New docs look slick"
