Leaders and professionals<\/p>\n
Carrying too much responsibility<\/h2>\n
You step in when work is left undone. Over time, more and more lands on your shoulders, leaving little room for your own work.<\/p>\n Many leaders and professionals will recognize this: you notice what is being left undone, step in, and make sure it gets done. That can work for a long time. Until more and more lands on your shoulders and you barely have room for your own work.<\/p>\n I experienced this myself as a project manager. People appreciated that I always found a way to get things done. But it also meant long days, stress, and the feeling that I was on my own. Just because I could pick something up did not mean it was mine to carry.<\/p>\n An important moment came when I decided to step away from an assignment. It did not solve everything, but I stopped pushing ahead at my own expense.<\/p>\n I bring that experience to my work as an independent sparring partner. When someone is carrying more and more, we explore what is happening: what belongs to their role, what they are taking on for others, and which agreements or circumstances keep that pattern going. From there, it becomes clearer what they can change themselves and what needs to be discussed within the team or organization.<\/p>\n<\/div>\n<\/details>\n<\/article>\n Teams<\/p>\n An experienced team knows what to do. Yet constant oversight, overlapping roles, and mandatory meetings leave people frustrated.<\/p>\n Challenge<\/strong> Approach<\/strong><\/p>\n Restoring trust<\/strong>: making it explicit that team members could handle their responsibilities without constant oversight.<\/p>\n<\/li>\n Clarifying roles<\/strong>: creating a clear distinction between leading, coordinating, and executing to prevent duplication and micromanagement.<\/p>\n<\/li>\n Reducing meeting load<\/strong>: replacing endless mandatory calls with short, purposeful check-ins that actually added value.<\/p>\n<\/li>\n Enhancing autonomy<\/strong>: giving people the space to take ownership, with support available only when needed.<\/p>\n<\/li>\n Facilitating open dialogue<\/strong>: creating room to express how control was experienced and how trust could be rebuilt.<\/p>\n<\/li>\n<\/ul>\n Result<\/strong><\/p>\n Team members felt heard and regained autonomy in their work.<\/p>\n<\/li>\n Meeting pressure was drastically reduced, increasing productivity.<\/p>\n<\/li>\n Trust was restored within the team, leading to a better atmosphere and stronger collaboration.<\/p>\n<\/li>\n The team lead learned that letting go produced far better results than strict control.<\/p>\n<\/li>\n<\/ul>\n<\/div>\n<\/details>\n<\/article>\n Organizations<\/p>\n Deadlines are fixed, implementation is falling behind, and trust is fading. How do you build a shared understanding of what is happening?<\/p>\n Situation<\/strong> Challenge<\/strong> An unrealistic deadline that had to be met at all costs.<\/p>\n<\/li>\n Employees being assigned to multiple projects simultaneously, leading to overload.<\/p>\n<\/li>\n Apathy across the organization after previous difficult transitions.<\/p>\n<\/li>\n Lack of structure and connection between different layers of the organization.<\/p>\n<\/li>\n<\/ul>\n Approach & Insight<\/strong> Made bottlenecks and risks concrete and transparent for the steering committee.<\/p>\n<\/li>\n Connected the voice of the business with the ambitions of management.<\/p>\n<\/li>\n Provided hands-on support where needed to create progress and restore momentum.<\/p>\n<\/li>\n Set clear boundaries when pressure and expectations became unrealistic.<\/p>\n<\/li>\n<\/ul>\n Result & Lessons<\/strong><\/p>\n There was appreciation for the openness and the way complexity was made transparent.<\/p>\n<\/li>\n Both successes and problems could be addressed openly, creating more realism.<\/p>\n<\/li>\n For myself, this was a turning point: my strength lies in bringing clarity and connection, not in pushing or pulling. This led to the insight that my role is better suited as an independent advisor and sparring partner, rather than as a classic project manager.<\/p>\n<\/li>\n<\/ul>\n<\/div>\n<\/details>\n<\/article>\n HR and culture<\/p>\n A development plan is meant to support progress. But what happens when employees experience mainly tension and judgment?<\/p>\n A small consultancy used development plans and annual performance reviews. In practice, these conversations caused employees anxiety. They often centered on judgments about one another, while employees felt there was little room to discuss what they needed to do their work well.<\/p>\n What this experience taught me<\/strong><\/p>\n A development plan or performance review can be valuable. But a format alone does not make a conversation useful. It matters whether people understand how they are being assessed, whether expectations have been made explicit, and whether there is room to ask questions or disagree.<\/p>\n That is why I look at both the conversation and the conditions around it. What is the process meant to achieve? What actually happens in practice? And what needs to change to make the conversation useful again for both the employee and the organization?<\/p>\n<\/div>\n<\/details>\n<\/article>\n<\/div>\nRead the full story<\/summary>\n
When control replaces trust<\/h2>\n
Read the full story<\/summary>\n
A skilled and experienced team found itself stuck. Team members knew their work well, but were constantly slowed down by mandatory calls, overlapping roles (a team lead and an additional coordinator), and continuous monitoring. The coordinator often listened in on conversations and hovered over colleagues\u2019 shoulders. For the team, this felt like a lack of trust, creating nervousness, frustration, and a loss of motivation. The team lead perceived the setup as efficient, tasks seemed to be taken out of their hands, but in reality, it drained the team\u2019s energy and reduced their sense of ownership.<\/p>\n\n
\n
An ERP transformation at a standstill<\/h2>\n
Read the full story<\/summary>\n
A large organization was in the midst of an extensive ERP transformation project. Deadlines were tightly set, but implementation was falling behind. Pressure from senior management was increasing, while the business was beginning to lose confidence in the project.<\/p>\n
The project risked stalling due to:<\/p>\n\n
With a pragmatic and collaborative approach, I brought clarity to the situation:<\/p>\n\n
\n
When development conversations create tension<\/h2>\n
Read the full story<\/summary>\n