raganwald
(This is a snapshot of my old weblog. New posts and selected republished essays can be found at raganwald.com.)

Monday, August 23, 2004
  Surprize Quiz!


Try to answer this question honestly, without trying to "reverse engineer" the correct answer. This isn't a job interview, so you gain the most if you answer correctly and learn something about yourself:
You have just been promoted to head of an important department in your organization. The previous head has been transferred to an equivalent position in a less important department. Your understanding of the reason for the move is that the performance of the department as a whole has been mediocre. There have not been any glaring deficiencies, just a perception of the department as so-so rather than very good. Your charge is to shape up the department. Results are expected quickly. Rate the quality of the following strategies for succeeding at your new position.
  1. Always delegate to the most junior person who can be trusted with the task. This gives juniors an opportunity to learn and develop, raising the overall competence of the group.
  2. Give your superiors frequent progress reports. This makes your star shine brightly, obtaining support from stakeholders. More importantly, frequent reports are opportunities for frequent feedback, keeping the group's direction in harmony with the organization's goals.
  3. Announce a major reorganization of the department that includes getting rid of whomever you believe to be "dead wood." Letting go of "C" players is harsh, but it's just as important as hiring people who are "smart" and "get things done." The team is only as strong as the weakest link.
  4. Concentrate more on your people than on the tasks to be done. Process, process, process. Experienced people know how to do their jobs, but the performance of the group depends on motivating the team and process improvements.
  5. Make people feel completely responsible for their work. If no-one is accountable for results, there's no accounting for the results you'll obtain :-)
This question was crafted by Richard Wagner, a psychologist at Florida State University (I have added the italicized points to the strategies). I found the question in The Talent Myth, an excellent article by Malcolm Gladwell (author of The Tipping Point) on the relationship between talent and job performance.

Gladwell's explanation of the results, plus a comparison to my experience with Agile practices, can be found in Quiz Answers, plus "Instilling Responsibility".

Labels:

 

Comments on “Surprize Quiz!:
I selected E), but couldn't wait for your post so I went ahead and read the article. Turns out I might be a good manager... but of course that wasn't the point of that article.

The article was quite interesting. Still, the conclusions are not all that surprising. I agree that talent should always be rewarded, but I cannot imagine rewarding talent that doesn't perform.

If you are running a dinner theatre production of Hamlet with a cast of Tony award winners, would you give the talent a raise if they never perform the show? Or worse, they went on stage and performed MacBeth?

andre
 
It's funny that you chose a theatrical example! Most of my management experience (well, successful experience, anyway) is in theatre. My inspiration as a director was William Ball. One of his techniques in dealing with actors who don't "perform" (ouch!) is to give them more attention, more responsibility. In particular, he insists that you should never give negative feedback - only positive. Sounds wacky, but it actually works. People very quickly learn that "lack of positive" means "negative." Works for kids too, speaking as a parent.

In short, I disagree with your assessment that "rewarding talent that doesn't perform" is a bad idea. Sometimes it's precisely what you need to do to motivate people.
 




<< Home
Reg Braithwaite


Recent Writing
Homoiconic Technical Writing / raganwald.posterous.com

Books
What I‘ve Learned From Failure / Kestrels, Quirky Birds, and Hopeless Egocentricity

Share
rewrite_rails / andand / unfold.rb / string_to_proc.rb / dsl_and_let.rb / comprehension.rb / lazy_lists.rb

Beauty
IS-STRICTLY-EQUIVALENT-TO-A / Spaghetti-Western Coding / Golf is a good program spoiled / Programming conventions as signals / Not all functions should be object methods

The Not So Big Software Design / Writing programs for people to read / Why Why Functional Programming Matters Matters / But Y would I want to do a thing like this?

Work
The single most important thing you must do to improve your programming career / The Naïve Approach to Hiring People / No Disrespect / Take control of your interview / Three tips for getting a job through a recruiter / My favourite interview question

Management
Exception Handling in Software Development / What if powerful languages and idioms only work for small teams? / Bricks / Which theory fits the evidence? / Still failing, still learning / What I’ve learned from failure

Notation
The unary ampersand in Ruby / (1..100).inject(&:+) / The challenge of teaching yourself a programming language / The significance of the meta-circular interpreter / Block-Structured Javascript / Haskell, Ruby and Infinity / Closures and Higher-Order Functions

Opinion
Why Apple is more expensive than Amazon / Why we are the biggest obstacles to our own growth / Is software the documentation of business process mistakes? / We have lost control of the apparatus / What I’ve Learned From Sales I, II, III

Whimsey
The Narcissism of Small Code Differences / Billy Martin’s Technique for Managing his Manager / Three stories about The Tao / Programming Language Stories / Why You Need a Degree to Work For BigCo

History
06/04 / 07/04 / 08/04 / 09/04 / 10/04 / 11/04 / 12/04 / 01/05 / 02/05 / 03/05 / 04/05 / 06/05 / 07/05 / 08/05 / 09/05 / 10/05 / 11/05 / 01/06 / 02/06 / 03/06 / 04/06 / 05/06 / 06/06 / 07/06 / 08/06 / 09/06 / 10/06 / 11/06 / 12/06 / 01/07 / 02/07 / 03/07 / 04/07 / 05/07 / 06/07 / 07/07 / 08/07 / 09/07 / 10/07 / 11/07 / 12/07 / 01/08 / 02/08 / 03/08 / 04/08 / 05/08 / 06/08 / 07/08 /