If I were To

Re

Design

AllTrails
Mobile App
ALLTRAILS CASE STUDY -- DEC '25
Building Safety &
Community Through
Platform Expansion
Transforming AllTrails from a trail discovery app into a comprehensive outdoor safety and commerce platform.

+15% user retention

First-mover advantage

Outdoor guide marketplace

STRATEGIC CONTEXT: WHY THIS, WHY NOW
The Market Inflection Point
Three simultaneous shifts created a unique 12-month window:
Supply Shock

REI shut down their $50M+ guided experiences program (June 2024), leaving 500+ certified guides without a platform and thousands of customers without trusted access to outdoor education.

Safety Crisis

Western US wildfires increased 400% since 1970. In 2024 alone, 68% of our Western users canceled trips due to air quality—but our app showed "perfect weather" because we didn't surface AQI data.

Competitive Vulnerability

Google Maps added hiking trails (March 2024), Strava launched route discovery (July 2024). Our differentiation as "just a trail database" was eroding.

THE STRATEGIC QUESTION
How do we defend our moat while the competition treats trails as a commodity feature?

Build what only AllTrails can build—a trust-based platform that leverages our 65M users' intent signals to connect outdoor experiences, not just catalog them.

PROBLEM DEEP-DIVE: THREE USER JOBS-TO-BE-DONE

Help Me Hike Safely in Wildfire Season

"I drove 3 hours to Lake Tahoe only to find the air quality was hazardous. AllTrails showed perfect weather but didn't mention the smoke. I felt betrayed—isn't safety your whole thing?"

— User Interview #47, Premium subscriber
The Opportunity
xx%
Trip cancellations
xx%
Avg wasted drive time
xx%
NPS detractor mentions

Help Me Recover What I Lost  (and Help Others)

"Lost my $300 Garmin watch on Angels Landing. Posted on 6 Facebook groups, Reddit, called the park. Nothing. I'd pay $100 to get it back but there's no system."

— Reddit r/hiking, 847 upvotes
The Opportunity
$2.3B in outdoor gear lost annually with no structured recovery system
Why This Beats a Gear Marketplace: Creates stickiness through emotional investment. Users who post lost items check app 4.2x more frequently. No operational burden—we're matching people, not handling physical goods.

Help Me Learn Outdoor Skills Safely

"I want to try backpacking but don't know where to start. REI classes are gone. I'd pay $200 for a trusted first experience."

— User Interview #47, Premium subscriber
WHY ALLTRAILS WINS
Demand signals: Users downloading "Half Dome" trail = they're planning to hike it = perfect moment to offer guide
Trust transfer: AllTrails verification >> random marketplace profile
Network effects: More guides → more trail coverage → more bookings → more guides
SOLUTION DESIGN & STRATEGIC DECISIONS

Air Quality Integration

AirNow API + PurpleAir sensors + NOAA smoke forecasts with color-coded AQI badge on every trail page, push notifications when saved trails exceed AQI 100, and 48-hour forecasts.

KEY DECISION: FREE VS. PREMIUM
Made it free for all users. Safety features = brand moat.
Trade-off: Forgo ~$2M annual premium revenue to build trust that enables marketplace monetization

AllTrails Marketplace

Lost & Found (10% commission)
GPS-based matching with reward escrow. Users post lost items, finders claim rewards.
Guide Marketplace (15% commission)
GPS-based matching with reward escrow. Users post lost items, finders claim rewards.Verified guides create trail-specific experiences. Strict certification requirements.
KEY DECISION: FREE VS. PREMIUM
Made it free for all users. Safety features = brand moat.
Trade-off: Forgo ~$2M annual premium revenue to build trust that enables marketplace monetization

Critical Strategic Decisions

DECISION
CHOICE
RATIONALE
Launch Timing
Both features together
Shared infrastructure (notifications, payments). Safety builds trust for marketplace.
Commission Rate
Lost & Found: 10%
Guides: 15%
Low enough to feel fair, high enough to cover fraud prevention and support sustainable business.
Geographic Rollout
California → West → National
Concentrate supply. Highest wildfire impact + largest user base + most displaced REI guides.
Guide Verification
Strict (WFR + insurance)
Quality over quantity. Trust compounds exponentially. Better 100 great guides than 1,000 sketchy ones.

