Asana · Execution · Entry · 60 to 90 minutes

Asana Forms, What to Prioritize This Quarter

Asana is a work management platform that helps teams organize projects, track tasks, and coordinate work across teams. Answer this product management case and get it graded line by line against a weighted rubric.

Prioritization
User segmentation
Metric design
Execution planning
Stakeholder communication

The situation

Your team owns Asana Forms, which customers use to collect work requests and turn them into tasks inside projects. Your Group PM has asked you for a proposed Q3 plan after three pressures landed at once. First, Support and Success have escalated a reliability issue: some form submissions fail or create duplicate tasks when the destination project has many custom fields. Assume the following numbers: about 0.7% of submissions fail, related support tickets are up 35% quarter over quarter, and three enterprise renewals have mentioned the bug. Second, a salesperson is pushing for a prospect request, domain-restricted file uploads plus a confirmation receipt after submission, and says the deal could be worth $50k ARR if Asana can commit this quarter. Third, leadership wants progress on a strategic bet, making cross-functional intake workflows easier to set up at scale, and has suggested smarter routing from forms into the right team workflow. You have a small squad, 4 engineers, a half-time designer, and limited SRE help. The hard part is choosing between trust, near-term revenue, and a broader workflow investment.

What to produce

A 1 to 2 page quarterly prioritization memo.

Your answer must

State your recommendation for the quarter, including what you would build, what you would investigate, and what you would explicitly defer.
Segment the affected users and stakeholders, and explain who is helped or hurt by the reliability fix, the sales request, and the strategic bet.
Use a simple prioritization framework with explicit criteria and a clear ranking or scoring of the three competing items.
Define 3 to 5 success metrics for the quarter, including at least one reliability metric and one business metric.
Give a realistic execution plan for the first 4 to 6 weeks, plus a communication plan for Sales, Support, and leadership.

Constraints

The quarter is 12 weeks long.
Team capacity is 4 engineers, 1 designer at 50%, and shared SRE help for 1 sprint, enough for one large item and one small item, or two medium items.
You cannot promise or build a one-off solution that only works for a single customer.
Any change to file uploads or identity controls needs a security review, which may add about 1 week.

Format

Start with your recommendation and why. Then show your prioritization method, the quarter plan, the metrics, and how you would communicate the decision.