Enterprise Admin Vetting Portal for Dreamscape Learn Pods at ASU
A mobile-first enterprise tool to streamline request tracking, slot approvals, and SLA-driven operations at DSL ASU.
🔒 This project was part of a larger enterprise solution built at scale. Due to NDA constraints, only select flows are shown. The full case study is available upon request.
— Overview
It was June of 2024 when I joined the EdPlus SPLIT team and started working on a DSL Project.
It was June of 2024 when I joined the EdPlus SPLIT team and started working on a DSL Project.
While users could easily book VR pod sessions through an existing self-service portal, the backend operations were still entirely manual: admins reviewed requests over email, tracked availability in spreadsheets, and confirmed sessions one by one.
While users could easily book VR pod sessions through an existing self-service portal, the backend operations were still entirely manual: admins reviewed requests over email, tracked availability in spreadsheets, and confirmed sessions one by one.
While users could easily book VR pod sessions through an existing self-service portal, the backend operations were still entirely manual: admins reviewed requests over email, tracked availability in spreadsheets, and confirmed sessions one by one.
I led the 0 → 1 product design of the DSL Admin Portal — a self-service backend platform to centralize booking management, streamline session vetting, automate approvals, and bring operational clarity to a system scaling across campus.
I led the 0 → 1 product design of the DSL Admin Portal — a self-service backend platform to centralize booking management, streamline session vetting, automate approvals, and bring operational clarity to a system scaling across campus.
I led the 0 → 1 product design of the DSL Admin Portal — a self-service backend platform to centralize booking management, streamline session vetting, automate approvals, and bring operational clarity to a system scaling across campus.
Team
Team
Team
Myself – UX Designer
Michelle Torres – Senior Immersive Designer
UX Research Team
Engineering Team
Myself – UX Designer
Michelle Torres – Senior Immersive Designer
UX Research Team
Engineering Team
Myself – UX Designer
Michelle Torres – Senior Immersive Designer
UX Research Team
Engineering Team
— Background
Founded in 2019 through a collaboration between Arizona State University and Dreamscape Immersive, DSL reimagines the traditional classroom through instructor-led immersive VR experiences.
Founded in 2019 through a collaboration between Arizona State University and Dreamscape Immersive, DSL offers educational experiences that blends cinematic storytelling, virtual reality, and advanced teaching to transform how students learn.
Founded in 2019 through a collaboration between Arizona State University and Dreamscape Immersive, DSL offers educational experiences that blends cinematic storytelling, virtual reality, and advanced teaching to transform how students learn.
Dreamscape Learn offers educational experiences that blends cinematic storytelling, virtual reality, and advanced teaching to transform how students learn.
Following its successful pilots, DSL rapidly expanded its pods across multiple colleges and academic units at ASU, driving high demand for scalable booking and operations management.
Following its successful pilots, DSL rapidly expanded its pods across multiple colleges and academic units at ASU, driving high demand for scalable booking and operations management.
Following its successful pilots, DSL rapidly expanded its pods across multiple colleges and academic units at ASU, driving high demand for scalable booking and operations management.
— Problem Space & Impact
Manual booking worked, until DSL scaled
Manual booking worked, until DSL scaled
Manual booking worked, until DSL scaled
Every student booking submitted through the self-service portal triggered a manual response process:
Admin teams lacked a centralized platform to vet, approve, and manage booking requests. This led to :
Every student booking submitted through the self-service portal triggered a manual response process:
Admins reviewed requests via email threads
Admins reviewed requests via email threads
Admins reviewed requests via email threads
Confirmations were sent individually
Confirmations were sent individually
Confirmations were sent individually
Pod capacity was cross-checked in shared Google Sheets
Pod capacity was cross-checked in shared Google Sheets
Pod capacity was cross-checked in shared Google Sheets
No-show history or duplicates went unnoticed
No-show history or duplicates went unnoticed
No-show history or duplicates went unnoticed
Business Goals
Centralize booking workflows to reduce manual tracking and errors.
Enable faster, more efficient guest vetting and approvals.
Enable Mobile, Real-Time Decision-Making
Business Goals
Centralize booking workflows to reduce manual tracking and errors.
Enable faster, more efficient guest vetting and approvals.
Enable Mobile, Real-Time Decision-Making
Business Goals
Centralize booking workflows to reduce manual tracking and errors.
Enable faster, more efficient guest vetting and approvals.
Enable Mobile, Real-Time Decision-Making
This wasn’t just a UX pass or an interface overhaul; it was a ground-up system design that touched operations, technology, and user behavior in equal measure.
Date
Date
— Solution: A streamlined, automated, and scalable booking system for admins
Tab-Based Request Management on the dashboard
Modular triage for focused task execution
I designed the request interface using a tabbed navigation model, separating requests into Pending, Approved, and Denied.
Impact
Reduced decision fatigue and improved clarity.
why?
In interviews, admins said they often “got lost” in raw request lists and wasted time searching for what needed action.
Tabs reduced time-to-decision and improved clarity under pressure.
SLA-Driven Priority Tagging & Color Coding
Each request is assigned a real-time SLA status, visible both in the request queue and the right-hand detail panel.
🟢 On Time: plenty of time left before breach
🟡 At Risk: <1 hour remaining
🔴 Breached: SLA window has expired
Impact
Admins could immediately identify at-risk requests and act before breaches occurred.
why?
Prior to this, admins treated all requests equally, not realizing which were about to breach.
SLA tags converted invisible urgency into visible priority, making the system responsive, not reactive.
Mobile Vetting with One-Tap Actions
As a B2B operations tool, mobile was not just a responsive view it was a mission-critical workflow layer for real-time, on-ground vetting.
The mobile version was designed for moments when time is tight and context-switching isn’t an option. Whether staff are walking between pods or handling a high volume of requests during peak hours, the interface allows:
Tap-to-approve or reject in seconds
Color-coded SLA tags visiblility at a glance
One-tap access to rejection reasons
why?
76% of vetting now happens on mobile. Staff can make decisions while walking between pods without logging into a desktop, a major boost in SLA performance and workflow flexibility.
Intelligent Request Flagging (Duplicates & No-Shows)
To support more consistent and informed decisions, I introduced automated flagging for risky patterns. The system now detects and marks:
Duplicate bookings — when a student has two overlapping sessions
Repeat no-shows — based on attendance history
Flagged requests are visually highlighted in both the queue and detail view, with tooltip context available on hover or tap.
why?
Before this, decisions were inconsistent; some admins would approve repeat offenders, others wouldn’t.
Flagging introduced fairness and system memory.
Live Status Indicators in Approved Tab
Real-time session visibility for fast operational insight
Each approved request displayed a live session state, such as Started, Completed, Canceled, or No Show. Admins could monitor session outcomes directly from the queue.
Admins could reassign vetting ownership based on workload or pod responsibility, with assignment logs tracked in the system.
why?
Admins gained instant insight into ongoing or past sessions.
Reduced need to check external logs or calendars.
Helped with follow-ups, escalations, and performance tracking.
— Research Process - Understanding the problem in depth
A lean but deep discovery effort focused on surfacing operational friction, mobile constraints, and team dynamics inside the DSL booking workflow.
A lean but deep discovery effort focused on surfacing operational friction, mobile constraints, and team dynamics inside the DSL booking workflow.
Research Process
Operational Audit
Identifying Systemic Inefficiencies
Role-Based Interviews
Surfacing Pain Point Themes
Aligning on Product Vision
Mapping the Existing Workflow (Operational Audit)
The goal was to understand how requests are currently vetted and where the process breaks down.
Methods
Shadowing sessions
Internal documentation review
Workflow mapping with ops leads
What I found
Requests came in via self-service portal
Reviewed through emails and spreadsheets
Approvals sent manually; pod capacity tracked separately
No consistent view of who was working on what
Back then, the admin team relied on a simple system: students emailed their booking requests, and admins tracked everything manually in spreadsheets. It was fine until it wasn’t.
This revealed a system held together by manual effort, tribal knowledge, and Slack messages
Identifying Systemic Inefficiencies
The goal was to spot where work was delayed, duplicated, or miscommunicated.
Methods
Journey mapping
Timestamp analysis of booking flows
Internal metrics review
Friction Points
SLA breaches were common often unnoticed until escalations
Multiple admins reviewing the same request = duplicate approvals
Compliance risks – No way to track minors in bookings.
Students sometimes got confirmed for already-full pods
This framed the case for automation, prioritization logic, and live pod visibility.
Role-Based Interviews (Ops Personas)
The goal was to understand the needs of each admin role involved in vetting and coordination.
Methods
1:1 interviews with DSL vetting staff
Pod managers
Escalation leads
User Frustations
Field staff needed mobile access
Leads needed workload visibility to reassign tasks
Escalation paths were informal and hard to track
These insights validated the need for a centralized, intuitive platform to streamline approval workflows.
This shaped the interface logic: who sees what, who does what, and when.
Surfacing Pain Point Themes
The goal was to translate qualitative findings into a design-ready problem area
Methods
Affinity mapping
Insight clustering,
Synthesis workshops with the team
Themes Identified
Visibility: "I don’t know which pod is full or who’s handling this."
Urgency: "I can’t tell which requests are about to breach"
Consistency: "We all approve differently, there’s no proper system."
These directly informed features like SLA badges, assignment tags, and auto-flagging.
Aligning on Product Vision
The goal was to get stakeholder buy-in on core functionality and product scope
Methods
Playback sessions with DSL leadership
Product Roadmap Co-Creation
Themes Identified
Visibility: "I don’t know which pod is full or who’s handling this."
Urgency: "I can’t tell which requests are about to breach"
Consistency: "We all approve differently, there’s no proper system."
These directly informed features like SLA badges, assignment tags, and auto-flagging.
— Ideation & Design
Modeling Admin Behavior Across the Booking Lifecycle
To translate the product vision into actionable design, I first mapped out the complete lifecycle of a session booking from the admin’s perspective, from receiving a request to monitoring the final attendance.
This exercise clarified the decision points, required inputs, and the system responsibilities at each stage of the process.
Why
It ensured we captured real-world scenarios and prioritized efficiency in every interaction, from viewing pending requests to approving, scheduling, or flagging edge cases.
Structuring Information for Decision Velocity (Information Architecture)
To streamline admin workflows, I restructured the information architecture to prioritize the key decision inputs: SLA timers, pod availability, student booking history, and action status, all surfaced in context.
The layout minimized the need to switch views or dig through tables, making triage, vetting, and escalation feel fluid and immediate.
Why
Admins were operating under time pressure and on mobile so the system had to deliver clarity at a glance, not just completeness. The IA ensured critical info always appeared at the right moment, in the right place.
Wireframing for Systems, Not Just Screens
I created low-fidelity wireframes that mapped directly to back-end rules, decision workflows, and operational behaviors not just UI components.
Wireflows captured how admins would triage requests, reassign tasks, and interact with SLA logic across both desktop and mobile scenarios.
Why
Designing screens wasn't enough, this was a system in motion. Wireframing helped validate logic before building fidelity, keeping workflows grounded in real admin behavior.
Testing for Friction and Flow (Usability Testing)
Ran rapid usability tests with DSL staff, using clickable prototypes and scenario prompts. Tested flows like: “Approve a request while on the move,” or “Handle a duplicate booking flagged during triage.”
Feedback led to refinements in action placement, tab language, icon use, and confirmation prompts, especially on mobile.
Outcome
Even small delays during high-volume shifts can lead to missed bookings. Testing helped shape a tool that not only worked, but fit the pace and pressure of the real environment.
— Projected Impact
Defined collaboratively with DSL stakeholders, based on observed bottlenecks in the manual vetting workflow.
Targeted KPIs (Pre-Launch)
Reduce Average Request Resolution Time by 50–6de0%
Goal:
Speed up approvals through centralized booking data, context-rich vetting panels, and mobile-first access.
Why?
Faster vetting = fewer missed sessions and a smoother student experience.
Achieve >85% SLA Compliance Within First Month
Goal:
Help admins prioritize urgent requests using SLA countdowns and visual urgency tags.
Why?
Missed SLAs cause scheduling gaps and increase student drop-off rates.
Cut Booking Conflicts by 50%
Goal:
Use system logic to automatically flag overlapping bookings and repeat no-shows.
Why?
Prevents manual clean-up, scheduling errors, and pod overbooking.
— Reflection
Challenging yet rewarding
Designing the DSL Admin Portal pushed me to think beyond UI and into system logic, operational flows, and real-world constraints.
I learned that great internal tools don’t just support teams, they shape how work gets done. Leading this 0→1 product taught me how to design for urgency, fairness, and scale all within the complexity of mobile, time-sensitive workflows.
More projects
More projects
More projects
— Solution: A streamlined, automated, and scalable booking system for admins
Tab-Based Request Management on the dashboard
Tab-Based Request Management on the dashboard
Tab-Based Request Management on the dashboard
This reduced cognitive load and eliminated clutter.
This reduced cognitive load and eliminated clutter.
This reduced cognitive load and eliminated clutter.
This modular view helped admins focus on specific tasks without distraction.
This modular view helped admins focus on specific tasks without distraction.
This modular view helped admins focus on specific tasks without distraction.
Scalable IA & Admin-first UX
Scalable IA & Admin-first UX
Scalable IA & Admin-first UX
From the start, I approached the portal with an “admin-first” mindset.
From the start, I approached the portal with an “admin-first” mindset.
From the start, I approached the portal with an “admin-first” mindset.
I worked closely with the ops team to understand how they mentally grouped actions, and used that to inform a clear information architecture.
I worked closely with the ops team to understand how they mentally grouped actions, and used that to inform a clear information architecture.
I worked closely with the ops team to understand how they mentally grouped actions, and used that to inform a clear information architecture.
Each interaction was designed to minimize clicks and reduce training time; key for future team onboarding.
Each interaction was designed to minimize clicks and reduce training time; key for future team onboarding.
Each interaction was designed to minimize clicks and reduce training time; key for future team onboarding.
Integrated Calendar View
Integrated Calendar View
Integrated Calendar View
I designed a clean, responsive calendar system that allowed admins to see all scheduled events by day, week, or month.
I designed a clean, responsive calendar system that allowed admins to see all scheduled events by day, week, or month.
I designed a clean, responsive calendar system that allowed admins to see all scheduled events by day, week, or month.
Event cards were clickable for quick review. This provided a big-picture view and helped prevent double bookings or overlooked requests.
Event cards were clickable for quick review. This provided a big-picture view and helped prevent double bookings or overlooked requests.
Event cards were clickable for quick review. This provided a big-picture view and helped prevent double bookings or overlooked requests.
Badge System for Booking Context
Badge System for Booking Context
Badge System for Booking Context
We needed a quick way to identify the status of the event. I designed a color coded badge system, enabling admins to instantly filter and assess bookings based on event staus reducing time spent scanning request details.
We needed a quick way to identify the status of the event. I designed a color coded badge system, enabling admins to instantly filter and assess bookings based on event staus reducing time spent scanning request details.
We needed a quick way to identify the status of the event. I designed a color coded badge system, enabling admins to instantly filter and assess bookings based on event staus reducing time spent scanning request details.
Design System Considerations
Design System Considerations
Design System Considerations
The portal components were created with modularity in mind, enabling future reusability across other DSL tools.
The portal components were created with modularity in mind, enabling future reusability across other DSL tools.
The portal components were created with modularity in mind, enabling future reusability across other DSL tools.
I ensured alignment with the broader design system while introducing new patterns tailored to admin needs.
I ensured alignment with the broader design system while introducing new patterns tailored to admin needs.
I ensured alignment with the broader design system while introducing new patterns tailored to admin needs.
— Behind the scenes - Understanding the problem in depth
In order to dig deeper, I started with foundational research and since it was an internal tool that needed to be built quickly due to tight timelines, I adopted a lean research process focused on understanding users and their core challenges.
In order to dig deeper, I started with foundational research and since it was an internal tool that needed to be built quickly due to tight timelines, I adopted a lean research process focused on understanding users and their core challenges.
In order to dig deeper, I started with foundational research and since it was an internal tool that needed to be built quickly due to tight timelines, I adopted a lean research process focused on understanding users and their core challenges.
Research Process
Understanding Existing Workflows
Conducting a High-Level Audit
Identifiying User Pain Points
Defining Product Vision and Goals
Research Process
Understanding Existing Workflows
Conducting a High-Level Audit
Identifiying User Pain Points
Defining Product Vision and Goals
Research Process
Understanding Existing Workflows
Conducting a High-Level Audit
Identifiying User Pain Points
Defining Product Vision and Goals
How the DSL was managing booking requests?
When I joined the Dreamscape Learn Self-Service Admin Portal project, the booking system was live for end users, but there was no defined backend experience for admins
When I joined the Dreamscape Learn Self-Service Admin Portal project, the booking system was live for end users, but there was no defined backend experience for admins
When I joined the Dreamscape Learn Self-Service Admin Portal project, the booking system was live for end users, but there was no defined backend experience for admins
Back then, the admin team relied on a simple system: students emailed their booking requests, and admins tracked everything manually in spreadsheets. It was fine until it wasn’t.
Back then, the admin team relied on a simple system: students emailed their booking requests, and admins tracked everything manually in spreadsheets. It was fine until it wasn’t.
Back then, the admin team relied on a simple system: students emailed their booking requests, and admins tracked everything manually in spreadsheets. It was fine until it wasn’t.
The admin teams were manually tracking guest requests through emails, spreadsheets, and disconnected tools.
As demand for Dreamscape Learn exploded, that fragile setup started cracking. Requests got lost. Approvals were delayed. The system just couldn’t keep up and the people running it were feeling the strain.
The admin teams were manually tracking guest requests through emails, spreadsheets, and disconnected tools. As demand for Dreamscape Learn exploded, that fragile setup started cracking. Requests got lost. Approvals were delayed. The system just couldn’t keep up and the people running it were feeling the strain.
The admin teams were manually tracking guest requests through emails, spreadsheets, and disconnected tools.
As demand for Dreamscape Learn exploded, that fragile setup started cracking. Requests got lost. Approvals were delayed. The system just couldn’t keep up and the people running it were feeling the strain.
Identifying inefficiencies in the existing workflow
To design a system that met real-world needs, I audited admin workflow, uncovering gaps in information flow, approval bottlenecks, and fragmented user touchpoints.
To design a system that met real-world needs, I audited admin workflow, uncovering gaps in information flow, approval bottlenecks, and fragmented user touchpoints.
To design a system that met real-world needs, I audited admin workflow, uncovering gaps in information flow, approval bottlenecks, and fragmented user touchpoints.
Friction Points
High administrative burden – Manual approvals created inefficiencies.
No real-time visibility – Admins lacked insights into guest bookings.
Compliance risks – No way to track minors in bookings.
Repetitive tasks – Affiliates manually scheduled each event.
Friction Points
High administrative burden – Manual approvals created inefficiencies.
No real-time visibility – Admins lacked insights into guest bookings.
Compliance risks – No way to track minors in bookings.
Repetitive tasks – Affiliates manually scheduled each event.
Friction Points
High administrative burden – Manual approvals created inefficiencies.
No real-time visibility – Admins lacked insights into guest bookings.
Compliance risks – No way to track minors in bookings.
Repetitive tasks – Affiliates manually scheduled each event.
Understanding challenges through user interviews
I analyzed feedback from various stakeholders to identify key pain points and expectations.
I analyzed feedback from various stakeholders to identify key pain points and expectations.
I analyzed feedback from various stakeholders to identify key pain points and expectations.
As this was a live internal tool for admins, I worked directly with real users. Instead of formal personas, I built empathy through interviews and observations, focusing on their actual workflows and pain points.
As this was a live internal tool for admins, I worked directly with real users. Instead of formal personas, I built empathy through interviews and observations, focusing on their actual workflows and pain points.
As this was a live internal tool for admins, I worked directly with real users. Instead of formal personas, I built empathy through interviews and observations, focusing on their actual workflows and pain points.
User Frustations
Lack of visibility into guest details
Cumbersome manual processes
Difficulty managing growing booking volumes.
User Frustations
Lack of visibility into guest details
Cumbersome manual processes
Difficulty managing growing booking volumes.
User Frustations
Lack of visibility into guest details
Cumbersome manual processes
Difficulty managing growing booking volumes.
These insights validated the need for a centralized, intuitive platform to streamline approval workflows.
These insights validated the need for a centralized, intuitive platform to streamline approval workflows.
These insights validated the need for a centralized, intuitive platform to streamline approval workflows.
Turning challenges into product vision and goals
Based on the findings from the audit and research sessions, I worked on bridging the user needs and design solutions with a focus on five core goals:
Based on the findings from the audit and research sessions, I worked on bridging the user needs and design solutions with a focus on five core goals:
Based on the findings from the audit and research sessions, I worked on bridging the user needs and design solutions with a focus on five core goals:
Centralized Management
Centralized Management
Centralized Management
Efficient Vetting Flows
Efficient Vetting Flows
Efficient Vetting Flows
Clear Visibility
Clear Visibility
Clear Visibility
Scalable Infrastructure
Scalable Infrastructure
Scalable Infrastructure
Minimal Training Required
Minimal Training Required
Minimal Training Required
— Ideation & Design
Task flow of an admin across the booking lifecycle
To translate the product vision into actionable design, I first mapped the tasks of an admin across the booking lifecycle,
To translate the product vision into actionable design, I first mapped the tasks of an admin across the booking lifecycle,
To translate the product vision into actionable design, I first mapped the tasks of an admin across the booking lifecycle,
This helped clarify the decision points, necessary inputs, and system responses throughout the booking management process.
This helped clarify the decision points, necessary inputs, and system responses throughout the booking management process.
This helped clarify the decision points, necessary inputs, and system responses throughout the booking management process.
Why
It ensured we captured real-world scenarios and prioritized efficiency in every interaction from viewing pending requests to approving or denying them.
Why
It ensured we captured real-world scenarios and prioritized efficiency in every interaction from viewing pending requests to approving or denying them.
Why
It ensured we captured real-world scenarios and prioritized efficiency in every interaction from viewing pending requests to approving or denying them.
Information Architecture
Based on the user flows, I defined the portal’s information architecture.
Based on the user flows, I defined the portal’s information architecture.
Based on the user flows, I defined the portal’s information architecture.
This included grouping actions and data based on how admins mentally categorize their tasks (e.g., by request status, calendar view, or guest type).
This included grouping actions and data based on how admins mentally categorize their tasks (e.g., by request status, calendar view, or guest type).
This included grouping actions and data based on how admins mentally categorize their tasks (e.g., by request status, calendar view, or guest type).
Why
A clear IA helped reduce cognitive load and made it easier for users to find what they need without excessive clicks or confusion.
Why
A clear IA helped reduce cognitive load and made it easier for users to find what they need without excessive clicks or confusion.
Why
A clear IA helped reduce cognitive load and made it easier for users to find what they need without excessive clicks or confusion.
Low-Fidelity Wireframes
With the IA in place, I created low-fidelity wireframes to explore layout, hierarchy, and task flows.
With the IA in place, I created low-fidelity wireframes to explore layout, hierarchy, and task flows.
With the IA in place, I created low-fidelity wireframes to explore layout, hierarchy, and task flows.
These wireframes were used in early design reviews to gather feedback from internal teams.
These wireframes were used in early design reviews to gather feedback from internal teams.
These wireframes were used in early design reviews to gather feedback from internal teams.
Why
Wireframing enabled rapid iteration without overinvesting in high-fidelity visuals. It allowed us to test structural ideas and quickly align across stakeholders before refining the UI.
Why
Wireframing enabled rapid iteration without overinvesting in high-fidelity visuals. It allowed us to test structural ideas and quickly align across stakeholders before refining the UI.
Why
Wireframing enabled rapid iteration without overinvesting in high-fidelity visuals. It allowed us to test structural ideas and quickly align across stakeholders before refining the UI.
Usability Testing
Usability testing was conducted by the internal research team to assess portal effectiveness. I led multiple sessions to analyze feedback, prioritize issues, and apply learnings to refine the design.
Usability testing was conducted by the internal research team to assess portal effectiveness. I led multiple sessions to analyze feedback, prioritize issues, and apply learnings to refine the design.
Usability testing was conducted by the internal research team to assess portal effectiveness. I led multiple sessions to analyze feedback, prioritize issues, and apply learnings to refine the design.
Note: Blurred report excerpts were included in documentation to protect confidentiality while highlighting our testing approach.
Note: Blurred report excerpts were included in documentation to protect confidentiality while highlighting our testing approach.
Note: Blurred report excerpts were included in documentation to protect confidentiality while highlighting our testing approach.
Outcome
Informed actionable UI updates through impact-based prioritization
Improved admin task speed, clarity, and confidence
Enabled smoother validation of key interaction changes
Outcome
Informed actionable UI updates through impact-based prioritization
Improved admin task speed, clarity, and confidence
Enabled smoother validation of key interaction changes
Outcome
Informed actionable UI updates through impact-based prioritization
Improved admin task speed, clarity, and confidence
Enabled smoother validation of key interaction changes
— Impact
Measurable Outcomes
4.8/5 Admin Satisfaction Score Improved usability and reduced errors in booking management
4.8/5 Admin Satisfaction Score Improved usability and reduced errors in booking management
4× Faster Request Processing Booking approvals dropped from 48 hours to 12 hours
4× Faster Request Processing Booking approvals dropped from 48 hours to 12 hours
85% Faster Guest Confirmation Guests received booking confirmations within hours instead of days
85% Faster Guest Confirmation Guests received booking confirmations within hours instead of days
Retrospective
The redesigned system dramatically improved administrative efficiency and booking visibility, while also elevating the guest and affiliate experience.
Retrospective
The redesigned system dramatically improved administrative efficiency and booking visibility, while also elevating the guest and affiliate experience.
Retrospective
The redesigned system dramatically improved administrative efficiency and booking visibility, while also elevating the guest and affiliate experience.
Reflection
Challenging yet rewarding
This project deepened my understanding of how user-centered design can drive organizational scale, even in the background systems that often go unnoticed.
Challenging yet rewarding
This project deepened my understanding of how user-centered design can drive organizational scale, even in the background systems that often go unnoticed.
Challenging yet rewarding
This project deepened my understanding of how user-centered design can drive organizational scale, even in the background systems that often go unnoticed.
Prototype
Explore the Admin Portal Experience
Explore the Admin Portal Experience
I created an interactive prototype to demonstrate key workflows, including:
Viewing and managing booking requests
Viewing and managing booking requests
Viewing and managing booking requests
Approving or denying guest entries
Approving or denying guest entries
Approving or denying guest entries
Navigating the calendar and identifying scheduling conflicts
Navigating the calendar and identifying scheduling conflicts
Navigating the calendar and identifying scheduling conflicts
Surfacing guest details such as contact info, minors, and group size
Surfacing guest details such as contact info, minors, and group size
Surfacing guest details such as contact info, minors, and group size
Sep'24 - Nov'24
DSL EdPlus
B2B, Saas, 0 → 1 Product Design
Admin Portal for Self-Service Booking
Designed the Dreamscape Learn Admin Portal from scratch to replace email-based bookings, improving request tracking by 60% and reducing admin workload by 40%.
Sep'24 - Nov'24
DSL EdPlus
B2B, Saas, 0 → 1 Product Design
B2B, Saas, 0 → 1 Product Design
DSL EdPlus