Aha! Roadmaps vs. Wrike

• Aha! is the all around product management tool. You need something once you build out a product management role and grow beyond a small scrum team with one or two products. JIRA, Pivotal, and project management tools don't cut it for aligning [engineering] with product initiatives once the backlog starts to scale.
• On the other hand, there are several unfinished features that my peers all admit to having to work around: Capacity Planning, Salesforce Integration, Roadmap Display Flexibility, User Feedback, etc. This year has been all about reporting in terms of feature releases. As Aha! grows, they will fill in these other areas, so stay tuned.

Negotiations often involve long timelines and multiple rounds of discussion. Wrike allows us to assign clear ownership, track due dates, and monitor progress so that nothing stalls or gets lost. Redlines, proposals, and finalized agreements can be stored and shared within Wrike, reducing reliance on scattered email chains and ensuring everyone is working from the most current version.

Incentivized

• Work breakdown - it allows teams to do initiatives, capabilities features and stories all in the same product release.
• Roadmapping - allows for simple combined visual plan of work breakdown across multiple initiatives.
• Customization - allows different levels of work breakdowns to be available on different projects.
• Integration with Rally and other tools.

Incentivized

• different views to accommodate different users workflow
• predecessors and successors to tie tasks together and adjust dates as a group
• Being able to see other people's workloads so when I am planning my projects for the upcoming quarter, I can set a project delivery date that is better suited to workload and is more realistic

Incentivized

• Notes - There's not a great place to leave lots of notes or instructions, almost like a Confluence page. Although not required, it would be nice to have this built in.
• Learning curve - As with most new tools, there's a bit of a learning curve to become proficient.

Incentivized

• Templating.
• For example, let's say we are onboarding a new client. There are certain tasks that need to be done. It would be great to be able to create a new project and have certain tasks preloaded.
• Importing.
• Importing may seem easy, but there is so much nuance to it. The fact that you need to make sure the parent task comes before child tasks is very difficult to do without the help of AI. Also, I am not sure it is possible if you have a thousand tasks to import, to make sure that you have a folder structure and parent/child tasks.
• I also find that the documentation is lacking and the 2 import methods lacking as well.
• Customize my inbox. When I log into Wrike, my Inbox is the first thing I see, but this doesn't show the full picture of what I want it.

Incentivized

I wish that Wrike had more drag and drop functionality that would be connected to assignee and also I wish that the finish date of a task would update to the date where you checked completed. It does not do that. Also finishing a task doesn't move the start date of the next task it "protects your time in that way", but our management team wants us to quickly see what we have down the pipeline rather than having to scroll down the list of upcoming tasks.

Incentivized

If you have the time and resources there really isn't anything you can't get Aha! to do for you in regards to managing workflow and releases. The Prioritization features are top of its class, the dashboards are getting better and better every day and the team all seem to really enjoy using it to manage their workloads.

Incentivized

I love the way task management is designed within Wrike. The full overview, followed by sequential updates, really works for us - this way, we don't need to go into individual people's work subtasks to find what's happening with a project. That's very useful from a project management perspective. The to-do feature also lets everyone access info in one place.

Incentivized

Over two years of (almost) daily usage without outages. Don't remember any errors. I give it 9 only because some Wrike plugins (for online document edit) are based on NPAPI architecture. These types of plugins are being phased out in new browsers, and NPAPI plugins are disabled by default in recent versions of Chrome so you have to do some browser adjustments when you switch browsers or move to another computer.

Wrike tasks loads fine, but I hate clicking files and wait for a bit of time since it is powerpoint or word, Wrike assumes I want to open those on Wrike. My suggestion is to link it to office 365 so we do not need Wrike based decoder for PPTX and DOCX

Incentivized

When we signed up for Aha!, we were assigned an Aha! team members to help us with training/questions. The meeting was set weekly, and it exponentially helped with our familiarity with Aha! Support is beneficial and has a lot of experience working with product teams.

Incentivized

We've had so many questions during the establishment of Wrike for our team, and the Wrike support team has exceeded our expectations. Our team is naturally curious, and the Wrike support team has always been willing to hold conversations about how we can make an idea work, to show us hidden features that delight us, and to help us plan ways to build out projects efficiently. They meet our questions with multiple solutions and best practices

Incentivized

We had staff in person provide some training

Incentivized

I love the Wrike training options. Wrike Discover has tons of courses, learning plans, certifications, etc. This is an area where Wrike definitely shines! I wish these resources were more in your face for new people, because it seems like a lot of coworkers didn't know all of this training was available to them.

Incentivized

There are a lot of bells and whistles in Wrike, and not all of it is easy or intuitive to understand once it's plopped in your lap. It's easier when there are a few choice people who understand Wrike as a platform and articulate it in such a way where it makes it easy to pass it along to others in the group

productboard was used in the organization when I arrived, but after assessing productboard, I felt it was too lightweight for our ambitious product goals. It's also critical, especially in a startup, that we focus our limited capacity on the work that matters most. Aha! far and away had superior capabilities in defining strategy directly in the product and associating all of our work to the strategy. Aha! is a serious product management tool and I found productboard to be more of a simple backlog management tool.

Incentivized

Jira did not at all help us get our work done as content creators. I think that was because Jira wasn't quite right for our uses. Wrike fits our needs so much better. I can't tell you enough the relief I felt when we adopted Wrike and I never had to use Jira again.

Incentivized

Wrike has significantly enhanced our workflow and productivity, ensuring accuracy and efficiency meet high standards. Our work now reflects professionalism and top quality. Other departments have taken notice of how organized we are thanks to Wrike, and we take great pride in our work—all made possible by this platform

Incentivized

• It has been able to deliver a good overall view of all the items we have going on in ADO.
• We are in the process of transforming from waterfall to agile development and to be able to see an overall picture of the work items is invaluable.

Incentivized

• Wrike has improved our resource management significantly.
• Wrike has improved the request intake process for us.
• One negative impact of using Wrike is that we had to include Workato for some customised automations, which were not supported by Unito, but this can be on a need-to basis.

Incentivized