Hey @Rashad_Issa
Thanks for your insights.
For starters, I think that being able to organize the Reporting page is necessary no matter what the use case… it is a mess and difficult to navigate even If I have 1 dashboard per project. There are no sorting options and no filter capabilities.
We have around 30 company goals, about 110 team goals with about 260 “sub goals” and something like 70 company projects to monitor…
many of these require universal reports, so you can imagine the clutter our project management and executives might have on there reporting pages.
The new portfolio dashboards are a great help for this, but still don’t solve all the issue’s.
I require several different dashboards because:
a. There is a limit of 20 charts per dashboard and sometimes I require more to be able to present all the different fields in my projects.
b. I have a different audience for each dashboard, so each dashboard focuses on the items most relevant to that audience.
If we focus on my example scenario, there are a couple of reason’s I work this way.
At the beginning of the year I create all these dashboards in advance. This in it’s self is much easier now that asana has added the capabilities to duplicate entire dashboards (a real time saver!), and I do it in advance because it is much more efficient this way rather than dealing with it several times during the year.
We work with the OKR methodology, and the Q1, Q2, Q3, Q4 dashboards are never static. At the beginning of the year we plan our goals, and monitor the progress on a monthly basis. A goal that is set for Q3 (for example) doesn’t necessarily mean that you only start the work at the beginning of Q3, your progress towards Q3 can begin in Q1. Monitoring on a monthly basis insures a better chance of achieving the goal on time, and more importantly raising red flags on time, in advance, so that planning can adapt to work around issues.
I think If Asana creates a “porfolio like” experience for the reporting page, users will benefit from a more organized, clutter free experience.
Lets see… I might be the only one that has this issue ![]()