Should Cognite prioritize expanding the industrial IoT capabilities of Cognite Data Fusion at the expense of its data contextualization features?

Introduction

The trade-off question at hand is whether Cognite should prioritize expanding the industrial IoT capabilities of Cognite Data Fusion at the expense of its data contextualization features. This scenario involves balancing the development of two key product areas within Cognite Data Fusion, each with its own strategic importance and potential impact on the company's market position.

To address this complex trade-off, I'll follow a structured approach:

1. Ask clarifying questions to understand the context
2. Identify the specific type of trade-off we're dealing with
3. Analyze the product and its ecosystem
4. Formulate a hypothesis and potential impacts
5. Define key metrics for evaluation
6. Design an experiment to test our hypothesis
7. Plan the data analysis approach
8. Create a decision framework
9. Provide a recommendation with next steps

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about the current market dynamics in the industrial IoT space. Could you share more about the competitive landscape and where Cognite sees the biggest opportunities for growth?

Why it matters: Helps prioritize features based on market demand and competitive advantage Expected answer: Growing demand for IoT capabilities, but strong competition in data contextualization Impact on approach: Would influence whether to focus on differentiation or catching up in IoT

• Business Context: Based on Cognite's revenue model, I'm assuming IoT capabilities might open up new revenue streams. How does the current revenue split look between IoT and data contextualization features?

Why it matters: Aligns product strategy with financial goals Expected answer: Data contextualization currently generates more revenue, but IoT has higher growth potential Impact on approach: Would help balance short-term revenue protection with long-term growth

• User Impact: Considering our user segments, I'm curious about the adoption rates of IoT vs. data contextualization features. Can you provide insights into which features are most valued by our key accounts?

Why it matters: Ensures we're prioritizing features that deliver the most value to users Expected answer: Mixed usage, with some key accounts heavily relying on data contextualization Impact on approach: Would influence how we phase any changes to minimize disruption to high-value customers

• Technical Feasibility: Given the complexity of both IoT and data contextualization, I'm wondering about our technical capabilities. How does our engineering team's expertise align with these two areas?

Why it matters: Assesses our ability to execute effectively in both domains Expected answer: Stronger expertise in data contextualization, but growing capabilities in IoT Impact on approach: Might suggest a gradual shift towards IoT while maintaining data contextualization strength

• Resource Allocation: Thinking about our current team structure, I'm curious about how resources are currently split between IoT and data contextualization efforts. What's the current allocation, and how flexible is it?

Why it matters: Determines our ability to shift focus without major organizational changes Expected answer: Resources are currently balanced, with some flexibility to reallocate Impact on approach: Would inform how quickly and extensively we can pivot towards IoT