Team Structure & Collaboration
Collaboration does not happen because people want it to. It happens when responsibilities are clearly held, communication channels are defined, and expectations are spoken rather than assumed. I examine existing team structures for what is actually happening, not for what the organisational chart suggests. Informal hierarchies, communication blockages, unclear accountabilities. What I find, I name. What I name, I work on. The result is not a team-building event. It is a structure that holds.

What I specifically examine
Every team has a formal structure and a lived one. The lived one determines how decisions are actually made, who genuinely holds influence, and why certain information never reaches the people who need it. I look at both.

In practice this means conversations with leaders and team members, observation of communication patterns, and analysis of interfaces between departments or functions. Not as an external audit that packages findings into a presentation and leaves. As work directly within the system, alongside the people operating inside it.

What frequently emerges is a recognisable pattern: accountabilities are clear in principle, but diffuse in practice. Decisions are made but not communicated. Feedback does not happen because no one is certain within which frame it is permitted. This costs time, energy, and trust.

An example from practice
A team of twelve people, three management levels, regular meetings. On paper, everything functions. In reality, operational decisions are made by one person who holds no formal leadership role, simply because she has been there the longest and knows the processes. The official leaders are formally responsible but substantively disconnected. This produces frustration on both sides and a team that functions but cannot scale.

The solution in such cases is rarely a restructuring. Most of the time it is enough to acknowledge the informal expertise, define clear decision-making frameworks, and formalise the communication routes that are already being used anyway.

What becomes measurable
Structural work does not show up in numbers immediately. It shows up in decisions being made more quickly. In misunderstandings becoming less frequent. In team members knowing who to approach when something is wrong. And in leaders being able to actually lead, rather than filling operational gaps.

Anyone looking to build, stabilise, or prepare a team for growth does not need theory. Anyone looking to make an existing team functional again needs someone who looks without an agenda. That is my work.