Senior Product Designer
Making complex products easy to trust.
Hi, I’m Tina! Most recently designing at Cisco, where I worked on complex products people rely on every day. I bring 12 years across SaaS, e-commerce, and community platforms, and I’m at my best where design, product, and engineering need to move together.
Accepting contract or fulltime work
•
Accepting contract or fulltime work •
Cisco | Compensation Experience
One Paycheck. Four Tools. Zero Answers.
Product Strategy · Zero-to-One Vision · UX Research · Enterprise Design
When sellers stopped trusting their pay, they built spreadsheets. We built them an answer. Cisco's 17,000+ commissioned sellers needed four tools to answer one question: am I being paid right? I led design on a from-scratch vision for the entire compensation experience, grounded in research with 1,100+ sellers across 65 countries. It won executive funding and is in development now.
hOp | Community Platform
Three audiences. One feed.
Product Strategy · Design Direction · UX/UI Design
A community app with 3 customers and one bet: get the resident to stay, and the property owner and the local business both win. Here's how I turned "borrow a hammer" into a behavior-change problem, and what I'd still test if I had the data.
Cisco | On-Prem Licensing
The foundation moved. Development didn’t stop.
Design Leadership · Enterprise UX · Information Architecture · Design Systems ·
Licensing was 8 portals becoming one when the design system underneath it was retired mid-project. Every screen had to be rebuilt, and development couldn’t stop. I led the migration, and along the way the platform saw its first year-over-year NPS increase in 6 years and about 40% fewer support cases.
Full walkthrough available on request
Design Philosophy
My Philosophy
Complexity is a debt, and users pay the interest.
Nobody designs a confusing product on purpose. It accrues, one reasonable decision at a time, until someone needs three tools and a spreadsheet to answer one question about their own work. Users rarely complain about that. They compensate. Every workaround is a design brief, and a pile of them is a roadmap.
Never throw data at a user.
Data-dense doesn't have to mean dense. A screen full of accurate numbers that answers nothing is a failure, even when every number is right. I learn the domain well enough to know which number carries the story, then build the hierarchy around it. Beautiful visualizations get cut when testing shows they don't do the work.
Ambiguity is the assignment.
The projects that need design most are the ones with no requirements, no budget, or no clear owner. I've said yes to work before it was funded and joined a project in firefighting mode and helped move it to building with intention. Then I make sure the next person doesn't fall in the same gap.