Should Solo.io focus on expanding Gloo Edge's plugin ecosystem or on simplifying its core functionality for easier adoption?

Introduction

The trade-off question at hand is whether Solo.io should focus on expanding Gloo Edge's plugin ecosystem or simplifying its core functionality for easier adoption. This scenario involves balancing the depth and extensibility of Gloo Edge against its ease of use and accessibility. I'll approach this analysis by examining the product context, evaluating potential impacts, and proposing a data-driven decision framework.

Step 1

Clarifying Questions (3 minutes)

• Based on Gloo Edge's positioning, I'm thinking it might be targeting enterprise customers. Could you confirm the primary market segment for Gloo Edge?

Why it matters: Helps tailor the solution to the right user base Expected answer: Enterprise-focused with some mid-market traction Impact on approach: Would influence the balance between advanced features and simplicity

• Considering the competitive landscape, I'm assuming Gloo Edge generates revenue through a subscription model. Is this correct, and are there any other significant revenue streams?

Why it matters: Aligns product strategy with business model Expected answer: Primarily subscription-based with some professional services Impact on approach: Would affect the prioritization of features vs. ease of adoption

• Looking at user behavior, I'm curious about the current adoption rate and user feedback. What percentage of users are actively using plugins, and what's the most common feedback about the core functionality?

Why it matters: Identifies current pain points and opportunities Expected answer: 30% plugin usage, feedback indicates complexity in setup Impact on approach: Would guide the focus between ecosystem expansion and simplification

• Regarding technical feasibility, I'm wondering about the current architecture. How modular is Gloo Edge, and what would be involved in simplifying its core?

Why it matters: Determines the effort required for each option Expected answer: Modular architecture, but simplification requires significant refactoring Impact on approach: Would influence the timeline and resources needed for each path

• Considering resource allocation, I'm curious about the current team structure. How are engineering resources split between core product development and ecosystem support?

Why it matters: Assesses capacity for different initiatives Expected answer: 70% core, 30% ecosystem Impact on approach: Would impact the feasibility of pursuing both options simultaneously