Focus #1: User Dashboard
When the project was in the ideation phase, I realized there was no place where all of our sections linked up. The user profile, where user information is usually found, was currently more of a resume/area for employers to see.
I designed & implemented a user dashboard so that Julian would have a central location to see all their project board information.
Evolution of the dashboard
Focus #2: Messaging/Notifications
User Journey Phase 3: Project Application Accepted is focused on what happens after Julian has submitted his application to a project and has been accepted.
Olas.io provides education for students to help them enter new tech career fields. However, students often struggle to find opportunities to gain experience & show their skill set after taking classes in a boot camp environment.
A new approach to education
Olas.io wanted to provide students with a project listing board to connect them with opportunities. Our team was tasked with designing the project board section of the app. I focused on the user dashboard, messaging, & notification systems.
The team met with the client to define the scope of the project & the current website brand. We defined the user journey & then divided the work into four sections. My section was Phase 3 of the user journey focused on after the client had been accepted & how they contact the company. The project timeline was 10 weeks.
1. View Projects/Courses
Main menu helps Julian to switch view between Projects/Courses
The submenu helps Julian view projects based on Status
Julian can see more information by clicking any of the project listing cards
2. View Badges & Endorsements
Julian can view his three most recent badges
Julian can view his three most recent Companies he has completed projects with and their skill endorsements of him
Dashboard Final Design
Due to the rest of the site design not existing yet, I needed to design a layout that could be expanded on in the future
When designing the menu and submenu there were lots of changes in content and order to best suit Julian's needs
When designing the project cards I had several iterations of content/layout trying to have the right amount of information that was beneficial to Julian
Final Design: Hi-fi Prototype
Design for sustainability: Working on a section of a website in progress, I had to keep in mind that most of the site was not created yet and think about how my design would work with future additions
Remote communication doesn't need to be hard: Working completely remotely was an initial challenge, however we made it work with strong communication across multiple platforms
Get client feedback early on: Running our early wireframes by the client saved us time by allowing up to fix things earlier instead of continuing to iterate on ideas that weren't what they envisioned.