How should CDK Global balance adding new features to its Dealer Management System versus maintaining system stability and performance?

Introduction

Balancing new feature development with system stability and performance is a critical challenge for CDK Global's Dealer Management System (DMS). This trade-off involves weighing the benefits of innovation against the risks of system instability. I'll analyze this situation using a structured approach, considering business objectives, user needs, technical constraints, and long-term strategic implications.

Step 1

Clarifying Questions (3 minutes)

• Based on the competitive landscape, I'm thinking feature additions might be driven by market pressure. Could you share insights on our main competitors' recent DMS updates?

Why it matters: Helps prioritize features based on market positioning Expected answer: Competitors have added AI-driven inventory management Impact on approach: Would focus on high-impact, differentiating features

• Considering our revenue model, I assume the DMS is subscription-based. What's the current churn rate, and how does it relate to system performance issues?

Why it matters: Balances feature development with retention efforts Expected answer: 5% annual churn, 30% citing performance issues Impact on approach: Would prioritize stability improvements alongside careful feature rollouts

• Looking at user segments, I'm guessing larger dealerships might have different needs. How does our user base break down by dealership size, and do we see varying feature requests or performance complaints?

Why it matters: Tailors solution to most impactful user segments Expected answer: 60% small, 30% medium, 10% large; larger dealers more concerned with advanced features Impact on approach: Would consider segmented feature rollouts and performance optimizations

• Regarding technical architecture, I'm curious about our current scalability. What's our current system load, and how close are we to capacity limits?

Why it matters: Determines feasibility of adding features without compromising performance Expected answer: Operating at 70% capacity during peak hours Impact on approach: Would necessitate infrastructure upgrades alongside feature development

• Thinking about our development resources, what's the current split between feature development and maintenance/performance optimization?

Why it matters: Assesses current resource allocation and potential for reallocation Expected answer: 70% feature development, 30% maintenance Impact on approach: Might suggest rebalancing resources towards stability before major feature additions