Item: Wrike
Rating: 8
Author: Verified User

Use Cases and Deployment Scope

We use Wrike for task based efforts relating to software integration and analytics needs. It's essentially our ticketing queue we use to coordinate efforts between multiple teams. Multiple teams use Wrike and it's been pretty effective for requests, communications, and delivery of work. We leverage blueprints for templating and analytics for reporting.

Pros and Cons

Templates/Blueprints
Barrier to entry
Tagging

Best practices
Dashboards

Return on Investment

Competitive pricing for project management software

Alternatives Considered

Jira Software

For a long time, we liked using both pieces of software separately. Product development agile work goes in Jira, all task-based work for integration, analytics, and legal goes in Wrike. Wrike offers more informal flexibility that's easy for anyone to set up. Jira is optimized for Agile work. We also like that Wrike auto-saves everything.

Key Insights

Do you think Wrike delivers good value for the price?

Yes

Are you happy with Wrike's feature set?

Yes

Did Wrike live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Wrike go as expected?

I wasn't involved with the implementation phase

Would you buy Wrike again?

Yes

Other Software Used

Looker

Likelihood to Recommend

We like it for everything that's not product development work. Our product and engineering teams prefer Jira for this. For quick tasks that require back-and-forth, Wrike is perfect. It's quick, easy, and intuitive. For product development where work ties into a bigger picture it could be better. Wrike's flexibility is both a pro and a con. It makes it easy to start using and improve over time. It seems to be less tailored to agile product development work in a traditional sense.

Wrike is easy and flexible. Low barrier to entry, but getting the most out of it may take some time.

Overall Satisfaction with Wrike