How we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
Summary
Shipra Kayan, the former head of insights at Upwork, will present the origin story of Upwork's hugely successful and long-running VoC program. From the moment that triggered the formation of a VoC initiative, the ups, and downs of experimenting with its operating model, to why this program is still going strong 7 years after it was launched. She will field questions like "Who owns the VoC?", "What is its purpose?", and "Will we just create another presentation that won't have any real impact?" - 15 minutes Upwork VoC case study - 15 minutes for Q&A
Key Insights
-
•
Rapid company growth creates chaotic, conflicting user feedback that overwhelms product managers without a clear VOC process.
-
•
Crisis moments, like Upwork's NPS drop post-rebrand, can catalyze executive support to start formal VOC programs.
-
•
Aligning around a single, existing customer loyalty metric (NPS) helps maintain focus rather than fragmenting goals.
-
•
The key operational metric was the number of VOC-tagged product issues fixed, translating feedback into actionable roadmap items.
-
•
Manual note-taking and affinity mapping worked initially but required evolution to collaborative software and AI tools as scale grew.
-
•
UserVoice was adapted internally to aggregate and cluster customer issues before migrating to more automated idiomatic software.
-
•
Monthly prioritization meetings with cross-functional stakeholders and frequent product leadership syncs ensured transparency and action.
-
•
VOC ownership was best handled as a coalition with a facilitator rather than a single owner to avoid silos or turf wars.
-
•
VOC findings expanded impact beyond product to pricing and legal policy changes, showing broader organizational influence.
-
•
Attempting to change company culture too quickly or solo is less effective than focusing on incremental, visible customer-driven product improvements.
Notable Quotes
"Going from 100 to 200 people, suddenly product managers started hearing from a dozen people a week with conflicting requests."
"I tried to do everything all by myself at first and it didn’t catch on because no one else knew I was doing it."
"The rebrand caused our NPS to plummet and freaked out our executives — that was the trigger to get serious."
"We stuck with NPS because it was a pure metric with a long history we could trend, instead of muddying things with loyalty or revenue."
"Our one metric that mattered was maximizing the number of VOС-tagged tickets solved – showing customer feedback made it to the roadmap."
"We moved from Evernote to spreadsheets, to a giant affinity board in Mirror, then to UserVoice, and finally to idiomatic software with AI."
"We had to push through analysis paralysis and trust our guts as customer-facing teams that knew the business."
"Ownership of VOC is a hot potato, so we built a coalition with a facilitator to keep it collaborative and effective."
"VOC wasn’t a replacement for user research, but an enhancer that captured nuggets researchers might miss during discovery."
"I spent too much time trying to change company culture and should have focused more on just getting things done."
Or choose a question:
More Videos
"You have to go from being able to deliver a message in three bullets and then turn around in the next moment and deliver a massive service blueprint or customer journey."
John CutlerOxbows, Rivers, and Estuaries: How to navigate the currents of change (without burning out)
December 3, 2024
"If you’re generating buy-in, don’t forget what it will mean for your difficult stakeholders—they may have external pressures you don’t know about."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"You don’t have to sit through two hours a day; we’ll spend about 15 minutes on setup then you’ll pair up and do the exercise."
Dave GrayGroup Activity: Making Sense of DesignOps
November 7, 2017
"The subtle art of taking care of yourself and giving a f in ways that generally encourage coherent behaviors."
John CutlerThe Alignment Trap
November 29, 2023
"Just because you can color code something doesn’t mean you should."
Abby CovertStuck? Diagrams Help
October 27, 2022
"Side-pav proposals answer what’s going on, why it matters now, what you propose, what action to take, and what benefit comes from it."
Mark InterranteCollaboration Flows in Product Development
June 9, 2017
"Too often, futures imaginaries want to erase or align difference rather than reckon with it."
Devon PowersImagining Better Futures
March 9, 2022
"Bring your research team as note takers and facilitators—they make excellent collaborators and help build feedback loops."
Prayag NarulaHow to Empower Your Designers to Do Good Research – And Why You Want To
June 10, 2022
"Cloud code wasn’t programmed to do this; it’s a very lightweight system where the model does most of the work."
Peter Van DijckHands on AI #3: Claude Code for UX people
October 22, 2025
