Competency Frameworks; The Good, the Bad and the Ugly

Effective use of competency frameworks providesrange of behaviours, skills and knowledge required to
employees with a clearly-defined set of personalcomplete the tasks undertaken by the organisation or
development objectives and managers with asection in question.The difference between behaviour
consistent measurement tool that could be usedskills and knowledge can be examined through
across geographical, cultural and work boundaries.Theoccupations which require the driving of a motor
concept is simple. To complete any task, people needvehicle.Firstly, a courier driver requires the behaviour,
to have the behaviour, skills and knowledge toskills and knowledge as follows.Behaviour; the driver
undertake the task. Defining the behaviour, skills andmust be courteous, punctual and not too much of a
knowledge (competence) to undertake a set of tasksboy racer in the traffic as we don't want to
(a job) and measuring the competence of peopleaccumulate fines. Skills; must be able to drive a car,
allows managers and employees to understand theevidenced by a licence, read a street directory and
gap between desired and demonstrated competenceable to use a hand held computer to access orders,
and develop a plan to close the gap.Manymake payments etc. Knowledge; must know the road
organisations however fail in their attempts to build arules, again evidenced by a licence, our delivery and
framework to proactively manage competencies.Thecredit terms and our returns policy.Secondly, let us
major reason for failure is that competenceexamine another driver, a specific one whose name is
frameworks are developed and implemented with noMichael Schumacher. Herr Schumacher needs to have
clear business purpose in mind. Without a businessthe following skills behaviour and knowledge.Behaviour;
purpose, there is no objective on which to base designhas ice cool nerves, steely determination and
decisions as the framework is built. The resultantconfidence in his ability to the point of arrogance. Skills;
design is usually flawed, serving too many mastersa much higher level of driving skill than our courier
and is discontinued after a year or two ofdriver, a licence will not suffice as evidence, able to
use.Competency development frameworks built with achange gears by pressing buttons and have reflexes
clear business purpose in mind suffer from other fatalmeasured in milliseconds. Knowledge; must know the
flaws limiting the use of and belief in the framework.racing line of every Grand Prix track, the relationship
Frameworks built which confuse tasks withbetween track, tyre and suspension set up.Designing a
competency are usually complex and difficult toframework with competencies defined at different
administer and therefore are difficult to communicatelevels, eg driving ability in the above example, allows a
to employees.For a framework to be successful, notrange of jobs to be described using the same
only do managers need to believe that businesscompetency set. Typically, a competency framework
performance will improve, but employees also need towill have between three and five levels of each
believe that the framework, especially thecompetency defined.If significantly more than twelve
measurement of competence, is fair and transparent.Acompetencies need to be defined to cover the range
common fault of competency frameworks is that theyof jobs in an organisation, it is better to develop
confuse competence with task. Tasks are betterseparate linked frameworks. The linkage comes
positioned in the job description. Frameworks whichthrough the behaviours and some of the skills.
confuse tasks with competencies generally haveBehaviours are closely related to the values and
between forty and fifty "competencies" described.organisation desires and therefore the requirement is
Each job description tends to have between twentylikely to be the same in different functions. Some skills
and thirty competencies to be evaluated in anwill also be the same, for example, communication.
employee.In the early days of the internet, beforeHowever, the knowledge requirement of different
people were careful about what they put in the publicfunctions is normally quite different.Good competency
domain, I stumbled across NASA's competencyframeworks will be easy to administer, easy to
framework. It was huge with hundreds of listedunderstand and built for a business purpose. Bad
"competencies" and resembling a list of all of the taskscompetency frameworks will confuse competency
that astronauts and the support staff do. It wasand task and be difficult to administer and understand
doomed to fail to deliver any business purpose otherand will have been built without an obvious business
than being a repository from which to write the "tasks"purpose.Kevin Dwyer is Director of Change Factory.
part of job descriptions.Competency developmentChange Factory helps organisations who do do not like
frameworks should have about twelve competenciestheir business outcomes to get better outcomes by
to describe and measure to be successful in the longchanging people's behaviour. Businesses we help have
term. Any more makes them difficult to administer andgreater clarity of purpose and ability to achieve their
communicate. The competencies need to cover thedesired business outcomes.