Marg Aha!

There is nothing I like. Perhaps the ability to organize projects and have a roadmap for when tasks will be completed, but honestly a google doc would be better.

It is impossible to navigate and to communicate with other members of your team on Aha! I can't tag members of various teams in posts (perhaps I don't have sufficient privileges?. We have been using Aha! for about 3 months now and I still can't figure out where the information I need to access is.

Don't get it. You may need a couple different softwares but it is better than one big mess.

I haven't realized any benefits, only more issues. Aha! was supposed to be one place where all the various teams of our company could post problems that needed to be fixed, upcoming releases we would be having, and a general roadmap for the year. I can't easily see all this stuff and the layout is terrible.

Aha offers a ton of tools for creating, assigning, managing, and getting an overview of projects & their tasks. If you don't like one way it presents that information, you're sure to find a couple of different views that might give you what you want.

I was not using the high-level project timeline and overview pages, but they seemed like they could be helpful for someone who's overviewing multiple teams.

Their support team was very responsive, but did tend to ignore some problems even when presented with a solution and offers to work with them.

All of the tools it does offer are cluttered, over-complicated, and half-baked. There's not a good way to keep your focus to a single project (Referred to as a "release" in Aha!. You're either in the board that shows all of the features (What Aha! calls the top-level tasks in a release for all of your releases, in the detailed view for 1 release which removes functionality like reordering priority, or you're on their attempt at a Kanban board which shows everything for all members, even ones who have no part in the current release you're looking at. With a team of ~30 members, having a board that shows 30 people for a project of 3 is just untenable.

Aha also doesn't seem to take a stance on how its features should be used. A "release" is comprised of "features", which can have attached the them "requirements" and "to-dos". Requirements MUST live on features, but to-dos can live outside of features. Todos and requirements have different fields which I always find myself wanting a combination of the two. And given all this, Aha offers no suggestion of how you should be structuring your projects. This caused every project in my organization to be managed in a different way, often leading to ignoring either todos, requirements, or both.

They also charge per user based on that user's permissions. We work in a very flat organization where everyone tends to have complete control, but because Aha gets costly when everyone's an admin, we had to bottleneck our flow to a few people who had full control.

For the usability issues, I resorted to writing a chrome extension to try and help people out on my team. You can find it here, though I've ceased development since we have stopped using Aha https://chrome.google.com/webstore/detail/hgohigknlcabobkokchfabjikhjhklgm/publish-accepted

Try using it and see if it makes sense to you. But don't try to force yourself to work in its ecosystem, if it's not working, it probably won't get better.

We're a product team that splits of developers and designers in to small teams to complete features for our product. These teams usually consist of 2-4 people in a team of ~30. Aha was good for keeping us all in the same system, but it was a complete mess within each team's organization of the individual projects.

Aha is customizable, but that is also its greatest weakness. If you have simple and regular workflows that can be easily broken down into structured deliverables, then this product might work for you.

We moved to this product from Trello, and it has been a difficult transition. Only one or two individuals in our company have the highest permission levels which are necessary to manage our team's unique workflows, which include projects with a series of steps that need to be transitioned to "Done" upon their completion. As such, I can only actually transition roughly 80% of steps within each project to "Done", then I need to ask an individual to transition the other steps for me (which is ridiculously annoying and time-consuming. Additionally, we now use the system to manage quite of bit of communication between the various teams in our company, but it is difficult to tag other users within the system when commenting, and some messaging requires logging into a separate portal. Altogether the system is trying to do way too much, and ends up being unable to do anything well. The team at Aha needs to seriously refocus its efforts on doing one thing well, like Trello does with its card-based project management system.

I mean, if you like to make more work for yourself, then by all means go right ahead. If you want to reduce the amount of work you have to do on a daily basis, try a different product.

I haven't really realized any benefits. What work used to take an hour by using a combination of google docs and Trello now takes a minimum of two hours in this system.

We like how the tool visualizes releases and features. When it worked it significantly improved cross-team communication and feature prioritization.

Aha's customer support is terrible I'm afraid. Every e-mail is with a different person, they are slow to respond, often do not have details shared previously with other people, and are unwilling to get on the phone long enough to actually solve a problem.

The integration between Aha! and JIRA is particularly terrible. It worked for us for a while but then we were encouraged to move to their newest version of the integration and it has since been non-functional for the past 3 months. No one at Aha! has been able to help resolve it and it appears that even if it worked, a key feature (displaying story points in Aha! has been removed from the integration.

Do not integrate it with JIRA unless you absolutely have to and be prepared for customer support to be slow and uninterested in really helping you.

When it worked, our product owner was able to lay out several releases of features for our business sponsors to see in a format friendly to non-technical people.

Aha gives users the ability to made roadmaps and views to layout an entire project or team goals. It also provides steps that can be checked off and completed as they're finished. Users can also assign their self or teammates on steps or projects.

The whole product is super unintuitive. It looks like it was designed in 1999. I know most users of the product will probably be dev or product teams, but for non developers or product managers, the tool is pretty awful.

Take a day or two to familiarize yourself with the navigation of Aha. Figure out what you want and need to get out of the product before implementing it. If not, it can feel like a hassle and a black hole.

Organizing and tracking team contributions and roadmapping upcoming projects.