How would you measure the success of Auth0's Single Sign-On (SSO) feature?

Introduction

Measuring the success of Auth0's Single Sign-On (SSO) feature requires a comprehensive approach that considers multiple stakeholders and metrics. To effectively evaluate this product success metrics problem, I'll follow a structured framework covering core metrics, supporting indicators, and risk factors while considering all key stakeholders.

Step 1

Product Context

Auth0's Single Sign-On (SSO) is a critical feature that allows users to access multiple applications with a single set of credentials. It's designed to enhance security, improve user experience, and streamline access management for organizations.

Key stakeholders include:

1. End-users: Seeking seamless access across multiple applications
2. IT administrators: Looking to simplify access management and enhance security
3. Application developers: Aiming to integrate SSO easily into their products
4. Auth0 (now part of Okta): Focused on growing market share and revenue

User flow:

1. User attempts to access an application
2. SSO redirects to centralized login page
3. User enters credentials once
4. SSO authenticates and grants access to multiple applications

Auth0's SSO fits into the company's broader strategy of providing comprehensive identity and access management solutions. It competes with other identity providers like Okta (pre-acquisition), Microsoft Azure AD, and OneLogin.

In terms of product lifecycle, SSO is in the growth stage, with continuous feature enhancements and expanding market adoption.