Time for a rethink of what we mean by talent?
Related content
Replies (1)
Please login or register to join the discussion.
This is a mantra that should be solidly implanted into every manager, every HR person, every union or staff association rep.
We try and compartmentalise people as it makes it feel easier to generalise. We use Myers-Briggs or Belbin to try and separate people into simplistic high-level groups, but we're still trying to put nice, clean, simple labels on incredibly complex and messy creatures. Worse still, we identify the labels, and then don't do anything based on them. I've seen various companies go through at least one of the major labelling exercises, and then make no changes to team structure based on it. It always seemed that simply knowing what the label was for each person was regarded as an adequate outcome for the exercise. I've never seen a company have the courage of their convictions and rebuild teams around the newly-identified labels.
And 'talent' is such a flexible word. Do you want someone super-smart, but also super-brittle? Or would you trade a few points of IQ for a few more social skills? Often, the greater the talent, the greater the baggage that comes with it. You might be happy for your high-performers to be high-maintenance, but there's a reason we use 'prima donna' as a perjorative term these days. There are certain fields, such as sport and the arts, where it's considered worthwhile to pander to the whims of the top stars, but the case for doing so in a more normal business environment seems a lot less clear to me.
I've seen it in action - a programming team had a member who was genuinely brilliant. He was the go-to guy for the nastiest bugs, and when they had to have a solution -now-. Which would have been wonderful, had he not also embodied many of the stereotypical traits of the hardcore geek. He had poor social skills, and questionable personal hygiene. He would say inappropriate things and claim refuge in honesty ("Well, she *is* fat...!"). He would take pleasure in ridiculing someone if he found an error in their work, or if they went to him for help with a problem. He was shielded from a lot of the fallout that would otherwise have come his way by his manager, who saw in him an extremely valuable resource. He did solve a lot of problems and he was never happier than when he was cranking out code, or ferreting through it looking for bugs. But nobody liked him. Not even the manager who took the flak for him. He was the antithesis of a team player.
Was he talented? Along certain very narrow lines, extremely so. But I was never of the opinion that the advantages outweighed the disadvantages.