Calculate feature-learning ROI: if (frequency × time saved per use) > learning hours within 90 days, invest in mastering the feature

Why This Is a Rule

Learning a tool's advanced features has a cost (time invested in learning) and a return (time saved per use × number of uses). Without calculating this, you either over-invest (spending 10 hours learning a feature you'll use twice) or under-invest (avoiding a 2-hour learning session that would save 5 minutes daily for years). The break-even calculation makes the investment decision rational rather than intuitive.

The formula: Break-even = learning hours / (time saved per use × uses per month). If learning a keyboard shortcut system takes 3 hours and saves 2 minutes per use at 20 uses per day: break-even = 3 hours / (2 min × 20 uses × 22 days / 60 min) = 3 / 14.7 = 0.2 months. The investment pays back in less than a week — clearly worth it. If learning an advanced reporting feature takes 8 hours and saves 10 minutes per use at 2 uses per month: break-even = 8 / (10 × 2 / 60) = 8 / 0.33 = 24 months. Two years to break even — probably not worth it.

The 90-day payback threshold provides a decision boundary: invest if break-even is under 90 days (3 months). This ensures the learning investment produces returns within the same quarter, preventing investments with multi-year payback horizons that may never materialize if you switch tools.

When This Fires

• When considering whether to learn an advanced feature of any tool
• When Monthly depth audit: find 10 unused capabilities, rate value, practice top 3 for a week — compound tool learning beats sporadic discovery's monthly depth audit identifies potentially valuable features
• When a colleague demonstrates a feature that could save you time
• Complements Invest in mastery proportional to frequency × impact — months of practice for daily consequential tools, basic competence for infrequent ones (mastery investment scaling) with the per-feature economic calculation

Common Failure Mode

Gut-feel investment: "This feature looks powerful, I should learn it!" without calculating whether the investment will actually pay back. The feature is powerful for someone who uses the tool differently — for your usage pattern, it saves 30 seconds twice a month, making the 5-hour learning investment a 10-year payback.

The Protocol

(1) For a candidate feature, estimate three numbers: Learning time (hours to reach competent use), Time saved per use (minutes saved compared to current method), Usage frequency (times per month you'd use the feature). (2) Calculate break-even: learning hours / (time saved × frequency / 60). (3) If break-even < 3 months → invest. The payback is within the quarter. (4) If break-even 3-12 months → invest only if you're confident you'll still use this tool in a year and the feature is part of your core workflow. (5) If break-even > 12 months → skip. The learning investment is unlikely to pay back before you switch tools, change workflows, or forget the feature from disuse.