In cross-functional software teams, I have led developers and worked with product owners, customer experts and decision-makers on solutions that have to work in daily use. When they see different parts of the challenge, I help them build a shared understanding, make clear decisions and leave room for specialists to own their work.
At Modified Solutions, it was my job to make sure the team had an understandable task, realistic frames and access to the right decisions. I could engage with architecture and backend, but technical ownership had to sit with the specialists. A leader does not need to be the first to answer every technical question. The leader has to make sure the questions are asked and settled.
Start with a shared understanding
When a customer describes a need, several possible solutions often emerge. Before the team can prioritise, we need to know which problem actually has to be solved, who uses the solution and what a good delivery means to them. I am happy to take the conversation with the customer and the domain experts, so the developers do not have to guess the business decisions. Conversely, the customer needs to understand what a change means for time, quality and operations.
That was clear in the work on a mobile service process for an international company. I clarified the need with the customer and led the development, while the customer's own managers made the decisions for their employees. The solution had to fit the service technician's daily work in the field and transfer information to the customer's system. It therefore required collaboration between people who did not use the same terminology and did not have the same priorities. Read the case about the mobile service process.
Clear decisions make room for expertise
I prefer to make responsibilities and decision paths clear early. Who decides the product's priorities? Who assesses the technical solution? Who takes a disagreement further if time, needs and quality pull in different directions? When that is unclear, specialists end up spending their time decoding expectations. When it is clear, they can spend it on their work.
I have led developers both up close and remotely, including in collaboration with employees in Slovakia and Thailand. Distance makes clear communication more important. It helps to agree on what is to be delivered, how we give each other feedback and when a decision has to be made together. I have also worked through a trusted partner and general manager, so responsibility could sit where the decision was best made.
To me, cross-functional leadership is also about listening. The expert who uses the system may spot a flaw in our assumptions. A developer may see a simpler path. A product owner may know about a dependency that changes the order of work. I want those perspectives on the table before we commit to a solution. After that, I take responsibility for moving us forward.
The people have to be able to work together again tomorrow
A team is more than this month's delivery. I have recruited and developed employees, held conversations about wellbeing and professional direction, and given experienced people more responsibility. We set aside time every other Friday for learning and knowledge sharing. Employees stayed with us for four to five years on average; that figure alone does not explain why, but it shows that the collaboration could last over time. See how I lead developers.
If your software team includes developers, testers, product owners and domain experts, I can contribute people leadership, technical understanding and the ability to bring different considerations into the same decision. I will first seek to understand the people, the product and the agreements that already work. From there, we can create a clearer direction together.
Contact: kontakt@tomc.dk · +45 299 297 67