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
"Stakeholder interviews shouldn’t be the only thing democratized—there’s a whole breadth of methodologies to consider."
Jemma Ahmed Steve Carrod Chris Geison Dr. Shadi Janansefat Christopher NashDemocratization: Working with it, not against it [Advancing Research Community Workshop Series]
July 24, 2024
"The work of the design system is constant change management, raising awareness, and fostering common language."
Nina JurcicThe Design System Rollercoaster: From Enabler and Bottleneck to Catalyst for Change
October 3, 2023
"Can a designer make a pull request and have it reviewed? That open boundary between design and code is key to unlocking design system potential."
Nathan Curtis Nalini P. Kotamraju Jack Moffett Dawn ResselDiscussion
June 9, 2016
"Measurements are always a conversation; they should not be a covenant imposed on you, especially when you’re trying something new."
Saara Kamppari-Miller Nicole Bergstrom Shashi JainKey Metrics: Comparing Three Letter Acronym Metrics That Include the Word “Key”
November 13, 2024
"Don’t forget the critical change agent persona — adoption and success was determined by the admin or practitioner users."
Malini RaoLessons Learned from a 4-year Product Re-platforming Journey
June 9, 2021
"Heat maps don’t just show where people click; they show where people think something is clickable but it isn’t, which causes frustration."
Mackenzie Cockram Sara Branco Cunha Ian FranklinIntegrating Qualitative and Quantitative Research from Discovery to Live
December 16, 2022
"If you want to talk about the things you’re learning, use the hashtag DAS 2021 on Twitter, Instagram, or LinkedIn."
Bria AlexanderOpening Remarks
June 9, 2021
"Growth boards enabled direction change sooner by objectively evaluating team health and strategic alignment."
Jackie HoLead Effectively While Preserving Team Autonomy with Growth Boards
January 8, 2024
"When they become important is when they recede into the background and become mundane."
Dan HillDesigning for the infrastructures of everyday life
June 4, 2024