North Star Metric

Trips Completed Safely

Users who check air quality + complete their planned hike. A canceled trip due to good intel = success. A completed trip in bad air = failure.

12-MONTH BUSINESS IMPACT

$X.XM
Incremental ARR
Lost & Found + Guide commissions + Retained subscription revenue
+YY%
WAU Growth
From Safety Features
+ZZ%
+ 6mo Month Retention.
Air quality checkers stay engaged
NYT Cooking
Mobile App
NYT COOKING CASE STUDY -- DEC '25
Community Intelligence & & Meal Composition
Transforming NYT Cooking from a recipe repository into a cooking companion

+15% user retention

1M+ paid subscribers

67% read comments first

STRATEGIC CONTEXT: WHY THIS, WHY NOW
The Engagement & Retention Crisis
concurrent challenges created urgency to evolve from recipe repository to cooking companion:
Casual User Churn Problem

With 1M+ paid subscribers and 456M annual visits, NYT Cooking faced a retention crisis: 40% of subscribers were casual users (1-2 recipes/month) but represented 65% of churn. Users who engaged with 5+ recipes monthly had 3x better retention, revealing a critical engagement gap. Lost LTV: ~$180 per churned user over 3 years.

Hidden Value in Community Data

Despite having 3M newsletter subscribers and rich community engagement, the platform's most valuable asset—community modifications that improve recipes—are buried in comment threads. 67% of users read comments before cooking, and top-voted comments frequently contained the same 3-4 modifications, but users have to manually parse through personal anecdotes and tangential debates.

Competitive Pressure from Free Alternatives

NYT Cooking operates in a crowded market where free alternatives like Allrecipes exist. Current technical issues (poor search, disorganized recipe box) create friction that drives users to competitors. 54% of users struggle to find simple, everyday solutions. Average session depth: 1.8 recipes vs. competitor benchmarks of 3-4 recipes.

THE STRATEGIC QUESTION
How do we transform NYT Cooking from a recipe repository into an indispensable cooking companion that drives daily usage?

Leverage unique assets—trusted community and editorial curation—to solve confidence and exploration gaps that keep users cooking incomplete meals.

PROBLEM DEEP-DIVE: THREE USER JOBS-TO-BE-DONE

Help Me Cook Recipes Confidently Without Guesswork

"I don't trust my own judgment on modifications. I spend 10-15 minutes reading through all the comments to see what worked for other people, but it's buried in personal stories and debates. I just want to know: should I add more garlic or not?"

— "Capable But Cautious Casey," intermediate home cook, ages 28-45
The Opportunity
xx%
Read comments before cooking
x-y min
Wasted parsing comments
x-y
Same mods in top comments

Help Me Plan Complete Meals, Not Just Main Dishes

"I find a great chicken recipe on NYT Cooking, but then I have no idea what to serve with it. Do I just make rice and salad again? I end up browsing Pinterest for 20 minutes or just giving up and making the same default sides."

— User survey response, 73% of users cook incomplete meals
The Opportunity
Despite having 20,000+ recipes, NYT Cooking doesn't help users answer: "What should I serve with this?" This creates incomplete meal planning, missed cross-sell opportunities (users cook one NYT recipe but source sides from Pinterest/Instagram), and lower session depth (avg. 1.8 recipes vs. competitor benchmarks of 3-4).

Help Me Increase Subscriber Retention Through Daily Value

"Our casual users (1-2 recipes/month) represent 40% of our subscriber base but 65% of our churn. Users who engage with 5+ recipes monthly have 3x better retention. We need to transform from 'special occasion cooking' to 'everyday meal planning.'"

— NYT Cooking Business Goals, internal stakeholder
WHY nYT COOKING WINS
Defensible moat: Competitors can copy features but can't replicate our community depth (3M newsletter subscribers) or editorial trust (test kitchen validation)
Flywheel effect: Better recommendations → more engagement → richer community data → better recommendations
Platform stickiness: Users invest time in meal collections and rely on our pairings, raising switching costs vs. free alternatives
SOLUTION DESIGN & STRATEGIC DECISIONS

