How Enetpulse Prepared Senior Developers to Become Team Leads?
The transition from senior developer to team lead is not just a promotion. It is a shift in identity, value creation, communication, and responsibility.
This philosophy guided our partnership with Enetpulse, one of Europe's leading sports data providers. Over the course of three months, CoTransition designed and delivered a leadership development program for experienced developers preparing to step into team lead roles. But before a single training session was delivered, we invested in understanding what these aspiring leaders actually needed - not what a generic curriculum would assume.
The deeper question was: what would make leadership a meaningful, clear, and realistic next step for them?
CoTransition partnered with Enetpulse to design and deliver a three-month leadership development journey for senior developers preparing to step into team lead roles. Instead of starting with a predefined curriculum, we began with a Discovery Sprint — interviewing current team leads, aspiring leaders, and senior management to understand the real motivators, blockers, expectations, and skill gaps around the role.
The result was a tailored leadership program combining structured group sessions, leadership assessment, individual coaching, practical templates, homework assignments, and digital learning resources. The goal was not simply to teach leadership concepts, but to help participants build the confidence, mindset, and practical capability to lead teams in Enetpulse’s real operating context.
The Background
Enetpulse is a Danish-headquartered technology company specializing in live sports data collection, analysis, and distribution. For over 25 years, the company has served more than 200 clients across sports media, broadcasting, and iGaming, delivering real-time scores and statistics from over 100 sports worldwide. With development teams operating from Sofia and across Europe, Enetpulse runs a fast-paced, cross-functional engineering organization where projects are cross-team dependent and priorities shift daily.
As the company continued to grow and evolve, leadership recognized a critical challenge: the next generation of team leaders needed to come from within. Several senior developers had the technical expertise, the organizational knowledge, and the respect of their peers. What they had to build however was a structured path to develop the leadership capabilities required for the role, and, in some cases, a clear reason to want it.
Enetpulse approached CoTransition with a thoughtful premise: before building a leadership development program, they wanted to understand what would motivate experienced developers to step into leadership, and what would make the transition compelling.
Challenge Identification: The Discovery Sprint
Rather than starting with a predefined curriculum, we began with a Design Sprint inspired discovery phase. The goal was to create a clear, evidence-based picture of the motivators, blockers, and perceptions surrounding the team lead role at Enetpulse, and to ensure the resulting program would resonate with the people it was designed for.
We assembled a cross-functional squad and conducted structured interviews and focus groups with distinct stakeholder groups: current team leads, aspiring leaders, and senior management. This multi-perspective approach was deliberate as it allowed us to map the gaps between what the organization believed was important and what employees actually experienced.
What Current Team Leads Told Us
The existing team leads provided the most grounded view of the role. They described a daily reality that was far more complex than any job description suggested. Communication was the constant - not just with their own team, but across teams, with project managers, clients, and upper management. Each audience required a different language, a different level of detail, a different approach.
They spoke candidly about the emotional weight of the role: carrying responsibility for others' performance, delivering feedback, navigating tensions that weren't always theirs to own. Several described learning the role through a "sink or swim" approach picking up leadership skills on the job without formal training or mentorship.
Delegation emerged as a persistent challenge. Not always the mechanics of assigning tasks, but the psychological difficulty of letting go and trusting someone else to deliver work you know you could do yourself, and accepting that their approach might be different from yours.
What Aspiring Leaders Told Us
The aspiring leaders (the program's eventual participants) were candid about both their interest in and their hesitation about the role. On the positive side, they were drawn to the bigger picture: understanding the business beyond code, influencing product decisions, having a voice that carries more weight, and the intellectual variety of a role that changes every day.
But the barriers were equally real. The most commonly cited fear was losing technical depth and the worry that stepping into leadership would mean trading the craft they had spent years mastering for meetings, bureaucracy, and administrative overhead. Several participants described watching current team leads move from meeting to meeting with little time for focused work, and questioned whether that was a future they wanted.
Cognitive overload was a major concern. The role demanded constant context switching from sprint planning to performance reviews, from technical debugging to stakeholder communication, and participants wondered how to manage that without burning out.
A striking theme was the question of authority. Participants wanted to know: would they have real decision-making power, or would the title come with more responsibility but no additional influence? The distinction between being a leader and being a messenger was important to them.
The most commonly cited skill gaps were delegation, presenting to upper management, navigating difficult conversations, and translating technical information for non-technical audiences.
How the Discovery Sprint Shaped the Curriculum
Gathering insights was only the beginning. The real value of the Discovery Sprint was in what we did with them and how we involved the organization in turning raw data into a program they would own.
We began with a synthesis of all interviews, clustering the findings into themes: skill gaps, perception mismatches, structural blockers, and motivational drivers. This step made the patterns visible.
From this synthesis, we elaborated a point of view: a clear articulation of what the transition from individual contributor to team leader actually requires at Enetpulse in this specific organizational context, with these specific teams, projects, and dynamics. This point of view became the compass for everything that followed. It named the real challenges rather than the assumed ones, and it framed the program not as a set of training topics but as a leadership journey designed around capability building.
Next, we ran a collaborative design workshop with a cross-functional team from the organization including HR, management, and representatives close to the aspiring leaders. Together, we defined the outcomes the program needed to deliver. This was not about selecting topics from a catalog. It was about agreeing on what participants should be able to do differently after the program, and what the organization needed to change to support them. The workshop ensured alignment between management expectations and the realistic development trajectory of the participants.
With outcomes defined, we prototyped the program structure: the sessions, each building on the previous one, with a deliberate arc from self-awareness (leadership identity) through team capabilities (trust, communication, delegation) to organizational impact (project delivery, change management). We mapped the assessment, coaching, and homework components into the design so that learning would be reinforced across multiple channels, not confined to the classroom.
The final step was validation. We presented the prototype to the aspiring leaders themselves, collected structured feedback, and refined the design based on their input. This was a deliberate change management decision. When participants see that a program was built from their own words, addresses their actual concerns, and incorporates their feedback on the design, adoption is no longer something you have to manufacture as it is already built in.
They do not show up as passive recipients of training. They show up as co-owners of their own development.
This entire process was as much about change management and personalization as it was about relevance. A curriculum can be relevant and still fail if people do not feel it was built for them. The Discovery Sprint ensured that the program was not just tailored to the right topics, but positioned in a way that participants trusted, management supported, and the organization could sustain beyond the final session.
Methodology and Approach
Based on the discovery findings, we designed a leadership development program delivered over three months, structured around six capability pillars that built progressively on each other.
Our Journey Framework:
Establishing leadership identity and differentiating between management and leadership
Building the conditions for team performance and growth
Developing communication effectiveness across all levels of the organization
Strengthening personal effectiveness, emotional awareness, delegation and time management
Equipping leaders with practical project delivery skills
Leading change and building consensus for organizational improvement
Program Components:
The program was designed as an integrated learning system, not a series of standalone workshops. Each component reinforced the others:
Leadership Assessment. Each participant completed a leadership self-assessment at the start of the program, creating a personalized development baseline. This provided clarity on individual strengths and areas for growth and became the starting point for personal development planning.
Interactive Group Sessions. Delivered every two weeks, each session combined conceptual frameworks with hands-on exercises, role-playing, and real-world case studies drawn directly from Enetpulse's context. Small group sizes ensured high engagement and the ability to personalize the experience.
Practical Templates and Tools. Every session came with ready-to-use templates : feedback conversations, delegation frameworks, team agreements, stakeholder mapping, change proposals, and more. These were designed for immediate application, not shelf storage.
Homework Assignments. Between sessions, participants applied what they had learned in their actual work environment. This created a continuous learning loop: learn a concept, apply it during the week, surface obstacles, and discuss them in the next session.
Individual Coaching. One-on-one coaching sessions were offered throughout the program. These provided a safe space for participants to discuss personal challenges, work through assessment results, address career questions, and build personalized development plans with concrete next steps.
Digital Learning Resources. A dedicated online platform gave participants access to supplementary materials, frameworks, and resources between sessions — extending the learning beyond the classroom.
The Learning Journey
The program unfolded over three months, with each session building on the foundations laid in the previous one.
The Role of the Leader
We started where every leadership journey should start - with identity. Participants explored the fundamental difference between managing tasks and leading people, and why the transition from individual contributor to team leader requires a genuine mindset shift, not just new responsibilities.
Using transformational leadership as the framework, participants examined how leaders create vision, build influence, and develop others. Each participant completed their leadership self-assessment and drafted initial personal development goals. This session surfaced a critical insight that many participants carried: the belief that leadership means having all the answers. Reframing leadership as enabling others to find answers was, for several participants, the most important shift of the entire program.
Growing the Team
This session moved from leading yourself to leading others. We focused on what it actually takes to build a team that performs - not by directing every outcome, but by creating the conditions where people can do their best work.
The topics included building trust as a deliberate practice, creating team agreements that set clear expectations, empowering team members to take ownership, and managing conflict constructively rather than avoiding it. Participants worked through scenarios drawn from their own team dynamics - including the particularly challenging situation of leading people who were recently your peers.
Effective Communication
Communication had been the single most frequently mentioned skill across all discovery interviews from current leads, aspiring leads, and management alike. This session addressed it head-on.
We explored how information flows (and fails to flow) across an organization, the structural and psychological barriers to effective communication, and the discipline of active listening. The most practically impactful segment was on giving and receiving feedback, moving it from something reserved for annual performance reviews to a regular, embedded team practice.
Participants practiced adapting their communication for different audiences: delivering a technical update to the team versus presenting progress to senior management versus having a difficult one-on-one conversation. This audience-adaptation skill was one of the most requested topics from the discovery interviews.
Personal Effectiveness
This session addressed the internal dimension of leadership. We covered motivation - both understanding what drives you and how to create conditions where others stay motivated. We worked on emotional awareness and regulation, giving participants practical techniques for managing their responses under pressure.
Delegation received significant attention here. The discovery interviews had revealed that delegation was not primarily a procedural problem, it was an emotional one. Letting go of hands-on work felt like losing identity, competence, and control. We worked through delegation frameworks that addressed both the what (what to delegate and to whom) and the how (how to let go without losing quality or oversight).
Time management was reframed as leadership prioritization, learning to allocate time and energy toward high-leverage activities like team development, strategic thinking, and coaching, rather than remaining trapped in reactive firefighting.
Managing work
This session brought leadership skills into the delivery context. Participants worked through how to initiate a project when information is incomplete, how to identify and manage stakeholders with competing interests, and how to surface risks early rather than reacting to them late.
We focused on agile execution discipline: running sprints that maintain their integrity, managing scope changes without losing momentum, and turning estimation from guesswork into structured conversations. These were not abstract frameworks - they were practiced using real project scenarios from Enetpulse's portfolio.
Change Management
The final session built on everything that came before. Leading change requires every capability developed across the program — clear communication, team trust, emotional regulation, stakeholder management, and personal conviction.
We explored how to lead change rather than merely respond to it — understanding the human reactions to new ideas, working with resistance instead of against it, and building consensus across teams. Participants practiced framing constructive proposals for organizational improvement and developed personal toolkits for initiating and sustaining change.
This session also served as a capstone — an opportunity for participants to reflect on their growth across the program, revisit their initial development goals, and chart the next phase of their leadership journey.
The Coaching Sessions
In the safety of a private conversation, participants raised concerns they were not comfortable sharing in a group setting - career plans or uncertainty, interpersonal friction with specific situation, doubts about whether leadership was the right path for them, and the challenge of leading people who had more seniority or experience.
For one participant, the primary challenge was delegation - not as a time management technique, but as an act of trust. Together, we worked on building a practice of gradually releasing control while creating development opportunities for team members.
Another participant was navigating the tension between individual contribution and team leadership. The coaching sessions helped reframe this not as a loss of technical identity, but as an expansion of impact from personal output to team and org level influence.
Several participants used the coaching sessions to process assessment results and translate them into actionable plans. The combination of a structured assessments, group learning, and individual coaching created a reinforcing cycle that accelerated development in ways that any single approach could not achieve alone.
Lessons Learned
Our experience with the Enetpulse leadership program reinforced several principles about effective leadership development in technology organizations.
Discovery before design. Interview data revealed that the real training needs diverge significantly from what job descriptions suggest. Formal role requirements focus on project management and technical oversight. The actual day-to-day struggles are about delegation, difficult feedback, cognitive overload, and navigating organizational dynamics.
Address identity. The most difficult aspect for many participants was not learning new skills but reimagining their professional identity. Moving from "expert who does the work" to "leader who enables others" requires confronting deeply held beliefs about what makes someone valuable. Without addressing mindset alongside skillset, the technical skills alone would not create lasting change.
Communication is the greatest multiplier. While many leadership competencies matter, communication skills proved to be the single greatest multiplier of effectiveness. Leaders who could articulate a vision, provide clear feedback, adapt their message to different audiences, and hold difficult conversations created noticeably higher team performance.
Useful “homework“ Applying concepts in the actual work environment within the same week made the learning concrete, surfaced real obstacles, and provided rich material for discussion in follow-up sessions. This continuous loop of learn-apply-reflect-refine was more effective than any amount of classroom time alone.
Group and individual learning create different — and complementary — value. Group workshops established common frameworks, shared language, and peer connections. But the one-on-one coaching sessions were where the most personal breakthroughs occurred. Leaders need a safe space to explore challenges that are too specific, too sensitive, or too personal for a group setting. The combination is more powerful than either approach alone.
Building on each session matters. Because each session built on the previous one -with templates that accumulated, concepts that layered, and homework that connected back and participants experienced the program as a coherent journey rather than a collection of topics. By session six, participants were integrating capabilities from all previous sessions into their change management proposals, demonstrating genuine skill development rather than isolated learning.
Conclusion
The Enetpulse program reinforced one of our core beliefs: leadership development works best when it starts with the real work, real people, and real organizational context.
Generic leadership training can introduce useful concepts. But when a company wants to build a leadership pipeline, the challenge is deeper. Future leaders need to understand the role, want the role, see themselves in the role, and develop the practical capabilities to perform it.
By starting with discovery, involving the organization in the design, combining group learning with coaching, and connecting every session to real work, Enetpulse created more than a training program. It created a structured pathway for senior developers to begin becoming leaders.
For technology companies, this is the real opportunity: not just filling team lead positions, but building a leadership culture from within.
CoTransition helps technology companies turn strong individual contributors into capable leaders through discovery-led leadership development programs that combine training, coaching, practical tools, and real-work application.
If your organization is preparing senior specialists to step into leadership roles, CoTransition can help you design a leadership development journey based on your real context - not a generic curriculum.