How might Temporal enhance its SDK language support to streamline development across more programming environments?

Introduction

Enhancing Temporal's SDK language support to streamline development across more programming environments is a critical initiative that could significantly impact our product's adoption and user satisfaction. This improvement aligns with the evolving needs of our diverse developer base and the rapidly changing landscape of software development. I'll approach this challenge by first clarifying our current position and goals, then analyzing our user segments and their pain points. From there, I'll propose and evaluate solutions, and finally outline a measurement strategy to track our success.

Step 1

Clarifying Questions (5 mins)

• Looking at Temporal's position in the workflow orchestration space, I'm thinking about our current market penetration and growth strategy. Could you share insights on our current user base size and growth rate across different programming languages?

Why it matters: This helps us prioritize which languages to focus on for maximum impact. Expected answer: We have a strong presence in Go and Java, with growing adoption in Python and JavaScript. Impact on approach: Would focus on strengthening support for rapidly growing languages while maintaining our core offerings.

• Considering the evolving landscape of cloud-native development, I'm curious about our users' deployment preferences. What's the breakdown of our users deploying Temporal in cloud environments versus on-premises?

Why it matters: This influences the direction of our SDK improvements to align with deployment trends. Expected answer: 70% cloud, 30% on-premises, with cloud adoption increasing. Impact on approach: Would prioritize features that enhance cloud-native development experiences.

• Given the importance of developer experience, I'm interested in understanding our current SDK satisfaction metrics. Do we have Net Promoter Score (NPS) or other feedback data specific to our SDK offerings across different languages?

Why it matters: Helps identify which SDKs need the most improvement and why. Expected answer: Go and Java SDKs have high satisfaction, while others lag behind. Impact on approach: Would focus on bringing other SDKs up to par with our best-performing ones.

• Thinking about our product roadmap, I'm wondering about our broader strategic goals. Are we aiming to expand into new verticals or deepen our presence in existing markets?

Why it matters: Aligns our SDK improvements with overall company direction. Expected answer: Focus on deepening presence in existing markets while cautiously exploring new verticals. Impact on approach: Would prioritize improvements that cater to our core users while ensuring flexibility for potential new use cases.