Approval
workflow

Approval workflow

Team

1 Product Manager

2 Engineers

Role - Lead Designer

Research, Product Design, Testing, Prototyping

Overview

Overview

Overview

Approval workflow centralizes all update requests into a unified platform, enabling Teamshares Board members, Customer team, and Committee team to review, track, and approve changes in real time. The solution simplified complex decision-making processes while maintaining compliance requirements across stakeholder groups.

I was the lead designer and collaborated with 1 PM, 3 engineers, and legal, finance, and accounting teams, as the project involved many compliance considerations.

Impact within 30 days of launch

The problem

The problem

The problem

Teamshares struggled to scale their approval process due to reliance on manual tracking and email chains for requests from small businesses and internal teams.

Challenge 1

Lost requests and delayed responses

Scattered across emails, Slack, and meetings, leading to missed approvals and delays.

Challenge 2

Unclear approval status and ownership

Multiple stakeholders were contacted, creating confusion about who should be approving.

Challenge 3

No standardized way to track approvals

Teams relied on fragmented tools like spreadsheets and email folders.

Our solution & goals

The goal was to develop a scalable approval platform that standardizes request handling and enables stakeholders to submit, track, and approve requests.

Business goals

To ensure our workflow is fully regulatory and legally compliant.

Eliminate lost requests by centralizing all approvals in one system.

Users & stakeholders

Users & stakeholders

Users & stakeholders

I mapped how Teamshares internal teams (L1), initial approvers (L2), and final approvers (L3) interact based on their responsibilities and authority levels.

I used a top-down design strategy, starting with L3, as they have the highest permission level and can perform all tasks. This approach allowed us to simplify the design progressively by hiding or removing features for L2 and even more for L1, ensuring each role only sees what is relevant to them.

Stakeholder map (L1, L2, L3)

With an understanding of the users, I created an user flow to help users seamlessly navigate and approve pending requests.

User flow: global View (all companies) and the specific company view

Other softwares

Other softwares

Other softwares

I researched and analyzed how other enterprise softwares handle approval workflows to identify opportunities for improvement in our use cases in the competitive market.

Analyzing approval flow interfaces to identify best practices

MVP features

MVP features

MVP features

Since this was the first approval workflow system at Teamshares, we focused on building core functionalities first. Together with the PM and engineers, we focused on prioritized 3 key interfaces:

  1. Review interface

  2. History tracking

  3. Notification system

MVP feature identification

After finalizing the MVPs, I met with the legal team to identify user-facing fields that ensured regulatory compliance for our product.

Regulatory compliance table

High fidelity explorations

High fidelity explorations

High fidelity explorations

I used components from the design library to create a high-fidelity prototype and conducted UX studies with 2 users.

Final designs

Final designs

Final designs

Global view of request page

Internal team view vs. Approver view

Specific view of a company's requests

Review currency transfers request

Mobile view

Email reminders for updates and reviews, accessible on the go

Lessons & takeaways

Lessons & takeaways

Lessons & takeaways

Collaborating with stakeholders

This project required extensive collaboration with stakeholders (legal, finance, and accounting teams). Many design elements, which appeared simple at first glance, had to accommodate complex compliance requirements. Through frequent syncs with these teams, I learned how crucial it is to listen to all parties involved and to ensure that design solutions meet legal and regulatory needs while still being user-friendly.

Plan, plan, and plan

The most time-consuming part of this project was planning the roles and permissions structure. I realized that understanding and defining how each role would interact with the system took more time than expected. We made adjustments near the end, underscoring the importance of thorough planning and flexibility in the design process.

Always keep scalability in mind

Initially, I was told that only 4-6 pieces of context would be displayed on each card. However, after working closely with the legal team, we found that the information could be 10+. This experience taught me to always keep potential future growth in mind, ensuring that designs can adapt to evolving requirements.

© 2025 Rachel Yang · Based in NY

© 2025 Rachel Yang · Based in NY

© 2025 Rachel Yang · Based in NY