One of our design goals with Asana is to find the right balance of structure to streamline work without getting in your way. This lets us adapt to a wide variety of project types and processes.
While there are a lot of process-specific tools for each individual type of data, we believe that the separation of data across multiple systems increases the “work about work”. We can get work of all kinds done better, with less friction, by keeping everything in one place.
For example, we use Asana as a bug tracker. It doesn’t have all the bells and whistles of a dedicated bug tracker, but we’ve found that we get more value out of seeing our bugs with the rest of our tasks like new feature work and writing up interview feedback. This allows me to look in one place for all the things I have to do today, and everyone from our engineers to our recruiter can be sure I won’t miss their tasks.
This week’s video shows how we track bugs in Asana.