Why Isn't This Done Yet? Matching Your Leadership to the Task

A developer accepts a task during a standup and says it looks straightforward. Two weeks later, there is no progress. The lead expected steady progress without check-ins, and the developer expected more guidance at the start. Neither person said their expectations out loud. 

As the mantra goes: expectations are premeditated resentment.

This session provides a practical way out of this cycle. Following the principles of Situational Leadership, participants will learn how to diagnose what their team members need in order to adjust their leadership style. The right leadership style depends on two things: who is doing the work and what the work is. Your strongest back-end developer can fully own a Drupal migration but may need close coaching for their first client demo.

Attendees will learn why defaulting to a single leadership style in all situations fails, like always delegating when coaching is needed. Attendees will also learn how to:

• Assess an individual team member’s skill and commitment for a specific task.
• Turn unspoken expectations into a clear, shared plan.
• Use a simple matrix during daily work to support the performance and experience of a team.