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 can overwhelm product teams with conflicting customer requests, necessitating a structured VOC program.
-
•
Launching a VOC program without broad consensus often fails, as happened initially when Shippra worked alone.
-
•
A sharp drop in NPS served as a critical trigger to rally executives and teams around customer feedback.
-
•
Focusing on NPS over other metrics like CSAT or revenue helps maintain focus on customer loyalty during VOC efforts.
-
•
Defining the core metric for success as the number of VOC-tagged product issues resolved creates clear impact measurement.
-
•
VOC inputs combine qualitative data from research, social media, and support, with quantitative analytics for comprehensive understanding.
-
•
Evolving tools—from Evernote to spreadsheets, Miro boards, UserVoice, and Idiomatic—enabled scaling VOC data management.
-
•
A coalition model with a dedicated facilitator ensures cross-functional alignment and shared ownership rather than conflict.
-
•
Monthly prioritization meetings balance data-driven analysis with trusting customer-facing team judgment to overcome analysis paralysis.
-
•
VOC programs can expand beyond product changes to impact pricing, legal, and other company areas, reflecting customer experience holistically.
Notable Quotes
"We went from 100 to 200 people but still had the muscle of a 50 person company—it was chaos for product managers."
"Don’t jump to a solution too fast without consensus; I tried to build a VOC system solo and it didn’t catch on."
"Our NPS plummeted after a rebrand and that freaked out executives—it was our fire moment to start VOC."
"We decided to stick with NPS because we had a long history with it and didn’t want to muddy our goals."
"The moment we felt customer feedback worked was when it got incorporated directly into the product roadmap."
"At first, VOC was just me synthesizing, but as the company grew, we needed tools like UserVoice and then Idiomatic."
"UserVoice let us merge similar requests internally, which was crucial before automation."
"We had to push through analysis paralysis and trust our guts on what to prioritize for product changes."
"Ownership of VOC is a hot potato—we decided on a coalition with a facilitator to avoid competition."
"VOC enhances but does not replace user research; it captures the nuggets that would otherwise get lost."
Or choose a question:
More Videos
"The hardest part about remote is making design reviews feel collaborative and team-based."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"Many product managers got their roles because they know the business or subject matter, but they don’t know how to manage product development."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Governance is about decision making, not workflow processes."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"Every small action contributes to a larger impact in the fight against climate change."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"If you get a perfect score on your OKRs, it means you didn’t set your sights high enough."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Linear perspective created this myth that we can see reality from a single perspective, which is the source of all misunderstanding."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"If you don’t bring stakeholders into the research journey, they won’t believe or use the data."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"The toy shouldn’t be the goal of play, but a tool or a process that unlocks the unlimited possibilities set forth before a child."
Designing Systems at Scale
November 7, 2018
"A lot of developers are way too confident they write perfect code; testing bug fixes often reveals hidden issues."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
