Feb 17, 2023
This week, Dan Neumann is joined by a long-time acquaintance and friend, Tricia Broderick, a leadership advisor and co-author of Lead Without Blame with Diana Larsen.
In this episode, Tricia talks about the book she wrote with Diana, their mission, and the most important messages that are carried in it, such as the true meaning of a Team, the relevancy of collaboration and connection, autonomy, metrics, and much more!
Key Takeaways
What makes a Team resilient?
Collaboration and connection are the foundations of an authentic Agile Team.
Online work does not make connecting to others any easier.
Do the leader’s team connections need to be cared for differently than the lateral connections between team members?
Power dynamics don’t have to be formal, it could be someone who the leader greatly respects or who has an influential power.
A psychologically safe environment welcomes everyone to express their true selves, even though it is impossible to assure emotional safety for everyone at all times since each Team member is unique.
Are you showing up with compassion?
Bounded autonomy:
You cannot empower someone to do something if they don’t have the knowledge or the skills.
Trust is required in both directions.
Information radiators and appropriate use of metrics are the right way of seeing trends.
Sometimes metrics are misused; they need to be used carefully.
Metrics need to help the team collaborate towards problem-solving and not as weapons.
A Team doesn’t become one only because it is named that way.
A group is not a Team, cooperation isn’t the same as collaboration.
You are a better leader because you are not perfect, own your mistakes and growth, since they have brought you to the point where you are today.
The only way it is impossible is if you stop trying.
Mentioned in this Episode:
Lead without Blame: Building Resilient Learning Teams, by Diana Larsen and Tricia Broderick
Want to Learn More or Get in Touch?
Visit the website and catch up with all the episodes on AgileThought.com!
Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!