Reducing time-to-resolution by 30% for admins through consistent workflows
The existing experience allowed admins to approve applications from a creator's profile, but it didn't account for the broader review lifecycle the business needed to support. I evaluidated the existing workflows against launch requirements, identified missing capabilities, and worked with stakeholders to translate those gaps into a more complete review experience. The result was a structured review system supporting three administrative roles, 14 permissions and three exception workflows.
What started as a backoffice cleanup evolved into a broader effort to establish the workflows, information architecture and permissions needed to support a complete creator review lifecycle. I worked on evolving the existing backoffice into a more complete review system by consolidating application information, designing workflows for exception, and translating business-defined roles into a permission model across the platform.
As Fanspark prepared to scale creator onboarding, the existing back office was built for a simple approval decision - not the operational complexity of managing an ongoing review process. I led the end-to-end design to evolve it into a more structure system that improved review efficiency, supported accountability, and aligned administrative access with business responsibilities.
Role
Product Designer
Timeline
3 Months
Outcome
↓ time-to-resolution by 30%
↓ average creator onboarding time by 30%
4 streamlined workflows

Context
Admins needed to review creator applications within a 72-hr turnaround window.
Fanspark's internal team would review creator verification applications before creators could post and monetize on the platform. The people reviewing applications were the founding team, who were also running the company atop of their other responsibilities. Review time competed with every other responsibility they had, so each minute spent in the tool had a real cost.
Problem
When an application couldn't be approved, there was no process to move forward.
New creator verification reviews were limited to a single-button action, leaving administrators without structured workflows for handling different outcomes and exceptions. This limited functionality cause reviews to sit in the queue. The backoffice allowed admins to approve applications, but it didn't account for the broader review lifecycle the business needed to support.
"Approval" was the only action. The "Request change" button was never implemented on the backend.
Business Goals
Improve operational efficiency
The intial goal was to streamline the existing backoffice and introduce additional review systems.
Establish accountability
The intial goal was to streamline the existing backoffice and introduce additional review systems.
Support the complete review cycle
The intial goal was to streamline the existing backoffice and introduce additional review systems.
Challenge
The intial goal was to streamline the existing backoffice and introduce additional review systems.
Challenge
Design a complete review lifecycle that could support different decisions, responsibilities and level of access within the existing system.
The intial goal was to streamline the existing backoffice and introduce additional review systems.
However, the existing experience wasn't built to support a complete review lifecycle. Admins navigated multiple pages and external platforms to make decisions, while the system lacked structured workflows for handling exceptions and differentiated permissions for administrative actions.
Simply adding more review capabilities would have expanded the existing experience without addressing the underlying gaps.
Structure the review lifecycle
Create a consistent process for reviewing applications and managing decisions.
Support exceptions
Account for scenarios that required additional review or intervention.
Establish decision-making authority
Introduce hierarchial roles and permissions to govern admin actions
Research
The platform had no workflow logic, no ownership model and no permission structure. The system wasn't optimized to support the workflows we wanted to add more of.
I interviewed with admins to and watched how they navigated their work. Admins had to navigate multiple pages to gather information and understand an application's status. The existing experience didn't provide a clear, centralized view of the review process.
Applications sat in the queue
Applications sat in the queue with no way to move forward
Context was scattered
Critical information was scattered across multiple views
No ownership
The system recorded that a decision was made, not who made it
Old review process
The Restructure
The system didn't support the the workflows we wanted to build on top of.
I interviewed with admins and watched how they worked. Adminstrations had to navigate multiple pages to gather information and understand an application's status. The existing experience didn't provide a clear, centralized view of the review process
Key Design Decisions
Designing a dedicated review experience
Consolidating the review experience into a single view
I designed a unified view that brought relevant creator information and review context together, reducing the need to navigate between multiple pages when evaluating an application.
Tradeoff
Since the people reviewing had limited time, keep all the information in one view mattered more.
New review experience
Give admins visibility into previous decisions and reviewer activity
I added an activity history above the summary and action area, showing previous decisions, reviewers, timestamps, rationale and notes. This helped prevent back-and-forth between admins
I incorporated decision history and clearer review states so admins could understand where an application stood and what actions had already been taken.
Creating consistent review patterns
Established a shared layout, review sequence and status placement across appeals, escalations and requests for changes.
Outcomes
A more structured review experience, designed to support operational scale
The design helped establish a more structured operational foundation for creator onboarding. Admins had better visibility into applications, a consistency way to handle different review scenarios, and access aligned with their responsibility.
This mattered because creator onboarding was more than an administrative task. It was part of the platform's ability to bring creators onto the product, maintain trust, and support monetization.
↓ 30% time-to-resolution
Reduced context switching and manual data investigation
3 user roles
Operators, managers and admins
4 streamlined workflows
Consistent workflows to review and resolve issues



