Wrike × City of Reno
Wrike x City of Reno, cross-department coordination for a growing city
Siloed and disconnected to cross-departmental visibility
Members read free
Unlock the full breakdown
Enter your email to open every case study in the library: the full screenshot, why it works, and the one thing worth stealing. One email unlocks all of them.
Free. No spam. Unsubscribe anytime.
You're in — enjoy the library.
Why it works
The story has a clear before-state: siloed software, too many moving parts, and no single tool that worked across all departments. The mechanism is concrete, showing exactly how Wrike was used for a specific deliverable, the State of the City event, with file sharing, reporting, and custom fields each given a named use case. No headline metric appears, which keeps this a Solid rather than Strong piece, and the primary type is a genuine coin-flip between Efficiency and Clarity since the win is both reduced coordination friction and new visibility into project status.
Steal this
Anchor the abstract platform benefits to one named, recurring deliverable (the State of the City event) so readers can picture the workflow instead of just reading feature claims.
Click to enlarge ↗ This is editorial commentary and curation. The case study, screenshot, and all metrics are Wrike's published work; we link to the source and lead with our analysis.