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.

As Fanspark prepared to scale creator onboarding, the back office needed to support a growing number of applications and more complex review scenarios. 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.

Problem

When an application couldn't be approved, that application sat in the review queue.

The existing process was simple: admins opened a creator profile and could approve the application. If an admin didn't approve it, it remained in the queue.

This process didn't provide the structure needed for ongoing reviews, exceptions, or different levels of administrative responsibility.

"Approval" was the only action. The "Request change" button was never implemented on the backend.

Business Goals

The business had defined several capabilities it wanted the backoffice to support:

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

Challenge

How might I evolve a basic approval experience into a structured review system that could support more complex decisions, different adminstrative responsibilities and efficient operations?

Research

Admins were losing time switching between screens and tabs to find information.

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.

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

Mapping the full review process

I interviewed with admins and watched how they worked. Adminstrators 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 - How does each decision help admins review faster and more efficiently?

Consolidated the review experience into a single view

I pulled all critical information into a signal unified view, reducing the need to navigate between multiple pages and screens when evaluating an application. Review items are on the left and review actions are on the right.

Tradeoff

Rather than introducing a dedicated review flow for each application, I kept the experience within the creator profile so admins could access creator details and make decisions inside of the profile.

New review experience

Create consistent and scalable review patterns

I established a shared layout, review sequence and status placement across appeals, escalations and requests for changes. A shared structure made the experience easier to understand, while scenario-specific actions accomodated the differences between cases. Admins didn't have to learn how a review process worked. This would scale across other review process that we planned to build later down the road.

Request change (left), Escalation (middle), Approval (right)

Give admins visibility into previous decisions

I added an a decision history above the summary and action area, showing previous decisions, reviewers, timestamps, rationale and notes. This could help admins quickly understand where an application stood and what actions had already been taken.

Tradeoff

Not all review data is visible in our backoffice. Because our backoffice is integrated with Stripe, reviewers will inevitably need to seek information outside the platform so instead I made it easier to access those pages.

Mapping roles into page and action-level permissions

Page level-access: restructured navigation to reflect which sections each role could access

Action-level permissions: determined which actions were available within each page based on the user's role

Making review statuses in the queue easier to understand

Page level-access: restructured navigation to reflect which sections each role could access

Action-level permissions: determined which actions were available within each page based on the user's role

An action based dashboard

Page level-access: restructured navigation to reflect which sections each role could access

Action-level permissions: determined which actions were available within each page based on the user's role

Only showing relevant information to each role

Page level-access: restructured navigation to reflect which sections each role could access

Action-level permissions: determined which actions were available within each page based on the user's role

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

Learnings

A more structured review experience, designed to support operational scale

I was so happy I was able to work really close to the people I was building it for. Validation was sometimes as simple as a yes or no question.

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

SAY HI ☺

Copy component

Copied

mariama.abellera@gmail.com

SAY HI ☺

Copy component

Copied

mariama.abellera@gmail.com

SAY HI ☺

Copy component

Copied

mariama.abellera@gmail.com