Operational product · HID Global
Voucher Management Console
Certificate voucher orders for partner organizations.
Certificate vouchers were run out of personal Excel sheets, and orders expired before anyone noticed. I designed the console that replaced them.
- Role
- Product designer, end to end
- Team
- Design, product, engineering
- Year
- 2022-2026
- Platforms
- Web, desktop first, works on tablets
- Methods
- Stakeholder interviews, spreadsheet walkthroughs, information architecture, usability testing, specs
- Outcome
- Excel replaced by one shared queue, with bulk assignment checked before commit
Screens are redacted. Customer, partner, and person names and emails are hidden.
Problem
There was no product yet. Customer admins managed certificate vouchers in Excel, each in their own sheet. Orders expired unnoticed, and a typo in a batch surfaced only when someone never got their voucher.
Excel also had no roles. Anyone with the file could change anything, so nobody could own the work.
Purchasing could not change. Customers still buy by purchase order or online, so the console starts from the order. The first order sets up the account, and later orders under the same email land in it.
What goes wrong without it
An expired order means vouchers a customer paid for and never used.
Research
This was a new product, so the spreadsheets were my first research material. They showed me the work was a queue, but Excel treated it as a list. Each finding below led to a design decision.
How I learned
Stakeholder interviews
Product, support, and partner-facing teams. I asked what breaks and who hears about it first.
Spreadsheet walkthroughs
Customer admins walked me through the Excel files they used. I noted every column, color code, and workaround.
Spreadsheet audit
I mapped each column to the job it served. That map became the first object model.
What I found
Finding 01
Expiry was just a column.
- What I saw
- Expiry dates sat in an Excel column. Nothing warned customer admins when an order was about to lapse.
- What it changed
- The home screen became a queue sorted by expiry, with a day count on each voucher order.
Finding 02
Every customer admin assigned vouchers differently.
- What I saw
- Each customer admin kept the sheet their own way. Some added one person at a time, others pasted lists.
- What it changed
- One bulk path from a CSV template, so every batch has the same format and can be checked.
Finding 03
Errors surfaced days later.
- What I saw
- A spreadsheet accepts anything. A typo in an email was often found by the person who never got a voucher.
- What it changed
- Check every row before commit. Mark it Valid or Error, and assign only valid rows.
Finding 04
Old records buried live work.
- What I saw
- Past assignments stayed in the same sheets as open orders. Customer admins scrolled past them to find live work.
- What it changed
- Expired voucher orders move to a searchable archive, out of the working list but never deleted.
Process
01Discover
- Stakeholder interviews
- Walkthroughs of the Excel files customer admins used
- Each spreadsheet column mapped to a job
Output. Four findings and a list of every job the console had to support.
02Define
- Object model: voucher order, assignment, customer admin, status, archive
- Sitemap built from jobs, not from spreadsheet columns
- One status word per state: assigned, redeemed, expired
Output. Product, engineering, and I agreed on one status word per state before any screen was drawn. We used those words in every screen and spec after that.
03Explore
- Three bulk directions: table multi-select, one-by-one dialog, CSV upload
- Low-fidelity flows in Figma
- Weekly reviews with product and engineering
Output. CSV upload with a review step. Customer admins have to prepare a file, but every batch then arrives in one format the system can check.
04Test
- Usability sessions on a clickable prototype
- Tasks: assign a batch with errors, find an expired order
- Findings logged against each screen
Output. Changes to the dashboard, validation, archive, and assign dialog. See iterations below.
05Ship
- Specs for every state: empty, loading, error, no permission
- Built on the HID pattern library
- Build reviews with engineering
Output. Specs engineering could build without guessing. Reusing the pattern library kept the console consistent with HID's other admin products.
Information architecture
Customer admins do three jobs here. They work live orders, manage who can assign, and look up old orders. Each job got its own place in the left navigation.
How an account starts
- A customer buys vouchers by purchase order or online
- The first order sets up the account
- Later orders under the same email land in it
Voucher Management Console
Left nav, start page
Voucher Orders
The live queue
Search
Email, voucher ID, or order number
Filters
Certificate type, issuance, validity
Order cards, expiring first
Available vouchers and a day count
Voucher order
Type, issuance, expiry
Assigned Vouchers tab
Redeemed Vouchers tab
Export
Assign Vouchers dialog
Manual or bulk upload. CSV template, row review, assign
Left nav
Voucher Managers
Who can assign
Manager list
Name and email
Add Voucher Manager
Row actions
Suspend or restore
Left nav
Expired Voucher Orders
Out of the live list, never deleted
Search
Order number
Expired order cards
The same card as the live list
Assignment history
Also always available: Profile, in the top bar. Registration Admin, Purchase Admin, and Voucher Manager each see different parts of this map.
User flows
The same three jobs, step by step. Bulk assignment has the most steps and the most ways to fail, so it gets the most room.
- Start
- Step
- Decision
- Console
- Result
Assign vouchers in bulk
Get vouchers to a list of people before the order expires.
Start
Open Voucher Orders. Expiring orders are at the top.
- Step:
Search or filter, then open the order.
- Step:
Select Assign Vouchers. The dialog shows how many vouchers remain.
Decision
Choose an assignment method
Manual
Enter recipients in the dialog.
Bulk upload
Download the CSV template, fill it in, and upload it.
Console
The console checks every row and marks it Valid or Error, with the reason.
Decision
Any rows with errors?
Yes
Fix the file and re-upload, or assign now and skip the error rows.
No
Every row will get a voucher.
- Step:
Select Assign.
Result
Recipients get redemption instructions by email. Each voucher shows Assigned, then Redeemed.
Look up an expired order
Answer who got a voucher from an order that has closed.
Start
Open Expired Voucher Orders from the left navigation.
- Step:
Search by order number.
- Step:
Open the order card. It is the same card as the live list.
Result
Review the full assignment history.
Share the load
Let more people assign vouchers, with clear ownership.
Start
Open Voucher Managers.
- Step:
Select Add Voucher Manager and enter their details.
Console
The new manager appears in the list.
Decision
Need to change their access later?
Suspend
Pause their access from the row menu.
Restore
Give a suspended manager access again.
Iterations
What changed between the first version and the one that shipped, and what made it change.
Dashboard
- First version
- Summary charts of voucher counts by status.
- Shipped
- A queue sorted by expiry. Counts shrink to a strip above it.
Why it changed. In testing, customer admins skipped the charts and scrolled down to see what was due.
CSV validation
- First version
- Upload, assign, then one success or failure message.
- Shipped
- A review table before Assign. Each row shows Valid or Error, with the reason.
Why it changed. One failure message didn't say which rows failed. Customer admins re-checked the whole file by hand.
Archive
- First version
- Expired voucher orders hidden behind a filter on the live list.
- Shipped
- A separate archive with its own search, using the same order card.
Why it changed. Customer admins forgot the filter was on and thought orders had gone missing.
Assign dialog
- First version
- An Assign button with no context.
- Shipped
- The dialog shows vouchers remaining and says rows with errors will be skipped.
Why it changed. Customer admins weren't sure whether a batch would use up the whole order.
Screens
Four screens, in the order a customer admin sees them. Each caption names the decision it shows.




