Should Absolute Software prioritize expanding device compatibility for its Absolute Resilience platform at the expense of developing new security features?

Introduction

The trade-off we're examining today is whether Absolute Software should prioritize expanding device compatibility for its Absolute Resilience platform or focus on developing new security features. This decision involves balancing the potential for market expansion against enhancing core product capabilities. I'll analyze this trade-off by considering market dynamics, user needs, technical feasibility, and business impact.

Step 1

Clarifying Questions (3 minutes)

• Based on the current market landscape, I'm thinking device compatibility might be a significant barrier to adoption. Could you share insights on our current device coverage and where we're seeing the most demand for expansion?

Why it matters: Helps prioritize which devices to focus on for maximum impact Expected answer: Limited coverage in emerging device categories (e.g., IoT) Impact on approach: Would influence whether to prioritize breadth or depth of compatibility

• Considering our revenue model, I assume expanding device compatibility could open up new market segments. How does our current pricing structure align with different device types or customer segments?

Why it matters: Determines potential revenue impact of expansion Expected answer: Tiered pricing based on device types and volumes Impact on approach: Might suggest focusing on high-value device categories first

• From a user perspective, I'm curious about the most requested security features from our enterprise customers. What are the top 3-5 features on our roadmap, and how critical are they for customer retention?

Why it matters: Helps weigh the value of new features against expanded compatibility Expected answer: Advanced threat detection, automated response, and compliance reporting are top priorities Impact on approach: Could influence decision to prioritize features if they're crucial for key accounts

• Regarding technical feasibility, what's our current architecture's flexibility for adding new device types versus implementing new security features?

Why it matters: Assesses the relative effort and risk of each option Expected answer: Modular architecture allows for easier device integration, but new features require more core changes Impact on approach: Might favor device expansion if it's significantly easier to implement

• Looking at our team capacity, how are our engineering resources currently allocated between device compatibility and feature development?

Why it matters: Determines if we have the right balance of skills for either option Expected answer: 70% on feature development, 30% on compatibility Impact on approach: Might need to consider team restructuring or hiring for the chosen priority