Why did we create views?

Context

R&I workers have a need to visualize data in a different way depending on the research they are conducting or the clients they are working with.

80% of the time? (assumption)

Pain points

• They are wasting X% of time per 
• Not configurable/editable, filters are too rigid and not adaptable
• Not responsive
• Not always easy to use
• Not directly usable as reports as the design is not presentable to clients
• Not made to collaborate between users
• No feedbacks from the system when there is a problem with data

Potential solutions

• Users should be able to choose the type of component (type of graph/table) that they want.
• Tables and graphs: users should be able to add/remove columns as well as modifying the order.
• Users should be able to change the amount of data displayed
• Users should be able to edit the name of the data
• Users should be able to edit the legend
• Users should be able to make the table more compact/large
• Users should be able to quickly export the visualization and use it in a report.
• The visualization should be clear, accessible, aesthetic 
• Users should be able to easily and quickly share a view with their team (with the filters/configurations applied)
• User experience

OKRs - Target gain for the user

Effective, quick, empowers the user and team collaboration, one end-to-end app from data visualization to report generation.

What are views?

Views are regrouping data (workflows & filters feature) and way of visualizing data (layout & modules).
They are spaces where a users can analyze data depending on their needs.
Their needs are mainly related to the customer/project they are working with/on.

How to create a view?

1 - Admins choose the data according to the workflow he wants to creates a view for.

2 - Admins choose the structure of the page: he creates a view using as many building blocks as he needs. Each building block is a module (table, bar chart, scatter plot...). Building blocks can be rearranged in the page. (not in v1)

3 - Admin can apply filters, configurate modules (modify the columns, legend, colors,...).

5 - Admin save a view by default for a workflow.

4 - User access the view, modify filters, modify configuration (for himself only).... in order to analyze the data.

Futur improvements

• User can create a view
• User can save a view
• User can share a view with other users
• User/Admin can delete a view

KPIs - Validate the needs for this feature

The amount of time per year a user is creating a view:

• 4 times out 5, we assume that a user will use a view that has been created by an admin.
• 1 time out 5, we assume that a user will use or create a view that has been created by a user or oneself.  

PELLERIN, Claire and LEFEVRE-ext, Marie-Hervine to confirm?