Implement Subdecks/Folders for Deck Organization

The primary business metric this feature affects is user retention and engagement. Users with a large number of decks currently find the app unwieldy, leading to potential frustration and abandonment. Better organization improves the user experience, making it easier to find and study relevant decks, thus increasing the likelihood they will continue using the app.

A secondary metric is activation/onboarding, as new users might be less intimidated if they see a clear path to organization.

However, the core pain point is for existing, engaged users with many decks, so retention is the key focus.

Estimating the scope of users affected:

• Assumption: Users typically start creating many decks after reaching a certain level of engagement, perhaps after a few weeks or months of consistent use.
• App Usage: Assume a significant portion of active users (e.g., 10-20%) will eventually accumulate enough decks to experience this problem.
• User Feedback: The prompt mentions 'many users are requesting this'. This suggests the problem is not niche.
• Estimating affected active users: If the app has 100,000 monthly active users (MAU), and 15% are affected by deck organization issues, that's 15,000 users.
• Impact on these users: For these 15,000 users, the current organization is a significant friction point, potentially impacting their willingness to add new decks or even continue using the app regularly.

Scope Estimate: ~15% of engaged users (translating to roughly 15,000 users in a 100K MAU base) are experiencing significant pain due to poor deck organization.

Understanding baseline metrics and benchmarks:

• Baseline Churn: For a typical mobile app, monthly churn can range from 5-15%. Let's assume a baseline monthly churn of 8% for our app.
• Impact of Organization Features: While direct benchmarks for deck organization are scarce, features that improve user experience, reduce friction, and increase discoverability generally have a positive impact on retention.
• Related Features: Improvements in search, filtering, or navigation have been shown to reduce churn by 1-3% absolute in comparable productivity or learning apps.
• User Satisfaction: Addressing top user requests and pain points is a well-established method for improving user satisfaction and loyalty.

Benchmark Assumption: Improving organization for a core user group could plausibly reduce churn by 1-2% absolute.

Calculating the potential retention improvement:

• Affected Users: 15% of MAU are significantly impacted.
• Potential Churn Reduction: Assume this feature could reduce the churn rate specifically for this affected group by 25% (relative reduction). If their churn rate was 8%, a 25% relative reduction would be 2% absolute reduction for them.
• Overall Churn Reduction: The overall MAU churn would be impacted by this 2% reduction applied to 15% of the user base.
  • Total churn reduction = 15% (affected users) * 2% (absolute reduction for them) = 0.3% absolute reduction in overall MAU churn.

Alternatively, applying the industry benchmark directly:

• Direct Application of Benchmark: If we assume the feature directly addresses friction causing churn, we can expect a 1-2% absolute reduction in churn for the 15% of users experiencing the pain.
  • Lower bound: 15% * 1% = 0.15% absolute MAU churn reduction.
  • Upper bound: 15% * 2% = 0.3% absolute MAU churn reduction.

Estimated KPI Impact: Reduction in monthly active user churn by approximately 0.15% - 0.3% absolute.

The estimated impact is a reduction in monthly churn by 0.15% - 0.3% absolute. This is a measurable improvement and directly addresses a significant user pain point.

• This level of churn reduction is moderate. It's not transformative (like a new revenue stream or a viral growth loop), but it's substantial enough to impact long-term user base health and stability.
• It directly tackles user feedback and improves core functionality for a considerable segment of engaged users.

Comparing to the impact scale:

• Negligible (1-2): Too low.
• Minor (3-4): This is more than a minor QoL improvement.
• Moderate (5-6): Fits well. A 0.15-0.3% absolute churn reduction is a meaningful business benefit.
• Significant (7-8): Likely too high for this specific metric improvement alone.

Given that this addresses a frequently requested feature that improves core usability for a large subset of users, leading to tangible retention gains:

IMPACT SCORE = 5