Changing team meetings to repair a working relationship
As Head of Product Design at a B2B platform company, I led a team of five and had a design function to build. The lesson I use most came from somewhere else: a working relationship that kept breaking down, and what changed when I stopped looking at the person and started looking at the conditions.
Change the conditions, and the collaboration follows
- The setting
- A B2B platform company in the middle of a platform shift. I was Head of Product Design, leading a team of five, including a design lead.
- The problem
- One engineer's work wasn't landing with the team. Meetings were tense, points got cut off, and the team had learned to route around the collaboration.
- What changed
- I changed the conditions the team met under: agendas shared early, material sent ahead, turn-taking on purpose, decisions in writing. Within months the dynamic shifted, and the habits became the team's default. What I observed as the team's lead; nothing here was measured.
- Three takeaways
- Ask what's wrong with the system before you ask what's wrong with the person. Make the cheap conditions the default. Answer "why change for one person?" with the cost.
Quick syncs that ran for an hour
The meetings had a pattern. A "quick sync" turned into an hour-long debate nobody could have prepared for. No agenda went out in advance. Discussion was fast and verbal, and whoever spoke first and loudest set the direction.
One engineer's points got cut off before they were finished. The discussion moved on. Over time, the team learned to route around the collaboration rather than work through it.
When collaboration fails, the reflex is to manage the person
This is a story about that working relationship, and about the question I ended up asking instead of the usual one.
The usual one is about the individual: what is wrong with that person? It is the comfortable question, because the answer never involves your own process. The question I now ask first is about the system, and it travels to almost any team.
Excellent work that kept getting talked over
I had joined to make design a real function, with the same weight as product and engineering. I built a planning process so design, product and engineering worked from the same picture. The design system was mine, and I set up joint governance with engineering around it.
Inside that team, one collaboration kept failing. It did not add up. The engineering work itself was excellent, and the ideas, once there was room for them, were often the sharpest in the room. They just kept getting talked over.
I stopped assessing a person and started recording conditions
So I started watching the pattern instead of the person. When did this collaboration fail, and when did it work?
The pattern I was actually looking at, once I stopped looking at the person.
It failed in fast, talk-over-each-other discussion and under time pressure. It worked in writing, and with time to think before answering.
Our collaboration ran on one default: fast, verbal, loudest voice first. It filtered out good ideas before anyone heard them.
Five changes to how the team worked, none of them about one person
Every one of these changed the conditions the whole team worked under. All of them were cheap, and all of them applied to everybody.
Five changes to how the team worked. None of them about anyone in particular.
-
Agendas, shared early
Every meeting got a written agenda in advance. No more "quick syncs" that turned into hour-long debates no one could prepare for.
-
Room to prepare
Context and material went out before group discussions, so thinking could happen ahead of the meeting rather than under time pressure inside it.
-
Turn-taking, on purpose
In group settings I made space for sequential input, instead of letting whoever spoke loudest set the outcome.
-
Decisions in writing
Important decisions were written down, so nobody had to rely on their own memory of the conversation.
-
Coaching the design lead
I coached my design lead through the same shift: how to work through a strained engineering relationship directly, rather than routing around it.
"Why change for one person?" Because the process had a cost.
Not everyone agreed. "Why should we change how we work for one person?" came sometimes out loud, sometimes through eye-rolls and foot-dragging.
Part of my answer was about fairness. Equality is everyone getting the same thing. Equity is everyone getting what they need to contribute, and people need different conditions to do their best work.
The other part was the plain business case. Our process was filtering out good ideas before they were heard. That is a cost, on top of the fairness question.
Within months, the habits belonged to everyone
Within months the dynamic shifted. The bigger change was that the structured habits spread: other people adopted the prep, the agendas and the written decisions for themselves. They stopped being a fix for one situation and became the norm.
None of this was measured. It is what I saw as the team's lead.
- The collaboration
- Tension, points dismissed, the team routing around the working relationship Ideas got airtime, and problems others missed got caught
- Team norms
- Loudest-voice-first discussions Written agendas, prep time, and documented decisions became how the team worked by default
- How the team thought about friction
- People started asking what was wrong with the process before deciding what was wrong with a person
The agenda goes out first now
The meetings still happen. The agenda goes out first, the material goes with it, and turns are taken on purpose. A decision ends up in writing instead of in five different memories.
And the points that used to get cut off now get finished.
Three things to try with your own team
-
Ask what's wrong with the system before you ask what's wrong with the person.
Write down when a collaboration fails and when it works. If the same person does well in one setting and struggles in another, the setting is your variable.
-
Make the cheap conditions the default.
An agenda sent ahead, material before the meeting, turns taken on purpose, the decision in writing. None of it needs a budget, and none of it helps only one person.
-
Answer "why change for one person?" with the cost.
Good ideas filtered out before anyone hears them are a business cost. Say so plainly, alongside the fairness argument.
If it fails in every setting, the setting isn't your variable
This approach is for collaboration that fails in some conditions and works in others. If it fails everywhere, in writing and with time to prepare too, changing the conditions won't fix it, and you need a different conversation.
Want to hear more?
- Ask me what changed once the agenda started going out in advance, and why habits meant for one working relationship spread to the whole team.