For Absolute Software's Persistence technology, should we focus on improving tamper resistance or enhancing cross-platform integration capabilities?

Introduction

The trade-off between improving tamper resistance and enhancing cross-platform integration capabilities for Absolute Software's Persistence technology presents a critical decision point. This scenario involves balancing security robustness against broader compatibility, each with significant implications for product efficacy and market reach. I'll analyze this trade-off through multiple lenses, considering technical feasibility, user impact, business priorities, and long-term strategic alignment.

Step 1

Clarifying Questions (3 minutes)

• Based on recent market trends, I'm thinking security might be our top priority. How does this align with our current threat landscape and customer feedback?

Why it matters: Helps prioritize features based on market demands and security needs. Expected answer: Security is critical, but customers are also demanding broader device support. Impact on approach: Would influence the balance between security enhancements and integration efforts.

• Considering our revenue model, I assume Persistence is a key differentiator. What percentage of our revenue does it currently contribute?

Why it matters: Determines the financial impact of potential changes to the product. Expected answer: Persistence contributes significantly, around 30-40% of revenue. Impact on approach: High revenue contribution would justify more resources for improvement.

• Looking at user segments, are we seeing a shift in device preferences among our enterprise clients?

Why it matters: Informs the urgency of cross-platform integration. Expected answer: Increasing diversity in device types, especially with remote work trends. Impact on approach: Strong shift would prioritize cross-platform capabilities.

• From a technical standpoint, how intertwined are our tamper resistance and integration codebases?

Why it matters: Affects the feasibility of focusing on one aspect without impacting the other. Expected answer: Moderate overlap, but improvements can be made independently. Impact on approach: Would influence whether we can pursue both improvements simultaneously or need to choose.

• Regarding our development resources, do we have specialized teams for security and integration, or is it a shared resource pool?

Why it matters: Determines our capacity to work on both aspects concurrently. Expected answer: Shared resource pool with some specialization. Impact on approach: Would affect how we allocate resources and prioritize improvements.