Engineering brief

Signals & Levers • Elisabeth Hendrickson, Joel Tosi & Charles Humble • GOTO 2026

GOTO Conferences

The Brief

Spot illusions and pull effective levers in complex software orgs using systems thinking, not vanity metrics.

Decision relevance

Read this for workflow impact, implementation trade-offs, and the claims that need technical scrutiny before they reach team planning.

Summary

This conversation reframes software delivery through systems thinking, arguing most orgs are misled by illusions of progress, predictability, and control. Agile/DevOps gains have plateaued; AI and rising complexity expose bottlenecks that rituals and platform teams can’t mask. Microservices often create a false sense of speed while integration delays dominate. Change-control boards masquerade as quality levers but throttle flow.

The authors push leaders to stop treating proxy metrics as truth. Velocity, tokens, and lines of code are opinions in numeric clothing; they optimize for motion, not value. Shift to flow-centric signals—cycle time, lead time variability, WIP—and acknowledge that measuring is itself an intervention: signals become levers as people respond to what’s watched.

Use variability analysis (control charts) to separate signal from noise. Don’t punish normal fluctuations or chase single root causes in complex systems—there usually isn’t one. Build causal models to surface reinforcing loops and find small, high-leverage nudges (e.g., isolate test data, reduce cross-team dependencies) that flip vicious cycles into virtuous ones. Expect time delays; avoid oversteering and change theater when results don’t land immediately.

Culture consistently beats policy. Treat culture as an organizational immune system: it resists misaligned mandates. You can shift it, but only by feeding desired behaviors—language, rituals, origin stories, and rewards (e.g., celebrate cross-team collaboration over heroics). Transformation by decree fails; transformation by incentives, stories, and consistent signals sticks.

Practically: adopt a multidimensional signal framework (capacity, risk, economics, adaptability, etc.) to prevent myopic fixes. Kill velocity targets and token leaderboards. Replace CCBs with progressive delivery and guardrails. Fund enabling constraints—test data bootstrapping, decoupled architectures, focus-limited planning—to reduce variability and restore predictability.

Why It Matters

Leaders are misled by vanity metrics and oversteer. Systems thinking provides practical levers to improve flow, quality, and culture amid AI-driven complexity.

Editorial analysis

Key claims

  • Measure flow, model causes, nudge constraints, and shape culture; stop worshiping velocity and control boards.

Practical use cases

  • Use this as input for tooling evaluation, workflow planning, and technical due diligence.

Risks / caveats

  • Velocity targets, token/LoC leaderboards, CCBs as quality fixes, root-cause silver bullets, transformation-by-decree.

Who should care

  • Engineering managers, tech leads, and CTOs evaluating AI or developer tooling decisions.

Related topics

Bottom Line

Measure flow, model causes, nudge constraints, and shape culture; stop worshiping velocity and control boards.

Watch

This video is blocked due to your privacy settings. To watch this video, please accept YouTube marketing cookies.

Related breakdowns

Get TL;DW

Too Long; Didn't Watch.

A concise breakdowns of the AI and devtools videos that actually matter for engineering leaders.

Free. Weekly. No hype.

Video and thumbnails remain the property of their respective creators. tldw.news provides editorial analysis, commentary, and discovery links to original content.

Signals & Levers • Elisabeth Hendrickson, Joel Tosi & Charles Humble • GOTO 2026 | tldw.news