Managing High-Performing Software Teams

High-performing teams expect their leader to help them make things better. The piece argues that autonomy in software teams supports faster decision-making, quicker delivery, and better impact, while managers should offer empathy, understanding, and guidance.

It also says that slow decisions hurt productivity, and that engineering expertise should live in the team rather than in one manager’s head. Managers can help by observing the system, asking why work takes as long as it does, and trying small changes.

Reading notes

#

• High-performing teams expect their leader to enable improvement, not to become the place where problems stall.
• Independent teams can make decisions faster, which helps delivery and impact.
• Motivated engineers often notice more things to improve than things that are already going well.
• When teams feel they cannot solve things fast enough, they start sounding negative and stop bringing problems for help.
• Waiting for decisions is described as the biggest productivity killer.
• In technology, thousands of decisions happen every day, so people far from the work cannot make high-quality decisions without blocking teams.
• Low-performing teams can be examined through cycle time, since much of it may be waiting for information or a decision.
• The text says managers should provide empathy, understanding, and guidance.
• Empathy comes from thinking like an engineer.
• Guidance comes from applying engineering fundamentals to get better results.
• Managers can improve cycle time by observing the system, asking why work took so long, and experimenting with small changes.
• One example describes work moving back and forth because a stakeholder specified the solution too precisely, QA found edge cases, and follow-up happened mostly by email with missing context.
• Engineering leaders cannot keep all expertise current in their own head.
• Knowledge and expertise should be treated as a group asset, not an individual asset.