tech-leadership

Tech Leadership

Core Rule

Treat technology leadership as an operating system, not a motivational role. Convert business context into explicit priorities, decision rights, capacity, risk appetite, financial trade-offs, technical strategy, cybersecurity posture, people systems, execution rhythm, and measurable outcomes.

First Pass

1. Classify the request: daily operating review, strategy, roadmap, portfolio, cybersecurity strategy, SME/COE, functional/technical requirements, framework selection, audit/compliance, board/shareholder report, delivery recovery, incident management, organization design, hiring/retention, appraisal, budget, vendor/partner strategy, R&D, AI/data transformation, culture, political risk, or cross-functional advisory.
2. Identify role level: CTO, VP Engineering, Head of Engineering, tech lead, engineering manager, platform leader, product/data/AI leader, non-executive tech leader, acting CTO, advisor, or founder-CTO.
3. Capture context: sector, geography, company stage, regulation, risk appetite, operating model, budget authority, reporting line, decision rights, team size, vendor dependence, technology estate, and current constraints.
4. Separate Fact, Inference, Assumption, and Question. Do not invent headcount, budget, maturity, compliance obligations, breach history, board priorities, or culture dynamics.
5. Choose the smallest useful output: decision memo, roadmap, dashboard, board report, audit pack, risk register, org map, meeting brief, policy, operating cadence, performance calibration, incident review, or change plan.
6. Define validation: stakeholder review, metric baseline, risk acceptance, financial model, delivery evidence, audit evidence, tabletop exercise, incident drill, pulse survey, architecture review, or post-implementation review.

Required Reads By Task

• Operating cadence, daily/weekly/monthly leadership work, decision rights, or CTO operating model: references/leadership-operating-system.md.
• Strategy, short/mid/long-term planning, roadmap, portfolio trade-offs, technology bets, technical debt, scalability, resilience, sustaining engineering, roadmap uncertainty, or over-engineering: references/strategy-roadmap-portfolio.md.
• Senior technology leadership role design, CTO vs VP Engineering, executive peer trust, senior leadership tasks, technical True North, role modeling, or business/technology executive alignment: references/senior-technology-leadership.md.
• KPI, KRA, OKR, CSF, scorecard, dashboard, performance reporting, root cause analysis, balanced scorecard, benchmarking, performance management system, or metric design: references/metrics-kpi-dashboard.md.
• Executive and managerial quantification, CTO metrics, technology value metrics, manager-system metrics, board metric synthesis, team diagnostic metrics, metric harm, or modern technology leadership blind spots: references/executive-managerial-quantification.md.
• Hiring, developing, retaining, mentoring, delegation, 1:1s, skip-level meetings, managing managers, manager accountability, calibration, appraisal, 360 feedback, incentives, team allocation, or succession: references/people-org-talent-appraisal.md.
• Enterprise risk, audit readiness, compliance, policy, controls, regulatory exposure, or governance: references/governance-risk-compliance-audit.md.
• SME, Subject Matter Expert, Center of Excellence, COE, community of practice, expert review, capability enablement, platform/service COE, governance COE, or reusable expert capability: references/sme-coe-operating-model.md.
• Functional requirements, technical requirements, product/engineering specs, non-functional requirements, acceptance criteria, traceability, launch readiness, migration requirements, or requirement review: references/requirements-engineering-for-tech-leads.md.
• Selecting or critiquing ITSM, ITIL, COBIT, TOGAF, ISO/IEC/IEEE, PCI DSS, PMBOK, CMMI, AICPA/SOC 2, CNCF, Gartner Magic Quadrant, HIPAA, GDPR, PDP, SAFe, Lean Six Sigma, DORA, MTTR, or deciding no framework: references/framework-selection-and-critical-prompts.md.
• Socio-technical risk, reliability management, hidden risk, near misses, barriers, redundancies, recoveries, just culture, burnout risk, human reliability, system reliability, organizational reliability, or predictive reliability: references/risk-reliability-leadership.md.
• Cybersecurity leadership, CISO/CTO boundary, cyber risk appetite, security roadmap, IAM, SOC, AppSec, cloud security, data security, third-party risk, incident/crisis leadership, or board cyber reporting: references/cybersecurity-strategy-management.md.
• Delivery predictability, unblocking, agile, incident/on-call, reliability, SLO, operational resilience, platform operations, or postmortem: references/delivery-incident-reliability.md.
• Budget, costing, ROI, value realization, business case, unit economics, vendor spend, cloud cost, or investment governance: references/finance-roi-costing.md.
• AI leadership, AI agents, agent autonomy, AI observability, AI security, AI ROI, data/product leadership, data value, R&D, technology research, innovation, experiments, hypotheses, evaluation, and adoption governance: references/ai-data-rd-innovation.md.
• Board, shareholder, executive, cross-functional, customer, vendor, and team communication; presentation, narrative, advisory, negotiation, and pushback: references/stakeholder-board-communication.md.
• Engineering culture, structure, career ladders, cross-functional pods, process-as-risk-management, code review, architecture review, learning reviews, Conway's Law, psychological safety, and scale-stage structure: references/engineering-culture-structure-process.md.
• Culture, incentives, organizational politics, power mapping, psychological safety, cross-cultural leadership, and office politics defense: references/culture-politics-cross-cultural.md.
• Sector-specific leadership forces across banking, energy, government, insurance, consulting, FMCG, healthcare, manufacturing, logistics, agriculture, defense, real estate, media, education, non-profit, vendor, and multinational contexts: references/sector-contexts-and-operating-models.md.
• Red flags, anti-patterns, failure modes, weak assumptions, and leadership smell checks: references/leadership-antipatterns-red-flags.md.