TiriVelo.Inc

A pet-care marketplace’s admin tool where support agents resolve disputes, no-shows, cancellations, and the day a dog doesn’t come home. I inherited a Bookings section colored by how much money moved, and I rebuilt it around a different question.
ROLE
UX Researcher & Designer
TIMELINE
5 weeks
CLIENT
Live product, real CEO
SCOPE
Bookings・Team of 3
THE PROBLEM
Making an admin tool answer one question:
what needs me right now?
There are sixty-eight open tickets. One is a refund dispute, three are overdue reports, one is a provider appeal, and one is a booking where a dog never came home. The agent has to decide which of them to open first.
BEFORE AND AFTER
The inherited screen and mine hold the same data.
INHERITED


CONSTRAINTS
I could only change one thing
This wasn’t a blank page, and knowing what I couldn’t move told me where the one real decision had to live.
01 It was already live
Buildable in the existing library, or it doesn't ship.
02 An inherited file, mid-flight
Reviewed more than 20 screens and justified every change to the CEO.
03 Policy set the rules
Fees, strikes, and appeal windows are contractual, so I had to obey the documents.
04 Five weeks, then handoff
Every decision needed a rule an engineer could build without me.
Chapter 01
INHERITED FILES
At first, none of it made sense.
I inherited more than thirty booking screens and I couldn’t tell them apart. Cancelled, disputed, and no-show all rendered the same saturated red on the same sprawling sidebar, so two screens asking completely different things of an agent looked identical. Nobody had decided what the colors were for.

The inherited logic, exaggerated: everything was urgent, so the eye has nowhere to land.
Chapter 02
THE COLOR SYSTEM
One question sorted every screen
I found three cancellation screens with identical bookings where only the fee differed. The higher the fee, the louder the screen, and the agent’s job in all three was the same. Policy had already closed the case.
THE INHERITED RULE
Color by how much money moved.
It’s a defensible instinct because $85 feels more serious than $0, but a fee that policy already charged doesn’t need anyone to do anything.
THE RULE I REPLACED IT WITH
Color by whose action unblocks the case.
One question drove every status, so the thirty screens sorted themselves, and the same rule fit every case in the whole admin system.

THE SYSTEM, UP CLOSE

KEY DECISIONS
The rule settled three hard calls
Every judgment from here answered to the same question.
DECISION 01
A no-show is really two states
Before an appeal is filed the case belongs to the provider, so the admin just watches a countdown. Once an appeal lands it’s the admin’s call, so the same booking goes orange and then red.
Click to watch the state and the color change↓

File an appeal ->
DECISION 02
Money moving doesn't make it urgent
DECISION 03
The sidebar shrinks when there's nothing to do
EVIDENCE PANEL
Everything needed to judge the case is one tab away.
A provider missed a walk, got a strike, and then appealed with hospital records.
Chapter 03
THE HARDEST CASE
The day the dog doesn't come home
An owner reports their dog never came back. The provider has gone silent and the agent has minutes.
What does "done" even mean here?

The finished emergency screen
THE REDESIGN
The sidebar becomes a procedure
Click each step to expand ↓

The agent works the sidebar top-down while the incident runs
It’s numbered and sequential. When a dog is missing an agent shouldn’t be choosing from a menu, they should be following a checklist someone wrote on a calmer day.
1
The steps are numbered 1 to 5, so the agent doesn’t have to remember the protocol.
2
Maroon sits a tier above the normal red, so an all-hands incident doesn’t read like a routine task.
THE TERMINAL STATE
I deleted the green "Resolved"
TiriVelo equips and investigates but it doesn’t run search-and-rescue, so a green checkmark would have been the tool lying to an owner whose dog was still missing. The flow ends gray.
WHAT I REMOVED
WHAT I SHIPPED

->

VALIDATION PLAN
Nobody was measuring, so I wrote the rubric.
TiriVelo tracked no metrics between their V2 and my V3. Instead of inventing a number, I built the plan I'd hand the next team.
TEST 01・TIME TO FIRST TRIAGE
< 3 seconds
Color should let an agent triage before reading.
Maze task, old build vs. new
TEST 02・LEGEND-FREE RECALL
> 80%
A rule that needs a legend hasn't landed.
Five-second test, key hidden
TEST 03・MIS-ACTION RATE
->
BASELINE
Whether confirmable modals stop wrong calls.
Cancel-vs-complete rate, real sprint
- THE MODAL SUITE -
Every irreversible action names what it will do before the agent confirms it.
OUTCOME
Every case sorts itself by whose move it is
One rule decides what needs an agent right now, and it led to a Senior Product Designer Intern role at TiriVelo.
Try the prototype





















