I went through a rough scoring approach, impact vs effort, and then tried to tie each selected feature back to a user persona with acceptance criteria.
Start by outlining a prioritization framework that balances business impact, user value, and technical feasibility, then explain how you translate the top-priority items into detailed user stories. Emphasize collaboration with engineering, design, and stakeholders throughout the process to ensure alignment and clarity.
Pro tip: Tie prioritization directly to Motorola's strategic goals (e.g., 5G innovation, battery life, or enterprise security) to show you understand the company's context and can make trade-offs that matter.
Collect inputs from user research, market trends, business goals, and technical constraints. Define clear prioritization criteria such as RICE (Reach, Impact, Confidence, Effort) or Value vs. Complexity.
Apply the chosen framework to score and rank features. Consider dependencies, strategic alignment, and quick wins vs. long-term bets. Validate with stakeholders to ensure buy-in.
Based on capacity and roadmap, select the top features. Ensure a mix of new value and technical debt reduction. Communicate the rationale behind selections and deferrals.
For each selected feature, write user stories in the format: 'As a [user], I want [goal] so that [benefit].' Include acceptance criteria, edge cases, and non-functional requirements. Collaborate with engineers and designers to refine.
Review stories with the team during backlog grooming. Ensure they are clear, testable, and sized appropriately. Iterate based on feedback and be ready to adjust as new information emerges.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.
Blanked for a second and listed a bunch of generic engagement metrics.
Start by clarifying the product context and business goals, then propose a metrics framework that aligns with Motorola's strategic priorities. Structure your answer around a hierarchy of metrics—from high-level business outcomes to product-specific engagement and quality indicators—and explain how you would prioritize and use them.
Pro tip: Emphasize leading indicators over lagging ones and show how you'd avoid vanity metrics by tying every metric to a decision or action. Mention the importance of setting targets and reviewing metrics regularly with cross-functional teams.
Ask clarifying questions to understand the product's stage, target users, and business objectives. This ensures your metrics are relevant and actionable.
Select a framework like HEART, AARRR, or OKRs to organize your metrics. This demonstrates structured thinking and coverage of key areas.
List specific metrics for each framework category, such as activation rate, retention, NPS, and feature adoption. Prioritize a few north-star and primary metrics.
Describe how you would instrument, track, and analyze these metrics over time. Mention tools, dashboards, and regular review cadences.
Tie the metrics back to business outcomes like revenue, market share, or customer lifetime value. Show how product metrics drive these results.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.