Aino explains that many organizations focus almost exclusively on success stories, overlooking the valuable lessons hidden in failure. This survivorship bias prevents real learning and encourages unrealistic expectations. By openly discussing what went wrong, teams can identify patterns, improve processes, and prevent recurring issues.

A central theme of the interview is psychological safety. Aino highlights how vulnerability supports trust, and trust enables people to speak up about mistakes, uncertainties, and risks. When teams feel safe, they address problems earlier, collaborate more openly, and produce higher-quality results. She also reflects on the positive shift over the past decades from "hero culture" towards more empathetic and human-centered ways of working.

Drawing inspiration from The Lord of the Rings, Aino illustrates how collaboration, shared purpose, and honest communication are essential for navigating complex challenges – both in storytelling and in real-world software projects.

Key Takeaways:

1. Survivorship bias limits learning by hiding the valuable lessons found in failure.
2. Vulnerability builds trust, and trust empowers teams to improve continuously.
3. Psychological safety leads to healthier collaboration and better outcomes.
4. Retrospectives are essential for structured learning and team growth.
5. Positive team cultures encourage individuals to become change agents for improvement.
6. Sharing failures openly strengthens resilience and long-term performance.

This interview is a must-watch for anyone who believes that real progress in software architecture and teamwork comes from honesty, courage, and the willingness to learn from what didn’t go as planned.