The 'you just onboarded' constraint is doing a lot of work here and I almost glossed over it.
Start by acknowledging the challenge of inheriting work and the need to quickly build context. Then present a structured framework that balances user value, business impact, technical feasibility, and strategic alignment, while emphasizing cross-functional alignment and data-driven decision-making. Conclude with how you would communicate the decision and next steps.
Pro tip: Show humility by asking 'what would have to be true' for the feature to succeed, and involve the team in defining those conditions—this builds trust and ensures buy-in.
Review the feature's original goals, target users, success metrics, and any research or data. Meet with the previous PM, engineers, designers, and other stakeholders to gather insights and understand the history.
Evaluate how the feature aligns with current company/team OKRs and user needs. Validate assumptions with fresh user research or data if needed, and consider opportunity cost versus other priorities.
Work with engineering to assess technical complexity, dependencies, and potential risks (e.g., scalability, security, legal). Identify any blockers and estimate effort to complete.
Establish clear, measurable criteria for success (e.g., adoption, engagement, revenue) and thresholds for a go decision. Define what would constitute a no-go or pivot.
Facilitate a discussion with cross-functional partners to review findings against criteria. Make a recommendation, document the decision rationale, and outline next steps (ship, iterate, or kill).
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.