November 2026 · conflict · alliance“My manager solves all my problems. That's my problem.”
A team member said this to me: “At our one-on-one my manager does ask me where I'm stuck, but then he doesn't hear me, interrupts, and solves it himself...”
I'm working with a team right now, and there's tension between a manager and his direct report (details changed). He's new to managing, after years as the expert who fixed everything. He rewrites her emails and takes her decisions. She feels she doesn't have any agency.
From the outside, it looks like conflict. He micromanages. She guards her territory. Someone has to give in. But it isn't a conflict yet. The tension that might grow into conflict is already there (let's name that elephant in the room), but nobody dares to talk about it.
And let's be honest: nobody teaches us how to do this. Not at school, not at university, and not early in our careers. Nobody trains us to design our relationships at work. Yet we work side by side from 9 to 5, as different people with different approaches. It's normal that our opinions sometimes clash. With some intention, we can talk about it skilfully. Without it, we either collapse into unskillful conflict, or we avoid it, simply because nobody showed us how.
Here is how I see it: underneath are two good intentions. He wants to help, and to feel useful in a new role. She wants to own her work. But the more he rescues, the less she owns.
I see this pattern in many teams: tension turns into unskillful conflict when people never designed upfront how they want to have these conversations. And the goal isn't 100% agreement. That's rare, and it's normal. The goal is an alliance: the common interest in how you work together.
So here is the tool I use personally with all my clients, without exception, especially with intact teams where everyone depends on everyone. We design our alliance, on a good day, before the hard one:
- Share your good intentions first.
- How do we want to be together? What atmosphere do we want between us?
- How do we want to be when things get difficult?
- Each of you shares one thing the other can count on. “You can count on me to ask how you'd solve it, before I jump in.”
Then flag it when you drift. It's not a guarantee. It's a shore to stand on before you step into the water. And it works far beyond the office: it's a very good tool to have when your in-laws visit for the holidays.
What's one thing your team could agree on this week, on a good day?
↑ all posts
November 2026 · conflict · team coachingWhy I didn't call it a conflict workshop
Last month I got an invitation to run a “Skillful Communication Workshop”. I intentionally didn't call it “Toxic Grid” or “How to resolve the conflict”, as that might already be triggering for the team members. The conflict was already there, and had been for a while. Nobody wanted to call it that, so we called it Skillful Communication.
On the first day, I walk into the room and you just feel it before anyone speaks. People sit a little too far from each other. They smile, but their arms are crossed. Everyone knows why I'm here, but nobody dares to say it out loud. I can see they're waiting for me to stand up and say, “Okay, let's resolve this conflict.” And I think: if I say that now, someone gets triggered in the first five minutes, someone else defends themselves, and the rest go silent. I would lose them from the very beginning.
So I don't say it. I say, “Before we dive into our topic for today, let's spend a couple of minutes designing how we want to be with each other in this particular conversation.” I ask what atmosphere they want in this team on an ordinary Tuesday, what values they want to honour and how they'll know they have that. Then I ask how they want to be with each other when things get hard, and what would actually help them start that difficult conversation instead of avoiding it, as they did before. Then I ask: how will we know we're keeping this?
And then something invisible shifts in the room. People share that they want respect and care in the conversation, that they are willing to have it without blaming, by actively listening to each other. Only after this design-the-alliance conversation is the team ready to open the conversation about the conflict.
Each team I work with teaches me something. Not every conflict can be resolved into full agreement on the topic, and this is normal. But every conflict can be aligned around a common interest. And it matters more than most of us admit. A study by Acas published last November, with more than 4,500 employees, found that 44% had a conflict at work in the past year, the highest level ever recorded. More than half said it left them stressed, anxious or depressed. One in ten left their job because of it. And one in five did nothing at all, so the conflict simply stayed.
In ORSC we teach coaches a tool called Designing the Team Alliance. I use it with every team I coach, and with couples too.
↑ all posts
October 2026 · trust · AI in teamsShe was rewriting her team's reports at 11 pm
Last week a manager told me she was rewriting her team's reports at 11:00 pm, and that she didn't know how to bring it up without sounding like she was against AI.
Her team had started sending each other reports that looked perfect at first glance. When she read them properly, the facts were often wrong, the context was missing, the words were generic and the recommendations were weak. And underneath all of that, she started noticing something more important: the team was losing trust in each other.
So instead of writing another AI policy, we did something different. We met in person, put a topic in the middle of the room and together called it “AI-assisted work”. Then I asked the fourteen people in the room to answer three questions by voting “with their feet”, standing closer to or further from the topic. What happened on the third question surprised everyone, including me.
Of course, AI can make us faster and more efficient. But what keeps a team together is still relationship systems intelligence.
What do you do when you receive “workslop”: work that looks polished but was clearly never thought through? Do you say something, fix it yourself, or let it go?
↑ all posts
October 2026 · presence · leadershipThe gap between what you intend and how you land
Every leader has a gap between what they intend and how they actually land.
Katie Zacharia's first White House briefing is a useful case study. Not for politics. For me it's interesting through the lens of leadership, presence and authenticity.
Here's what I noticed, looking only at impact:
- Reading for 8.5 of 14 minutes. The intent was probably “I'm prepared.” The impact was no connection with the room.
- “Amplify, multiply, expand.” Intent: loyalty. Impact: no voice of her own.
- A friendly first question. Intent: start safe. Impact: avoiding the hard ones.
- “I'll get back to you.” Intent: be careful. Impact: she disappeared, with no when, no how, no to whom.
- “My president — excuse me, my husband.” An unplanned slip, and the most authentic moment of the briefing.
The irony: the moment she came across as most real was the one she didn't plan.
None of this is about getting it wrong. We are all human, and we all create impact, whether we choose it or not. Presence is the discipline of making that impact conscious and intentional, especially under pressure, when the room is watching and the stakes are high.
A question worth sitting with: where do your intent and your impact drift apart?
↑ all posts
October 2026 · ORSC · facilitationWhat do you do when you're the facilitator, and you lose your voice?
This last ORSC course was, like so many before it, deeply insightful. I'm still contemplating what came up: what we teach, the conversations with the group, the wisdom of our Third Entity, and everything that played out along the way.
In one of our ORSC courses we guide participants through Deep Democracy. Its essence: every voice matters and deserves to be heard. We need this so much, in learning rooms, in teams, in organisations, and in the world right now. And then, at the end of day one, I lost mine. The very thing I rely on to deliver the material was cracking every second sentence. The universe put me on the spot: not just to teach the Metaskills, but to live them in front of the group.
Here's what helped me (and I'm still growing into it):
1. Fade away, physically.
I caught myself sitting on the edge of my chair, leaning into the group. That's how I usually “hold” the space, but it isn't relaxed. This time I consciously leaned back and let the conversations happen without answering every comment. My co-leader and I had designed our Third Entity together, and I knew the course isn't led by one of us. It's led by the Third Entity: the relationship we designed upfront between us. Fading away physically helped me relax mentally and truly lean into it. The real saboteur wasn't the loss of my voice. It was my controlling, limiting belief, and I am still working on letting it go.
2. Consciously choose a Metaskill that will serve the work.
I chose smoothness, relaxation and trust in the process. None of them is my go-to normally! I chose to trust that whether my voice cracked or not, the material would land. And an interesting thing happened: the moment I truly trusted that, my voice started coming back.
3. Be the Star Walker.
Star Walker is one of the ORSC front-of-room leader competencies. It means being conscious and intentional about using skills and tools, demonstrating them live to meet what's happening in the room, and then pointing to your own demonstration and discussing it openly. We sometimes call it the “unzipping moment”. Losing my voice became the most vivid demonstration I could have offered: Metaskills aren't just a theoretical concept we teach participants to use with their teams and clients. They're something we wear ourselves, especially when it's edgy and uncomfortable.
My personal insight: sometimes losing your voice is exactly how you learn where your real voice comes from.
Have you ever been forced to lead differently than you planned?
↑ all posts
October 2026 · AI in teams · ORSC“Can you please help?!”
That was the email I opened two weeks ago, with my first cup of coffee. A leader whose team I coached last year was anxious and worried about his own job: the whole AI budget for 2026 was spent, stakeholders had started asking about ROI, and apparently only three people in his team were actually using it, including him. So he asked me which facilitation tool could “fix” the situation.
From that conversation I sensed that what his team really needed first was a conversation (a facilitated one, of course). So we put one topic in the middle of the room, “USING AI”, and I asked the team three questions. People answered by where they stood.
What the team shared surprised all of us:
- using AI feels a bit like cheating
- if AI is first, where does that put me?
- why bother, if AI will replace my job anyway?
These are the questions that never show up in the investment and adoption process, but in a way they decide whether AI gets used at all.
By the end of the exercise, the team wasn't debating whether to use AI. They were agreeing on their “how”: what to delegate, what never to share, and how to keep this conversation going.
↑ all posts
September 2026 · leadership · educationWhat if we taught people skills as seriously as numbers?
What if we started teaching people how to work with people as seriously as we teach them how to work with numbers, strategy and business?
When I think about how to become a better leader, a better manager or even a better person in our own relationships, I realise how many of these essential skills I simply wasn't taught. Not at school, not during my Bachelor's or Master's, and, interestingly, not even during my own MBA in 2014 at Rotterdam School of Management:
- How to really listen.
- How to have difficult conversations.
- How to give and receive feedback.
- How to understand what is happening between people.
- How to notice the patterns we create together as a team.
These are skills we often expect people to somehow figure out along the way. That's why I'm so happy to see team coaching becoming a practical part of the MBA at RSM. Students work with a professional coach within their study teams, creating space to step back from what they are doing and explore how they are doing it together, and what kind of team they are actually creating.
I feel particularly connected to this work because I now have the privilege of contributing as a team and executive coach at RSM, the same place where I once sat on the other side of the classroom as an MBA student.
The students can start practising these skills while they are still learning. They can experiment, notice, reflect, have conversations they might otherwise avoid, and take that experience with them into their future organisations and leadership roles.
And these skills don't stay at work. They follow you into every team you join, every relationship you build, every difficult conversation you have, and every community you become part of.
A degree can open a door. But knowing how to work with people is something you carry with you for life.
↑ all posts
September 2026 · trust · feedbackYou don't have a feedback problem. You have a trust problem.
If the only time you speak to someone on your team is when something's gone wrong, you don't have a feedback problem. You have a trust problem.
Here's a frame that changed how I think about it. Treat every working relationship like a bank account. You can make deposits, and you can make withdrawals.
Constructive feedback is necessary; it's part of the job. But from a relationship standpoint, it's a withdrawal. It costs something from the account.
John Gottman's research on lasting relationships points to a “magic ratio”: roughly five positive interactions for every negative one. The same balance holds at work. For every hard conversation, you want about five genuine deposits to keep the trust healthy.
The deposits don't have to be big:
- A specific acknowledgement of something they did well
- A non-work check-in about how they're actually doing
- Noticing the effort, not just the outcome
- Asking their opinion, and actually using it
The problem I keep seeing: managers make mostly withdrawals and skip the deposits entirely. So when the necessary feedback finally comes, the account is already empty, and it lands as one more complaint instead of something that helps.
The most important part: don't wait for the withdrawal to make a deposit. Fund the account first.
And it works far beyond the office. Same skill, different room: your team, your partner, your friends.
This week, pick one person and make five small deposits before you need anything from them. Then notice what shifts.
↑ all posts