Should Ping Identity prioritize enhancing the user interface of PingOne for simpler customer onboarding or focus on adding advanced security features to appeal to enterprise clients?

Introduction

The trade-off we're examining today is whether Ping Identity should prioritize enhancing the user interface of PingOne for simpler customer onboarding or focus on adding advanced security features to appeal to enterprise clients. This scenario touches on the classic product management challenge of balancing user experience improvements with technical feature development, particularly in the context of a B2B identity and access management solution.

In my response, I'll walk through a structured analysis of this trade-off, considering key stakeholders, metrics, and potential outcomes. We'll explore the product context, design an experiment to test our hypotheses, and ultimately arrive at a recommendation with clear next steps.

Step 1

Clarifying Questions (3 minutes)

• Context: Based on the framing of the question, I'm thinking PingOne might be facing challenges with customer adoption or retention. Could you provide more context on the current state of PingOne in terms of market share and customer feedback?

Why it matters: Helps understand the urgency and potential impact of the trade-off Expected answer: PingOne has strong market share but faces increasing competition Impact on approach: Would influence whether we prioritize retention or acquisition

• Business Context: I'm assuming our revenue model is primarily subscription-based for enterprise clients. Is this correct, and are there any specific revenue targets or growth goals we're trying to meet this year?

Why it matters: Aligns solution with business objectives and revenue strategy Expected answer: Subscription-based model with aggressive growth targets Impact on approach: Would inform whether to focus on new client acquisition or upselling existing clients

• User Impact: Thinking about our user base, I'm curious about the split between small-to-medium businesses and large enterprises. Can you share some insights on our current customer composition and which segment is growing faster?

Why it matters: Helps tailor the solution to the most impactful user segment Expected answer: Mix of SMB and enterprise, with enterprise growing faster Impact on approach: Would influence whether to prioritize simplicity for SMBs or advanced features for enterprises

• Technical: Regarding the advanced security features, I'm wondering about the technical complexity and timeline for implementation. Do we have an estimate for the development time and resources required?

Why it matters: Assesses feasibility and opportunity cost of feature development Expected answer: Significant development effort, estimated 6-9 months Impact on approach: Would affect the trade-off calculation and potential phasing of improvements

• Resource: Considering our current team structure, do we have dedicated UX/UI resources available for enhancing the user interface, or would this require hiring or reallocating team members?

Why it matters: Determines the feasibility and speed of UI improvements Expected answer: Limited UX/UI resources currently available Impact on approach: Would influence the timeline and potential outsourcing decisions