Contractor admins could submit license details and required documentation with less guesswork — while reviewers had a clearer path from submission to approval or revisions.
Role Product DesignerCompany ISNShipped
Stack
Figma
Cross-functional collaboration
Internal + client review cycles
Problem
License submission is a compliance-heavy workflow where small mistakes cause delays. Admins needed clearer guidance on what was required per license type, and reviewers needed consistent states to reduce back-and-forth and keep approvals moving.
Intervention
Designed a structured, requirements-led license flow with conditional document requirements, clear state messaging, and review-ready output. Prototypes moved through an internal approval pass before being refined for client review to match production behavior.
Outcome
Improved first-time submission quality and reduced review friction by making requirements explicit and states predictable — supporting faster resolution and fewer "missing information" loops.
Impact
Clearer pipeline
Internal → client review alignment across submission states
Fewer revisions
Better first-time submission quality through explicit requirements
Less back-and-forth
Clear requirements and consistent states reduced review loops
Design artifacts are protected
Screenshots and design files for this project are kept confidential out of respect for the client. If you'd like to review them as part of a hiring or collaboration conversation, reach out directly.
Access request sent
Check your email — a passcode will be sent once the request is reviewed. Usually within 24 hours.
Incorrect code. Try again.
01 / Research
Research
Captured common failure points — missing docs, unclear requirements, inconsistent formatting — and mapped the journey from start → submission → review → resolution.
02 / Define
Define
Defined the state model and conditional requirements logic that scales across license types. States supported: Draft, Submitted, Needs Changes, Approved, Expired, Archived.
03 / The hard call
The hard call
The design could be flexible and forgiving, or it could enforce correctness. Validation and conditional requirements prevent incomplete submissions — even if it adds structure to the experience.
"Correctness over flexibility — the cost of a wrong submission is higher than the friction of a stricter form"
04 / Ship & Watch
Ship & Watch
Shipped with consistent states and guidance. Refined copy and validation patterns based on internal and client review feedback.
