Building a Customer-Centric Culture
Summary
When you’re building, not optimizing, you need everyone to learn from customers. But how do you build a team culture in which everyone, including backend engineers and compliance program managers, does research? I’ll share what I’ve learned so far on creative methods for how to coach, how to share insights, and how to impact company policies. You’ll walk away with a new approach to teaching non-researchers how to research, sharing insights from customers that get heard and impact decisions, and finally, ideas for selling your organization on policies that enable a more customer-centric culture.
Key Insights
-
•
Democratizing research means offering transparency, real insights, and permission for everyone to care about customer understanding.
-
•
Breaking down research training into micro-lessons embedded in existing team rituals boosts comfort and engagement.
-
•
Coaching teams to listen deeply to customer quotes together reveals underlying customer emotions like distrust.
-
•
Research office hours alone often fail to engage non-experts due to fears of doing research 'wrong'.
-
•
Assigning small 'quests' that let team members experience customer contexts directly is an effective entry point into research.
-
•
Sharing customer insights in multiple formats and cadences (like daily field postcards or Slack snippets) increases team curiosity.
-
•
Involving peers in feedback on insight-sharing initiatives creates allies who also share customer learnings.
-
•
Leadership support, including public recognition and explicit permission for research engagement, is vital to embed a customer-centric culture.
-
•
Customer-centricity should be integrated into hiring, performance reviews, and company values, not treated as a side task.
-
•
Real-world programs like ‘quest’ assignments and experiential scholarships help employees deeply understand customer challenges.
Notable Quotes
"Everyone needs permission from their manager and leaders to truly care about research outside of their job description."
"When you share a customer quote, the first layer is literal, but the goal is to dig deeper into what the customer is truly feeling."
"Research office hours sound good, but many people feel nervous or don’t know if they’re ready to participate."
"Embedding micro-lessons into team rituals sets an ongoing expectation that customer learning never ends."
"Sending team members on quests, like visiting a bank branch to understand immigrant experiences, makes research approachable."
"Sharing a quick customer insight story right after research sparks curiosity and invites more questions."
"A Slack bot that sends random customer quotes encourages ongoing learning and discovery."
"Leadership public recognition of time spent engaging with research is a powerful way to give people permission to participate."
"Customer centricity must be part of hiring, performance reviews, and budgeting for it to truly stick."
"Find an ally leader who can publicly encourage your team to take part in research initiatives and then support them."
Or choose a question:
More Videos
"Our community would not be what it is without you."
Bria AlexanderOpening Remarks
October 1, 2021
"Tay became a racist, sexist monster in less than eight hours because it learned from toxic internet data."
Nancy DouyonWe'll Figure That Out in the Next Launch: Enterprise Tech's Nobility Complex
June 15, 2018
"The products that you ship are direct reflections of your organizational processes and communication structures."
Tatyana MamutOpening Keynote: Breaking Conway's Law--or How to Work Differently and Not Ship Your Org Chart
June 3, 2019
"Everyone is learning and evolving right now; they just need language and frameworks to name what they’re growing."
Vanessa VarinTools are moments. Capabilities compound.
June 9, 2026
"Hosting is being a light presence to help the group see and listen without judgment, moving attention from me to us."
Marc RettigThe Urge to Migrate
June 4, 2026
"Sometimes the best way to understand a problem is to run the game multiple times and see why decisions differ."
Terry BuckmanWargaming (An Introduction)
August 10, 2023
"Developers are protective of their code, so AI coding tools naturally landed with them first."
Allan LowsonRehashing the Double Diamond: Collaborating across functions with AI-assisted prototyping
June 9, 2026
"Embedding process knowledge directly into work surfaces helps teams unpack and collaborate effectively."
Surya VankaUnleashing Swarm Creativity to Solve Enterprise Challenges
June 10, 2021
"One researcher per team for at least three days a week was considered an outrageous luxury at GDS in 2013."
Leisa ReicheltOpening Keynote: Operating in Context
November 7, 2018
