How can Looker balance the depth of customization in its dashboards with the need for faster, out-of-the-box solutions for new users?

Introduction

Balancing the depth of customization in Looker's dashboards with the need for faster, out-of-the-box solutions for new users presents a critical product trade-off. This scenario involves weighing the power of advanced customization against the ease of quick adoption for newcomers. I'll analyze this trade-off by examining user needs, business implications, and potential solutions.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about Looker's position in the competitive BI landscape. Could you share insights on our market share and primary competitors?

Why it matters: Helps frame the urgency and scale of this trade-off. Expected answer: Looker has a strong position but faces competition from Tableau and Power BI. Impact: High competition might push us towards faster solutions, while a dominant position allows for deeper customization focus.

• Business Context: Based on our revenue model, I assume customization services contribute significantly. How much of our revenue comes from customization vs. standard licenses?

Why it matters: Determines the financial impact of shifting towards out-of-the-box solutions. Expected answer: 30% from customization services, 70% from licenses. Impact: Higher customization revenue would make us more cautious about simplifying too much.

• User Impact: I'm curious about our user segmentation. What percentage of our users are power users vs. casual or new users?

Why it matters: Helps balance the needs of different user groups. Expected answer: 20% power users, 80% casual/new users. Impact: A higher percentage of new users would prioritize out-of-the-box solutions.

• Technical: Regarding our current architecture, how modular is our dashboard system? Could we easily implement a tiered approach?

Why it matters: Determines the feasibility of a hybrid solution. Expected answer: Moderately modular, would require some refactoring. Impact: High modularity would allow for a more nuanced approach to this trade-off.

• Timeline: Considering our product roadmap, is there a specific timeline or upcoming release we're targeting for addressing this trade-off?

Why it matters: Influences the scope and urgency of our solution. Expected answer: Aiming for improvements in the next major release, 6 months out. Impact: A shorter timeline might favor quicker, out-of-the-box solutions, while a longer one allows for more comprehensive changes.