What metrics would you use to evaluate Ping Identity's PingFederate single sign-on solution?

Introduction

Evaluating the success of PingFederate's single sign-on (SSO) solution requires a comprehensive approach that considers multiple stakeholders and various aspects of the product's performance. To address this product success metrics challenge, I'll follow a structured framework covering core metrics, supporting indicators, and risk factors while considering all key stakeholders.

Step 1

Product Context

PingFederate is an enterprise-grade SSO solution that enables organizations to provide secure, seamless access to multiple applications and services using a single set of credentials. It's a critical component of Ping Identity's identity and access management (IAM) suite, designed to improve user experience, enhance security, and streamline IT operations.

Key stakeholders include:

1. End-users: Employees, partners, and customers who need access to various applications
2. IT administrators: Responsible for implementing and managing the SSO solution
3. Security teams: Focused on maintaining the organization's overall security posture
4. Business leaders: Interested in productivity gains and cost savings

User flow:

1. User attempts to access a protected application
2. PingFederate intercepts the request and initiates authentication
3. User provides credentials (or uses existing session)
4. PingFederate validates credentials and creates/updates session
5. User is granted access to the application

PingFederate fits into Ping Identity's broader strategy of providing comprehensive IAM solutions for enterprises. It competes with products like Okta and Microsoft Azure AD, differentiating itself through its flexibility and support for complex enterprise environments.

Product Lifecycle Stage: PingFederate is a mature product in the growth stage, with ongoing feature enhancements and integrations to maintain its market position.