For Domo's data integration tools, should we emphasize expanding the number of supported data sources or enhancing the depth of integration with existing popular connectors?

Introduction

The trade-off we're examining today is whether Domo's data integration tools should focus on expanding the number of supported data sources or enhancing the depth of integration with existing popular connectors. This decision is crucial for Domo's product strategy and will significantly impact our users' ability to leverage data effectively. I'll analyze this trade-off by considering user needs, technical feasibility, business impact, and long-term strategic implications.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about Domo's current market position. Could you share how we're performing against competitors in terms of data source coverage and integration depth?

Why it matters: Helps understand competitive pressures and market gaps Expected answer: We're mid-tier in source coverage but leading in integration depth for key connectors Impact on approach: Would influence whether to focus on catching up in breadth or doubling down on our strength

• Business Context: Based on our revenue model, I assume deeper integrations drive more value for enterprise clients. Is this accurate, and how does it align with our current strategic priorities?

Why it matters: Aligns solution with revenue drivers and company strategy Expected answer: Deeper integrations are indeed more valuable for enterprises, a key growth segment Impact on approach: Would lean towards enhancing depth if enterprise growth is a top priority

• User Impact: I'm curious about user adoption patterns. Are we seeing more requests for new data sources or enhanced capabilities with existing ones?

Why it matters: Ensures we're addressing actual user needs rather than perceived ones Expected answer: Mix of both, with power users asking for deeper integrations and new users wanting more sources Impact on approach: Might suggest a balanced strategy or segmented approach based on user types

• Technical: Regarding our current architecture, how scalable is it for adding new data sources versus deepening existing integrations?

Why it matters: Assesses technical feasibility and resource implications Expected answer: Adding sources is easier short-term, but deepening integrations provides more long-term scalability Impact on approach: Could influence timeline and resource allocation for each option

• Resource: Can you give me an idea of our current team capacity and skill set distribution between adding new connectors and enhancing existing ones?

Why it matters: Determines if we have the right resources for either approach Expected answer: Team is more experienced in enhancing existing connectors Impact on approach: Might favor depth option unless we're prepared to invest in new skills or hiring