// Topics / Technical Leadership

Technical Leadership

Technical leadership is an operating-system problem: who decides, who owns the boundary, how feedback moves, and what signals trigger a change in direction.

The AI era has not changed that. It has made weak ownership and slow decisions more expensive.

Start Here

Leadership Questions That Matter

  • Who owns the production behavior of an AI feature after launch?
  • Which decisions can product teams make without waiting for a platform group?
  • Which risks require security, legal, or executive approval?
  • How does the organization know when an AI initiative should stop?

Reading Paths

For AI operating model:

For classic engineering leadership:

Failure Modes

  • Adding process where the real problem is unclear ownership.
  • Measuring headcount instead of throughput, quality, and decision latency.
  • Centralizing every AI decision until platform becomes a bottleneck.
  • Treating leadership communication as ad hoc once the system enters production.

References

    Your AI Tool Needs an Adoption SLO Seat counts can't justify an AI tool renewal. Define one adoption SLI, governed completions over eligible cases, with guardrails and a breach rule. ai operations metrics The Handoff Tax 80% report personal AI gains while EBIT impact stays flat. The handoff tax: task time down, throughput flat, queues rising at one nameable transition. leadership operations ai Don't Book the Cut Before the Work Disappears Expected AI headcount cuts outran reported ones last year. Let forecasts drive scenarios; book a saving only once the work has observably gone. leadership teams ai The Rung Contract Competency matrices describe skills. Apprenticeship needs a contract per rung: permission, evidence, reviewer, a promotion rule two managers apply alike. leadership teams ai The Junior Developer Cliff Is a Leadership Problem AI eats the work juniors learned on. Rebuild apprenticeship around verification and ownership, or starve your senior bench. leadership ai teams The Diffusion Gap: Why Pilots Don't Become Capability Most AI pilots pass the trial and then die. Closing the gap takes ownership, cadence, and incentives. Write exit criteria as operating changes. ai operations leadership The Board's AI Oversight Problem Is Operational Board AI oversight is operational: a named owner per system, a rehearsed halt path, an incident threshold, and a failure rate you can defend. governance ai executive Unsupervised Producing the work can be handed to a machine. Answering for it cannot. What an organization values when machines do most of the making, what people are for, and four things to try this week. opinion ai strategy Leading Senior Engineers in the AI Era: Autonomy, Standards, and Accountability Leading senior engineers on AI features: a written definition of done with an owned eval, a named failure mode, a rollback drill, and a paging threshold. leadership ai teams The Anti-Fragile AI Organization A warm LLM fallback is a standing cost that needs an owner. Price portability per feature, and turn each vendor shock into a capability you keep. teams ai reliability The Post-Prototype AI Org: Operating Models That Survive Year Two Canon post — Year-two AI failure usually comes from org-design mismatch, not model-quality mismatch. The handoffs are where the system slows down. ai teams leadership The Operating Cadence: Turning AI Leadership Interfaces Into Predictable Output Canon post — Leadership interfaces decay without rhythm. A weekly metrics review, monthly outcome review, and quarterly architecture audit keep AI ownership real. leadership ai operations Designing the AI Leadership Bench: Roles, Interfaces, and Failure Boundaries Canon post — Scaling AI needs a leadership bench: named owners for product, platform, applied AI, and governance, with failure handoffs rehearsed before incidents. leadership teams ai Decision Latency as a P&L Variable: The Leadership Metric Nobody Owns Canon post — Slow decisions are a hidden cost. How to measure decision latency, from issue to decision to action, and cut it with clear ownership of decision classes. leadership metrics strategy How to Run an AI Incident Review That Changes Architecture, Not Slides An AI incident review is done when it changes architecture, evals, alerting, or ownership. An eight-part template that ends in fixes, owners, and dates. reliability ai governance AI Roadmaps That Survive Contact With Reality Canon post — AI roadmaps fail when they are sequenced around ambition instead of dependency, verification, and rollback cost. strategy ai leadership Hiring for AI Teams: The Operator Profile That Scales The AI hires that scale are operators who handle ambiguity, systems tradeoffs, and verification pressure. Four traits and four interview questions. hiring ai leadership Technical Leadership in the AI Era: Throughput Over Trends Technical leadership in 2026: anchor decisions in throughput, verification, and operability instead of chasing the latest agent framework. leadership ai teams Stop Building Internal AI Tools No One Uses Internal AI tools die quietly when teams optimize for launch over workflow fit, output trust, and post-launch ownership. One tool failed, one stuck. productivity ai leadership Why Most AI Platform Teams Become the New Bottleneck Canon post — AI platform teams become bottlenecks when they centralize decisions instead of capabilities. The warning signs, the metrics that expose it, and the fix. platform-engineering ai teams Build the System the Model Cannot Break Canon post — A manifesto for AI-native organizations: twelve tenets across strategy, architecture, economics, and people, and the one test that matters in year two. opinion ai strategy The CTO Communication Protocol for AI Programs Canon post — AI programs fail when engineers, executives, and investors hear different definitions of success. A communication cadence that keeps one true story. leadership ai executive AI Governance Without Bureaucracy AI governance that works: tighter defaults, named owners, fast escalation, and a small control stack engineers can follow at 2 a.m. No new committees. governance ai security AI Strategy Metrics: Margin, Risk, and Speed Replace AI novelty metrics with three executive numbers: margin, risk, and speed. Give each a baseline, target, owner, cadence, and rollback path. ai metrics strategy AI Evaluation and Production Governance: A Maturity Model A five-level maturity model for AI evaluation and production governance, from vibes-based deploys to CI eval gates, production sampling, and rollback. governance ai reliability AI Capital Allocation: What to Stop Funding First Strong AI strategy starts with a kill list. If a project cannot defend margin, risk, or speed, it should not survive the next budget meeting. ai strategy cost AI Strategy for CTOs: It's Data Infrastructure AI strategy for CTOs: the moat is the context pipeline, the eval loop, and the fallback path. Picking a model is the easiest problem in the room. strategy ai executive The Throughput Engineer: Why Headcount Is a Lagging Metric Canon post — Headcount is a lagging metric. The best engineering organizations measure throughput: decision speed, defect containment, and constraint removal. leadership productivity operations AI Team Structures 2026: Central, Embedded, and Hybrid Models Central, embedded, or hybrid AI team? How to decide where AI ownership lives, with roles, tradeoffs, platform-to-product ratios, and scaling rules. teams ai architecture Scaling AI in the Enterprise Is a Management Problem AI pilots work. What fails is going from five demos to fifty production features without an operating model. That's a management problem. business ai architecture Building AI Teams: Ownership and Evaluation Beat Hiring Most AI team failures come from unclear ownership and weak evaluation, not missing talent. Team structures that work, who to hire, and the operating loop. ai teams hiring Why Enterprise AI Pilots Stall Between Demo and Production Most enterprise AI pilots stall between demo and production. The blockers are organizational: ownership, security review, data access, governance. business ai strategy Restructuring Engineering Orgs After Layoffs Most post-layoff reorgs redraw boxes instead of fixing ownership gaps. What worked in 2023: explicit owners, killing work, and direct communication. leadership teams Leading Engineering Teams Through Uncertainty Early 2023 layoffs and budget cuts brought startup-style uncertainty to every engineering team. What helps: weekly updates, explicit stops, firm standards. leadership teams startups Resilient Engineering Teams Are Boring Teams The engineering teams that got through 2022 best had the least drama: no heroics, no single points of failure, sane on-call, and bad news raised early. teams leadership reliability Tech Layoffs 2022: What I Saw From the Inside What I saw during the 2022 tech layoff wave, and what helps engineering teams survive contraction without burning out. leadership teams hiring Engineering Metrics: DORA, Error Budgets, and DevEx Signals Most engineering metrics measure activity. The few worth tracking: DORA, user-facing reliability with error budgets, developer friction, and outcomes. metrics leadership productivity Engineering Onboarding: Ship a Real PR by Day Three Most engineering onboarding wastes the first week on access requests and context overload. The fix is simple: ship a real PR by day three. hiring leadership teams SRE Team Structures: Stop Renaming Your Ops Team Centralized, embedded, or platform SRE: how each model fails, the engagement tiers and entry criteria I use, and why renaming ops to SRE changes nothing. reliability teams leadership Most 'Technical Debt' Is Just Decisions You Disagree With Now Most 'technical debt' is code that aged, not debt. How to spot real debt by its costs (incidents, delivery, security, hiring) and get fixes funded. technical-debt leadership architecture Remote Work for Engineering Teams: Benefits and Dangers Years of running distributed engineering teams: what remote work gives you, where it hurts (isolation, blurred boundaries, eroding trust), and what works. remote-work leadership teams Hybrid Work for Engineering Teams Is Harder Than Full Remote Hybrid engineering teams drift into a two-tier system unless you run them remote-first: written decisions, async defaults, outcome-based reviews. remote-work teams leadership Developer Productivity Metrics: Why I Only Trust DORA Lines of code, commit counts, and velocity charts fail as developer productivity metrics. The four DORA metrics, tracked per team, are worth your time. productivity metrics engineering Async-First Remote Work: Stop Recreating the Office on Zoom Most teams that went remote just moved the office onto video calls. Async communication is the real unlock. These are the rules I work by. remote-work architecture leadership Engineering Onboarding: First PR on Day One Most engineering onboarding is a polite abandonment ritual. What I've learned across startups about getting new engineers shipping fast. hiring engineering teams How We Track and Prioritize Tech Debt at a Fintech Startup A framework for cataloging technical debt, scoring it by impact and risk, and scheduling paydown without stalling feature delivery. technical-debt engineering leadership Scaling Engineering Teams: What Breaks at 10, 25, and 50 How engineering teams change as they grow: what breaks at each size, explicit ownership, written decisions, and process that follows pain. engineering leadership teams Technical Interviews: Work Samples Beat Whiteboard Puzzles Most technical interviews test the wrong things. What hiring engineers at a fintech startup taught me: work samples, pairing, deep dives, and rubrics. hiring engineering leadership Async-First Engineering Teams: Cutting Decision Latency How our fintech team cut meetings and decision latency across time zones: written decisions, response-time rules, and calls only when they earn it. remote-work leadership teams Engineering Manager vs Tech Lead: How the Roles Differ Engineering manager vs tech lead: what each role does day to day, how we split them at a fintech startup, and how to test which track fits you. hiring leadership engineering The Business Case for Infrastructure: Pitch It in Money Boards fund money, risk, and speed. How I pitched infrastructure investment at a fintech startup: business framing, rough ROI, and a skimmable proposal. infrastructure leadership business Technical Leadership Without Authority: What Works A senior title meant little at a small fintech startup. How I earned technical influence instead: one-page proposals, leading with the problem, and allies. leadership engineering hiring Building a Startup Engineering Team: Lessons from 2016 What growing an engineering team at a mobility startup in 2016 taught me about hiring, trust, and the habits that actually matter. teams engineering leadership Technical Due Diligence: What Investors Actually Check Technical due diligence from both sides of the table: what investors check, how to prepare when you are evaluated, and what to look for when evaluating. executive governance startups Building a Security-First Engineering Culture Security culture is habits leadership enforces: no secrets in code, a security question on every PR, least privilege, patch deadlines, and champions. security engineering teams Hiring Engineers When You Can't Compete on Salary You can't outpay Big Tech. How I hired strong engineers at a mobility startup in 2016 by selling impact, speed, real autonomy, and honesty about pay. hiring startups engineering Building a DevOps Culture from Scratch Hiring a DevOps engineer won't end the dev vs ops fight. Put developers on the pager, pilot with one team, and fix incentives before tools. devops teams engineering The True Cost of Technical Debt, and How to Measure It Tech debt gets ignored until you price it. Track cycle-time drift, incident attribution, and engineer-days lost, then pitch paydown as a business tradeoff. technical-debt engineering leadership