stytch

· 2023

Docs

Redesigning Docs, Stytch's developer documentation experience, ensuring users can navigate new changes driven by B2B product expansion.

See experience

Role

Product designer, Researcher

Team

Technical content manager, Engineering

Contributions

UX / UI design, Visual design, Research and usability testing

Context

Stytch, an authentication (auth) platform for consumer-based companies, decided to expand its product offerings to B2B companies.

This caused a bifurcation, separating products and content into two distinct categories: Consumer and B2B auth.

Problem

B2B auth differs from consumer auth, requiring changes across Stytch's various surface areas, including its developer documentation (Docs) which is known as the blueprint for developers to build their application.

Objective

Identify the downstream impacts of bifurcation and adjust stytch.com/docs to support the new auth type, guiding users to 1) determine the applicable auth type for their project, and 2) easily access and navigate the relevant documentation.

Defining

How do auth companies approach content reorganization? How does bifurcation fit into Stytch's current architecture?

To help align cross-functional partners, comparative research, auditing, and mapping helped teams visualize ripple affects and inconsistencies across various surface areas.

Design and iteration

While addressing inconsistencies in the user journey, I iterated on low to mid fidelity designs for high touchpoint CTAs and pages, including the landing page and home pages for both consumer auth and B2B auth.

From a visual and design systems perspective, I blended the the current Docs, Dashboard, and stytch.com styles together to keep scope tight.

Home page

Navigation

Research

To gather quick feedback and a pulse check on the direction of the designs, I consulted with the UX researcher to develop a test plan, including defining user scenarios, writing a script, and building prototypes.

Sourcing participants qualified through Respondent, I conducted 5 usability tests which revealed key patterns to guide Docs forward.

Results and impact

The Docs home page remains a hub for users, particularly developers, with continuous additions of new developer resources on this page.

New experience

Key learnings

01

Shared language is essential in a SaaS environment. I found it helpful to consistently prioritize defining and documenting new/changed terminology early, even if concepts were still evolving.

02

In early-stage startups, reliable data is often scarce, making it challenging to guide product and design decisions. In these cases, advocating for usability testing and close collaboration with Go-to-Market roles can provide helpful direction.

03

Executing a design project and influencing stakeholders through design require different skills. As a newcomer to Docs, collaborating with technical partners was key in driving conversations around resourcing for north star designs.

see other case studies

stytch

·

2023

Docs

Redesigning Docs, Stytch's developer documentation experience, ensuring users can navigate new changes driven by B2B product expansion.

See experience

See experience

See experience

Product designer, Researcher

Technical content manager, Engineering

UX / UI design, Visual design, Research and usability testing

Stytch, an authentication (auth) platform for consumer-based companies, decided to expand its product offerings to B2B companies. This caused a bifurcation, separating products and content into two distinct categories: Consumer and B2B auth.

B2B auth differs from consumer auth, requiring changes across Stytch's various surface areas, including its developer documentation (Docs) which is known as the blueprint for developers to build their application.

Identify the downstream impacts of bifurcation and adjust stytch.com/docs to support the new auth type, guiding users to 1) determine the applicable auth type for their project, and 2) easily access and navigate the relevant documentation.

Defining

How do auth companies approach content reorganization? How does bifurcation fit into Stytch's current architecture?To help align cross-functional partners, comparative research, auditing, and mapping helped teams visualize ripple affects and inconsistencies across various surface areas.

Design and iteration

Research

Results and impact

The Docs home page remains a hub for users, particularly developers, with continuous additions of new developer resources on this page.

01

Shared language is essential in a SaaS environment. I found it helpful to consistently prioritize defining and documenting new/changed terminology early, even if concepts were still evolving.

02

In early-stage startups, reliable data is often scarce, making it challenging to guide product and design decisions. In these cases, advocating for usability testing and close collaboration with Go-to-Market roles can provide helpful direction.

03

Executing a design project and influencing stakeholders through design require different skills. As a newcomer to Docs, collaborating with technical partners was key in driving conversations around resourcing for north star designs.

see other case studies

Stytch, an authentication (auth) platform for consumer-based companies, decided to expand its product offerings to B2B companies.

This caused a bifurcation, separating products and content into two distinct categories: Consumer and B2B auth.

How do auth companies approach content reorganization? How does bifurcation fit into Stytch's current architecture?

To help align cross-functional partners, comparative research, auditing, and mapping helped teams visualize ripple affects and inconsistencies across various surface areas.