PM Quest · Practice cases · Learning resources

Prioritizing Key Features for Asana's Mobile App Roadmap

Feature Prioritization · advanced

Imagine you've just joined Asana as a Product Manager tasked with restructuring the product roadmap for their mobile app in Q1. How would you prioritize features to align with Asana's business goals of increasing user engagement and enterprise adoption?

Write your approach on PM Quest

Community approaches

Yuvraj’s approach

Product goal: 1. Increase user engagement- more daily active usage and retention. 2. Drive enterprise adoption- make the mobile app enterprise ready, secure and collaborative to increase usage team wide.

Options: 1. Collaboration enhancement: threaded comments, customised notifications, quick repky from notifictions, quick reactions. 2. Enterprise readyness: SSO,admin panel, compliance features 3. Mobile first UX improvements: Offline mode, faster ticket/task creation, reduce maual steps, simplify navigation for better UX and CSAT. Engagement increase: Personalised dashboards, customised notifications, daily, weekly and monthly summary of tasks/tickets actioned. 4. Integrations: slack, teams, google suite, notion, AI tools.

Prioritization criteria: Impact on engagement- daily active usage, retention impact on enterprise adoption- security, compliance, scalability Feasibility: effort, complexity, time, blockers or dependencies Differentiation: USP, competetive edge, pricing Guardrails: maintain app performance, reduce error rate in task creation, timely notification on mobile, avoid 2nd phase features and be iterative.

Recommended first priority: 1. Enterprise readiness features- SSO, admin panel, compliance related because this is a strategic win and advantage. Impact- increase growth and revenue from enterprise deals, increase trust and ensures the app can be accessed on the go for time sensitive tasks and collaboration.

Risks: engaegement trade off- focusing too much on enterprise may delay ux improvements for everyday users. Complexity: Enterprise features can be custom and slow down app performance. Adoption lag: Enterprise may take time to roll out mobile usage within their org even after features are added as they take things slowly and carefully.

Ranking options: 1. Enterprise readyness 2. Mobile first UX improvements 3. Collaborative enhancements 4. Integrations

Why this wins: Balance enterprise credibility with user delights and validate with usage metrics and feedback loops to make sure the goal is met.