Page 229 - Fearless Leadership
P. 229

216  FEARLESS LEADERSHIP


             At the end of a straight talk conversation, make sure you have closure:

             • Define the actions you and others need to take.
             • Make clear and specific requests and align on what you
               are agreeing to.
             • Identify who is accountable and by when.
             • Identify who needs to be included in your resolution of
               the breakdown.

           BUILDING A TEAM THAT TALKS STRAIGHT
           RESPONSIBLY
           By resolving issues quickly, you clear up assumptions, establish new com-
           mitments, and restore clarity and partnership. People are enlivened and
           replenished by conversations that efficiently cut through barriers and con-
           flict. A vast storehouse of energy is released when you communicate
           directly and responsibly and when you encourage others to do the same.
             Practicing responsible straight talk, even when done imperfectly,
           changes the dynamics of how teams interact. Assess your team’s ability to
           talk straight with one another using the statements in the sidebar “Do We
           Talk Straight Responsibly as a Team?” You may want to use a rating scale,
           with 1 as low and 5 as high, to provide a range of responses. Record your
           answers so you can reassess at a later date.


             Do We Talk Straight Responsibly as a Team?
             1. We talk openly and honestly about our blind spots.
             2. We are emotionally honest with one another.
             3. We are culturally sensitive.
             4. We speak responsibly and respectfully without blaming
                or attacking others.
             5. When we have a breakdown, we address the issue and
                recover quickly.
             6. We communicate fully and accurately.
             7. We talk to one another, not about one another.
             8. We include the entire team, in a timely manner, when issues
                have been resolved off-line between team members.
   224   225   226   227   228   229   230   231   232   233   234