Should Lattice prioritize adding more customization options to performance reviews, potentially increasing complexity, or focus on simplifying the process for better user adoption?

Introduction

The trade-off between adding more customization options to performance reviews and simplifying the process for better user adoption is a critical decision for Lattice. This scenario touches on the core functionality of the product and its impact on user experience. I'll analyze this trade-off by examining the product context, potential impacts, key metrics, and experimental approaches to inform a strategic recommendation.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about Lattice's current market position. Could you share insights on our market share and primary competitors in the performance management space?

Why it matters: Helps understand competitive pressures and user expectations Expected answer: Mid-market leader with 20-30% share, competing with Workday and 15Five Impact: High market share might favor simplification, while lower share could justify more customization

• Business Context: Based on our revenue model, I assume customization impacts our pricing tiers. How does our current pricing structure relate to customization features?

Why it matters: Aligns product strategy with revenue goals Expected answer: Higher tiers offer more customization Impact: Could influence whether to make customization a premium feature or simplify across all tiers

• User Impact: Considering user segments, I'm curious about the adoption rates across different company sizes. How do small businesses vs. enterprise clients use our customization features?

Why it matters: Identifies which user segments might benefit most from each approach Expected answer: Enterprises use more customization, SMBs prefer simplicity Impact: Could lead to a segmented approach rather than one-size-fits-all

• Technical Feasibility: Given our current architecture, I'm wondering about the technical complexity of adding more customization. What's our engineering team's assessment of the effort required?

Why it matters: Determines resource allocation and timeline Expected answer: Moderate complexity, 3-4 month development cycle Impact: High complexity might favor simplification, while low complexity could support more customization

• Timeline: Considering our product roadmap, how urgent is this decision in relation to other priorities?

Why it matters: Helps prioritize this decision against other initiatives Expected answer: Critical for next quarter's release Impact: High urgency might lean towards simplification for quicker implementation