2026
Health literacy for healthcare newcomers
Overview
The challenge
Aviera was originally designed for individual and small-team expense tracking. As organizations grew, finance teams needed more control over how spending requests, reimbursements, and vendor payments were reviewed and approved.
Without approval workflows, financial operations relied on manual communication, spreadsheets, and disconnected processes that slowed decision-making and reduced visibility across departments. The goal was to expand Aviera into a more capable B2B platform while maintaining the simplicity that existing users appreciated.
Problem
Supporting growing organizations
Aviera was originally built around expense tracking and spending visibility. As organizations grew, finance teams needed more control over how requests, reimbursements, vendor payments, and department budgets were reviewed and approved. Many approval processes were still handled through email, chat messages, and spreadsheets, creating unnecessary delays and reducing visibility across teams.
Users often struggled to understand who was responsible for a request, where approvals were blocked, and what action was required next. The challenge was to introduce enterprise workflows without sacrificing the simplicity that made the product easy to use.
FINAL PRODUCT
Manage and organize in one place
Team members can search and organize 200+ materials, view key details, and switch to Orders to track reorders all in one place.
switching between inventory and orders tab
Request and track orders
Team members and managers can view and change status of a request directly from the order tab. Managers are notified, and the request can be followed through Pending, Accepted, or Rejected states.
updating request order card
Reflection
What I learned
Designing for more than one team.
Different people cared about different parts of the product. The Finishing Team focused on the daily workflow, while my manager and developers focused on what was realistic to build. I learned to consider both sides instead of designing from only one perspective.
Simple designs take a lot of work.
The final workflow looks straightforward, but getting there meant working through existing habits, stakeholder feedback, and technical constraints. I learned that my role as a designer is to understand that complexity and turn it into something that feels simple to use.
