Introduction
The challenge at hand involves evaluating and prioritizing customization requests from 10 Google Cloud customers, given limited engineering bandwidth. This scenario requires a strategic approach to customer selection, balancing individual needs with broader product goals and resource constraints.
I'll walk you through a structured decision-making process, focusing on customer evaluation criteria, potential impact assessment, and alignment with our product strategy.
Step 1
Clarifying Questions (3 minutes)
- Why it matters: Helps prioritize based on financial impact
- Hypothetical answer: Varied, ranging from $100K to $10M annually
- Impact: Will influence prioritization based on revenue potential
- Why it matters: Strategic relationships can have broader business implications
- Hypothetical answer: Two customers are Fortune 500 companies with potential for expansion
- Impact: May prioritize these customers for long-term growth opportunities
- Why it matters: Assesses complexity and potential for broader applicability
- Hypothetical answer: Mix of UI changes, API integrations, and performance optimizations
- Impact: Influences decision based on development effort and reusability
- Why it matters: Helps in scheduling and managing customer expectations
- Hypothetical answer: Varied urgency, from immediate needs to long-term roadmap items
- Impact: Affects prioritization and potential for phased implementation
- Why it matters: Assesses scalability and long-term product value
- Hypothetical answer: 30% of requests have potential for broader application
- Impact: Prioritizes features with wider appeal and long-term product enhancement
Practice similar questions
Subscribe to access the full answer