Item: Wrike
Rating: 8
Author: Verified User

Use Cases and Deployment Scope

I am a UX Designer that works on the product team, and I use Wrike often to communicate with teams and submit requests for items and assets. It solves the problem of staying organized and keeping on track with pending requests. Wrike allows us to keep moving forward and informs the right people to get us what we need to complete our designs.

Pros and Cons

Allows all requests to be managed and accounted for in one place.
Keeps track of pending ideas and future product designs by submitting requests to add to 'backlog'.
Provides an understandable and easy-to-track log of items that team members can interact with intuitively.

Better tracking for the status of a request.

Return on Investment

Alternatives Considered

Atlassian Jira Align

At my company, we use both Jira and Wrike. Jira is used more for task management and communication between designers, developers, QA, and product owners, and Wrike (at our company) is used more for request submission to specific teams.

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

Atlassian Jira Align, Trello

Likelihood to Recommend

In the user case that we use it in at Torrid, it is a bit difficult because I believe we can analyze it a bit more. We also use a software called Jira which we also use to submit tickets and requests. If there were more functionalities within Wrike that I/the company was aware of, maybe we could find more ways to incorporate them into our workflow!

Wrike for Request Submission!

Overall Satisfaction with Wrike