Asana, your solution to workflow in distributed teamshttps://www.trustradius.com/project-managementAsanaUnspecified8.410021012018-12-12T00:15:32.236Z
December 11, 2018
Asana, your solution to workflow in distributed teams
Score 10 out of 101
Overall Satisfaction with Asana
We use Asana across our design and development teams in a modified dual agile format. It's an incredibly useful and effective tool for communication and information sharing. Implementing Asana helped resolve many communication issues we had between teams around needs, user stories, requirements, the intended implementation, and how the details fit together, both large and small.
- Cross-team communication is always a challenge, but Asana helps make information transparent and accessible to all members of the team.
- It's easy to share with individuals outside of the organization and still control the flow of information.
- Being able to link in other design resources like InVision prototypes is a huge time saver.
- Integrating with Slack makes much of our necessary communication automatic.
- Asana does a lot, so it can sometimes be hard to find the right place to be to find the tools you need.
- Organization is only as good as you make it and just because a system makes sense to the person that creates it does not mean it will make sense to anyone else.
- It can be challenging to find the information you need via search.
- Asana helped unify our software design and development teams, reducing churn and re-work, and saving money.
- Asana ensured we had clear design requirements mapped to business goals and product requirements.
- It helped with our overall communication.
There were a combination of factors that led us to decide on Asana, including ease of use and external system integrations, but primarily we could use it across geographically distributed offices successfully and incorporate a variety of end user work flows based on global geography, team constitution, and market focus.
Asana functions particularly well in scenarios with well-established teams with well-established processes and a mature SDLC. The reason is that Asana can be configured to do many, many different things, and be used in many, many different ways, and with that power comes a lot of responsibility to figure out your process before you try and automate it. It's software, not magic.