Should Grafana Labs prioritize expanding Loki's scalability for large deployments or improving its ease of use for new adopters?

Introduction

The trade-off we're examining today is whether Grafana Labs should prioritize expanding Loki's scalability for large deployments or improving its ease of use for new adopters. This decision is crucial for Loki's growth strategy and market positioning. 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)

• Based on Loki's current market position, I'm thinking scalability might be a key differentiator. Could you share more about our current market share and primary competitors?

Why it matters: Helps understand competitive landscape and potential growth areas Expected answer: Moderate market share, competing with established players Impact on approach: Would influence whether to focus on enterprise or new user acquisition

• Considering user adoption trends, I'm curious about our current user base composition. What's the split between large enterprise deployments and smaller teams or individual developers?

Why it matters: Identifies which user segment might benefit most from each option Expected answer: Mix of enterprise and smaller deployments, with growing interest from startups Impact on approach: Would help prioritize features based on user segment needs

• Looking at our revenue model, I'm wondering how Loki's pricing structure aligns with scalability and ease of use. Is our pricing primarily based on data volume, user count, or a combination?

Why it matters: Helps understand financial implications of each option Expected answer: Tiered pricing based on data volume with some user-based components Impact on approach: Would influence whether to focus on features that drive data volume or user count

• Considering our engineering resources, I'm thinking about the technical complexity of each option. How does our current team capacity and expertise align with scalability improvements versus UX enhancements?

Why it matters: Assesses feasibility and potential timeline for each option Expected answer: Strong backend team, growing UX resources Impact on approach: Would help determine which option is more achievable in the short term

• Given the rapid evolution of observability tools, I'm curious about our product roadmap. Are there any major feature releases or integrations planned that might influence this decision?

Why it matters: Ensures alignment with broader product strategy Expected answer: Upcoming integrations with popular cloud services Impact on approach: Would help prioritize features that complement planned integrations