CaSE: Conversations about Software Engineering · CaSE Podcast Team

Aino Corry on Better Tech Meetings

·1 hr 9 min·6 clips

Aino Corry reveals why a good facilitator sometimes needs to halt a meeting entirely to avoid wrong decisions.

Aino comes in as an independent consultant who helps clients with meeting facilitation in general and retrospectives for agile software development in particular. She works with retrospectives, OKR meetings, design sprint facilitation, architecture health workshops, mob programming sessions, and executive strategy summits. Sven also knows her from program committee meetings for conferences like GoTo, YOW, and QCon. The conversation starts with her book on retrospective anti-patterns. Sven notes that the book still helps even if retrospectives are not on the calendar every week. That opens the door to a wider discussion of meetings in general. They talk about technical meetings, architecture design reviews, and other situations where people have to disagree in public. Sven describes the problem of walking into a meeting where a topic is likely to create tension. He is trying to raise concerns about code without making the room hostile. Aino answers by starting before the meeting itself. If you already know who is likely to create tension, she suggests talking to them one on one first. That helps move conflict out of the group setting, where bystanders and other reactions can make things worse. She says aggressive reactions usually come from fear, frustration, or feeling insulted. If people watch the facilitator lose their temper, the temperature in the room tends to rise instead of fall. The practical goal is to separate the conflict from the larger meeting whenever possible. She also points to nonviolent communication as one way to build empathy between sides. When conflict appears without warning, she advises keeping your head cold. The discussion stays focused on making the meeting concrete enough that people can respond usefully. Near the end, she suggests asking for feedback on a specific part of the facilitation rather than a vague judgment of the whole meeting. That gives the other person something they can actually answer while still staying inside the meeting's purpose.

As heard by us

A grounded guide to keeping hard technical meetings from turning sharper than they need to be.

Aino Cori comes across as a seasoned independent consultant, and that background gives the conversation a useful range. It starts with retrospective anti-patterns, then keeps widening the lens to technical meetings, architecture reviews, and the everyday friction that shows up…

Read the full review in PlayNext →

Why you'd press play

Turn a tense code discussion into a calmer, more useful meeting.

Read the full recommendation in PlayNext →

Listen to the show on

Apple Podcasts Spotify

Play clips from this episode More from CaSE: Conversations about Software Engineering