> Markdown version of [/videos/2141-how-to-use-feedback-to-build-better-software-vicky-pirker](https://www.wearedevelopers.com/videos/2141-how-to-use-feedback-to-build-better-software-vicky-pirker). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# How to use Feedback to Build Better Software - Vicky Pirker

Vicky Pirker warns that treating colleagues like AI chatbots is destroying team empathy. Learn to overcome the IKEA bias and deliver feedback that actually builds better software.

- **Speakers:** 
- **Event:** 
- **Published:** August 7, 2026
- **Duration:** 31:47
- **URL:** https://www.wearedevelopers.com/videos/2141-how-to-use-feedback-to-build-better-software-vicky-pirker

## Summary

Developers often struggle with delivering and receiving feedback, especially across cultural divides where blunt criticism can trigger the "IKEA bias"—the psychological tendency to take critiques of one's own creations personally. Emphasizing a human-centric approach, UX advocate Vicky Pirker explores how bridging the communication gap between technical and non-technical stakeholders requires empathy rather than just factual corrections.

Effective feedback requires speaking the stakeholder's language. Instead of relying on technical jargon, developers should frame software issues around business impacts like project deadlines and return on investment, or use relatable analogies to explain complex systems. Furthermore, understanding the neuroscience behind emotional reactions highlights the importance of pausing and breathing to prevent amygdala hijacking before responding to critique. By asking colleagues about the context and constraints that led to a specific technical decision rather than immediately pointing out flaws, teams can eliminate finger-pointing and foster a psychologically safe space for innovation.

As the tech industry shifts toward an AI-driven landscape, developers face a new communication challenge: the blunt, demanding prompts used to interact with large language models risk bleeding into human interactions and deteriorating team empathy. Counteracting this requires intentional practice and repetition. By consciously separating personal identity from the software product and actively practicing empathetic feedback, developers can build cognitive resilience and maintain crucial human connections in an increasingly automated world.

**Keywords:** software developer feedback, cross-cultural tech communication, IKEA bias psychology, technical stakeholder communication, neuroscience of feedback, amygdala emotional response, technical jargon translation, business impact framing, context of use in UX, psychological safety in tech, LLM prompt communication impact, generative AI empathy loss, cognitive resilience practice, product critique separation

## Chapters

1. **Overcoming cognitive bias and cultural differences in feedback** (00:39) — Recognizing the psychological attachment developers have to their code prevents blunt criticism from causing emotional harm.
1. **Regulating emotions and translating technical issues for stakeholders** (04:22) — Pausing to manage neuroscience triggers allows developers to translate technical problems into business impacts effectively.
1. **Discovering project constraints through blameless problem solving** (09:35) — Asking about historical constraints and processes avoids finger-pointing and creates a safe space for collaborative debugging.
1. **Navigating the impact of generative AI on team empathy** (14:49) — The aggressive tone required to prompt large language models risks deteriorating polite and empathetic human communication.
1. **Balancing automated efficiency with genuine human connection** (20:37) — Relying solely on automated systems for customer service and communication can alienate users who require empathetic interactions.
1. **Engaging with developer communities to foster industry collaboration** (26:56) — Attending technical congresses breaks anti-social stereotypes and revitalizes developers through shared expertise and networking.
1. **Practicing repetition to build resilience against critical feedback** (29:03) — Repeatedly separating personal identity from the product trains the brain to process technical criticism without defensive emotional reactions.

## Related Moments

- [Addressing developer burnout and the impact of artificial intelligence](https://www.wearedevelopers.com/videos/1504-cracking-the-code-to-tech-team-satisfaction) (from "Cracking the Code to Tech Team Satisfaction")
- [Addressing psychological safety and ethical risks of AI adoption](https://www.wearedevelopers.com/videos/1950-the-scrum-master-as-an-orchestrator-guiding-human-ai-collaboration-in-modern-teams) (from "The Scrum Master as an Orchestrator: Guiding Human–AI Collaboration in Modern Teams")
- [Connecting empathy to technical resilience in software development](https://www.wearedevelopers.com/videos/465-empathy-the-secret-sauce-of-resilience) (from "Empathy: The secret sauce of Resilience")
- [Communicating software deviations with empathy to encourage positive improvement](https://www.wearedevelopers.com/videos/87-excellent-software-testing) (from "Excellent Software Testing")
- [Cultivating a learning-focused and empathetic engineering culture](https://www.wearedevelopers.com/videos/64-shared-mobility-for-everyone) (from "Shared mobility for everyone!")
- [Designing engineering workflows around human judgment and project context](https://www.wearedevelopers.com/videos/1998-from-code-to-culture-why-leadership-determines-software-quality) (from "From Code to Culture: Why Leadership Determines Software Quality")

## Related Articles

- [Lessons for Vibe Coders and Developers](https://www.wearedevelopers.com/magazine/614-lessons-for-vibe-coders-and-developers)
- [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift)
- [Exploring AI: Opportunities and Risks for Developers](https://www.wearedevelopers.com/magazine/522-exploring-ai-opportunities-and-risks-for-developers)
- [Transforming Software Development: The Role of AI and Developer Tools](https://www.wearedevelopers.com/magazine/527-transforming-software-development-the-role-of-ai-and-developer-tools)

## Related Jobs

- [Senior Engineer, Infrastructure Platform](https://www.wearedevelopers.com/jobs/ext/328836-senior-engineer-infrastructure-platform) at **Intercom, Inc.**
- [Staff Software Engineer, Copilot Experiences](https://www.wearedevelopers.com/jobs/ext/164361-staff-software-engineer-copilot-experiences) at **GitHub**
- [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx**
- [AI Operations Manager (all genders)](https://www.wearedevelopers.com/jobs/48263-ai-operations-manager-all-genders) at **envelio**
- [Principal Software Engineer, Enterprise AI Platform](https://www.wearedevelopers.com/jobs/ext/1467292-principal-software-engineer-enterprise-ai-platform) at **GitHub**
- [AI Full Stack Engineer](https://www.wearedevelopers.com/jobs/ext/1354435-ai-full-stack-engineer) at **Almedia**