Integrating Lessonly and Seismic
Here is the problem we are solving:
How might we integrate multiple standalone products in a way that is ideal for our customers?
My role was to create a high-level vision for how Lessonly Training and Lessonly Skills can integrate into 1 experience, renamed to "Training." Since the 2 experiences were designed to work very similar, this was an easier step 1 before integrating 2 systems that were completely different (Seismic and Lessonly).
Another Product Designer's role was to create a high-level vision for how the new Training experience and Seismic's existing product can integrate into 1 experience.
My role was one piece of the puzzle:
This was a highly collaborative effort that required multiple Product Managers, VPs, and Product Designers across multiple teams. This initiative required for me to communicate more than designing itself. I facilitated an ideation session with all of the Lessonly designers since everyone had expert knowledge of their product areas.
Some challenges: Of course, this process was not as linear as this visual communicates; we often jumped around and even backtracked since it was easy for stakeholders to misinterpret the goals, miss decisions that were made, or even get their voice heard. This resulted in me (and everyone on the team) focusing on over-communication, putting out fires, and even needing to voice concerns more than designing the experience itself.
Solution 1 of 2: The Long-Term Vision
Although this process was long and often bumpy, we were able to come up with a first-draft of how Lessonly Training and Skills can work together.
The major changes we made here:
- Learners (Lessonly’s end-users) can see skills, assigned content, events, and more in 1 dashboard experience (Skill levels and training content were 2 separate environments before, which resulted in confusion when understanding the connection between the 2 and lack of usage for the Skills app).
- Skills is the foundational element that branches out into training and learning content (From a mental model standpoint, the ideal hierarchy for a Learner is 1. Understanding the skills I need to build and 2. Viewing what training content is connected to that skill. The experience should reflect that mental model/workflow.)
- For an admin, skills is treated as another "element" when managing all content within the application (From an access standpoint, admins had to switch between environments to create skills, edit content, and linking those skills with the appropriate content. This was heavy-weight and often resulted in lack of usage for the Skill app.)
Some Screens of the highlighted Moments
Another Product Designer lead the effort to understand how Skills and Training can integrate into the broader Seismic environment. At the time of my transition into a new role at another company, the short-term goal was to iframe the Skills and Training experiences into the Seismic environment in a way that aligns with their structural UX and UI patterns.
Here is my interpretation of how this goal can work. This was not finalized when I left, but I was apart of the ideation and conversations for how this may work, so I had an idea of what the team was envisioning.
Consider the below screen as conceptual and not what was actually designed/built within the company.
For some of the design activities I helped facilitate, here are a few examples of the outcome!
Current features and where they overlap
Before we could truly ideate, we needed to outline all of the different product features across the board and identifying overlap. This helped us eliminate any duplicate functionality and create a more cohesive workflow.
- Document and Content Management
- Knowledge-based Information Tracking
- Data and Insights
- Training Creation and Completion
- Grading and Feedback Resources
- Repeated Practice Scenarios and Learner-led Training
- Data and Insights
- Creation of Coaching Plans
- Tracking of Assessments and Coaching Plans
- Assessment Data and Skill Insights
For the Lessonly Training and Skills products, it was important for us to understand the ideal user flow based on what our customers were doing today. We then highlighted which solutions linked back to that step in the flow, which provided a high-level understanding of how to best position each feature in the overall workflow of Lessonly.
An Ideation Session with Other Designers
Each designer at Lessonly had expert knowledge in different product areas. Instead of working in a silo, I brought together all of the designers for us to educate each other on how the products work + what the future goals and considerations are. Then, we brainstormed how we can begin to update the workflow to match the user flow outlined above. Here are a few screen grabs of that ideation in InVision Freehand!