My Portfolio - Learner communication report
2023
My Start
This project started with the need to deprecate an existing workspace holding multiple admin reports. I entered this project with the understanding others had determined what data was important to keep and who should see it.
My goals:
- Understand the legacy purpose, use, and user permissions for each of the 5 reports
- Understand the risks and benefits of exposing the data
- Determine how to architect data to provide meaningful insights that lead to increased administration satisfaction
- Supply direction on who can access the new reports
- Provide a UI mockup for changes to the reporting dashboard, the new report view, and instructions for all interactions (including sorting, filtering, and export)
Building an Understanding
We conducted client interviews with simple excel data prototypes to better understand perceived values and ask purpose-driven questions. I wanted to know who was using these reports, how it was going, and most notably what they wanted with the data. Another meeting with our client services stakeholders helped us determine the most important data could be more widely distributed and better benefit our customers.
I went through UX review exercises on the legacy reports helped me uncover a method of supplying more information in fewer reports and the initially desired 3 reports became 1.
From there, Product Management and I dug into the existing system site structures, user roles, and user permissions. Then, outlined who should have what permissions and roles needed to gain access to the new reports. This ultimately leads to a workshop including stakeholders from the customer services team, product management, and the senior engineering resources.
Exploration
Atypically, the limited explorations revolved around naming and the visual graphic used for the card in the report dashboard. This was the shortest phase of the project as most of the interface design was shackled by the existing reporting system - to change this report's behavior would mean changing them all.
The success in our earlier understanding and the reusability of the reporting dashboard meant most of my explorations fell inside validating the mockups from our understanding & research.
With the number of reports shown on the dashboard landing page increased, I had decided to change our grid for our largest breakpoint (1400) globally. This is an example of when work time is reduced through designing and developing. I added the new media styles and began regression testing to confirm the behavior I wanted was happening everywhere this grid was in use.
Wrap Up
I created new custom reports in our user tracking software to track both admin session counts to the application as well as interactions with this new report.
The communication plan was set and we had 100% legacy user satisfaction and new adoption in the first month.
The user persona work was made reusable as CorpU had no persona library before this project.
Success!
Want more?
I invite you to check out my LinkedIn profile or view my web resume page.
If you have any questions, I welcome you to contact me via my Google form or via your preferred social network.
Recently added FAQ on my About page.
Recently added design process page.
Recently added certificates page.