For UKG's Dimensions scheduling software, should we invest in developing more industry-specific features or concentrate on improving core functionality that benefits all customers?

Introduction

The trade-off we're examining today is whether UKG's Dimensions scheduling software should invest in developing more industry-specific features or concentrate on improving core functionality that benefits all customers. This decision is crucial for UKG's product strategy and market positioning. I'll analyze this trade-off by considering user needs, market dynamics, and potential business impacts.

Step 1

Clarifying Questions (3 minutes)

• Based on the current market landscape, I'm thinking UKG might be facing increased competition. Could you share insights on our market position and primary competitors?

Why it matters: Helps determine if we should focus on differentiation or strengthening core offerings. Expected answer: UKG is a market leader but facing pressure from niche, industry-specific solutions. Impact on approach: Would influence whether to prioritize industry-specific features or core functionality.

• Considering our revenue model, I assume we have a mix of enterprise and SMB customers. What's the current revenue split between these segments?

Why it matters: Different customer segments may have varying needs and priorities. Expected answer: 70% enterprise, 30% SMB. Impact on approach: Would help determine which customer segment to prioritize in our decision.

• Regarding user impact, I'm curious about our customer satisfaction scores. Have we seen any trends in feature requests or pain points across industries?

Why it matters: Identifies areas of improvement and potential opportunities. Expected answer: Increasing demand for industry-specific features, but also complaints about core functionality. Impact on approach: Would help balance the trade-off between specialized and general improvements.

• From a technical perspective, how modular is our current architecture? Could we easily add industry-specific modules without disrupting core functionality?

Why it matters: Affects the feasibility and resource requirements of each option. Expected answer: Moderately modular, but would require some refactoring for industry-specific features. Impact on approach: Would influence the cost-benefit analysis of each option.

• Considering our development resources, what's our current team capacity and how is it allocated between maintenance and new feature development?

Why it matters: Determines our ability to pursue either option effectively. Expected answer: 60% maintenance, 40% new features, with limited bandwidth for major initiatives. Impact on approach: Would impact the timeline and scope of potential solutions.