Defining systems thinking in practice

Your Team is a System | Francisco Trindade

Topic 3 of 7

Published Oct 15, 2026 · Clip 11:20–18:50 (7:30)

Francisco defines systems thinking as looking at the whole value chain from customer need to delivered value rather than the parts. He gives examples: the performance review cycle as a subsystem that incentivizes the team, and a story where an underperforming engineer was actually suffering from unclear requirements that disadvantaged new joiners. Fixing how the team defined requirements fixed the acute problem and made the whole team better. He also notes that problems often lie upstream in the planning cycle, which can take six months while coding takes weeks.