The work of leading software teams.

Almost every senior developer I've coached into a lead role has said, "I don't feel productive anymore." The work changes when your contribution is helping other people do theirs, and letting someone solve a problem differently can be difficult.

Takeaway: Recognize your contribution beyond commits by looking at the decisions and problems you help other people own.

For: Developers moving into leadership, new technical leads and the managers supporting them.

For years, when something got hard, I took the keyboard. It felt like helping, but it taught the team to wait for me. A discussion about handing problems over, staying clear about direction and giving people room to own the solution.

Takeaway: Hand over a problem with clear direction, stay available for support and resist taking control back when the solution differs from yours.

For: Technical leads and engineering managers who still find themselves solving every hard problem.

I started a software company in 2005 and closed it in 2010, with debts I carried for years. That experience changed how I respond to mistakes and think about delivery today: what the work costs, who is waiting for it and what happens if it's late.

Takeaway: Ask business and delivery questions earlier, and respond to mistakes by asking what can be learned.

For: Engineering leaders, founders and teams looking to connect technical delivery with business needs.