Dashboard for Tracking Software Usage

Dashboard for Tracking
Software Usage

Ontario Public Service

I led early phase of design for a dashboard for tracking software usage (Power Platform) amongst Ontario Government staff. I collaborated with managers and data analysts to identify workflow gaps and technical constraints, translated them into product requirements, and produced a high-fidelity prototype and a component library to serve as a proof of concept.

Read Full Case Study

Read Full Case Study

Research

Workshops

Interviews

Card Sorting

Design

Prototyping

Information Architecture

UI and Components

Tiimeline

2 Months

Internship

Tools

Figma

Product / Industry

B2B

Government

Web Application

Internal Tool

Team

Individual

Define product requirements and design a proof of concept for a new dashboard for tracking employee usage of Power Platform software.

Overview

During my internship at the Ontario Public Service I led an initiative to improve an internal dashboard tool that helps Ontario Government managers track Power Platform usage and licensing across teams. Over four months, I gathered requirements through stakeholder interviews, identified KPI reporting needs, and delivered a high-fidelity prototype and component library to serve as a proof of concept.

Identifying how Managers Track Software Usage

There was no concrete source of information for what metrics and resources we wanted to track and how they can be organized. Through workshops and interviews with managers and data analysts I not only established, for the first time, consensus on what we were tracking but also identified mental models around the data through card sorting sessions.

Research Driven Information Architecture

Because of the previous research on data organization, I was able to translate my findings into an information architecture, which after being tree-tested and refined, ensured an organized and efficient set of screens.

Defining Components and Design Patterns

After defining the key screens, I designed modular components and refined navigation patterns, resulting in a high-fidelity prototype that, while conceptual, clearly conveyed design intent for future designers and developers to build on.

AI Features

Research showed that it was common to receive a list of user emails and asked to check for their license statuses. For similar use cases I conceptualized user flows that use AI to process searches using "messy" text formats such as a long list of email addresses, and file attachments such as spreadsheets.