Monthly Archives: February 2012

Removing blocks to employee development

I was confronted recently with the all-too-common  chicken and egg problem when beginning the bquest development process with a highly pressured employee.

To develop his marketing skills, he needed to find time. But to find time, he needed to develop time management skills. For which he need to find time! Over many years, I have come across many such blocks to employee development in small businesses, for example:

- I don’t have the time.

- I don’t know how to read books effectively and efficiently.

- I don’t have the energy or motivation.

- I am afraid of trying anything new.

- My boss says I must do things a certain way.

- Development isn’t a priority right now, I have other more pressing business problems to solve.

- Sitting, thinking is a waste of time that should be spent doing things.

- I’ve done things this way for years and it has worked alright for me so far.

- Academics and consultants with their ideas, pah!  They should join the real world.

- It’s alright in theory, but not in practice.

- I want you to give me the answer.

- Stop asking questions, you’re making my head hurt.

Give me an hour and I will come up with quite a few more.

Are these familiar to you? How do you manage them?

Blocks are blocks; the client needs help in removing or overcoming them or minimising them before they can get on with what they actually want and need to learn and develop.

Some of the blocks are mental blocks, and the client needs help to see them in a different way, to ’reframe’ or by giving them information that changes
their understanding. “So, you say you don’t value theories; but how do you organise your life now? What rules of thumb, assumptions and beliefs do you use? When you see a green traffic light, are you certain the driver coming from the side road sees a red light and will stop, or do you theorise it and still keep an eye out? Without such theories we would never be able to function effectively.”

Some of the blocks are actual blocks. Help might be in the form of some skills development (how to read, how to organise some time, etc.) or it might be in the form of changing their environment (influencing the boss, finding a quiet place, changing their shift, etc.)

Sometimes, removing blocks requires a bit of underhandedness. For the highly pressured employee who said he didn’t have time to develop marketing skills, we didn’t talk about time management. Instead, in discussion about his marketing ‘problems’, I asked how he priced his products. He got so fired up about this he immediately decided to get one of his people to collect some information about different ways of pricing.  A few days later, they had met several times, discussed the information, and decided to make some changes.

Afterwards, when he told me what he had done, and when I had encouraged him to reflect on what he had learned from this, it dawned on him that he had actually been using time management methods in the form of delegation. I haven’t heard any more from him about not having time to learn!

In bquest, as part of the initial ‘diagnosis’ of need we always identify mental or actual blocks. We make sure learning and development goals are achieved.

Share

Employee development is a matter of trust

I am not sure where this originated but I heard someone talk about three stages of developing networking relationships; maybe it was a BNI model. The model suggests you first get to KNOW someone, then you UNDERSTAND them and what they do, and then you can TRUST them.

There are probably other ways of skinning this particular cat but the model – yes, it’s a mental model - struck a chord with me not only as a useful way of developing a strong network but also as a model for the relationship between bquest and our clients.

Here’s my take on it. (Let’s not get into semantics about words like ‘know’ and ‘understand’):

KNOW – in this model, this is when you meet someone, shake hands and exchange a few words. You ‘know’ their name, what they do, maybe some other basic facts about them. But that’s about it. In your network, you can say to someone “I don’t know much about him, but I do know a lawyer who specializes in xyz. Here’s his number.”

UNDERSTAND – in this model, the person you meet may go into more detail, explaining what they do, how they do, why they do it, what’s important to them, what their problems are….. And so on. You  ’understand’ them because they communicate to you in some way what they think and feel as well as what they do; you can get ‘inside their head’ and see the world as they do. Then in your network, you can say to someone “I haven’t personal experience of him, but I know a lawyer who specializes in xyz.  He comes across as a clever and sincere person and I think you should give him a call.” This is a recommendation of sorts  - it’s qualified – rather than simply passing on the contact details.

TRUST – this is the tricky stage. Most people would say that the word ‘trust’ implies you believe in someone, that you know they have ability to do something, that you can rely on them and that you think  they are honest. (OK, it is possible to argue that trust isn’t necessarily about doing ‘good’. You can argue that you can trust a person to do something, but that you can also trust a person not to do something or do something bad. In other words, you can argue that trust isn’t about doing good, it’s more that you understand a person so well you can predict their behaviour, good or bad. But let’s stick with the trust/good connection here.)

A good criteria for your level of trust in someone is whether you would recommend them and whether you are prepared to put your own reputation on the line when doing so. In your network, can you say
“I know a lawyer who specializes in xyz. I know him well, I have seen how he works and, in your situation, I would trust him to do a great job. Give him a call and tell him I thought he would be the ideal person for you.” ?

As a people developer, a question I ask is “How can you move beyond the stage of just understanding someone to trusting them?” The answer is by working with them, by having a shared positive experience with them. When you can say “My lawyer did a fantastic job for me when I had a problem with xyz; I cannot recommend him highly enough” you are communicating a high level of trust.

What’s the connection between this model and employee development? In bquest, our goal is to help clients achieve ‘deep’ learning, not just learning ‘surface level’ techniques and methods. Only when you deeply understand something can you make full use of it and adapt it to deal with new situations and make significant changes and improvements. But deep learning at times means challenging deeply held beliefs and long-held mental models, which some people with years of learning under their belt
feel uncomfortable with. So, to go there requires a lot of trust between bquest coach and client.

For bquest therefore, our relationship with a client is a trusting partnership. We make sure the relationship is a positive shared learning and development experience for both of us.

Share

Seeing the need for employee development

As a trained and experienced business coach, I fully accept the view that I should not tell nor persuade the client who is being coached what to do, but that it is the client who should set the agenda and who should find the answers to their questions. The goal of the coach is to enable or empower the client so they are equipped – and motivated – to sort out their own problems in the manner of their choosing. But what happens if I, the coach, see a problem in the client’s behaviours that the client doesn’t? Do I have a responsibility to point this out to them?
The simple answer is usually for the coach to find a suitable time and way to ask questions like “When other people see you doing (‘bad’) behaviour, what do they then say and do?” In this way, the client can get the feedback they need to make choices about whether to change those behaviours. Only if the (‘bad’) behaviour is being shown in the coaching session can the coach give direct feedback and say “When you do (‘bad’) behaviour with me, I feel…. whatever.”
On the bquest program, we often see clients who are not initially very self-aware and they identify their development needs inaccurately. They may not have identified a need because they are not aware of it. They may be ‘blind’ to it (remember the Johari window). Or they may downplay its significance - “My team are tough enough to put up with me when I shout at them and abuse them.” Or they may have identified a situation which they would like to perform better in, but their diagnosis of the ‘problem’ is inaccurate and they set out to develop the wrong competencies.

With bquest, it is part of our agreement with clients that we have a responsibility to point out behaviours we suspect may not appropriate to a situation. We go back to Richard Boyatzis and George Klemp, the people in McBer who kickstarted all the work done on competencies in the last 30 years. who said that competency development begins with the recognition of the competencies in action and then understanding their role in effective performance. Our skill in bquest is helping the client to achieve recognition and understanding in a way that they accept. After all, a lot of people don’t like to hear ‘bad’ news, however necessary it is, especially if they are paying for it!

Share