How should Rapid7 balance adding new features to InsightVM versus improving the performance of existing vulnerability scans?

Introduction

Balancing the addition of new features to InsightVM versus improving the performance of existing vulnerability scans is a critical trade-off for Rapid7. This scenario touches on the core challenge of product evolution: enhancing functionality while maintaining efficiency. I'll approach this by examining the business context, user impact, technical considerations, and resource allocation to provide a strategic recommendation.

Step 1

Clarifying Questions (3 minutes)

• Based on market trends, I'm thinking cybersecurity needs are rapidly evolving. How urgent is the demand for new features in InsightVM compared to performance improvements?

Why it matters: Helps prioritize development efforts Expected answer: High urgency for both, with slight lean towards new features Impact on approach: Would suggest a balanced strategy with slightly more resources towards new features

• Considering our revenue model, I assume InsightVM is a key product. What percentage of our overall revenue does it contribute?

Why it matters: Determines the strategic importance of this decision Expected answer: Significant portion, likely over 30% Impact on approach: Higher contribution would justify more investment in both areas

• Looking at user behavior, I'm curious about the current scan performance. What's the average scan time, and what's the target we're aiming for?

Why it matters: Helps quantify the performance improvement needed Expected answer: Current average is X hours, target is Y hours Impact on approach: Large gap would prioritize performance improvements

• Regarding technical feasibility, are there any architectural limitations that might impact our ability to improve scan performance significantly?

Why it matters: Determines the potential for performance improvements Expected answer: Some limitations, but room for optimization Impact on approach: Significant limitations would shift focus to new features

• Considering team capacity, how are our development resources currently allocated between new features and performance improvements?

Why it matters: Helps understand current priorities and potential for reallocation Expected answer: 70% new features, 30% performance Impact on approach: Imbalance might suggest need for reallocation