The scope of the project was to improve findability on MuleSoft / Training to ensuring that leaners can easily locate courses, learning path information or resources they need. Next, the team align with Salesforce’s WES design system, and update the WCAG 2.1 compliant debt.
My team worked within 4 epics:
- User stories
- Info architecture
- WES component adoption
- Accessibility
We created a dedicated Slack channel as a space for conversation. Any PM, developer, visual designer, or engineer could post questions, feedback, and solutions. Our channel lead would link project resources, figma components, meeting notes, and more.
The team focused on the following:
- Clarify project goals
- Roles and Responsibilities
- Road mapping
- Jobs to be done alignment
The team worked with a developer population to find a narrative and the expected outcomes for these users.
The team used the “As a, I want, So that” format for our user stories. For example:
- As a new learner, I want to have suggested resources based off my job role, so that I can easily find relevant recommendations.
After capturing and vetting the stories, we created requirements that we pitched to leadership.
The team found findability and understanding content was not efficient. We tested hierarchies, labeling and browser search functions.
We found a good information structure that enabled new and legacy user to quickly and easily find the resources they need.
Now that we had a good IA structure, we started collaborating with the Salesforce design system team to review new component solutions.
We wireframed the IA within a few components to test with our developers. After which, we adopted the necessary components with the Salesforce style hooks.
The deliverables were standard figma and interaction specifications for each component.
The team focused efforts on micro animation and accessibility UAT audits. We backlog all issues for future sprints.
