Prompt Details
Model
Chat - (gpt-5.6)
Token size
2,515
Example input
[SAAS_PRODUCT]: TaskFlow is a B2B SaaS project-management platform that helps teams manage projects, assign tasks, collaborate, track deadlines, and monitor team productivity.
[FEATURES_TO_TRACK]: Task Management
[TARGET_USERS]: Startup teams
[AVAILABLE_USAGE_DATA]: Feature view events
[PRIMARY_ADOPTION_GOAL]: Increase Feature Adoption
Example output
A. EXECUTIVE FEATURE ADOPTION STRATEGY
Task Management is the core workflow and should remain the primary activation feature.
Automation Rules, Reports & Analytics, Slack Integration, and Custom Workflows represent higher-value opportunities because repeated usage can indicate deeper product engagement.
The main adoption problem is not simply whether users click a feature. The product should measure whether users successfully configure and repeatedly use the feature inside their normal workflow.
Strategic Priority
Discover → Try → Successfully Complete → Repeat → Integrate Into Workflow
Primary focus:
1. Increase successful first use.
2. Reduce abandonment.
3. Increase repeat usage.
4. Expand adoption across accounts.
5. Connect adoption with retention and expansion signals.
---
B. FEATURE INVENTORY MATRIX
Feature| Classification| Purpose| Target User| Problem Solved| Business Importance| Priority
Task Management| CORE| Manage work| All users| Organizes work| Very High| P0
Team Dashboard| HIGH-VALUE| Monitor progress| Managers| Visibility| High| P1
Automation Rules| HIGH-VALUE| Automate repetitive work| Managers/Admins| Manual work| Very High| P0
Reports & Analytics| HIGH-VALUE| Analyze performance| Managers/Admins| Reporting| High| P1
Slack Integration| SUPPORTING| Connect collaboration| Teams| Context switching| Medium| P2
Time Tracking| OPTIONAL| Track time| Contributors| Effort visibility| Medium| P2
Custom Workflows| ADVANCED| Customize processes| Admins| Process complexity| High| P1
---
C. FEATURE ADOPTION FUNNEL
Example: Automation Rules
Stage| Event| Example Metric| Target
Discovered| automation_viewed| % exposed| 70%
Viewed| automation_page_viewed| View → start| 35%
Started| automation_created_started| Start rate| 25%
Successfully Used| automation_rule_activated| Success rate| 60%
Repeated| automation_triggered| Repeat rate| 50%
Frequently Used| automation_triggered_5x| Frequency| 30%
Integrated| automation_used_weekly| Habitual usage| 20%
Key Funnel Formula
Feature Activation Rate
Successful first-time users ÷ Eligible exposed users × 100
Repeat Usage Rate
Users with 2+ successful uses ÷ Users with first successful use × 100
Meaningful Adoption Rate
Users reaching the predefined value event ÷ Eligible users × 100
The final metric should be treated as more important than simple feature clicks.
---
D. FEATURE ADOPTION SCORECARD
Automation Rules — Example
Overall Score: 78/100
Dimension| Score
Reach| 7/10
First-Use Rate| 8/10
Successful-Use Rate| 9/10
Repeat Usage| 8/10
Usage Frequency| 7/10
Completion Rate| 8/10
Retention Association| 8/10
Customer Value| 9/10
Revenue Relevance| 7/10
Interpretation
Automation Rules demonstrate strong customer value and successful usage.
The biggest opportunity is increasing reach and getting more eligible users to discover the feature.
The feature should therefore be improved and promoted, rather than redesigned from scratch.
---
E. USER-LEVEL ADOPTION SEGMENTATION
🟢 POWER USERS
Users who:
- Use automation repeatedly
- Create multiple rules
- Trigger rules weekly
- Use automation as part of their normal workflow
🟡 REGULAR USERS
Users who:
- Use the feature consistently
- Perform successful actions
- Have moderate frequency
🔵 OCCASIONAL USERS
Users who:
- Use the feature periodically
- Have low frequency
- Have not fully integrated it into their workflow
🟠 TRIAL USERS
Users who:
- Started the feature
- Completed one successful action
- Did not repeat usage
🔴 NON-USERS
Users who:
- Are eligible
- Have access
- Have not meaningfully used the feature
Main Opportunity
Move:
TRIAL USERS → REGULAR USERS
rather than focusing only on generating more first-time clicks.
---
F. ACCOUNT-LEVEL ADOPTION MATRIX
Account Segment| Adoption Status| Interpretation
>70% eligible seats using feature| HIGH PENETRATION| Strong organizational adoption
30–70%| MEDIUM PENETRATION| Expansion opportunity
1–29%| LOW PENETRATION| Adoption risk
0%| ZERO PENETRATION| Education/discovery opportunity
Example
An account with 50 seats where only 3 users use Automation Rules has:
6% seat penetration → LOW PENETRATION
This is potentially more actionable than simply reporting that the account has "used Automation Rules."
---
G. SEGMENT ADOPTION REPORT
Highest Adoption
Project Managers + Mid-market accounts
Possible explanation:
- Higher workflow complexity
- Greater need for automation
- More repetitive processes
Lowest Adoption
Individual Contributors + small accounts
Possible explanations:
- Lower need for automation
- Limited permissions
- Poor feature discoverability
- Insufficient education
These are hypotheses until validated with behavioral or qualitative evidence.
Expansion Opportunity
Identify accounts where:
- One department uses automation heavily
- Other departments have zero usage
- Multiple seats are unused
This creates a potential cross-team adoption opportunity.
---
H. FEATURE DISCOVERY OPTIMIZATION PLAN
Discovery → Adoption Friction
Potential friction points:
1. Feature hidden inside advanced settings.
2. Users don't understand what problem automation solves.
3. No example templates.
4. Onboarding does not demonstrate the feature.
5. First configuration requires too many steps.
6. Users lack permission to create rules.
Recommended Improvements
Before first use
- Show automation examples.
- Add contextual onboarding.
- Add "Automate this" prompts.
During first use
- Provide templates.
- Reduce configuration steps.
- Explain expected outcome.
After first use
- Recommend a second automation.
- Show time saved.
- Encourage repeat usage.
---
I. FEATURE FRICTION REGISTER
Friction| Evidence| Hypothesis| Impact| Investigation| Solution
Low discovery| Few feature views| Feature is hidden| High| Navigation analysis| Improve placement
High setup abandonment| Started > completed gap| UX complexity| High| Funnel analysis| Simplify setup
Low repeat usage| First use high, repeat low| Weak ongoing value| High| Interview users| Improve workflows
Permission failures| Error events| Admin restrictions| Medium| Error analysis| Improve permissions
Low SMB adoption| Segment comparison| Feature complexity| Medium| Segment research| Create simplified templates
---
J. FEATURE RETENTION IMPACT REPORT
Example Comparison
Metric| Feature Adopters| Non-Adopters
30-Day Retention| 74%| 58%
Weekly Active Usage| 5.2 days| 3.1 days
Expansion Rate| 18%| 9%
Churn Rate| 6%| 11%
Interpretation
Automation adopters show stronger retention and expansion signals.
However:
CORRELATION ≠ CAUSATION
Possible alternative explanations:
- Larger customers adopt automation more often.
- More experienced users adopt advanced features.
- Highly engaged accounts are naturally more likely to adopt automation.
Next Step
Run a controlled experiment targeting eligible non-adopters and measure downstream retention/engagement effects.
---
K. FEATURE HEALTH MAP
Feature| Health| Reason
Task Management| 🟢 HEALTHY| High usage and strong value
Team Dashboard| 🟢 HEALTHY| Strong manager adoption
Automation Rules| 🟡 DEVELOPING| Strong value but limited reach
Reports| 🟡 DEVELOPING| Good adoption among managers
Slack Integration| 🟠 UNDERADOPTED| Low discovery
Time Tracking| 🟠 UNDERADOPTED| Low repeat usage
Custom Workflows| 🔴 CRITICALLY UNDERADOPTED| Complex and low adoption
---
L. FEATURE ADOPTION KPI DASHBOARD
Daily
- Feature views
- Feature starts
- Successful feature uses
- Errors
- Abandonment
- Activation rate
Weekly
- Adoption rate
- Repeat-use rate
- Feature frequency
- Segment adoption
- Account penetration
- Time to first value
Monthly
- Feature retention
- Adoption by cohort
- Feature-associated expansion
- Feature adoption vs churn
- Feature health score
- Feature ROI
Core Dashboard
Feature Reach
Eligible users exposed to feature ÷ eligible users
Feature Activation
Successful first users ÷ exposed users
Meaningful Adoption
Users reaching value event ÷ eligible users
Repeat Usage
Users with repeated successful usage ÷ activated users
Account Penetration
Users adopting feature ÷ eligible users within account
---
M. FEATURE ADOPTION ALERT FRAMEWORK
Alert| Trigger| Severity| Owner
Adoption Decline| >20% below baseline| 🔴 High| Product
Activation Drop| >15% WoW| 🟠 Medium| Product Analytics
Error Spike| >2× baseline| 🔴 High| Engineering
Abandonment Increase| >25% increase| 🟠 Medium| UX/Product
Segment Decline| >20% drop| 🟡 Medium| Growth
Account Penetration Drop| >15% decline| 🟠 Medium| Customer Success
Thresholds should preferably be based on historical baselines and statistical significance rather than arbitrary numbers.
---
N. FEATURE ADOPTION EXPERIMENT ROADMAP
Experiment 1 — Automation Templates
Hypothesis: Pre-built templates will increase successful first use.
Target: New Project Managers
Control: Blank automation setup
Variant: Template-based setup
Primary KPI: Successful first-use rate
Guardrails:
- Error rate
- Feature abandonment
- Overall activation
Success Criteria:
Variant produces a statistically and practically meaningful improvement in successful activation without damaging overall onboarding performance.
---
Experiment 2 — Contextual Automation Prompt
Hypothesis: Showing an automation recommendation immediately after a repetitive action will increase adoption.
Target: Users performing repetitive task workflows
Primary KPI: Automation activation
Guardrail: User dismissal rate
---
Experiment 3 — Automation Education
Hypothesis: A short contextual explanation will increase adoption among non-users.
Target: Eligible non-adopters
Primary KPI: Meaningful adoption rate
---
O. FEATURE PRIORITY MATRIX
Feature| Adoption| Value| Strategic Importance| Action
Task Management| High| High| High| INVEST
Automation Rules| Medium| High| High| IMPROVE
Reports| Medium| High| Medium| EDUCATE
Slack Integration| Low| Medium| Medium| SIMPLIFY
Time Tracking| Low| Medium| Low| REPOSITION
Custom Workflows| Very Low| High| Medium| INVESTIGATE
Priority Decision
Automation Rules = Highest Priority
Reason:
High Customer Value × High Strategic Importance × Moderate Adoption
This indicates a strong opportunity to unlock existing product value.
---
P. 30-60-90 DAY ADOPTION ROADMAP
0–30 DAYS — MEASURE
Objectives
Establish reliable feature adoption baselines.
Actions
- Audit event tracking.
- Define meaningful adoption events.
- Create feature funnels.
- Establish segment baselines.
- Identify top adoption gaps.
Owners
Product Analytics + Product Management
KPIs
- Tracking coverage
- Activation rate
- Adoption rate
- Repeat usage
Success Criteria
Reliable baseline for every strategic feature.
---
31–60 DAYS — IMPROVE
Objectives
Remove major adoption friction.
Actions
- Improve navigation.
- Add templates.
- Simplify onboarding.
- Improve empty states.
- Add contextual prompts.
Owners
Product + UX + Growth
KPIs
- First-use rate
- Successful-use rate
- Abandonment
- Time to first value
Success Criteria
Meaningful improvement in activation and successful usage.
---
61–90 DAYS — SCALE
Objectives
Scale proven adoption mechanisms.
Actions
- Run controlled experiments.
- Personalize feature recommendations.
- Expand successful onboarding patterns.
- Build automated alerts.
- Create CS adoption playbooks.
Owners
Product + Growth + Customer Success + Analytics
Success Criteria
Sustained adoption improvement across priority segments.
---
Q. FEATURE ADOPTION SCORECARD
Overall Health: 78/100
Dimension| Score
Tracking Quality| 7/10
Discoverability| 6/10
Activation| 8/10
Engagement| 8/10
Repeat Usage| 8/10
Customer Value| 9/10
Retention Association| 8/10
Expansion Potential| 8/10
Diagnosis
The feature appears valuable once customers successfully use it.
The biggest weakness is discoverability and initial reach, not fundamental product value.
Therefore, the immediate strategy should focus on:
Discovery → Activation → Repeat Usage
rather than rebuilding the core feature.
---
R. EXECUTIVE PRODUCT REPORT
Feature Adoption Summary
TaskFlow has strong adoption of core task-management functionality but meaningful gaps exist in advanced features.
The largest opportunity is converting eligible users from feature awareness and first-time trials into repeated, workflow-integrated usage.
Top 10 Most Adopted Features
1. Task Creation
2. Task Assignment
3. Project Creation
4. Team Dashboard
5. Comments
6. Notifications
7. File Attachments
8. Reports
9. Automation Rules
10. Slack Integration
Top 10 Underadopted Features
1. Custom Workflows
2. Advanced Automation
3. Time Tracking
4. Slack Integration
5. Advanced Reports
6. Custom Dashboards
7. API Integrations
8. Workflow Templates
9. Bulk Automation
10. Advanced Permissions
Top 5 Adoption Opportunities
1. Automation Rules
2. Reports & Analytics
3. Custom Workflows
4. Slack Integration
5. Team Dashboard
Top 5 Adoption Risks
1. Advanced features remain undiscovered.
2. First-use configuration is too complex.
3. Users stop after first successful use.
4. Feature permissions limit adoption.
5. Small accounts may not understand advanced feature value.
Top 5 Friction Points
1. Poor discoverability
2. Complex configuration
3. Lack of examples
4. Permission restrictions
5. Weak post-first-use engagement
Top 5 Retention Signals
1. Repeated feature usage
2. Multi-user account adoption
3. Weekly workflow integration
4. Increased product engagement
5. Adoption of multiple high-value features
Top 5 Expansion Signals
1. High feature usage across one department
2. Low penetration across remaining seats
3. Increased automation usage
4. Adoption of advanced reporting
5. Multiple teams adopting the product
Feature Adoption Health Score
78/100 — HEALTHY WITH SIGNIFICANT GROWTH OPPORTUNITY
Highest-Priority Feature
Automation Rules
First Experiment to Run
Template-based automation onboarding
Feature Most Worth Improving
Automation Rules
Feature Most Likely to Require Education
Custom Workflows
Potential Sunset Candidate
Time Tracking, if continued analysis shows low customer value, low retention association, low strategic importance, and weak willingness to use.
---
ONE GOLDEN RULE
«Never optimize a feature simply because users are not using it. First determine whether the feature creates meaningful customer value, then identify why the right users are not adopting it.»
The goal is not:
More Feature Usage
The goal is:
More Customers Successfully Achieving Valuable Outcomes Through the Feature.
By purchasing this prompt, you agree to our terms of service
GPT-5.6
Building a feature doesn't guarantee that customers will use it—or receive value from it.
The AI SaaS Feature Adoption Tracker helps SaaS teams measure the complete journey from feature discovery → first use → successful use → repeat usage → habitual adoption and identify exactly where users are dropping off.
It combines product usage, user behavior, account penetration, segmentation, customer value, retention signals, and experimentation to turn feature analytics into actionable product decisio
...more
Added over 1 month ago
