Friday 29 July 2011

What and How in order to Why - 2 Stage Development Planning



I've spent much of the last month working with various managers at all levels in a business to focus on development planning of their employees.

Much of the time, it is seen as a simple box ticking exercise in order to 'fill out the paperwork'.  The reason for development seems to have been forgotten by all but those who are actively focussed on progression and promotion.  Of course, everyone can develop and improve.

Stage 1

Drivers for your Development
Begin with the outcome in mind. The goal is the activity in which you are trying to deliver a result.

What you need in order to deliver that goal is both the technical skills required for that activity and more importantly the behavioural competencies to help you be more effective in delivering that great result.

Your development should focus on satisfying a need for one or the other of these things, either the technical skill or the competency to help you make a success of it.

This is the first stage; identifying why you are doing it.

Stage 2

Stage two is to figure out the mechanism in which you are going to 'develop'.  This is the second stumbling block to people creating a good development plan.  A simple thought process to this however is to follow the model What and How in order to Why.

What?

What is the actual need, the specific thing that is required?  Is it a strength that you want to develop to greater effect (yes, development doesn't need to be focussed on a weakness) or perhaps plug a gap?

Is it a skill required or a competence?

Some examples might be develop presentation skills or learn how to type.


These are not the activities themselves (the How) and they are not the rationalle for doing it (the Why) but they are an essential part.





How?
How really starts to get into the interesting part which requires you to truly get into the specifics of how this can be achieved.  This will likely be more than one action step.

For those followers of GTD, this taps into the idea of a 'Next Action'; what actually needs to happen to turn the 'what' into reality.

Continuing the examples above, it could be read Garr Reynold's book Presentation Zen or complete tutorial from online touch typing class.

Why?

Lastly, the Why.  This actually brings us all the way back to the starting point in Stage 1 of beginning with the outcome in mind.  What goal are you ultimately trying to reach some kind of output on?

When you couple these three things with the transition phrase 'in order to' then you get:



Develop presentation skills by reading Garr Reynold's book Presentation Zen in order to have a more effective communication style when pitching ideas to senior management.
or
Learn how to type by completing the tutorial from the online touch typing class in order to become more efficient in creating monthly technical reports.

Now these are relative simple development plans (if only skills and competencies could be gained so easily) but I hope they give you the idea.

Development planning does not need to be complicated but you do need to step back and get back to basics.  Why don't you try this two stage model with something you want to achieve this month.  Good Luck.

Please see my website at www.managingforthefirsttime.com for more techniques, tips and advice on this topic and others.

('What' photo by judepics, 'How' photo by ivanwalsh, 'Why' photo by theeerin via flickr used under a creative Commons Licence)

Wednesday 27 July 2011

You're not really a leader until...

I was recently watching the film "The Core" when I heard this dialogue.


Col. Robert Iverson: Being a leader isn't about ability. It's about responsibility.
Maj. Rebecca Childs: Got it, sir.
Col. Robert Iverson: No you don't, Beck. I mean, you're not just responsible for the good ones. You've got to be responsible for the bad ones. You've got to be ready to make the shitty call.
Maj. Rebecca Childs: What makes you think I'm not?
Col. Robert Iverson: Because you're so damn good. You haven't hit anything you couldn't beat. I mean, hell, you were the one who figured out how to save the space shuttle. You made me, you made the rest of NASA just look like an ass. It's just you're used to winning... and you're not really a leader until you've lost.

Couldn't have put it better myself; so I won't.

Please see my website at www.managingforthefirsttime.com for more techniques, tips and advice on this topic and others.

Wednesday 20 July 2011

Audits - Prepare Yourself

I’m always slightly amused by the fear that comes over everyone when they are told an audit is due.

The issue is that we are all sometimes guilty of only using the frameworks audited against every year (or however often they are audited) in the month the audit is due. You go into the cabinet and dust off the folder of materials from last time and then update; making it up as best as you can to try and score the most points.

Sound familiar?  Don't you want to get the best score?

Begin with the outcome in mind. It is worth remembering an audit’s purpose.

The definition of the word is to conduct a systematic review of and its origin is from late middle english from the Latin auditushearing’ deriving from audirehear’.

It’s this point that staggers me every time, the fact that (unless your job depends on a certain ‘score’; and how often does that actually happen) the value of the audit is in your listening to the feedback.

Don’t see the one day audit as something in which you have to justify your team’s processes and performance against; see it as your own private consultant who has just spent eight hours looking for ways to help you improve what you and your team does.

Don’t fear an audit, embrace it.

Please see my website at www.managingforthefirsttime.com for more techniques, tips and advice on this topic and others.

(Photo by DaveFayram via flickr used under a creative Commons Licence)

Wednesday 13 July 2011

Greater than the sum of its parts

I recently posted on another blog, some thoughts about ‘Diversity and Inclusion’. I had also talked recently about embracing difference in your team to get the best from your team.

The pitfall from any initiative in regards to diversity and inclusion is that diversity is often the primary (or initial) focus rather than Inclusion.

These are not interchangeable words in the same way that thunder and lightning are related and linked but are different things.

If we start with the outcome in mind, we are seeking to generate and support a higher performing team at every level (based on a varied group that challenges and innovates; and most importantly, is truly engaged). Inclusion can be seen as a definition of what this team looks and acts like from a behaviour or action point of view.

Diversity therefore is an extension of the described differences, the constituent elements or labels to define the differing pieces of the team.

A greater focus on the Inclusion piece might provide some desire to sustain this change rather than simply focussing on the diverse elements within.

When you eat a great meal, the ingredients are important but you don’t focus only on them. When you enjoy a great meal, you focus on the experience of it and the way it worked in harmony together to be greater than the sum of its parts.

Always keep the outcome in mind.

Please see my website at www.managingforthefirsttime.com for more techniques, tips and advice on this topic and others.


(Photo by jlastras via flickr used under a creative Commons Licence)

Wednesday 6 July 2011

Confident and Humble

If you are going to succeed as a manager then you clearly need be seen to be confident and sure in your thoughts and actions (even if you do not feel super confident inside).

Your strength in tough times gives a crutch to your team when they need to know they are on the right path.

However, take caution in ensuring that your confidence does not become overbearing and turn into perceived arrogance.

One way to do this is by ensuring that you constantly challenge yourself to be humble.  Taking the word's definition from the Oxford Dictionary, "offered with or affected by a modest estimate of one's importance"

What a great way to lead.  The strength that the team looks for will simply come from your character rather than how you try and 'show' yourself to be.

I believe that confidence is demonstrating that you respect yourself and coupling this with a humble nature in which you respect others as equals is a powerful leadership combination.

Those that think they are important and act as such, seldom are.

Those that don't seem to be the more content, relaxed, self assured, interested and ultimately more genuine managers and leaders.

How do you want to portray yourself?

Please see my website at
www.managingforthefirsttime.com for more techniques, tips and advice on this topic and others.

(Photo by
Wonderlane via flickr used under a creative Commons Licence)

Friday 1 July 2011

Inheriting a Team

You'll always be told to recruit well; matching the skills of the person to the job.  But what about the real world where you 'inherit a team' and the people within it. 

Matching the required skills to the people might not cover all the bases required. The backgrounds of the team members might be varied and in some cases a little "out there". You need to embrace the fact that that diversity is in fact healthy rather than something to fix or change. Don't necessarily try and mould the team, why not try and mould the team's output (as much as possible) to match their skills.

Get to know your staff so that when you need to make that hard call to get them doing something they might find hard or uncomfortable, they trust that you have understood them and have taken that into account the best you can.

You've got to earn trust so you need to start now to build it for when you really need it.

What do you really know about your employees?  Why don't you try and find out something new about each one of them today.


Please see my website at www.managingforthefirsttime.com for more techniques, tips and advice on this topic and others.