IT Lead & Tech Manager Training That Fuses Human Leadership, Engineering Discipline, and Risk Governance
A modern tech manager carries three loads at once: delivery rhythm (DORA), system health (SRE / error budget), and security governance (DevSecOps, NIST CSF 2.0). The Neksus 10–14 week program builds integrated competencies for IT Leads, Engineering Managers, and Heads of Engineering across enterprise, banking, BUMN, and tech-enabled organizations.
- Target audience
- Tech Lead · Engineering Manager · IT Lead · Head of EngineeringTarget audience
- Typical duration
- 10–14 weeks (cohort)Typical duration
- Core focus
- DORA · SRE · DevSecOps · ITIL 4 · LeadershipCore focus
- Format
- Hybrid: workshop, lab, peer-coachingFormat
The Neksus IT Lead / Tech Manager program builds five foundations: context-driven engineering team leadership, delivery rhythm using the four DORA metrics (Forsgren-Humble-Kim Accelerate), Google SRE reliability discipline with SLO/SLI/error budget, a DevSecOps security posture aligned to NIST CSF 2.0, and ITIL 4 service governance. Delivered as a 10–14 week cohort with workshops, hands-on lab in the client's stack, and weekly peer-coaching.
Why the modern IT Lead carries a different load from the waterfall era
The Engineering Manager and IT Lead roles in Indonesian enterprises have shifted sharply since cloud and microservices adoption. Accelerate research (Forsgren, Humble, Kim) shows high-performing engineering organizations ship 208x more frequently with 106x shorter lead times and 2604x faster recovery than low-performing peers. The distinguishing factor is measured cultural-technical discipline; team size becomes secondary. A modern IT Lead owns the four DORA metrics (deployment frequency, lead time, change failure rate, MTTR), the team's error budget, the DevSecOps security posture, and ITIL 4 service governance — while still leading humans. The Neksus program integrates all five domains in a single cohort, with hands-on lab on the client's stack and practice on real team KPIs.
- Accelerate (Forsgren-Humble-Kim) proves the four DORA metrics correlate directly with business performance and engineer satisfaction
- Google SRE introduced the error budget — a measured failure allowance that balances delivery against reliability
- NIST Cybersecurity Framework 2.0 (February 2024) adds a Govern function alongside Identify-Protect-Detect-Respond-Recover
- ISO/IEC 20000-1:2018 and the ITIL 4 Service Value System are the reference frames for IT service governance in enterprise and BUMN contexts
- OWASP Top 10 (2021 release) is the application security literacy baseline for every engineering team
The strongest senior engineer is often promoted to Engineering Manager with zero framework for the new role. The result: micro-management of code, 1-on-1s collapsing into code review, and engineers leaving within 6–12 months. The Stack Overflow Developer Survey 2024 lists 'bad management' as the #2 driver of engineer churn across Southeast Asia.
Neksus modules integrate Accelerate (DORA), the Google SRE Book (SLO/SLI/error budget), NIST CSF 2.0, OWASP Top 10 2021, the ITIL 4 Service Value System, COBIT 2019 (for BUMN/banking audit context), and SAFe / Scrum at Scale for multi-team contexts. Leadership practice follows The Manager's Path (Camille Fournier) and An Elegant Puzzle (Will Larson).
DORA metrics, SLO compliance, and MTTR can be tracked weekly. A Tech Manager who leads without a numeric baseline leads by intuition alone. The Neksus program begins with instrumenting a 30-day baseline of the four DORA metrics on the client's stack.
CIOs and CTOs in Indonesia are now fluent in Accelerate and SRE frameworks. A Tech Manager fluent in DORA, error budget, and NIST CSF 2.0 speaks on the same wavelength as their technology directors.
The TNA pattern we most often find in IT Leads / Tech Managers
These patterns emerge consistently from initial Neksus diagnostics across banking, BUMN, manufacturing, and tech-enabled enterprises.
Symptom: The engineering team ships without measuring deployment frequency, lead time, change failure rate, or MTTR. Performance discussions run on intuition.
Business impact: The board doubts the ROI of engineering investment; engineers lose the compass for continuous improvement.
Symptom: Reliability requests and delivery requests are treated as permanent conflict. Every incident is handled reactively with no error budget frame.
Business impact: The team oscillates between over-engineering and extreme tech debt; the CIO struggles to prioritize the roadmap.
Symptom: Security review happens post-development; OWASP Top 10 is no part of standard checklists; threat modeling is missing from the backlog.
Business impact: Vulnerabilities surface during external audit; releases slip due to late-stage fixes; remediation cost runs 10–100x higher.
Symptom: A newly promoted Tech Lead still dominates every technical decision; engineers receive no room to grow.
Business impact: Senior engineers fail to progress; the team becomes single-point-of-failure dependent; psychological safety stays low.
Symptom: Incident management runs without runbooks; change management is ad-hoc; problem management is missing. ITIL 4 or ISO/IEC 20000-1 has yet to map onto daily practice.
Business impact: IT audits (BPK / external KAP / regulator) produce many findings; internal service SLAs are hard to meet.
Symptom: Backlog grooming is ad-hoc; sprint review becomes a formality; retros are absent or yield action items with no follow-through.
Business impact: The team runs without rhythm; the learning loop fails to form; continuous improvement stalls.
Pain points IT Leads / Tech Managers feel on the ground
Root: The board sees output as the count of features per quarter, with zero visibility into lead time or change failure rate.
Program response: The 'DORA Storytelling for the Boardroom' module turns the four metrics into a narrative CFOs and CEOs understand, using a 30-day baseline from the client's stack as evidence.
Root: There is no blameless post-mortem ritual; SLO / error budget remain undefined, so every incident feels like a personal failure.
Program response: The 'Blameless Post-Mortem + Error Budget' module installs the Google SRE ritual: 5-why, contributing factors, action items with owner and due date.
Root: Security review happens after PR readiness; engineering feels security throttles delivery.
Program response: The 'Shift-Left DevSecOps' module embeds threat modeling into sprint planning, SAST/DAST in CI, a security champion per team, and OWASP Top 10 as a code-review checklist.
Root: Daily practice has yet to map to ITIL 4 / ISO/IEC 20000-1 / COBIT 2019; documentation is thin.
Program response: The 'Audit-Ready Engineering Org' module maps practice to ITIL 4 and COBIT 2019 controls and provides runbook, change log, and evidence trail templates.
Root: There is no technical career ladder (IC track) alongside the management track; the only path up is becoming a manager.
Program response: The 'Engineering Career Ladder Design' module installs a dual-track IC ladder (Senior → Staff → Principal → Distinguished) plus a Manager ladder (EM → Director → VP) based on Patterson and Camille Fournier.
Root: Migration runs team-by-team with no landing zone, tagging policy, or FinOps discipline.
Program response: The 'Cloud Governance & FinOps Foundations' module installs landing zone, tagging convention, cost allocation, and RACI with the Infra and Finance teams.
The IT Lead / Tech Manager capability ladder — first 14 months
Each stage lists the core competencies and the KPI signal that the next stage is ready to enter.
- Internalize the shift from hands-on engineer to leader of engineers
- Map the stakeholder graph: Product, Security, Infra, Finance, Compliance
- Establish weekly 1-on-1 with every engineer (GROW + technical mentoring split)
- Instrument a DORA metrics baseline on the client's stack (deployment frequency, lead time, CFR, MTTR)
- Define SLO/SLI for 2–3 critical team services
- Apply an error budget policy with a board-agreed 'freeze release' trigger
- Embed threat modeling into routine sprint planning
- Implement SAST/DAST in CI; OWASP Top 10 as a code-review checklist
- Run a blameless post-mortem ritual for every P0/P1 incident
- Map daily practice onto the ITIL 4 Service Value System
- Author standard runbooks for the top 10 incident types
- Stand up a lightweight change advisory board (CAB) for high-risk changes
- Integrate governance with COBIT 2019 controls for BUMN/banking audit context
- Lead audit response (BPK / KAP / regulator) with an evidence trail prepared
- Design a dual-track engineering career ladder (IC + Manager)
- Build the engineering operating cadence: quarterly planning, monthly review, weekly sync, bi-weekly retro
- Cultivate engineering brand: tech blog, open-source contribution policy, hiring playbook
- Prepare a successor (manager-once-removed thinking)
KPIs that should shift while this program runs
Pick 3–5 KPIs from the list before the program starts so impact is measured with numbers, with anecdote kept as a supporting layer.
The most sensitive indicator of CI/CD pipeline health and trunk-based development discipline.
Measures speed from idea to production; correlates directly with business responsiveness.
Validates the quality of test automation and code review discipline.
Measures observability maturity, incident response, and runbook discipline.
Provides an error budget that funds aggressive delivery.
The direct manager is the #1 factor in engineer retention (Stack Overflow Developer Survey 2024).
Evidence of DevSecOps maturity and NIST CSF 2.0 Detect-function posture.
Three-day intensive vs 10–14 week cohort vs embedded coaching
Three intervention shapes with distinct ROI profiles. The 10–14 week cohort is the Neksus default recommendation for Engineering Managers and IT Leads.
| Criterion | Three-day workshop | 10–14 week cohort ★ | Embedded coaching |
|---|---|---|---|
| Investment per participant | IDR 6–10 million | IDR 18–35 million | IDR 60–120 million |
| DORA baseline instrumentation on client stack | None | Yes — 30-day real baseline | Yes — 90-day deep instrumentation |
| Scalability to 15+ engineering managers | High — parallel cohorts | High in cohort format | Low — limited by senior coach capacity |
| Practice on real incidents + audit | None | Yes — assignments + live blameless post-mortem | Yes — on every P0/P1 incident during engagement |
| Best fit | DORA / NIST CSF awareness for the board | Default for Engineering Managers and IT Leads | Heads of Engineering / VP Eng transitioning to a C-level role |
The 10–14 week engagement flow — from kickoff to sustaining
- 1
Diagnostic and technical assessment
Week 0Online pre-assessment (DORA self-assessment, NIST CSF 2.0 maturity questionnaire, ITIL 4 readiness check) plus 1:1 interview with every participant plus a walkthrough of the client engineering stack. Output: DORA baseline + team capability heatmap.
- 2
Three-day onsite kickoff workshop
Weeks 1–2Day 1: Engineering Manager role identity + DORA framework + storytelling for the boardroom. Day 2: SRE foundation (SLO/SLI/error budget) + blameless post-mortem. Day 3: shift-left DevSecOps + OWASP Top 10 + threat modeling. Assignment: each participant drafts a 90-day plan.
- 3
DORA baseline instrumentation lab
Weeks 2–4The Neksus team plus client tech leads instrument the four DORA metrics on the client pipeline (GitHub/GitLab + CI/CD tooling). The 30-day baseline dashboard is signed off before moving into the SRE module.
- 4
Thematic live workshops (bi-weekly, 3 hours)
Weeks 3–12Rolling topics: SLO Workshop (defining SLO for 2–3 critical services), Error Budget Policy, Practical Threat Modeling, ITIL 4 mapping, COBIT 2019 audit readiness, Engineering Career Ladder Design. Each session ends with a two-week practice assignment.
- 5
Peer-coaching pods (four managers per pod)
Weeks 3–13Weekly 60-minute sessions between participants with a peer-coaching frame (problem framing, GROW peer-questioning, accountability check). A Neksus coach facilitates the first three sessions remotely; the pod runs self-managed afterwards.
- 6
Mid-program check-in with CIO / CTO
Week 7Participants plus CIO/CTO plus a Neksus coach in a 60-minute session. Review the 90-day plan, DORA baseline, SLO definitions, and calibrate delivery-vs-reliability expectations.
- 7
Capstone presentation — engineering org transformation
Week 13Each participant presents: DORA baseline → 90-day target, one incident handled via blameless post-mortem, one running SLO, one vulnerability closed through shift-left DevSecOps, and the career ladder plan for the team.
- 8
Sustaining: quarterly clinic + audit-readiness review
Week 14 → 12 monthsA 90-minute quarterly clinic with a Neksus coach to work through live cases (DORA regression, major incident, upcoming audit). Access to the Engineering Manager Indonesia alumni network.
Decision-makers in an engineering leadership program
Five stakeholder rings that must align before the program succeeds.
Justifies engineering investment ROI, connects the program to the corporate technology roadmap, and secures audit-readiness.
Cross-team consistency of engineering practice, dual-track career ladder standards, and Tech Lead → Engineering Manager succession readiness.
DevSecOps posture, NIST CSF 2.0 / ISO 27001 compliance, and security champion integration per engineering team.
Operational logistics, Kirkpatrick evaluation, LMS integration, and reporting up to the CHRO.
Mapping engineering practice to ITIL 4, COBIT 2019, and ISO/IEC 20000-1:2018 controls.
Vendor scoring, contracting, e-procurement (BUMN/government via SPSE LKPP) for multi-cohort engagement.
Design notes — why we built it this way
- Hybrid format (live + lab + async)50% live cohort, 30% lab instrumentation on the client stack, 20% async assignmentEngineering leadership demands practice on a real stack. Theory workshops without a lab create awareness that evaporates within 30 days.
- Cohort size8–14 Engineering Managers / IT Leads per cohortSmall enough for deep 1:1 role-play, large enough for cross-domain diversity (microservices, legacy monolith, data platform).
- Total duration10–14 weeks (SRE + DevSecOps + ITIL 4 modules need repeated practice)Kirkpatrick L3 research shows meaningful impact emerges after at least 8 weeks of practice with feedback; engineering leadership adds extra latency for natural incident cycles to surface.
- Facilitator profileFacilitators with at least 12 years of field engineering leadership experience plus one credential of ICF ACC/PCC, AWS/GCP/Azure Professional, ITIL 4 Managing Professional, or CISSPField experience earns credibility; the vendor credential enforces methodological discipline.
- Language of deliveryBilingual ID/EN — engineering jargon stays in English (DORA, SLO, error budget, blameless post-mortem); contextual discussion in Bahasa IndonesiaIndonesian engineers speak mixed-language daily; forcing every term into Indonesian adds friction. Leadership discussion runs deeper in the mother tongue.
- Effectiveness measurementKirkpatrick L1 (satisfaction) + L2 (competency) + L3 (behavior, 3 months post) + L4 (DORA + SLO + engineer churn, 6 months post)L4 for engineering leadership is clearly measurable via DORA and SLO compliance; an engineering leadership program has no excuse to stop at L2.
Neksus topics most often paired with an IT Lead / Tech Manager program
Cloud Foundation (AWS / Azure / GCP Essentials)
Tech Managers need the same cloud literacy as their team. The cloud foundation module accelerates cloud-native onboarding for Engineering Managers with an on-premise background.
Kubernetes & Container Orchestration for Engineering Teams
Containers and Kubernetes are the new deployment standard. This module gives Engineering Managers the depth to discuss capacity, cost, and reliability with the platform team.
DevSecOps Foundations for Corporate Engineering Teams
The flagship DevSecOps module for Engineering Managers — threat modeling, SAST/DAST CI integration, OWASP Top 10 as a code-review checklist, security champion per team.
Employee Cybersecurity Awareness
Tech Managers lead security awareness within engineering. This module supports onboarding security awareness for new engineers.
Agile & Scrum for Product Teams
DORA delivery rhythm cannot be separated from product rhythm. The Agile/Scrum module for Engineering Managers reinforces prioritization discussions with the Product Manager.
Typical outcome patterns from comparable clients
A top-10 national Sharia bank, 12 Engineering Managers from mobile banking, core banking, and the data platform, targeting better OJK audit outcomes on change management practice.
A 12-week cohort with emphasis on ITIL 4 + COBIT 2019 audit readiness. DORA instrumentation lab on the mobile banking pipeline. Thematic DevSecOps workshop with the CISO as co-facilitator. Mid-program check-in with the CTO.
The next OJK audit showed change-management findings dropping significantly. Mobile banking lead time moved from 5 days to 1.5 days within 4 months post-program. Three Engineering Managers presented the new practice at a national CIO Bank forum.
A large telecommunications BUMN, 18 IT Leads from network operations, BSS, and OSS units, targeting team readiness for a cloud-native transformation.
A 14-week hybrid cohort. Cloud governance + landing zone design lab. SRE workshop with SLO definitions for 3 critical customer-facing services. Coaching paired with the Head of Cloud as mentor.
SLO compliance across three critical services stabilized at 99.95% after 5 months. MTTR fell 60% (from 4 hours to 90 minutes on average). Four of the 18 IT Leads moved into Engineering Manager positions within 12 months.
A tech-enabled FMCG enterprise (digital commerce + supply chain platform), 10 Engineering Managers from various product teams, targeting unified engineering practice after acquisition.
A 10-week cohort focused on DORA and engineering career ladder design. Embedded peer-coaching pods. Thematic workshops on blameless post-mortem and engineering brand.
The four DORA metrics across teams converged into a single enterprise dashboard within 8 weeks. Engineer churn fell from 22% annualized to 11% within 12 months post-program. The dual-track career ladder was adopted as a corporate HR standard.
Procurement information
- Contract formatInhouse fixed cohort (10–14 weeks), multi-cohort continuous program (3–4 cohorts per year), or long-term engagement (12 months with periodic refresh + quarterly clinic).
- LocationOnsite at client offices (Jabodetabek with no extra transport fee), regional onsite for multi-city BUMN, hybrid (onsite kickoff + bi-weekly online sessions), or fully online.
- Language of deliveryBilingual ID/EN (default); full English for multinational corporates; full Bahasa Indonesia for selected BUMN/government contexts.
- Participant materials and certificateModules, workbook, runbook + SLO + threat modeling + RACI templates, 12-month access to the Engineering Manager Indonesia alumni resource hub, Neksus participation certificate. Onward certifications (ITIL 4 Foundation / AWS / GCP) available via a separate track.
- Tax documentation and e-procurementVAT (PPN) tax invoice, official receipt, BAST. Support for BUMN/government e-procurement (SPSE LKPP). Comprehensive vendor scoring document available for internal evaluation.
- Payment terms30% down payment at contract signing, 40% milestone after kickoff + instrumentation lab, 30% balance after capstone.
- Optional add-onsPersonal 1-on-1 coaching for Head of Engineering / VP Eng (separate hour-based package) plus a 90-minute executive briefing for CIO / CTO / Board IT Committee on engineering capability roadmap.
- NDA and confidentialityStandard or client-specific NDA; the Neksus team is accustomed to working with confidential engineering stacks (mobile banking, core banking, regulator systems).
Frequently Asked Questions
Let's design the Engineering Manager cohort for your technology team
Send the number of Engineering Managers / IT Leads, the domains involved (mobile, core banking, data platform, infra), and your target cohort start date. The Neksus team studies your context and prepares a tailored program design within 2 business days.
- 10–14 week cohort with workshop, DORA instrumentation lab, and peer-coaching
- Facilitators with field engineering leadership experience plus ITIL 4 / AWS / ICF credentials
- Mid-program check-in with CIO/CTO so participant 90-day plans land with board support
- Kirkpatrick L1–L4 measurement using DORA metrics, SLO compliance, and engineer churn
- Bilingual ID-EN delivery, with materials audit-ready for BPK / KAP / OJK