Smart Recipe Insights

Surface the most valuable community modifications directly in the recipe interface using NLP analysis + editorial curation. Shows 3-5 most relevant insights (e.g., "87% of cooks who tried this added extra garlic") with one-tap to apply modification.

KEY DECISION: ALGORITHMIC + EDITORIAL VS. PURE ALGORITHM
Hybrid approach with test kitchen validation. Pure algorithm risks surfacing unhelpful mods; editorial maintains NYT's quality standards.
Trade-off: Slower to scale (editorial review) vs. maintaining brand trust. NYT's differentiator is human judgment—users trust us because professionals test recipes.

Meal Companion Recommendations

Suggest 3-4 complementary dishes to create complete meals using rule-based pairing logic (flavor profiles, cooking method balance, nutritional balance, timing alignment). Each suggestion shows why it pairs well: "Complements richness with bright acidity" or "Uses same oven temperature."
KEY DECISION: CURATED PAIRINGS VS. AI MEAL PLANNING
Made it free for all users. Safety features = brand moat.Start with rule-based pairings (3-4 months to ship) vs. full AI meal planner (9-12 months). Users already comfortable with "recipes that go together."
Trade-off: Simple immediate value vs. comprehensive personalization. Pairing data becomes training set for future AI features—iterative learning approach.

In-Recipe Placement Strategy

Community Tips appear as collapsible card directly below ingredient list. Meal Companion module appears below recipe header. Meet users where they are (89% of sessions start with single recipe search), then guide to deeper planning features through progressive disclosure.

KEY DECISION: IN-RECIPE VS. DEDICATED MEAL PLANNING SECTION
In-recipe placement with option to explore meal planning hub. Users browse recipes individually, not in planning mode initially.
Trade-off: Higher discoverability (in-context) vs. dedicated planning experience. A/B test flexibility to iterate on placement (above/below recipe, sidebar, modal).

Phased Implementation

Suggest 3-4 complementary dishes to create complete meals using rule-based pairing logic (flavor profiles, cooking method balance, nutritional balance, timing alignment). Each suggestion shows why it pairs well: "Complements richness with bright acidity" or "Uses same oven temperature."
LEARNING APPROACH: BUILD-MEASURE-LEARN
Phased rollout with clear hypotheses: (1) Community tips increase recipe success rates, (2) Meal pairings drive cross-recipe discovery, (3) Confidence features reduce reliance on "safe" recipes.
Trade-off: Simple immediate value vs. comprehensive personalization. Pairing data becomes training set for future AI features—iterative learning approach.Risk mitigation: Editorial review flags problematic modifications, A/B test specificity of recommendations, progressive disclosure to avoid overwhelming users.

Critical Strategic Decisions

DECISION
CHOICE
RATIONALE
Algorithm Strategy
Hybrid (NLP + Editorial)
Pure algorithm risks bad advice; editorial maintains NYT quality standards and brand trust. Test kitchen validation adds credibility: community wisdom + professional endorsement.
Pairing Approach
Rule-based → ML later
Ship curated pairings in 3-4 months vs. AI meal planning (9-12 months). Users already comfortable with "recipes that go together." Pairing data becomes training set for Phase 3 ML.
Feature Placement
In-recipe (progressive disclosure)
Concentrate supply. Highest wildfire impact + largest user base + most displaced REI guides.
MVP Scope
Strict (WFR + insurance)
80% of recipe browsing on desktop. Focus on learning and iteration with manageable scope before scaling to all 20K recipes and mobile app.

North Star Metric

Subscriber Retention Rate (90-Day Cohort)

If we increase retention among casual users (1-2 recipes/month) by 15%, we validate that we've transformed NYT Cooking from recipe repository to indispensable cooking companion. Retention is the ultimate measure of delivering ongoing value.

12-MONTH BUSINESS IMPACT

$X.XM
Retention among casual users
+YY%
Daily active users (3+ recipes/week)
+ZZ%
Churn in first 90 days
Alaska Airlines
Mobile App
DoorDash
AllTrails
Wealthfront
Strategy
Open Table

Engineering delightful solutions to problems that matter.

Home
IMPACT
RE: DESIGN
BEYOND