Should Jobber prioritize adding more advanced scheduling features to its field service management software or focus on simplifying the user interface for better adoption among small businesses?

Introduction

The trade-off we're examining today is whether Jobber should prioritize adding more advanced scheduling features to its field service management software or focus on simplifying the user interface for better adoption among small businesses. This scenario touches on the classic product management challenge of balancing feature depth with user accessibility. I'll approach this analysis by first clarifying key aspects of the situation, then diving into a structured evaluation of both options, considering their impacts on various stakeholders and metrics.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming Jobber is targeting small to medium-sized field service businesses. Could you confirm if this is still our primary market, or if we're looking to expand into larger enterprises?

Why it matters: Influences feature complexity and UI simplicity needs Expected answer: Primarily small businesses, with some mid-sized companies Impact on approach: Would lean towards UI simplification if confirmed

• Business Context: Based on our current growth trajectory, I'm thinking user acquisition might be a key priority. How does this trade-off align with our current fiscal year objectives?

Why it matters: Helps prioritize between depth (retention) and simplicity (acquisition) Expected answer: Balanced growth, with a slight emphasis on new user acquisition Impact on approach: Might favor UI simplification for easier onboarding

• User Impact: Considering our user base, I'm hypothesizing that many of our customers might not be tech-savvy. What's the typical tech proficiency level of our target users?

Why it matters: Determines the level of complexity our users can handle Expected answer: Varied, but skewing towards basic to intermediate tech skills Impact on approach: Could strongly influence the decision towards UI simplification

• Technical: Given our current architecture, I'm wondering about the feasibility of implementing advanced scheduling features. What's our engineering team's assessment of the technical complexity for both options?

Why it matters: Affects timeline and resource allocation Expected answer: Advanced features more complex, UI simplification more straightforward Impact on approach: Might favor UI simplification if advanced features are significantly more complex

• Resource: Considering our product team structure, I'm curious about our capacity for these initiatives. Do we have dedicated teams for both UI/UX and advanced feature development?

Why it matters: Influences our ability to execute on either option effectively Expected answer: Smaller UI/UX team, larger feature development team Impact on approach: Might need to consider team reallocation or hiring for UI simplification