How would you measure the success of BlackBerry's Enterprise Mobility Management (EMM) solution?

Introduction

Measuring the success of BlackBerry's Enterprise Mobility Management (EMM) solution requires a comprehensive approach that considers multiple stakeholders and metrics. To effectively evaluate this enterprise software product, I'll follow a structured framework covering core metrics, supporting indicators, and risk factors while considering all key stakeholders.

Step 1

Product Context

BlackBerry's EMM solution is a comprehensive platform designed to help enterprises securely manage mobile devices, applications, and content. It's a critical tool for organizations looking to implement bring-your-own-device (BYOD) policies or manage company-owned devices while ensuring data security and compliance.

Key stakeholders include:

1. IT administrators: Seeking efficient device management and security
2. End-users: Employees wanting seamless access to work resources on mobile devices
3. C-suite executives: Concerned with data security, compliance, and productivity
4. BlackBerry's business units: Aiming for product adoption and revenue growth

The user flow typically involves IT admins setting up policies and configurations, which are then pushed to employee devices. Employees enroll their devices, gaining secure access to corporate resources while adhering to company policies. IT admins can then monitor, manage, and secure these devices remotely.

This product fits into BlackBerry's broader strategy of pivoting from hardware to enterprise software and services, leveraging their reputation for security. It competes with solutions like Microsoft Intune and VMware Workspace ONE, differentiating through its focus on security and its legacy in mobile device management.

In terms of product lifecycle, BlackBerry's EMM solution is in the maturity stage. It's a well-established product in a competitive market, with ongoing updates and feature enhancements to maintain its position.

Software-specific context:

• Platform: Cloud-based with on-premises options
• Integration points: Active Directory, enterprise apps, productivity suites
• Deployment model: SaaS with modular components for flexibility