Leading software teams with systems thinking
summary
Argues that systems thinking turns vague priorities into concrete actions by following a three-step routine: understand goals, inspect work as processes, then manage and measure system changes. Shows practical checks — trace an idea to production, map who defines requirements, audit incident and QA flows, and formalize feedback loops for career growth — and uses those artifacts to get buy-in, make small experiments, and measure outcome changes, claiming continuous fine‑tuning improves delivery and engineer fulfillment.
AI-written summary · about
chapters (6)
- 0:00Leading with systems thinking
- 1:23Systems thinking in practice
- 3:50Three-step systems leadership
- 5:15Team productivity and fulfillment goals
- 8:23Acting on system insights
- 10:28Summary
related talks
28mFinding better problems
01h 25mA Systemic Approach to Organisation Design & Change Management
34mSystems Thinking For Dev Organisations
38mSolving the Hard Problems
44mUnderstanding Teams Through Systems Thinking and Stories
43mBetter Software Development Systems through Stress
26mApplying A Technical Brain To Organizational Design
45mTaking Back "Software Engineering"