Should InVision prioritize adding new features to Freehand or improving the performance of existing collaborative tools?

Introduction

The trade-off we're examining today is whether InVision should prioritize adding new features to Freehand or improving the performance of existing collaborative tools. This decision is crucial for InVision's product strategy and will impact user experience, team productivity, and market positioning. I'll analyze this trade-off by considering user needs, business objectives, and technical feasibility.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking about InVision's current market position. Could you share how Freehand is performing compared to competitors like Miro or Figma's FigJam?

Why it matters: Helps understand the urgency of feature additions vs. performance improvements. Expected answer: Freehand is growing but facing stiff competition. Impact on approach: Strong competition might push towards new features, while a solid market position could favor performance improvements.

• Business Context: Based on InVision's business model, I assume Freehand is a key revenue driver. Can you confirm if it's a significant portion of our revenue or more of a user acquisition tool?

Why it matters: Aligns the decision with financial priorities. Expected answer: Freehand is a significant revenue contributor. Impact on approach: If it's a major revenue source, we might lean towards performance improvements to retain users.

• User Impact: I'm curious about our user segments. Are we seeing different behaviors or needs between enterprise and individual users of Freehand?

Why it matters: Helps tailor the solution to our most valuable or growing user segments. Expected answer: Enterprise users value collaboration features more, while individuals prioritize ease of use. Impact on approach: Could lead to a segmented strategy, focusing on different aspects for different user groups.

• Technical: Regarding our existing collaborative tools, are there any known performance bottlenecks or scalability issues?

Why it matters: Determines the technical urgency of performance improvements. Expected answer: Some latency issues during peak usage times. Impact on approach: Significant issues might prioritize performance improvements over new features.

• Resource: Can you give me an idea of our current team capacity? Are we staffed more heavily on feature development or performance optimization?

Why it matters: Helps understand the feasibility of different approaches given our current resources. Expected answer: Balanced team, but slightly more feature developers. Impact on approach: Might influence whether we can pursue both paths simultaneously or need to choose one.