So we’ve been using QS for over a year now.
We started small, and everyone knew where everything is.
fast forward to today, we have a giant mess -
Some dashboards are team related (i.e. product, marketing, etc.) that contain many sheets, others are initiative related (i.e. adoption team which is cross functional), and others are ad-hoc-ish (annual campaign dashboard, feature rollouts) that are usually single or two sheets.
naturally, this causes much confusion, double work, and general dissatisfaction across the board.
Can you advise on how would you plan the dashboards “architecture” (not sure what is the right term here) so that we can scale and yet keep things organized and clear.
Edit: we’re a small team of 4 analysts, serving around 25 users. few of them are authors as well. Majority are busy and have little time to look for the right dashboard sheet.
Currently everyone are permitted to enter wherever they want (C-level and managers).
Hi @Ronny - First of all “Welcome to AWS QuickSight Community” and post the question. It is a very interesting question and I do agree when number of dashboard, data sets are increased, it is quite difficult to manage. From my experience we have implement below approach to have some control.
- Define a Governance process for AWS QuickSight to ensure right people has right access and organize the folders.
- We created different folders under shared folder structure w.r.t LOB. In your case, it can be marketing, Sales etc. Each folder has subfolders like Dashboard, Analysis and data sets and the require department artifacts are stored in respective folders. By saying that, it is bit operational head but down the line it will help us.
- We created a common folder where there is a common datasets or dashboard require.
- We provided the access to the end user depending upon their role and department.
By Saying that yes, we have to robust our governance process and with time, it will be better.
Hope above points provide your some details.
Regards - San
Thank you for the detailed answer!
I’ll edit the original question to better explain our scenario - as we’re a small team, and your solution is at much larger scale than what we’re currently handling.
But I am taking better usage of folders for controlling right person right permissions direction - thank you!
Hi @Ronny - To start with, collect all data sets, analysis and dashboard in an excel sheet. You can extract those details from QuickSight boto3 API programmatically. Once you got all details, start putting in a structure ( possibly in an excel sheet) and then start your governance process. Once you define the process, slowly it can be scattered to a larger team
Regards - San
So this is the path we’ve decided to try -
We’re re-grouping our sheets based on topics, and not teams - so that a certain feature’s dashboard would include everything there’s to know about that feature - product, marketing, etc.
Teams will still have dedicated dashboard, but it’ll include only team’s specific (UA for marketing for instance).
Ad-hocs would be build separately, and deleted after they’re no longer needed - analysis will remain so that we’ll be able to recreate easily.
thanks @Ronny , sounds logical. Can you please mark this solution so that it will help to other community members.
Regards - Sanjeeb
Thanks @Sanjeeb2022 for encouraging the community to help eachother by marking solutions. Thx!