01 / Approval journey
Review the queue.
Scan the requester, product, location, and time before opening a request.
TAPS — UI / UX DESIGN
Complex operations.
Clear connections.
Connecting people, inventory, and places
in one focused workspace.
ROLE-BASED WEB APPLICATION
ONE CONNECTED WORKSPACETAPSDESIGNED AROUND THE WORK.
The business reasoning
From an inventory record to an informed decision.
Problem
An item record alone cannot answer who is responsible for it, where it belongs, or why a location request needs approval. The design challenge was to connect those questions across company, template, and inventory roles.
Why it mattered
Inventory decisions depend on reliable context. When responsibility or location is unclear, teams risk extra coordination and inconsistent approvals. Administrators also need consistent records as the inventory grows.
Design decision
I brought the owner, custom fields, activity, QR code, and location into the item detail view. Reusable templates structure the records, while role-specific journeys separate administration from daily inventory work. Approval review connects the request with its product and location comparison.
Design outcome
The resulting design gives reviewers a connected evidence trail from request to item to map. QR scanning provides a direct entry to a record, and templates provide a repeatable way to capture information. These are concrete design outcomes that support clearer decisions; faster lookup and approval remain goals to validate.
01 / The challenge
A record is only useful when you understand its context.
TAPS connects an item to its location, the people responsible for it, and its activity. The design brings company oversight, template setup, and daily inventory work into one system, with a focused path for each role.
02 / The overview
Start wide.
Move into the detail.
Summary cards establish scale. Activity shows what changed. The map gives every record a physical context.
03 / People & structure
The right starting point for each responsibility.
Company admins need the whole picture. Template managers define how information is captured. Inventory managers need a direct route to the item. Shared components keep those experiences familiar.
Make responsibility visible.
Role labels and member details connect the person to the work.
Give information a consistent shape.
Reusable templates make different records part of the same system.
Explore the three journeys
The overview
See the operation. Organize the team.
The company experience brings members, activity, locations, templates, and inventory into a shared dashboard. Invitations and role assignment establish who can do what.
- 01Invite members
- 02Assign roles
- 03Review activity
- 04Manage requests
04 / Create with context
From a structure
to something real.
Choose fields, add an item, and establish its location. Each step keeps the surrounding workspace in view.
05 / The daily work
From the physical item to the full story.
A QR code provides a direct route to an inventory record. The detail view brings together the product, custom fields, owner, activity, and location, so the next decision starts with useful context.
INVENTORY DETAILEverything about
Everything about
one item. Together.
A shorter path
Scan.
Find.
Continue.
The scanning state makes the next action clear while preserving the inventory behind it.
06 / Approval workflow
A decision is easier when the evidence is connected.
Out-of-location requests link the person, product, time, and place. The journey moves from the queue to the record, then reveals the map when a spatial comparison is needed.
02 / Approval journey
Understand the item.
Bring product details and decision controls into a focused review panel.
03 / Approval journey
Check the place.
Compare the allowed area with the reported position before making the decision.
07 / The interface system
Different journeys. A familiar visual language.
Role-specific navigation, repeatable cards, clear blue actions, and consistent fields carry the experience across the product. Wireframes established the core journeys; the next pass added operational states, with prototype links communicating the intended transitions.
About this study
Presented from the original UI exports, wireframes, and prototype. Design analysis is based on the visible work; research results and business impact have not been measured here.
Explore the original Figma design ↗What comes next
Validate how easily each role finds a record, understands location, and recovers from a failed scan or denied access. Test keyboard use, contrast, and action targets with users.
YOUR NEXT PRODUCT
Make the complex
feel clear.
Have a product with connected workflows, dense information, or multiple user roles? Let’s make it easier to use.
Let’s work together