Should Temporal prioritize expanding language SDK support or improving existing SDKs' performance and stability?

Introduction

The trade-off question at hand is whether Temporal should prioritize expanding language SDK support or improving existing SDKs' performance and stability. This scenario involves balancing the breadth of our product offering against the depth and quality of our current solutions. I'll approach this analysis by examining the context, evaluating potential impacts, and proposing a data-driven decision framework.

Step 1

Clarifying Questions (3 minutes)

• Context: Based on Temporal's position in the workflow orchestration market, I'm thinking we might be at a critical growth stage. Could you provide more context on our current market share and primary competitors?

Why it matters: Helps determine if expansion or consolidation is more strategic Expected answer: Growing market share, facing pressure from established players Impact on approach: Would influence whether to focus on new user acquisition or existing user retention

• Business Context: Considering our revenue model, I assume we charge based on usage or have a tiered pricing structure. Is this correct, and how does SDK adoption impact our revenue?

Why it matters: Aligns product strategy with business model Expected answer: Usage-based pricing, SDK adoption directly correlates with revenue Impact on approach: Would prioritize actions that drive SDK adoption and usage

• User Impact: I'm thinking about our user segments. Can you tell me more about the distribution of our users across different programming languages and their typical use cases?

Why it matters: Identifies potential high-impact areas for expansion or improvement Expected answer: Diverse user base with some languages dominating Impact on approach: Would focus efforts on either underserved segments or optimizing for power users

• Technical Feasibility: Regarding our current SDK architecture, how modular is it? Would improvements to one SDK easily translate to others?

Why it matters: Determines efficiency of improvement efforts Expected answer: Moderately modular, some shared components Impact on approach: Would influence whether to focus on cross-cutting improvements or language-specific optimizations

• Resource Allocation: Can you give me an idea of our current engineering team structure? Are we organized by language SDK or by cross-functional features?

Why it matters: Assesses our ability to execute on different strategies Expected answer: Mix of language-specific and cross-functional teams Impact on approach: Would inform how to allocate resources for maximum impact