Tasks have a large number of fields designed to capture every facet of data to be collected. Very few team members need to see all the fields. In some cases, specific fields should be hidden due to sensitive information.
Further, in a large company such as mine, many stakeholders want access to projects but only need to see a handful of items (example: task name, status, priority, and due date).
Project owners should be able to create multiple, customized list views, being able to control which fields are visible on these views. Each view has its own visibility rules (who can see the list view as a whole).
This allows a very dynamic solution described as the following:
Project owners and high ranking personnel can see the full project list view, seeing every field. This allows projects to tie in sensitive information such as finances or management notes.
Employees see a custom list view, seeing only what the project owner has determined to be safe (example: no financial data).
Other organizational stakeholders see yet another list view, showing only the high-level items described above.
With custom list views, it completes an important gap in Asana’s stakeholder management framework. Project owners can use Asana projects to work AND communicate the right information effectively. This feature will increase revenue by making Asana list views desire to a larger number of employees within an organization, as the number of stakeholders who can now utilize Asana for useful information would expand substantially.