2.2 - My transformation: From process-delivery to tech-led coach
Transitioning from an Individual Contributor (IC) track into engineering management is rarely a straight path. Many new managers wait for the title before changing their behavior. However, the most effective way to transition is to practice engineering management skills long before the official appointment.
This chapter breaks down the practical stages of moving from a process-driven manager to a hybrid Tech-Led Coach, demonstrating how to apply core EM frameworks to resolve delivery bottlenecks and manage mixed IC/EM responsibilities.
Phase 1: The pre-EM stage – Preemptive practice & gap analysis
Before officially moving into an EM role, the first step is conducting a thorough gap analysis. This involves researching the precise responsibilities of an EM, mapping out how it differs from an Architect or Tech Lead role, and identifying which skills are missing.
You do not need an official EM title to start acting like an EM. You can practice core management methodologies while still holding an IC title like "Software Architect".
flowchart LR
A[Research Responsibilities] --> B[Identify Skill Gaps]
B --> C[Apply EM Techniques Immediately]
When stepping into this territory without prior management experience or internal mentorship, self-education through external frameworks and internet resources becomes your primary tool. The goal during this phase is to treat your current team challenges as a laboratory for management theories.
Phase 2: Operating as a delivery EM (Archetype 3)
The most logical entry point for a technical person shifting into management is often Archetype 3: The Process & Delivery EM. This archetype becomes necessary when a team suffers from chronic delivery failures, missed stakeholder requirements, and fragmented, siloed work dynamics.
In many broken engineering organizations, Project Managers and Delivery Managers become overly reliant on technical leads to make every operational decision. When this happens, product requirements are usually fine, but a breakdown occurs across two specific variables: People and Process.
flowchart TD
A[Problem Identified: Disconnected Team + Chaotic Workflows] -->|Result| B[Blocked Delivery]
C[EM Intervention] --> D[Implement Process Optimization + Informal 1:1 Coaching]
D -.->|Resolves| A
Tactical Interventions for the Process-First EM:
-
Process Streamlining: When your formal authority does not yet allow you to make structural people decisions, focus heavily on optimization of the workflow grid (e.g., clearing task blockages, refining sprint backlogs).
-
Informal 1:1s as a Tool of Influence: Utilize unofficial 1:1 syncs to practice active listening. Even without administrative power, you can use these conversations to discover individual developer bottlenecks and use persuasion to align them with the team's delivery goals.
Operating successfully in this phase provides the foundational resume material and proof-of-concept needed to secure an official, dedicated EM role in another organization.
Phase 3: Moving to people-first and the power of connection
As you mature into a dedicated EM role, the focus naturally expands from strict process mechanics to the human element (Archetype 2: The Team Lead/People-First EM).
Through structured mentoring, career coaching, and formal 1:1s, you uncover the true leverage of an Engineering Manager in a modern organization: Cross-Functional Connectivity.
flowchart TD
C((Cross-Functional Connectivity))
H[Human-to-Human] --- C
TP[Tech-to-People] --- C
TB[Tech-to-Business] --- C
P[Product Delivery] --- C
An EM acts as a multi-directional translator, building bridges across four critical nodes:
Human-to-Human: Resolving conflicts and building psychological safety within the engineering team.
Tech-to-People: Translating complex architectural constraints into human impacts (e.g., preventing burnout caused by technical debt).
Tech-to-Business: Aligning technical capabilities with business goals to ensure predictable product delivery.
A successful application of this hybrid focus is proven when a major legacy system is stabilized, successfully delivered, and completely handed over to stakeholders after a sustained period of reliable execution.
Phase 4: Reaching the "half-half" maturity (The tech-led coach)
The ultimate evolution occurs when you are dropped into an environment that demands a "Half-Half" Split (50% IC Hands-on Coding / 50% Engineering Management). This is a common and highly challenging scenario in agile setups, especially if you have spent recent years focusing purely on high-level delivery and processes.
This is where a strong historical background as a Software Architect becomes a major competitive advantage. Returning to hands-on development requires specific re-balancing techniques:
Balancing the 50/50 Split:
Context Switching Mitigation: Avoid taking critical-path features that block the sprint if management duties pull you away. Instead, dedicate your 50% coding effort to system maintenance, code reviews, debugging legacy modules, and refactoring underlying architecture.
The Hybrid Advantage: By writing code alongside the team, you maintain high technical authority (Tech-Led EM). By running the management track, you protect their focus (People/Process EM).
This combination places you directly into the matured state of The Tech-Led Coach: you no longer use tech to control developers, nor do you use process to track them. Instead, you use your technical depth to coach them through architectural roadblocks while optimizing the system environment so they can deliver autonomously.
🎯 Self-Reflection for You
If you are transitioning tracks or managing a hybrid role right now:
-
Are you waiting for management permission to fix your team's broken workflows, or can you start applying informal EM techniques today?
-
If you are in a hybrid 50/50 role, are you accidentally blocking your team by taking on high-priority feature coding instead of focusing on system maintenance and coaching?
Balancing hands-on architecture with people leadership is an advanced skill. If you are trying to navigate a 50/50 split or looking to scale your engineering delivery, let's build your operational framework in a virtual coffee chat.