What metrics would you use to evaluate Under Armour's MapMyRun app integration with their connected footwear?

Introduction

Evaluating the success of Under Armour's MapMyRun app integration with their connected footwear requires a comprehensive approach to product metrics. This integration represents a significant intersection of digital technology and physical products, aiming to enhance the user experience for runners while driving value for Under Armour's footwear business. To address this product success metrics challenge effectively, I'll follow a structured framework that covers core metrics, supporting indicators, and risk factors while considering all key stakeholders.

Step 1

Product Context

Under Armour's MapMyRun app integration with connected footwear combines a popular fitness tracking app with sensor-equipped running shoes. This integration allows users to track their runs, analyze their form, and receive personalized coaching tips based on their performance data.

Key stakeholders include:

1. Runners (users): Seeking improved performance and insights
2. Under Armour: Aiming to drive footwear sales and app engagement
3. Retailers: Looking to sell more Under Armour products
4. Investors: Expecting growth and innovation in the connected fitness space

User flow:

1. Purchase: User buys Under Armour connected shoes
2. Setup: Pair shoes with MapMyRun app via Bluetooth
3. Activity: User goes for a run, shoes collect data
4. Analysis: App processes data and provides insights
5. Coaching: User receives personalized tips and recommendations

This integration fits into Under Armour's broader strategy of combining physical products with digital experiences to create a more engaging and valuable ecosystem for athletes. It also helps differentiate their footwear in a competitive market.

Compared to competitors like Nike's Nike+ Run Club and Adidas Runtastic, Under Armour's integration offers more detailed form analysis and shoe-specific insights.

Product Lifecycle Stage: Growth - The integration is past its initial launch but still expanding its user base and feature set.

Software considerations:

• Platform: iOS and Android mobile apps
• Integration points: Bluetooth connectivity, cloud data sync
• Deployment model: Regular app updates, firmware updates for shoes

Hardware considerations:

• Manufacturing: Sensor integration into shoe design
• Supply chain: Ensuring consistent quality of sensor-equipped shoes
• Service infrastructure: Maintaining Bluetooth connectivity and data processing capabilities