Role
Lead UI/UX designer, product design, design systems, UX writing
Context
As part of my promotion to Senior Media for the Computer Room Consultant (CRC) team, I led a capstone project focused on improving the Computer Lab Management (CLM) applications. These internal tools—including the Training Database, Lost and Found Database, IT Prob, and Knowledgebase—are essential for daily lab operations, but their fragmented and inconsistent interfaces made them difficult to use efficiently.
The Problem
The objective of this project was to research, redesign, and create a unified design system for CLM applications, streamlining workflows for both student consultants, admin, operational support, and lab managers.
Team
Joe Castillo / Project Manager
Timeline
10 weeks
Tools
Figma
Solutions
PREVIEW
Research
👩💻 Competitor Research
My first step was to understand the constraints of the Computer Lab Management Design Library System (DLS) and find components I can leverage. I began by cataloging interface elements such as inputs, data display, feedback, and navigation. I researched in-class examples of existing React component libraries, such as Shadcn and Tailwind UI.
💬 Interviews
I conducted user interviews with student consultants, supervisors, and admin to learn more about how they used existing CLM applications. They revealed that they learned to navigate these platforms through in-person coaching, trial & error, or did not use certain features at all.
👤 Behavioral Testing
I conducted behavioral testing by observing each user group interact with the existing CLM apps while performing real tasks, such as logging IT issues or searching the Lost and Found database. During these sessions, I noted differences in task completion times, navigation strategies, and which features were used most or overlooked, uncovering specific pain points and inefficiencies unique to each role.
Synthesis
Personas
I recognized that the applications serve distinct user groups: student consultants, admin, and IT staff. Each group interacts with the tools differently and has unique priorities:
Student Consultants are the primary day-to-day users, needing quick access to data, intuitive navigation, and minimal friction in completing tasks like logging IT issues or checking the Lost and Found database.
Admin focus on oversight and reporting, requiring clear dashboards, aggregated information, and easy management of workflows across multiple consultants.
IT Staff rely on accurate and complete problem reports and documentation to troubleshoot issues efficiently.
Information Architecture
I mapped out the structure of each CLM application to uncover redundancies, gaps, and inconsistencies in their design. I created an information architecture (IA) framework by breaking down each tool into its core functions and categorizing them into logical hierarchies.
Affinity Mapping
Based on the affinity mapping of my research, user feedback revealed key usability issues across the four applications, primarily in navigation, information presentation, and discoverability of features. These insights highlighted the need to streamline cluttered interfaces, implement consistent navigation, and improve the visual hierarchy of information to enhance the overall user experience.
Redesign
Knowledgebase
While the Knowledgebase (KB) was relatively easy to use, users noted that critical information was not always visually clear. This made it difficult to quickly scan articles for urgent details. My solution was to apply a clear visual hierarchy. I maintained the strong search functionality while using bold text, larger fonts, and strategic spacing to highlight key information within articles. I also added collapsible sections to reduce scrolling. The redesign made the KB a more reliable reference by making vital details easier to access at a glance.
IT Prob
IT Prob was the central hub for IT support tickets, but it was plagued by confusing buttons, excessive scrolling, and underused search features. Users struggled to find information quickly and found the interface frustrating. To fix this, I redesigned the page with clear, updated buttons, and reorganized tables to prioritize recent items. I also made filtering options more prominent. The redesign led to a clearer, more efficient interface and faster task completion.
Lost & Found Database
The Lost & Found DB was cluttered with too much information, making it difficult to find items quickly. My research showed that users found scrolling faster than search and filtering functions. I simplified the layout by highlighting only the most important columns (item description, location, and date) and hiding secondary information. I also improved sorting tools and added tooltips to guide users. This redesign reduced frustration and enabled faster item lookups for both students and staff.
Training Database
The Training DB lacked basic navigation support, which made moving between screens inconvenient and frustrating for new student consultants. The biggest pain point was the absence of a back button. I addressed this by adding consistent navigation elements, including a prominent back button and a clear header hierarchy. I also simplified workflows to minimize clicks and user error. This improved the overall navigation and provided a smoother onboarding experience for new hires.
Usability Testing
Validating my designs
I conducted usability testing and A/B testing to evaluate whether the new interfaces improved efficiency and clarity for consultants.
For IT Prob updates, I redesigned the split view into a threaded layout showing issues, stats, and past updates together, with edit options directly below. Testing showed consultants found information faster and felt more confident when making updates.
For Lost & Found edits, I replaced a multi-step form with a pop-up modal to keep users in context. Consultants completed edits more quickly and with fewer mistakes, since they no longer had to switch pages.
Design System
Branding
My goal for our design system was to modernize the UI for a better user experience while maintaining core functionalities. I used Shadcn components to streamline development, added subtle drop shadows and rounded elements for a contemporary look, and used a bright blue to highlight key interactions while incorporating the existing UC Davis colors.
💎 Component Library
I designed my project to scale it as a reusable component for the Design Library System for teams across the Computer Lab Management to adopt in custom solutions. I detailed development notes and handed-off an organized final Figma file to allow the engineer to jump in and implement without needing to ask for much input from design.
Solution
Knowledgebase
FINAL PROTOTYPE
Search online resources containing guides, FAQs, and troubleshooting tips to quickly find answers.
IT Prob
FINAL PROTOTYPE
Report and track technical issues so support staff can resolve them efficiently.
Lost & Found Database
FINAL PROTOTYPE
Look up items that have been turned in or reported lost to help reconnect belongings with their owners.
Workshops
FINAL PROTOTYPE
Join interactive training sessions to learn new skills and get hands-on practice.
Takeaways
✨ Develop Design Craft
This project allowed me to practice critical thinking, attention to detail, and human-centered design thinking to consider all the useful features I could add to such a simple tool. I sought opportunities to experiment with novel interactions and patterns and explore edge cases that were not initially captured in the project brief. Through my collaborations with engineering, I was able to learn how to consider edge cases and understand backend logic to build a component for the Design Library System.
In the end, I was able to deliver a feature that is intuitive and functional, with a visual system designed to subtly educate the users of shortcuts available but ultimately give all control and flexibility to the end-user. The most rewarding experience for me is knowing that the Computer Lab Management teams will use my capstone project.
❓Determining feasibility of additional features
While my user-interviews were extremely valuable to understand my users, I had to distinguish what suggestions were absolutely necessary vs nice-to-haves. To solve this issue, I created a product requirements document allowed us to categorize features by lowest and highest priority, and it ensured we had a defined end goal that was realistic for our short timeline.