Should Cornerstone OnDemand prioritize adding more features to its Learning Management System or focus on simplifying the user interface for better adoption rates?

Introduction

The trade-off we're examining today is whether Cornerstone OnDemand should prioritize adding more features to its Learning Management System (LMS) or focus on simplifying the user interface for better adoption rates. This scenario touches on the classic product management dilemma of feature richness versus usability. I'll analyze this trade-off by considering the business context, user impact, technical feasibility, and strategic implications.

Step 1

Clarifying Questions (3 minutes)

• Based on recent market trends, I'm thinking Cornerstone might be facing increased competition. Could you share insights on our current market position and how it's evolving?

Why it matters: Helps contextualize the urgency of this decision Expected answer: Increasing competition, need to differentiate Impact on approach: May lean towards feature addition if differentiation is critical

• Considering our revenue model, I assume LMS is a core product. What percentage of our revenue does it represent, and how's its growth trajectory?

Why it matters: Determines the strategic importance of this decision Expected answer: Significant revenue contributor with slowing growth Impact on approach: Might prioritize UI simplification for broader adoption

• Looking at user segments, I'm curious about our primary users. Are they mainly HR professionals, or do we have a significant number of end-users (employees) directly interacting with the LMS?

Why it matters: Influences the balance between power features and ease of use Expected answer: Mix of HR admins and employees, with growing emphasis on employee experience Impact on approach: Could suggest a two-tiered UI approach

• Regarding our engineering capacity, I'm wondering about our ability to execute on both fronts. Do we have separate teams for feature development and UI/UX, or would this be a direct trade-off of resources?

Why it matters: Affects the feasibility of pursuing both options simultaneously Expected answer: Limited resources, need to prioritize one direction Impact on approach: Might lead to a phased strategy rather than an either/or decision

• Considering our product roadmap, I'm thinking about how this decision aligns with our long-term vision. Are there any major platform changes or integrations planned that could influence this decision?

Why it matters: Ensures alignment with broader product strategy Expected answer: Plans for API expansion and ecosystem development Impact on approach: Could favor feature addition if it supports ecosystem growth