"Team performance is mostly about what happens between us." It is how Mogens Ejby Villadsen begins almost any conversation about what makes teams work. Not individual talent, not process design, not tooling — the space between people. How they align, communicate, misunderstand each other, and find their way back.

It is a perspective shaped by direct experience. Before becoming a coach, Mogens spent years inside development teams himself. He watched talented people struggle not because of technical shortcomings but because collaboration was unclear, expectations were unspoken, and the purpose of the work was assumed rather than shared. Those observations became the foundation of the work he does now.

What he looks for when he enters a team

Mogens observes before he intervenes. The clues he is looking for are not in the backlog or the burndown chart — they are in behaviour. "Confusion around goals, hesitation to speak up, conversations that are too polite — those are signals," he says. "You also notice when people make excuses or go quiet in stand-ups. Body language tells you more than the data."

His first move is typically reflection rather than correction. He describes what he observes and invites the team to wonder about it. The tone matters: deliberate curiosity signals safety. Sometimes he will introduce a concept — how forecasting works, what velocity is actually measuring — as much to establish credibility and clear up noise as to teach. The goal of the early teaching is dual: reduce confusion, demonstrate that he knows his craft without taking over.

"It's important they see I know what I'm doing," he says. "But also that I'm not there to make them do it my way."

When trust becomes visible

A large meta-analysis by De Jong and Dirks, covering more than 7,700 teams, found that intrateam trust is one of the most consistent predictors of performance. Mogens has seen this pattern play out across sectors — healthcare, energy, advanced manufacturing, financial services — across Europe and the Middle East. Trust, in his experience, becomes visible in specific moments.

One is when a team in the middle of a tense conversation pauses and asks for his perspective. Not to have him decide, but because they believe he will help them think more clearly. "That's when I know they're letting me in," he says.

Another is the quieter signal: a team member who says, "I don't know exactly what you do, but I'm better at my work when you're here." This kind of comment reflects a deeper shift — greater clarity or focus produced not by directive intervention but by the quality of the conversations being facilitated.

Methods that build connection

Two formats appear consistently in his practice. The Market of Skills, developed by Peter Lang, creates space for team members to share what they bring and what they want to learn from each other. It builds mutual awareness in a structured way and tends to surface resources within the team that were previously invisible.

His Future-spective 5F, an adaptation of the 5F team coaching framework, helps teams articulate how they want to work together going forward rather than remaining focused on what has gone wrong. Expectation alignment — clarifying what people expect from each other and from the work — runs through both formats and through all of his engagements. "It's closer to navigating a course than following a plan," he says. "You check direction often, especially early on."

The underlying philosophy

Better Change's approach combines the human dimension with data. Lead time, flow metrics, and learning loops act as mirrors rather than targets — information that helps teams see their own system more clearly. "If you want to improve team performance, you need to learn faster and put your effort where it actually matters," Mogens says. "Value grows from shared learning, and shared learning grows from strong relationships."

Real agility, in his view, begins when people genuinely understand how their work connects — to each other, to the customer, to what the organisation is trying to achieve. Not when the framework is implemented. When the connection is understood.