I have led developers directly and through a day-to-day manager. At Modified Solutions, I gave specialists ownership of technical decisions, discussed growth and wellbeing with them, and made sure customer needs were clarified. My aim was a team where skilled people could grow and deliver good work over time.
Leading developers with ownership and support
I agree with the developer what the work needs to achieve. They make the technical decisions. If two tasks are urgent or the customer still needs to make a decision, I help sort that out.
Written recommendations from three employees give a more personal insight. Kirsten describes trust and freedom with responsibility. Sureewan talks about accessibility, clear explanations and me taking the customer dialogue when something goes wrong. Kristián describes clear quality expectations and room to grow as a developer, including when working remotely. I would rather let their own words stand as evidence than declare myself a particular kind of leader.
Learning and retention
We set aside every other Friday for learning and knowledge sharing. When the capacity we had reserved for unforeseen tasks was not used, it could also go towards upskilling. It was a concrete choice to give developers time to get better. Employees stayed four to five years on average, and several stayed considerably longer. That figure alone cannot prove why people stayed, but it shows that our collaboration worked over time.
The manager's role with customers
When a customer reports a fault, I first find out what happened. If the problem is on our side, I speak to the customer so the developers can concentrate on fixing it.
Contact: kontakt@tomc.dk · +45 299 297 67