Purdue UX x Cisco U
Purdue UX Experience Studio Spring 2023
Cisco U is a personalized online learning platform intended to prepare people to have the knowledge they need to acquire new certifications. Our focus on this project was to take the desktop learning platform and adapt it for a mobile platform while also adding new features that specifically cater to the mobile learning experience.
For this project, we focused on one of Cisco’s user personas: “The Rising Professional.” We chose this persona because it was most similar to our interviewees. We also found that the Rising Professional persona integrates well into the idea of Cisco U mobile. Since these people are employed and commuting to work, they have a bit of downtime during their commute that could easily be used for mobile learning.
Below is a visual describing Cisco’s Rising Professional persona. Rising Professionals are full-time employees looking to either develop new skills or brush up on pre-existing ones
Our Process
In order to best tackle our project’s problem space, we centered our work around three different pillars of Cisco U. For each of these pillars, our team utilized several research and design methods to eventually create our final designs.
Each pillar of our work and the methods that accompanied it are as follows:
Guidance | Depth | Community |
Goal: To develop a more personalized experience for users that is tailored to their needs as a learner. Methods Used: Secondary Research, Interviews, Ideation, Wireframing, User Testing | Goal: To support users in enriching their learning through clearer access to supplemental materials. Methods Used: Interviews, Ideation, Wireframing, User Testing | Goal: To provide opportunities for users to aid each other in their learning. Methods Used: Competitive Analysis, Interviews, Ideation |
Guidance
To understand how Cisco U currently incorporates guidance into its design, we looked into the existing feature set and tried to map out a journey for any areas that could serve as a foundation for opportunities to enhance the journey in a mobile experience. Our main focus was looking at features that incorporated personalization and provided users with a clear blueprint for their learning.
“Thinking about my future goals and wanting to stay up-to-date with the rapidly changing tech industry helps me hold myself accountable.”
Based on the interviews, our main goal here was to create a study plan questionnaire to help users create a customized learning plan that fits within their schedule and helps them balance their time between working and studying.
Our original idea (as shown on the left) was that users would complete a questionnaire to make a custom study plan. The app would generate a plan based on their answers and the study plan would then be integrated with a calendar on the app. This form also allowed users to indicate whether or not they wanted to be paired with a mentor since many interviewees indicated that they liked having a study buddy to hold them accountable. |
We conducted concept testing of our study plan wireframe with members of our user group, our professor, our TAs, and classmates to evaluate our ideas and get their feedback on what aspects they liked, what we should change, and what we should add. (see our protocol in Appendix C)
Based on our feedback, we decided to just focus on three questions from the original study plan wireframe. We changed the phrasing of some questions to be more clear such as:
We chose these questions because they are the most important to consider when creating goals.
Instead of filling out a questionnaire, the user sets goals for themself. First, they select the day they would like to complete their course. Then, they select the days of the week they would like to study and the start and end times for their study sessions on those days. The user can modify their goals at any time.
Overall, our goal setting feature was well-liked and many people said they would find it useful.
This wireframe was our initial design for how users could create their calendar. Our initial idea was that users could view their calendars and goals. The darkened circles were dates with study activities, with the black circle being the planned completion date. |
We concept-tested the above prototype with several users in our target user group..
We user-tested this calendar with people in our class, our professor, and TAs.
Depth
Since our definition of depth involves both information retention as well as allowing users to go into more detail within the subject matter that the users were already learning about using Cisco U, we wanted to explore the features that were already available to them and evaluate how effectively they were doing so. Our initial research also focused on understanding how the average Cisco U learner goes about learning and if the current Cisco U journey caters to those needs effectively. Any gaps identified in this stage could be key ideas we could take into our ideation sessions.
The main activities we performed to get a better understanding of depth in Cisco U were:
The Supplemental Content section provides users with all the additional materials necessary to broaden their comprehension of a given topic. This includes a variety of resources such as podcasts, webinars, and videos, which can all be accessed from this page.
We interviewed several rising professionals, and they discussed supplemental learning. We kept the questions open-ended to get genuine and honest answers from the interviewees. These interviews were provided by UserTesting.com and scheduled by Aiza.
This is the prototype of the supplemental content. We have it organized by content. It will be found under the course. We brainstormed on where to put it, and we want the user to see what content they have based on the module they are in. If they are struggling, of course then they can see all the supplemental content they can watch. |
We conducted user testing on our teaching assistants (TAs), where we demonstrated the features we developed and solicited feedback on our designs. Our objective was to gauge the confusion levels and areas requiring assistance for someone who is new to the features.
Users want supplemental content and to learn more, so by having it all on Cisco U the user does not need to find their content. Our goal with Cisco U is to have all the resources a user would need to study on one application, and supplemental content is all the extra content in one place.
Some next steps are to collect supplemental content and make it organized in an easy way (general content or based on the certificate the user is taking to have a filter on the content). We brainstormed on where this will be found, right now, we have it under the course but we also thought about having supplemental content as its own page.
Our flashcards section was designed to provide users with a tool to study and review content. Flashcards will be populated with the end of module questions, and users can also make their flashcards based on the content they want to review.
We interviewed several professionals who have worked through a certificate and discussed their study habits. Protocols for these interviews can be found in Appendix A.
Prototype + InspirationThis is the flashcard page. A feature to start the card allows users to select cards they struggle with. Also, users can see the cards in an expanded form by scrolling down on the page. |
A round of user testing on the flashcards was performed on our TA’s to gain feedback. Protocols can be found in Appendix D.
Our notes function was designed to be a storage space for all of the saved information throughout a course.
We interviewed several rising professionals, and they discussed how they like to maintain depth within their learning. The protocol can be found in Appendix B.
We decided to model our notes function based on the notes app and wanted to sort sections by lesson, course, and module.
Notes will be organized by content. WIthin the notes per content user’s can copy over sections and texts from the module and add their own annotations and notes. |
A round of user testing on the flashcards was performed on our TA’s to gain feedback on our features. The protocol for this test is in Appendix D.
Community
To understand how Cisco U currently approaches community, we analyzed the platform and held some interviews with members of our user group. Additionally, we want to understand how we could create new opportunities for a community on Cisco U to enhance users' learning and networking experience. Our main focus of this part of our project was to understand how we could integrate elements of community into the existing framework of Cisco U. We wanted to avoid adding entirely new and separate features that are withdrawn from the current user flows and processes we identified earlier on in our work.
We looked into 5 different learning tools containing varying kinds of community centered features. These included: LinkedIn Learning, Coursera, Duolingo, Rosetta Stone, and the Discord for Google Certificates (a recommendation to look into from the Desk Critique). For each we asked questions such as, “What community features do we want to take inspiration from?” “Existing resources for help? How can someone answer their questions?” and “How do they connect people?” and we also categorized strengths, weaknesses, and opportunities for each.
Based on four 45 minute interviews with industry professionals who have experience using Cisco Learning Network, we found insights relating to how they might engage with their community through their learning process.
We completed some open-ended sketching activities to ideate how the concept of community might look within Cisco U.
After scoring low on review questions, users could “Post on a Forum” to receive help from the community | Users can access a Q/A tab within a learning path |
Provide users the opportunity to join relevant communities based on the learning path they are studying | Use tabs to organize users’ relevant information, including a tab for “Groups” |
We felt that the most realistic and helpful way, based on our research, to involve the community into Cisco U would be to nest a forum styled Q/A within each course.
Rationale for this includes:
Home Page
In our competitive analysis, we found Rosetta Stone’s home page was very clean and efficient and detailed everything very clearly. We took some page layout inspiration from here as well as from the progress bars shown on top of the homepage. |
EX: “Starship” app banner | Goal: Connect all features to make them easily accessible for users. Our Ideas:
Rationale:
|
In these iterations, we combined ideas from our initial ideation stage and created a variety of slightly higher fidelity wireframes based on our different concepts. These designs kept the carousel, the sync function, the layout, in addition to adding progress bars and goals. |
In our final wireframe, we combined features from our two iterations. As shown in the example screen to the left, the top of the screen will list the user’s name and goal for the selected day. As the user selects each day it shows their goals for the week. The carousel will show current features of Cisco U, promotions, or anything else that could be important for the user to see. The “Jump Back In” button will be used so users can sync with where they left off on desktop on mobile. Going down to “My List”, all of the learning paths the user is currently taking along with their progress will be shown. The “Study” page will also have the user’s flashcards and notes. |
Towards the end of our project, our group began to develop a set of slightly higher fidelity wireframes for our home page with some refined features or new concepts. Most of our work here involved concepts for a navigation bar that included features such as a goals/calendar view, a q/a page, and notes. Although we were unable to thouroughly test these designs with members of our user group, we did perform some rapid fire-styled user testing with our UX peers and TAs. Through this feedback, we found that having a traditional-styled navigation bar would be more easy to use on the go and that the “Jump Back In” button should get pushed below the My List. |
When opening a learning path, this is the screen a user would see.
In our competitive analysis, we again took inspiration from Rosetta Stone’s progress bars. We also took inspiration from Duolingo’s goal setting. Through our interviews with users of Cisco U, we were able to find that many of them believed they would benefit from a linear progress bar styled graphic, similar to the one seen with Rosetta Stone. Our interviewees also stated that they believed a set of daily goals would be beneficial in helping them stay on track with their learning. |
Goal: Create a learning path homepage that aligns with our home page layout. Our Ideas:
Rationale:
|
After receiving feedback that our material for each module should not be separated from the supplemental and study material, we developed the final version of our learning path home screen. The top of the screen now shows how much of the learning path is completed, followed by numbered modules and the goal date to complete each module. There are also progress bars for each course as well as the pre and post assessments. |
Conclusion
We wanted to test with Cisco U users interested in a mobile app. However, due to time constraints, we could not test with people from our user group; instead, we tested and evaluated with our TAs in class.
Users would like to see more relevant information in the homepage carousel, such as:
Testers were confused about what “jump back in” meant. Changing the wording so it is clearer to users that this button is for returning to the content users were on their desktop would be better. | |
We learned that users would like to know if they are falling behind on deadlines or goals that they set for themselves. They would also like to have a pop-up asking if they would like to change their goals.
Some of the interactions in the Q & A section were unclear
A tester said that they would use the notes section on the phone as a reminder of content to review rather than a way to annotate content.
Users want both auto-generated content and a way to add their flashcards of the material.
Users expect a menu item with a home, their profile, and your courses.
During the exploration of multiple features throughout this project, we explored a few concepts that were more exploratory on our end and could be expanded on in the future. For the sake of this project’s scope, however, these ideas were excluded from the final designs we created but have been documented here for the sake of completion.
Based on four 45 minute interviews we conducted with people who have experience using Cisco Learning Network, (see Appendix B) we found insights relating to how our users engage with mentorship.
The initial sketches of this concept explored the option of allowing users to contact and be matched up with a mentor who best suits their learning needs The option to contact a mentor could be accessible from the learning path itself. The pairing process would be based on the learner’s preferred mode of communication and areas of interest. Paired mentors can also be highlighted on the learning path so that users can contact them when needed. |
These wireframes were designed for concept testing to evaluate if users would like having the option to contact mentors. Users can contact a mentor if they are confused by a certain course section through a button at the end of the lesson. |
This is a conceptual design of how the navigation bar would look within Cisco U Mobile. We used our final user test to determine what would be most helpful to have on a navigation bar, and we found the best features were the home page, a user profile, and the last opened course. |
Our design is for mobile software, so we had to design around mobile constraints, creating additional limitations.
For this project, our team was more focused on exploring new ideas and experiences for mobile instead of refined high-fidelity wireframes. Our focus was on how features would be integrated into supplemental learning rather than focusing on the visual design. Instead of design, we focused more on user interaction with specific learning features, and how those features would transfer to a mobile experience.
Something we found in our own testing of Cisco U mobile was that a lot of our depth-based content (flashcards, notes, and supplemental material) was nested too deeply within a given learning path. In our designs, it currently resides at the course level. However, for future iterations, our team felt that it would be smart to have this content at either the module level or learning path level. This would help with accessibility and allow for this content to be more actively used within Cisco U Mobile.
Our team also developed a few designs for a navigation bar in order to allow users to quickly switch between features such as notes, courses, and a user profile. Our team felt this would help users navigate the app easier and allow them to access more content in an easier manner.
Since all of the screens in this project are low to mid-fidelity, our team ideally wants to push these screens into a high fidelity if we have a chance to further the design process.
Our team was able to work collaboratively and effectively over the course of this semester during the process of this project. As a result of this, our team has been able to trust each other really well and operate smoothly. A huge thing our team struggled with was getting the scope of the design down quickly. There were a lot of times early in development where our team would struggle with Cisco U itself and how vast the scope is meant to be for this project.
Ideally, our team could have done more testing to narrow the scope of our design early on. Our team also was unable to schedule sessions to help understand Cisco U as a platform and work with Cisco to build a design strategy. This was always an option, but our team failed to reach out due to anxieties about communication with our sponsors. As a whole, our team communicated well internally, but had a bit more of a struggle externally.
Working on this project has been a pleasure for everyone on the team. We really hope you find use out of our work. It’s been a pleasure to work with Cisco this semester.