A lot has been written about developing trust with your team members. Trust takes time to build and can be destroyed in a minute with a careless remark. In Asia, trust is maybe even more critical when leading a team. We know all that. Nothing new here. But I have seen senior leaders attempting to build trust with their team yet at the same time destroying the very foundation of that team.
Here is what I have observed more than once. The leader sits down with Tom, one of his direct reports, to review an important project. "Great job Tom, I am really happy I asked you to be in charge of this project. We are on track and the client is really satisfied. You have definitely confirmed your capabilities". So far so good ... great expression of trust in what Tom has done so far. And then the conversation continues ... "Now, for the next step, you will need to work with the marketing manager Susan. You know she can sometimes be a bit reluctant about launching under the circumstances we are in. You may want to spend some extra time to convince her. But at the same time, I trust Susan that she will lead the marketing campaign successfully."
What has happened here ? The leader has created great trust between him or herself and Tom. Tom probably walks out of this meeting really pumped and motivated. But what about Tom and Susan ? The leader gave some advice about how to approach Susan, and also added that he or she trusted Susan with her part of the project. So all should be set and done between Tom and Susan, right ? Unfortunately, trust does not work that way. Trust is dyadic, a difficult word to indicate it can only exist between two people. I can trust A and I can trust B, but that does not mean that A trusts B or that B trusts A.
Developing a team requires not just trust between the leader and the direct reports. There is much more potential for value - as well as downside - in the trust relations between the team members. If the leader talks to Tom about Susan, when Susan is not there (and doesn't this happen all the time ?), then what does this do to the relationship of trust between Tom and Susan ?
Trust between your team members is as important as trust between you and each of them. As a leader, you cannot "manage" this trust, but what you say - and what you don't say - to each of your team members influences these trust relationships to a large extent. Something to think about for your next one-on-one.
my thoughts and a bit of experience on working with teams, learning and knowledge management, and management in general ...
Sunday, October 25, 2015
Wednesday, October 14, 2015
Learning ... one KISS at a time
KISS Keep It Simple Stupid was originally coined by the US Navy to emphasize the importance of keeping things as simple as possible. The target the navy commander had given to his mechanical design team was to ensure that a ship's engine system could be repaired by a mechanic with limited experience or specific training. The idea was never to refer to that mechanic as stupid. In fact, the original KISS was written without a comma, meaning that things needs to be kept simple AND stupid (without writing the 'and'). Since then, many have changed the original meaning and added a comma to read Keep It Simple, Stupid ... Written that way, the 'stupid' becomes an insult to whoever the message is addressed to.
I recently came across another meaning of KISS I had never heard before. A business leader told me his team always ended their meetings and working sessions with a "KISS" ! KISS in this context stands for:
Keep: what did we do well in this meeting that we should keep doing ?
Improve: what did we do that was so-so and we should think about improving next time ?
Stop: what did we do that didn't work and we should commit to not doing again ?
Start: what was missing and we should add or start doing for our next meeting ?
A simple way to remind yourself and your team that learning happens all the time. There is no need to make things complicated. The only requirement is to spend a very small amount of time to reflect together on a key number of questions and create a shared commitment on making sure the next meeting, project, session or retreat is better than the last one.
I recently came across another meaning of KISS I had never heard before. A business leader told me his team always ended their meetings and working sessions with a "KISS" ! KISS in this context stands for:
Keep: what did we do well in this meeting that we should keep doing ?
Improve: what did we do that was so-so and we should think about improving next time ?
Stop: what did we do that didn't work and we should commit to not doing again ?
Start: what was missing and we should add or start doing for our next meeting ?
A simple way to remind yourself and your team that learning happens all the time. There is no need to make things complicated. The only requirement is to spend a very small amount of time to reflect together on a key number of questions and create a shared commitment on making sure the next meeting, project, session or retreat is better than the last one.
Subscribe to:
Posts (Atom)