How can Cognite balance the ease of use of its Asset Data Insight application with the depth of technical functionality demanded by expert users?

Introduction

Balancing the ease of use of Cognite's Asset Data Insight application with the depth of technical functionality demanded by expert users presents a classic product trade-off. This scenario involves navigating the needs of diverse user segments while maintaining the product's core value proposition. I'll approach this challenge by analyzing user needs, exploring potential solutions, and proposing a strategic framework for decision-making.

Step 1

Clarifying Questions (3 minutes)

• Based on the product context, I'm thinking there might be distinct user segments with varying levels of technical expertise. Could you provide more details on the primary user groups for Asset Data Insight?

Why it matters: Helps tailor the solution to specific user needs Expected answer: Mix of technical experts and less technical users Impact on approach: Would inform potential segmentation or tiered feature access

• Considering the business model, I assume Asset Data Insight is a key revenue driver. How does this product fit into Cognite's overall product portfolio and revenue strategy?

Why it matters: Aligns solution with business objectives Expected answer: Critical product, significant revenue contribution Impact on approach: May justify more resources for a comprehensive solution

• Looking at user behavior, I'm curious about the most frequently used features by different user types. Can you share any insights on feature usage patterns across user segments?

Why it matters: Identifies core functionality to preserve Expected answer: Varied usage patterns between expert and novice users Impact on approach: Could inform a modular or adaptive interface design

• From a technical perspective, I'm wondering about the current architecture of Asset Data Insight. How flexible is it for implementing user-specific customizations or feature toggles?

Why it matters: Determines feasibility of potential solutions Expected answer: Moderately flexible, some limitations Impact on approach: Might influence the scope of proposed changes

• Regarding timeline, is there a specific market event or customer commitment driving urgency for this improvement?

Why it matters: Helps prioritize short-term vs. long-term solutions Expected answer: Upcoming industry conference or major client onboarding Impact on approach: Could lead to a phased implementation strategy