Registration Admin, Purchase Admin, and Voucher Manager each see different work.

Principles I used
Visibility of system status
Expiring orders lead the queue, with a day count on each one.
Error prevention
Before Assign, the dialog shows how many vouchers remain and says rows with errors will be skipped.
Help users recover from errors
Each invalid CSV row shows the reason. Customer admins fix the file and upload again. Only valid rows get vouchers.
Consistency and standards
Assigned, redeemed, expired. The archive uses the same order card as the live list.
Accessibility notes
Contrast
Text and status indicators meet WCAG 2.1 AA contrast.
Keyboard
Search, filters, the assign dialog, and tables all work with a keyboard.
Status in words
Valid, Error, and Expired appear as words. Color only backs them up.
Outcome
- What changed
- Voucher work moved from personal Excel sheets into one shared queue. Expiring orders now show up first. Bad rows get caught before commit, instead of by the person waiting for a voucher. Recipients get redemption instructions by email, and each voucher is tracked from assigned to redeemed.
- Roles
- The console added the roles Excel never had. Registration Admin, Purchase Admin, and Voucher Manager each see their own work. Customers can add Voucher Managers to share the work, and everyone can see who owns what.
- Reported result
- On my résumé: task completion time on core admin workflows fell 35% after I simplified flows and screen logic. It covers HID admin work, not this console alone.
- What I delivered
- The console from sitemap to specs: order list, order details, CSV bulk assignment, archive, and manager settings.
- What I'd do next
- Watch the week orders expire. If people still export failed CSV rows to fix them offline, the validation screen isn't done.