Introduction
Measuring the success of Absolute Software's Persistence technology requires a comprehensive approach that considers multiple stakeholders and metrics. To effectively evaluate this endpoint security solution, I'll follow a structured framework covering core metrics, supporting indicators, and risk factors while considering all key stakeholders.
I'll follow a simple success metrics framework covering product context, success metrics hierarchy.
Step 1
Product Context
Absolute Software's Persistence technology is an endpoint security solution embedded in the firmware of devices. It allows IT administrators to maintain visibility and control over endpoints, even if they're off the corporate network or the operating system has been wiped.
Key stakeholders include:
- IT administrators: Seeking robust security and device management
- End users: Requiring seamless device operation
- C-suite executives: Concerned with data protection and compliance
- Absolute Software: Aiming for product adoption and revenue growth
User flow:
- IT admin deploys Persistence on devices
- End users operate devices normally
- If a device is lost/stolen, IT can track, lock, or wipe it remotely
- Persistence reinstalls itself if removed, ensuring continuous protection
Persistence fits into Absolute's strategy of providing unbreakable endpoint resilience. It competes with other endpoint security solutions but differentiates itself through its firmware-level persistence.
Product Lifecycle Stage: Mature - Persistence is an established technology, but continuous innovation is needed to stay ahead in the competitive cybersecurity market.
Software-specific context:
- Platform: Firmware-level integration
- Integration points: Device management systems, security information and event management (SIEM) tools
- Deployment model: Pre-installed on devices or deployed via firmware update
Practice similar questions
Subscribe to access the full answer