What I’m proudest of from fifteen years at MED-EL is seeing the managers of each function take responsibility for their work. The global IT organization, the first AI strategy and the ISO work are on my CV. Much of what made them possible happened in ordinary decisions: someone handling an audit, making a hire or resolving a problem without first checking what I would have done.
Getting there asked more of me than I expected. I had grown into the organization from a helpdesk seat. For years, being useful meant knowing the systems, taking the difficult ticket and being available when someone needed an answer. I was comfortable in that role. Letting other people make those calls took practice.
Giving managers room to decide
An organization of more than a hundred people across fourteen countries needed more judgment than I could personally supply. We had to agree on what each function owned, which decisions its managers could make and when a question needed my involvement.
Writing that down was only part of the work. I also had to respect it. When a manager made a sound decision that differed from the one I would have made, reversing it told everyone that the authority I had handed over was conditional on agreeing with me.
There were still decisions I needed to challenge. The distinction was between a decision that put the organization at risk and one that reflected another capable person’s judgment. I did not always make that distinction well.
The standards had to be clear enough for someone else to apply them. So did the support they could expect from me. Giving a manager responsibility in front of their team meant being prepared to back them when using it became difficult.
The appointment I waited too long to address
One of my most expensive mistakes began with appointing a strong technical specialist to lead a team. I trusted their expertise. They knew the domain and had credibility with the people doing the work, and I thought the management side would follow.
Within months, the team had slowed down. Decisions gathered at one desk, and issues I thought I had delegated kept coming back to me. I could see that the role was not working as intended, but I kept hoping that more coaching and time would help.
We eventually parted ways. I regret how long I waited. The delay made things harder for the team and for a person who was excellent at their technical work and deserved clarity sooner.
Since then, I have paid much closer attention to how a prospective manager develops other people and handles responsibility. I ask about a difficult standard they held, or a time delegation went wrong and what they did next. Technical depth still matters. It does not tell me enough about how someone will lead.
I also watch my own behavior. If I find myself repeatedly doing parts of a manager’s job, I need to address what is happening with them. Taking the work back while hoping the problem will resolve itself is unfair to both of us.
What responsibility looked like in practice
My managers owned the evidence for certification audits and faced the auditors. I provided the executive backing, dealt with investment decisions and helped resolve questions that crossed functions. Budget decisions and hiring happened within the frameworks we had agreed, and I often heard about them afterwards.
There was a stretch when I could be away for weeks without an escalation that could not wait. Things still broke. People handled them and knew which questions needed help. That gave me confidence in the organization and, more personally, in the people I had worked with for years.
I can speak to what I saw while I was there. My role ended in 2025, and I cannot claim that the organization’s later performance proves anything about my leadership. What I had seen was managers taking care of their functions with the authority we had agreed they should have.
What I carry into the work now
At SQUER, my work includes commercial leadership and helping enterprises adopt AI. The setting has changed, but I still pay attention to who will own the work after a project team has moved on. A cloud migration, an ISO program and an AI rollout each need people who can make decisions and recognize when to ask for support.
Those capabilities take time to develop. Hiring matters, as do clear expectations, difficult conversations and the room people get to exercise their judgment. I learned some of that by getting it wrong. The managers who grew into their roles are why I think the effort was worthwhile.
