Discussion
Summary
In this talk, Maria emphasizes the concept of the minimum lovable experience, contrasting it with the traditional minimum viable product, highlighting ways to measure loveability using customer sentiment, active usage, and goodwill. She shares her qualitative approach of engaging deeply with employees across all levels to surface patterns and foster honest communication without formal data tools. Steve contributes his perspective on managing organizational change, emphasizing communication, inclusion, and cross-training to reduce fear and build empathy among teams facing uncertainty. Harry adds real-world examples of companies transitioning from product-focused to experience-driven cultures, noting challenges such as internal politics and the difficulty in identifying customers when products serve indirect users. The group discusses vulnerability, psychological safety, and structured creativity techniques—especially favoring quiet individual ideation before group sharing over traditional brainstorming. They also share practical conflict resolution methods, including role-reversal exercises to build empathy between opposing parties. The overall discussion underscores the importance of intentional design in culture change, collaboration, and innovation processes.
Key Insights
-
•
Minimum lovable product focuses on customer love and goodwill, measured through sentiment and engagement, unlike minimum viable product which focuses on basic functionality.
-
•
Maria spends months informally and formally engaging with employees to collect qualitative data revealing cultural patterns beyond surveys or recordings.
-
•
Avoiding recording interviews helps gain more candid employee feedback by reducing fear and sugarcoating.
-
•
Transitioning a company from product- or technology-centric to experience-driven requires cultural shifts, not just new teams, often creating political tensions.
-
•
Empathy and understanding between groups can be enhanced by cross-training, helping reduce uncertainty about job security during organizational change.
-
•
Designing for change means over-communicating and creating safe spaces for dissent to minimize resistance and build healthy collaboration.
-
•
Structured brainstorming with individual quiet ideation before group discussion prevents groupthink and ensures all ideas surface.
-
•
A conflict resolution technique involves role reversals, where each side defends the other's position to foster empathy and find middle ground.
-
•
Creating coalitions of the willing and embracing vulnerability helps accelerate cultural change through grassroots movements rather than mandates.
-
•
Accepting and managing failure as a natural part of innovation allows teams to take manageable risks without fear of catastrophic outcomes.
Notable Quotes
"Minimum viable product has become the minimal thing you can do to get out in the world, but doesn’t necessarily satisfy the needs of people you’re serving."
"I relied very largely on just qualitative information and looking for patterns from talking to over 100 people in a 9,000-employee company."
"I never record interviews with staff, never. Recording invites sugarcoating or lying because people are already vulnerable."
"Cultural shifts to experience-driven companies are less about creating new teams and more about creating a collective movement everyone owns."
"Cross-training helps teams feel more capable and less afraid of losing their jobs during transitions, creating less resistance to change."
"Being a change agent means designing for change, which is harder than the change itself."
"I prefer techniques where individuals generate ideas quietly first, so their train of thought isn’t lost in group dynamics."
"The empathy in defending the opposing team’s idea is very, very powerful and helps find a third way in deadlocked conflicts."
"I’m adopting a mindset of vulnerability and openness to failure because the worst outcome won’t shut the servers down or fire people."
"Communication over communication and creating safe spaces for people to disagree leads to healthy exchanges and minimizes detractors."
Or choose a question:
More Videos
"The more participatory the practices, the deeper and more intentional the engagement needs to be."
Alexia Cohen Adriane AckermanIncreasing Health Equity and Improving the Service Experience for Under-Served Latine Communities in Arizona
December 4, 2024
"Building in interruptions exponentially increases the accuracy of the findings."
Marc Majers Tony TurnerInterrupted UX - Add A Dose of Reality To Usability Testing
March 11, 2022
"Language itself can be a powerful design object, shaping social roles and organizational interactions."
Jorge ArangoDesign as an Antidote to VUCA
May 9, 2019
"Engineers spending 40 to 50% of their time building prototypes for research studies don’t have launch metrics to show for promotions."
Brenna FallonLearning Over Outcomes
October 24, 2019
"The Shaker village sidewalks followed people’s natural inclinations, not forcing unnatural movement."
Daniel GloydWarming the User Experience: Lessons from America's first and most radical human-centered designers
May 9, 2024
"If you build accessible shopping with these four keys, compliance with legal standards like WCAG will naturally fall into place."
Sam ProulxOnline Shopping: Designing an Accessible Experience
October 3, 2023
"Technology can revolutionize how we think about education."
Kristin SkinnerFive Years of DesignOps
September 29, 2021
"Racism is by design, and there's no way to counter it unless we counter it with design."
Denise Jacobs Nancy Douyon Renee Reid Lisa WelchmanInteractive Keynote: Social Change by Design
January 8, 2024
"You can send NDAs and informed consent forms directly through the platform, cutting down admin overhead."
Roberta Dombrowski Lianna Aduana5 Reasons to Bring your Recruiting in House
September 30, 2021
Latest Books All books
Dig deeper with the Rosenbot
What design strategies can support community-led rebuilding of maternal healthcare in rural maternity care deserts?
What are the main categories of survey tools and how do they differ in use cases?
How do enterprises balance qualitative and quantitative tools while integrating AI into UX research workflows?