Automagic dashboards

[janagombitova]

Context

Lumen dashboards are the end result of working with data (and they then feed insights into the initial phase of the data journey, so it's more of a circular process).

The dashboards are used for multiple purposes:

• monitoring the progress of a data collection
• understanding the data before starting analyzing it
• analysis of the data
• reporting

The great things about Lumen dashboards is that Salim can define them fully based on his need. He decides which visualizations to use, how to organize them, what other components to add.

This benefit however also has setback - it takes time to create a dashboard. And especially for cases where the intention of the dashboards is the same, where it's structure is used over and over again.

Opportunity

How might we give Salim insights into his dataset with zero effort needed from him (with no to only a very few clicks)?

Re-usable dashboards

We know from partners out because we create such dashboards for them, that in some cases the same dashboards are created but for different datasets. So the structure of the dashboards is the same, visualizations are based on the same columns, etc.

The known cases and possible other cases are:

• to monitor the progress of a data collection
• to get an overview of the dataset before actually analyzing it (Flow comprehensive summary export)
• for data coming from survey templates as the indicators/questions/columns are identical

Risks

How do we handle scale?

How do we ensure that the dashboards are useful and also follow good visualizations practices and are also interesting to use? (Involve data analytics team)

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.