Flow chart
After collecting my different types of research, I fleshed out some of the logic in the steps a user would take to build their widget. I wanted to explore the different types of data that could be involved, as well as what those types of data may additionall entail.
Design process
Once I felt comfortable with my understanding of KPI widgets, I began my process with design iterations.
Phase 1
In phase 1, I really wanted to just block out the elements in the widget in a minimal sense. I didn't add any complex content that was new -- only used the core elements that needed to be present and visually tested a few things out.
Phase 2
After conducting my different phases of research, I tackled the designs again but with functionality in mind (and less design). Below, the widgets may not be aesthetically pleasing, but I tried many different combinations of features to test the relationship between different types of data.
Phase 3
The third phase combines a couple of different design sprints, but below is a collection of the key contenders. Ultimately, I maintained the two column layout, but created different options (that the user can configure to their needs) for the user to choose as their supplementary data point. This can be in the form of a graph (line, pie, or bar, with their own restrictions to meet the standards of the small space they situate in) or another key metric. I gave more care into visual balance and consistency, and upheld the blue branding that Agilence has.