Complex, but Worth it Once You Build the Processes.
Updated December 13, 2022

Complex, but Worth it Once You Build the Processes.

Stewart Foster | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with Wrike

We use Wrike as a project management system, mostly to ensure that requests from outside our team don't fall between the cracks. Originally, we brought Wrike in as a solution for all teams at our company, but the adoption rate was low, and it wound up only being used by the Marketing team. My particular use case revolves around the reviewal systems since I often have an eye on designs, copy, and other projects before they are approved to go live. Wrike solves a lot of problems for us, from task and deadline management to reporting. That said, I wish we could use a suite that was paired down and simplified for our less technologically-versed users.
  • Gantt Chart Task Dependency.
  • Notification System for Dependent Tasks,
  • Templates for Common Jobs,
  • Request System.
  • Personalized Workspaces (can be made specific for your position in the company).
  • Difficult to create/manage projects with no clear deadlines.
  • Steep learning curve, especially for older/less technological employees.
  • Many features go unused since we are a single team, not an entire enterprise.
  • Projects are hard to follow and annoying to organize if you are involved with multiple steps in the process.
  • I don't particularly like the comment system--it's just one thread as opposed to nesting replies.
  • Requests
  • Gantt Chart.
  • Project Statuses.
  • "Space" Creation and Organization.
  • Customizable Dashboards.
  • Reviewal Process.
  • Wrike has kept our freelancing budget from ballooning due to miscommunication. We now know exactly what is being done outside our company, how long it's taking, and what it's costing. I'm guessing it's saving us $10,000+ a year.
  • Our team's creative output speed has increased, particularly when it comes to the reviewal of assets. Things don't get stuck in the reviewal stage because of missed notifications.
  • We've seen an interesting decrease in emails within our team since many of our communications are now consolidated within one program.
Asana seemed pretty comparable to Wrike, and the decision ultimately came down to pricing. On the other hand, Monday has been something our team has been considering for a while, which would also be a cut in cost and significantly more simple (geared toward smaller teams). We're currently still using Wrike since we're in a year-long contract and because we now have a lot of internal infrastructure in Wrike.

Do you think Wrike delivers good value for the price?

No

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?

No

Would you buy Wrike again?

Yes

Wrike is obviously made for enterprise-level project management and is perhaps too complex of a tool for our size of the team. That said, I can still recommend Wrike because of its flexibility. If you need it to do something, chances are it has the features, and you can customize your workspace/workflows to your needs. We have been able to create highly specific workflows for peculiar and industry-specific tasks that an average Gantt chart or linear process wouldn't be the best solution for. Same with the requested feature, which allows our users to quickly and easily create common tasks that are frequently needed. Overall, I would recommend Wrike if you're looking for something a little more in-depth and are willing to put in the effort to set up your systems and get to a point where the time used in the program is small enough to justify the utility.

Wrike Feature Ratings

Task Management
8
Resource Management
5
Gantt Charts
9
Scheduling
7
Workflow Automation
9
Team Collaboration
3
Support for Agile Methodology
Not Rated
Support for Waterfall Methodology
Not Rated
Document Management
4
Email integration
4
Mobile Access
6
Timesheet Tracking
Not Rated
Budget and Expense Management
Not Rated
Project & financial reporting
8
Integration with accounting software
Not Rated

Wrike Implementation

Unfortunately, the implementation of Wrike was the reason why it didn't succeed at our company (we will likely be switching services midyear). It was originally slated to be a company-wide adoption but was immediately more useful to our creative team than our sales, engineering, or other project-based teams. Perhaps it was the fact that it seemed like processes outside of the average marketing team project needed custom workflows built, and we didn't have a dedicated employee who was implementing the system. In fact, now that I'm thinking about it more, that was a serious oversight: no dedicated, project-manager-like employee was heading the charge of rollout. Instead, the implementation was a bit of a wild-west, individual affair, so the marketing team ended up primarily using the software.
Yes - As a marketing team, we decided to roll it out in three phases, but they were not company-wide phases. It was just the way we thought it would take hold for our group. First, we had leadership attend a company offsite where they trained to train our team. The second phase was a personal meeting with leaders and their employees, who would explain some of the basic functionality and get them set up on the tool. The third phase was watching Wrike's training videos, which we did individually and then reported on in a weekly standup.
Change management was minimal - Our team at the time of implementation was growing, but not being restructured. So, our implementation focused on handling interdepartmental requests that had historically just been given verbally to the individual thought most capable, but now needed to be systemized if we had any chance at effectively handling a larger and more complex team. One notable management change that occurred because of Wrike was that requests for the marketing team that came from the sales team were now passed through a single member of marketing leadership (via Wrike), reducing the chance of non-priority projects getting elevated on an individual's workflow.
  • Adoption across the whole company.
  • CEO buy in.
  • Project manager specifically dedicated to company-wide implementation, not just team-wide.