UI/UX Design
TiriVelo: Enhancing Admin Dashboard Workflows
Prototype
Project Detail
Industry Design Project
Case Study
Role
UI/UX Designer
Product Designer
Interaction Designer
Duration
Jan - Feb 2026
(4 weeks)
Tools
Figma
Slack
Problem
TiriVelo administrators lacked a clear and efficient workflow for reviewing provider applications, leading to confusion during verification, inconsistent rejection documentation, and slower decision-making.
Solution
I designed structured admin dashboard workflows that streamlined provider verification, including clear approval and rejection flows, standardized rejection reasons, and guided prompts to support consistent moderation decisions.
Impact
The redesigned workflow reduced provider review time by an estimated 25–30% and improved documentation consistency through standardized rejection flows.
Deliverables
Mid and High-Fidelity Wireframes
Provider Verification Workflows
Approval & Rejection Decision Flows
Rejection Reason Modal
Interactive Prototype (Figma)
Workflow Decision Mapping
Requirements
I first conducted stakeholder interviews to identify pain points in the provider verification process and define the project scope. Key challenge include:
Clarify Admin Decision Actions
Design clear approval, rejection, and request-for-information workflows that guide their actions and provide structured feedback to reduce errors.
Improve Visibility and Status Tracking
Create layouts that allow admins and stakeholders to see provider status, verification progress, and communication history in a centralized view.
HMW Statement
Track Activity Documentation
Implement structured documentation features, such as required rejection reasons and status logs, to support tracking and ensure accountability.
Based on these requirements, I defined the core challenge for this project:
How might we structure admin workflows that allow users to quickly locate profiles, review provider applications, and complete actions without confusion or delays?
Process
Research
To understand the provider verification workflows, I reviewed previous team work, project documentation, and stakeholder-provided materials. Using affinity diagramming and workflow mapping, I synthesized 5 key problem areas and prioritized them based on severity, identifying 3 core challenges that accounted for over 80% of overall workflow inefficiencies:
Ambiguous Actions
Target Audience
Poor Visibility
Internal admin professionals responsible for managing users and verifying provider applications while maintaining platform accuracy and operational efficiency.
Limited Auditability
Context & Handoff from Previous Team
Before starting my iterations, I reviewed the handoff materials from the previous team, including existing workflows, wireframes, and dashboards. They had laid the groundwork for provider verification and user management, but there were gaps in clarity, feedback, and traceability.
User Management - Pet Providers
Reject Provider Application Flow
Provider Profile
Identity Verification Screen
What They Asked Me to Do Next:
Expand the Provider Verification workflow to cover all decision paths (Approve, Reject, Request Info).
Create additional screens for admin feedback, confirmations, and status tracking.
Improve dashboard hierarchy to highlight urgent actions and verification priorities.
Ensure all actions were traceable with audit logs and status updates.
Original Design (Previous Team): Rejection Reason Pop-Up Screen
Limited rejection flexibility
Used radio buttons, allowing only one rejection reason instead of selecting multiple applicable issues.
Missing admin communication features
No fields for internal admin notes or options to notify providers about status changes.
Lack of guidance and validation
No instructions explaining multi-selection or requirement to select at least one reason before rejecting.
Incomplete verification workflows
Screens for Approve Provider and Request Additional Information were not designed, leaving workflow gaps.
Challenges
Provider Application Flow
Limited search and filtering options
No search bar or clear filtering methods, making it difficult to quickly locate specific users or sort by verification status.
Weak visual hierarchy and scanning
Similar white backgrounds and lack of alternating row colors made it hard to scan user information efficiently.
Unclear total page count
Total number of pages was not displayed, making it unclear how much data existed or how far users had navigated.
Low contrast navigation structure
Light sidebar blended into the interface, reducing visibility and making key sections harder to distinguish.
User Management Dashboard
Original Design (Previous Team): User Management - Pet Providers
Provider Identity Verification Screen
Original Design (Previous Team): Pet Providers Dashboard
Original Design (Previous Team): Pet Providers ID Verification Pop-Up Screen
Unclear verification context
Screen only showed “Identity” without specifying verification or displaying front/back of ID.
Low urgency to act
No visual cues or deadlines emphasized that action was required.
Reviewer accountability unclear
Current admin’s name and activity were not visible, making it hard to track responsibility.
Poor organization of related info
Related tickets and verification history were mixed with general user activity, reducing focus.
No confirmation of completed actions
Approved requests did not indicate which admin completed the verification.
Top 3 Prioritized User Goals & Needs
User needs
Dashboard navigation clarity
Structured profile review
Visible action buttons
User goals
Quickly locate user and provider information
Complete verification efficiently
Manage platform activity efficiently
User frustrations
Difficulty locating user information
Unclear verification steps
Excessive action clicks
Clear navigation between
dashboard sections
Added new sections like KPIs, priority
actions, and verification queues to show
hierarchy clearly
Solution Design & Feature Development
Structured layouts for
reviewing provider profiles
Organized provider profile screens with
application details, status indicators, and
decision buttons
Goal
Visible actions for verification tasks
Created clear action buttons and modal
for Approve, Request Info, and
Reject flows with feedback
Help admins efficiently manage provider verification by making status, actions, and priorities clear, traceable, and easy to act on
Design
Wireframing
After reviewing the handoff materials from the previous team, I focused on expanding the Provider Verification workflow by defining clear action steps and structured decision flows.
My goal during wireframing was to ensure administrators could confidently review provider applications and complete actions without confusion.
What I Focused On
Structuring provider profile review layouts
Designing clear action flows for Approve, Reject, and Request Info
Creating feedback prompts when required fields were missing
Establishing consistent modal layouts for decision-making
Concept Development
Approve Provider Application Screen
Approve Provider Screen (V.1)
Key Decisions
Used progressive steps to guide admins through approval decisions
Designed clear messaging prompts to prevent incomplete actions
Structured rejection flows with selectable reasons
While exploring the original “Request Additional Info” design, I envisioned a streamlined “Approve Provider Application” screen to simplify the admin workflow. My goal was to make the approval process clear and actionable, even without additional provider information.
Key Features I Designed:
Description of the current action to clarify the approval step
Visual checkmark indicating what approving the provider entails
Basic UI section for internal admin notes
Notification box to inform providers of changes
Clear CTA button to confirm approval
‘Request Additional Information’ Screen
‘Request Additional Info’ Screen (V.1)
‘Request Additional Info’: ‘Other’ Selected (V.1)
I started by analyzing the previous design and noting areas for improvement. My goal was to make the workflow clearer and the UI more modern and user-friendly.
Key Features I Designed:
Added an introductory prompt guiding admins to select a reason for requesting additional info
Replaced radio buttons with selectable boxes for multiple reasons
Added an “Other” option to capture requests outside the listed reasons based on admin thinking
Included the ability for admins to write a personal message to the provider
Refreshed the overall UI for a more modern look
Adjusted spacing and layout for easier scanning and analysis by admins
Reject Provider Screen
Reject Provider Screen (V.1)
I designed the rejection screen to help admins efficiently categorize reasons for rejecting a provider application. Drawing from research, I created multiple categories and structured the UI for clarity and consistency with other admin workflows.
Key Features I Designed:
Defined four main rejection categories based on research
Used selectable boxes within categories for multiple reasons
Added internal notes section for admins
Included a notification area to inform providers of the rejection
Followed a similar layout and workflow style as the Approve and Request Additional Info screens for consistency
Iteration & Improvement
Approve Provider Application Flow
Approve Provider Screen (V.1)
Final Version
1.Approve Provider Initial Window
3.Double Confirmation Window to Approve Provider
5. Provider status change: Active Provider
The Provider Verification flow evolved through multiple iterations as I refined interaction clarity and improved feedback mechanisms.
1st Iteration (v.1)
Result
Reduced ambiguity in the approval process by adding clear status visibility, confirmation steps, and structured logging to support more traceable admin actions.
Final Version
First 2 opt selected + Auto Generated Message
Status change: Pending Provider Response
Key Feedback Points 🧐
Make provider account status changes more visible to help admins track progress.
Provide clarity on communication sent to providers during approval.
Ensure all critical actions are logged for accountability and transparency.
Introduce safeguards to prevent accidental approvals.
Consider opportunities to enhance trust and safety in the approval workflow.
Solution ✅
Added visual indicator of account status to show Pending → Active clearly
Updated email notification section with clear description of content and workflow
Included fields to log internal notes and automatically capture admin and timestamp
Added double confirmation “Confirm Approval” button to reduce accidental approvals
Maintained consistent layout with other admin workflows for clarity
2.Active “confirm provider approval” button
‘Request Additional Information’ Screen
Request Additional Info Window
4.Activity Log when Provider Got Approved
Result
Improved clarity in follow-up requests by aligning selected issues with provider messaging and making pending responses easier for admins to track.
Reject Provider Screen (V.1)
Reject Provider Window
Fraud Alert Triggered +
Rejected - Permanently Restricted
Double Rejection Confirmation
Admin Activity Timeline (All Activity + Audit Log)
Key Feedback Points 🧐
Improve clarity of communication sent to providers when additional information is requested.
Ensure internal documentation and external messaging are clearly separated.
Add safeguards to support clear explanations when custom requests are needed.
Make workflow states more visible to help admins track pending provider responses.
Enhance feedback visibility to ensure selected issues are reflected in outgoing communication.
Solution ✅
Added automatic message preview that reflects selected reasons for requesting additional info.
Separated Internal Notes (admin-only) from Message to Provider fields.
Required a written message when the “Other” option is selected to ensure clarity.
Introduced a Pending Provider Response status indicator to track waiting applications.
Maintained multi-select checkbox functionality to support multiple issue selection.
‘Request Additional Info’ Screen (V.1)
1st Iteration (v.1)
1st Iteration (v.1)
Reject Provider Screen
Work by Previous Team
Status change: Rejected Application
Result
Strengthened rejection workflows by requiring documented reasons, clarifying final outcomes, and adding safeguards to prevent accidental decisions.
Key Feedback Points 🧐
Ensure rejection decisions are consistently documented for moderation tracking.
Provide flexibility to handle cases that do not fit predefined categories.
Improve visibility of final rejection outcomes within the provider lifecycle.
Strengthen safeguards for high-impact moderation actions.
Clarify provider communication following rejection decisions.
Solution ✅
Required at least one rejection reason to be selected before enabling the Reject Application button.
Added an “Other” rejection option with a required explanation field for internal notes.
Displayed a clear Rejected Application status on the provider profile to reflect the final decision.
Updated button labeling from Return to Review to Back to Application Review for clearer navigation.
Added a confirmation step before rejection to prevent accidental actions.
Next Steps
Add Feedback Screen: Display notifications or confirmations for each action, e.g., highlight missing selections before continuing.
Standardize UI Components: Ensure consistent sizing, spacing, and styles across all screens.
Create a Component Library: Build reusable components for faster design updates and team consistency.
Enhance Workflow Visibility: Add indicators for pending or completed tasks to improve tracking.
Iterate Based on User Testing: Collect feedback from admin users to refine flows and interaction patterns.
Discovered
I realized that even small gaps in context or feedback can create confusion and slow down critical admin workflows.
Learned
I learned that thoughtful visual hierarchy, clear decision flows, and feedback loops are essential to help users act confidently and efficiently.
Takeaway
This project reinforced the importance of iterating with empathy, designing for accountability, and creating systems that feel predictable and trustworthy.