Roadmap
IT Manager / Team Lead
The manager who leads a team of IT professionals. Hires, develops, directs, and retains engineers, analysts, and administrators while owning the technical strategy, budget, and service delivery for their area of responsibility.
OPTIMISTIC 5–7 years · REALISTIC 7–10 years
Stage 00
Technical Depth (Prerequisite)
IT managers must have genuine technical credibility. Teams do not respect managers who have not done the work. This requires 3–5 years of senior IC experience in the domain you will manage.
Required: Deep IC Experience in Your Domain
- You must have genuine senior-level competency in at least one IT domain and solid awareness across adjacent domains. Choose from: - Systems Administration — Windows Server, Linux, Active Directory, virtualization, cloud (see System Administrator path) - Network Engineering — routing, switching, firewalls, VPN, cloud networking (see Network Engineer path) - Software Engineering / DevOps — full-stack development, CI/CD, infrastructure as code (see DevSecOps path) - Security — security operations, AppSec, GRC, threat detection (see Security Engineer path) - Database Administration — SQL Server, PostgreSQL, Oracle, cloud databases (see DBA path) - Cloud Engineering — AWS/Azure/GCP architecture and operations
Technical Credibility as a Manager
- Why it matters: engineers will test your knowledge. If you do not know the domain, they will not respect your decisions.
- You do not need to remain the best technical person on the team. Your job is to enable the team.
- You must be able to: - Evaluate the quality of technical decisions your team makes - Understand when estimates are realistic or inflated - Identify when technical debt is being accumulated inappropriately - Participate credibly in architecture discussions - Assess whether a proposed solution is sound - Read and understand code, configurations, or design documents for review
Staying Current as a Manager
- Time split: 80% people/process/strategy, 20% staying technically current
- Reading engineering blogs, design documents, post-mortems
- Attending architecture reviews as an engaged participant
- Occasional hands-on work to stay grounded (avoid becoming a bottleneck)
- Sponsoring and learning from team's technical innovations
Stage 01
Project Management Fundamentals
IT managers direct and sponsor projects. Understanding how projects work, what PMs need, and how to be an effective project sponsor is required for management effectiveness.
Essential PM Knowledge
- Project lifecycle — initiation, planning, execution, monitoring, closing
- Scope, schedule, cost, quality, resource — the constraints PMs balance
- Critical path — understanding what is blocking delivery
- Risk management — identifying risks; expecting contingency; not confusing risk with issues
- Agile fundamentals — sprint planning, backlog, retrospectives, velocity
- Change management — how to evaluate and approve change requests
As a Manager Sponsoring Projects
- Sponsor responsibilities — provide resources; remove organizational blockers; make decisions; champion the project with leadership
- What PMs need from sponsors — clear prioritization, timely decisions, escalation support, protection from scope creep
- Reviewing project status — reading RAG status; distinguishing real risks from noise
- Going/no-go decisions — when to hold, when to proceed, when to stop a project
Stage 02
ITSM and IT Operations
IT managers own service delivery. Understanding how IT services are planned, operated, and improved is the operational backbone of IT management.
ITIL 4 Foundation — Required Knowledge
- ITIL 4 service management framework — from IT processes to a holistic service approach
- Key ITIL concepts: - Value — co-created between provider and customer - Service — a means of enabling value co-creation by facilitating outcomes customers want without risks and costs - Value streams — series of steps providing services or products - Four dimensions of service management: Organizations & People, Information & Technology, Partners & Suppliers, Value Streams & Processes
- Service Value System (SVS): - Opportunity/Demand → Service Value System → Value - Guiding principles → Governance → Service Value Chain → Practices → Continual Improvement
- Service Value Chain activities: Plan, Improve, Engage, Design & Transition, Obtain/Build, Deliver & Support
- ITIL 4 Practices (replacements for ITIL v3 processes): - Service Desk — single point of contact for users - Incident Management — restoring normal service as quickly as possible - Problem Management — eliminating root causes of incidents - Change Enablement — ensuring changes are made safely and with appropriate controls - Service Configuration Management — maintaining CMDB - Service Level Management — maintaining agreed service levels - Capacity and Performance Management — ensuring sufficient capacity to meet demand - IT Asset Management — lifecycle management of IT assets - Monitoring and Event Management — systematic observation of services and infrastructure - Release Management — planning and scheduling release activities - Deployment Management — moving new or changed software/hardware into live environments
SLA and Service Level Management
- SLA (Service Level Agreement) — agreement between IT and business defining expected service
- OLA (Operational Level Agreement) — internal agreement between IT teams
- Underpinning Contracts (UC) — external vendor commitments supporting SLAs
- Defining SLAs: - Availability — percentage uptime (e.g., 99.9% = 8.7 hours downtime per year) - Response time — how quickly incidents receive initial response - Resolution time — how quickly incidents are fully resolved - MTTR (Mean Time to Repair) — average time to restore service - MTBF (Mean Time Between Failures) — reliability measure
- SLA review and improvement — monthly service review meetings with business
ITSM Platforms
- ServiceNow — enterprise standard: - Incident Management — ticket creation, categorization, assignment, resolution - Problem Management — linking incidents to problems; root cause documentation - Change Management — CAB (Change Advisory Board) process; normal vs emergency change - CMDB — Configuration Management Database; mapping IT assets and relationships - Service Portal — self-service for common requests - Dashboards — service performance KPIs; SLA compliance reporting
- Jira Service Management — DevOps-adjacent ITSM; popular in tech companies
- Freshservice — SMB and mid-market ITSM
- Zendesk — customer support and IT support convergence
Change Advisory Board (CAB)
- Purpose — review significant changes to the production environment before implementation
- CAB participants — representatives from IT operations, security, applications, business
- Change categories: - Standard — pre-approved, low-risk, repetitive; no CAB required - Normal — scheduled; follows full change process; CAB review - Emergency — unplanned; abbreviated review; high-risk; post-implementation review required
- Change record components — description, justification, risk assessment, rollback plan, test plan, communication plan
- IT manager role in CAB — approve changes from your team; challenge weak rollback plans
Monitoring and Operations
- Monitoring platforms — Datadog, Splunk, New Relic, PagerDuty, OpsGenie
- On-call management — rotation design; escalation policies; runbook requirements
- Runbooks — documented procedures for common operational scenarios; required before on-call
- Blameless post-mortems — culture of learning from incidents; 5 Whys root cause analysis
- SRE (Site Reliability Engineering) concepts — error budgets, SLOs, SLIs. Increasingly expected of IT managers in tech organizations.
Resources
- ITIL 4 Foundation study materials (Axelos, paid)
- ITIL 4 Foundation official book (Axelos)
- ServiceNow developer instance (free)
- TryHackMe ITIL module (free)
Stage 03
People Management and Leadership
The transition from IC to manager is the biggest career shift in IT. Technical skills stop being the primary differentiator. People skills become the job.
The IC-to-Manager Transition
- What changes: - Success is now measured by team output, not personal output - You delegate work you could do yourself, and that is the right call - Your calendar fills with meetings; they are now your primary work tool - Relationships with former peers become complex; boundaries shift - You absorb organizational stress so your team can execute
- Common mistakes: - Continuing to do IC work instead of managing, becoming a bottleneck - Managing too closely (micromanagement), destroying autonomy and motivation - Avoiding difficult conversations, letting performance issues fester - Treating everyone identically — individuals have different needs and development areas - Delegating without context — "just handle it" is not delegation
1:1 Meetings — The Manager's Primary Tool
- Purpose — build relationship, surface issues, support development; not a status report
- Frequency — weekly for new reports or junior team members; biweekly for experienced, stable reports
- Structure — employee agenda first; their priorities, blockers, questions; manager adds topics second
- Key questions: - What are you working on? What's blocking you? - How are you feeling about your workload? - What would you want to do more of? Less of? - What support do you need from me? - What's going well? What's frustrating you?
- Notes and follow-through — document action items; follow up; consistency builds trust
Performance Management
- Performance development — regular feedback, not saving everything for annual review
- Goal setting — OKRs (Objectives and Key Results) or SMART goals (Specific, Measurable, Achievable, Relevant, Time-bound)
- Feedback delivery: - Positive feedback — specific, timely, connected to business impact - Constructive feedback — behavior-specific, not personality; impact-based; what to do differently - SBI model — Situation, Behavior, Impact — structured feedback framework
- Performance improvement plans (PIPs) — formal process for underperformance; goal is improvement, not exit
- Recognition and rewards — catching people doing things right; public recognition; manager-directed rewards within authority
- Annual performance reviews — calibration across team; written summaries; connected to compensation decisions
Hiring and Talent Acquisition
- Writing job descriptions — accurate and compelling; avoid requirements inflation; inclusive language
- Interview design: - Technical assessment — evaluating actual skills; avoid purely theoretical questions - Behavioral interviews — STAR format; probe for specifics; past behavior predicts future - Structured interviews — same questions to all candidates; reduces bias - Diverse panel — multiple perspectives; avoid single-interviewer decisions
- Evaluation frameworks — scorecards; skill dimensions; calibrated against what the role actually requires
- Reference checking — ask behavioral questions; "tell me about a time..." format; not just "was this person good?"
- Offer management — salary range; equity; total compensation; competing offers
- Onboarding — first 30/60/90 day plan; buddy assignment; technical onboarding checklist
Retention and Development
- Career development conversations — where do you want to be in 3 years? what skills do you want to build?
- Career ladders — defined progression criteria; transparency about what senior/staff/principal means
- Learning and development — training budget allocation; conference attendance; certification support
- Stretch assignments — expanding team members into new areas, with support rather than sink-or-swim
- Promotion process — building a business case; calibration across peers; timing
- Retention risks — identifying early signs of disengagement; competing offers; role fit mismatches
- Exit interviews — learning from departures; addressing systemic issues
Team Culture and Dynamics
- Psychological safety — team members feel safe to raise concerns, admit mistakes, propose ideas
- Inclusion — ensuring all team members can contribute; reducing in-group/out-group dynamics
- Recognition culture — celebrating wins; surfacing team contributions to leadership
- Team norms — agreed working agreements; communication expectations; meeting standards
- Handling conflict — addressing team interpersonal issues early, not letting them fester
Difficult Conversations
- Delivering negative feedback without demotivating
- Managing underperformance — addressing it early; clearly communicating expectations; documenting
- Giving feedback upward — managing your own manager; surfacing concerns constructively
- Communicating decisions the team dislikes — transparency about rationale; acknowledging disagreement
- Letting someone go — if required; handled with dignity; HR partnership; off-boarding care
Resources
- "The Manager's Path" by Camille Fournier (book, essential for engineering managers)
- "An Elegant Puzzle" by Will Larson (book, engineering leadership at scale)
- "High Output Management" by Andy Grove (book, classic)
- "Radical Candor" by Kim Scott (book, feedback framework)
- "First, Break All the Rules" by Buckingham & Coffman (book, Gallup management research)
Stage 04
Budget and Financial Management
IT managers own budget. Understanding how IT budgets work, how to build a business case, and how to defend spend decisions is required at every level of IT management.
IT Budget Types
- Operating budget (OpEx) — recurring costs: salaries, software licenses, cloud services, maintenance contracts, training
- Capital budget (CapEx) — one-time investments: hardware purchases, major software implementations, data center upgrades
- Personnel budget — headcount planning; fully-loaded cost (salary + benefits + employer taxes)
- Project budget — allocated funding for specific initiatives; tracked separately
Budget Planning Process
- Annual planning cycle — typically Q3 or Q4 for the following fiscal year
- Bottom-up budgeting — team leads submit requirements; roll up to IT management; justification required
- Top-down constraints — executive budget targets; fitting priorities within constraints
- Budget categories: - Run the business — maintaining existing operations; non-negotiable baseline - Grow the business — expanding capabilities; must be justified with business value - Transform the business — strategic initiatives; requires strong business case
- Zero-based budgeting — justify every line item from scratch; common in cost-cutting years
- Rolling forecasts — updating projections quarterly, not just annual planning
Business Case Development
- Executive summary — what you are requesting, what it costs, what the return is
- Problem statement — what is the current state and why is it insufficient?
- Options analysis — usually 3 options: do nothing, minimal investment, full investment
- ROI calculation: - Cost avoidance — how much cost is prevented (incident reduction, efficiency gains) - Revenue enablement — does this investment enable revenue growth? - Payback period — when does the cumulative benefit exceed the investment? - NPV (Net Present Value) — present value of future benefits minus cost
- Risk of not investing — what happens if we don't do this?
- Assumptions and dependencies — what must be true for this to work?
Budget Execution
- Purchase orders and procurement — following organizational procurement policies
- Invoice approval — ensuring vendor invoices match deliverables; cost center coding
- Forecast vs actuals tracking — monthly variance review; explaining deviations
- Cost optimization — right-sizing cloud resources; license audits; vendor renegotiation
- Capital expenditure tracking — asset tagging; depreciation; write-offs
Vendor Management
- Contract lifecycle — negotiation, execution, performance monitoring, renewal
- Volume discounts — leveraging organizational spend for pricing
- Vendor risk assessment — concentration risk; financial stability; security posture
- Contract renewal strategy — evaluate before renewal; multi-year commitments vs flexibility trade-off
- Shadow IT control — managing unauthorized vendor relationships that appear in budget reviews
Resources
- "Financial Intelligence for IT Professionals" materials
- Harvard Business Review finance articles (free)
- Excel financial modeling tutorials (free YouTube)
Stage 05
IT Strategy and Governance
Senior IT managers and IT directors shape technology strategy. Understanding how to translate business objectives into IT roadmaps is the senior management skill set.
IT Strategy Frameworks
- IT-business alignment — IT strategy must serve business strategy, not technology for technology's sake
- IT portfolio management — balancing Run/Grow/Transform investments
- Technology roadmap — multi-year view of technology evolution; platform retirements; new capabilities
- Digital transformation — using technology to fundamentally change business processes or models
- IT operating model — how IT is organized to deliver value; centralized vs federated vs hybrid
Governance Frameworks
- COBIT (Control Objectives for Information and Related Technologies) — framework for IT governance and management; ISACA
- IT governance vs IT management — governance = directing and evaluating; management = executing and monitoring
- IT governance structures — steering committees, IT councils, architecture review boards
- Architecture governance — enterprise architecture (Zachman, TOGAF); solution architecture review
- Security governance — security policies; risk acceptance; exception processes
Digital Transformation Leadership
- Cloud adoption and migration leadership — see IT Project Manager Stage 3
- AI and automation strategy — evaluating AI tools; governing AI use; workforce implications
- Shadow IT governance — detecting and either formalizing or blocking unauthorized technology
- Legacy modernization — managing technical debt at the portfolio level; retire vs modernize decisions
- Data governance — data ownership; data quality; master data management; privacy compliance
Communication with Leadership and Boards
- Executive communication style — concise, business-impact-focused, action-oriented
- Board-level security and technology updates — risk language; business impact; not technical jargon
- IT metrics for leadership: - Service availability — uptime percentage by service - Mean Time to Resolve (MTTR) — operational effectiveness - Project delivery rate — on-time, on-budget delivery - Security posture — vulnerability metrics, incident trends - Technology debt — aging infrastructure percentage, upgrade backlog
- Technology investment ROI — demonstrating business value from IT spend
Resources
- "The Phoenix Project" (book, IT strategy through narrative)
- Gartner research (free analyst blogs)
- MIT Sloan Management Review IT leadership articles (free)
Stage 06
Hands-On Practice & Portfolio
Path to Management
- Technical lead role — informal leadership of a sub-team or project; best management on-ramp
- Senior IC ownership — owning a domain, mentoring juniors, representing team in cross-functional meetings
- PMO analyst or program support — exposure to program/portfolio management from the inside
- Volunteer leadership — mentoring programs, community organizations, SANS Institute local chapters
What to Document on LabList
- Team management case studies — projects you led as TL, hires you made as a manager, culture initiatives
- Technical architecture contributions — design documents, architecture decisions records (ADRs)
- Budget management examples — business cases developed, cost optimizations achieved
- Team development examples — promotions championed, training programs built, mentees advanced
- Leadership narrative — the story of your IC-to-manager transition; what you learned
FAQ
Common questions
How long does it take to become an IT Manager?
5–7 years optimistic, 7–10 years realistic. The career inflection point is harder than the technical depth — most IC engineers struggle with the transition because management is a different skill set, not an extension of engineering. Most IT Managers come from senior engineer or team lead roles with demonstrated cross-functional leadership and project ownership.
Which certifications matter for IT management?
PMP for project-heavy roles. ITIL 4 Managing Professional for service management organizations. CISM for security-adjacent management. MBA for senior management positions in larger enterprises. The cert market for IT management is fragmented; the strongest signal is demonstrated leadership track record, not paper credentials.
Do I need a specific degree?
Most IT Managers hold a bachelor's, often in CS, information systems, or business. MBAs accelerate progression at larger enterprises. Self-taught senior engineers move into management routinely; the gating factor is people skills and business fluency, not credentials. BLS projects strong growth for computer and information systems managers, with median salary exceeding $169,510 (BLS 2024).
What separates a hired IT Manager?
People-management track record, not technical depth. Hiring panels look for evidence of: hiring and developing engineers, mediating conflict, navigating performance issues, advocating for resources with executives, and translating technical work into business outcomes. Technical credibility is necessary but insufficient; the IC-to-manager transition is the most significant career inflection point. Engineers who resent management work make poor managers.