Asana × The Trevor Project

Asana x The Trevor Project, building infrastructure ahead of growth

The Leap Fit-proofROI-proofWritten narrativeChallenge-Solution-ResultsNonprofit

Why it works

Nothing was broken at The Trevor Project. They chose to build internal infrastructure proactively before growth made coordination painful. The story is squarely a Leap. The 348 workdays saved figure does ROI work but the framing leads with fit: a mission-driven nonprofit with cross-functional complexity finding a platform that could flex across teams with different working styles. The Fog Lifts archetype is adjacent given the transparency angle, but the before-state was suboptimal coordination, not an absence of measurement.

Steal this

Anchor the time savings metric to a mission consequence. The Trevor Project frames 348 saved workdays not as efficiency but as time returned to suicide prevention work, which makes the number land with weight a pure productivity claim never achieves.

View the original on asana.com ↗

This is editorial commentary and curation. The case study, screenshot, and all metrics are Asana's published work; we link to the source and lead with our analysis.

Vendor Asana
Customer The Trevor Project
Industry Nonprofit
Format Written narrative
Structure Challenge-Solution-Results
Medium Web page