Tasknest · Metrics · Entry · 45 to 60 minutes

Sign ups are high, engagement is low

Tasknest is a hypothetical SaaS productivity app for individuals and small teams to organize tasks and projects online. Answer this product management case and get it graded line by line against a weighted rubric.

metrics framing
funnel analysis
prioritization
product judgment
experimentation

The situation

The Head of Product at Tasknest has asked you to prepare a recommendation for next week's leadership review. Tasknest is attracting plenty of new registrations, but day to day usage is weak and advanced features barely get used. Marketing wants to keep investing in acquisition because sign ups look healthy. The CEO is worried the product is not delivering real value after the first session, and engineering can only support a small set of changes this quarter. Assume the web product funnel for recent new users looks like this: 100 percent sign up, 85 percent complete onboarding, 60 percent create a first task, 40 percent create a first project, 25 percent invite teammates, and 10 percent try advanced features such as recurring tasks, analytics, or automation. You are the PM assigned to recommend how the team should define success, where the biggest leak is, and what to do first. The hard part is separating vanity growth from meaningful product adoption without overbuilding.

What to produce

Write a 1 page product metrics memo, 600 to 900 words.

Your answer must

State 3 to 5 clarifying questions or explicit assumptions that shape your analysis.
Define 1 activation metric and 3 to 5 ongoing engagement or adoption metrics, with a brief reason for each.
Use the funnel data to identify the most important drop off point and at least 2 plausible causes.
Recommend exactly 2 product changes to test first, and prioritize them using expected impact and effort.
Propose a 30 to 60 day experiment and measurement plan, including what results would count as a win.

Constraints

Focus on new user engagement in the web product, not pricing, packaging, or sales changes.
Assume the team can ship only low to moderate effort changes in the next quarter.
Use existing product surfaces and in app messaging only, no full redesign and no new AI system.

Format

Use five sections: assumptions, activation and metrics, funnel diagnosis, recommendations, experiment plan.

How Tasknest actually played it

A metrics case about a SaaS productivity app where users sign up but few finish tasks or adopt advanced features. It proposes adoption and engagement metrics and ways to improve them.

Define activation before measuring engagement
Track feature adoption, not only sign-ups
Pick a few metrics tied to value delivered

Built from Product Metrics Case: SaaS tool with high sign-ups and low engagement by Sreerag Panat.