Leading in Tech, week 5 case

Case: the team that still asks the old lead

Three months into her first lead role, the team still brings decisions to the senior who led it informally for two years.

He voted to hire her. He also reorders her priorities in code review. Her manager has offered to make her authority official in writing, by Friday.

You will now hear the full case, one page, 5 minutes. Listen for what has already been tried.

Leading in Tech, week 5 case

Case: the laws in tension

  • Influence: the org chart names one lead; followership names another
  • Connection: one coffee did not buy what two years built
  • Buy-In: a written rule creates compliance, not acceptance

Three laws, and they do not point to the same answer.

Leading in Tech, week 5 case

Two captains, both tracks

Whether you lead a team of reports or lead technical direction without reports, you will inherit someone's followers.

A new EM inherits an old informal leader. A new senior inherits a team with an old go-to.

Structure can force compliance. Only connection creates followership.

Leading in Tech, week 5 case

Activity: prepare your camp

Assigned camps, 10 minutes. One camp argues: take the structural fix, end the ambiguity this week. The other argues: decline it, win Seif first, structure only if connection fails.

Build your opening and your best evidence from the case text.

Challenge: what is the other camp's strongest attack on you?