Skip to main content

Jack Bauer's Management Secrets #1: I need it!

This is part one of a series of posts unlocking the valuable management secrets and strategies of 24's best agent: Jack Bauer. What is it that makes Jack successful? Sure, he's a great shot, he's been trained in all sorts of combat, sometimes he's lucky, clearly he's very driven.

But what really makes Jack a winner are his managament skills. Jack successfully motivates and manages, he handles superiors and subordinates, he gains people's trust, he has high integrity, he's a team player and ultimately he helps his team win time and again.

These posts look into Jack's management secrets. In part one I look out how Jack creates a sense of urgency while at the same time binding his team together towards a common goal. And he does all of that with a simple phrase: 'I need it!'.

I need it!

Jack doesn't say "I want this done" or "You must do this", he tells his team members (especially, Chloe) "I need it!". Why's that so important?

Firstly, by saying "I need it!" Jack makes his request personal. It's not a simple matter of something having to be done, it's that Jack (in his position of authority) needs the task completed for his own success. That's an important technique because it binds the manager's success along with the subordinate's success. If the person Jack is asking successfully completes the task they can see clearly that they've been successful personally, made the manager successful and by extension made the entire team more successful.

It also gives the employee a sense of empowerment and reason for their work. Since they know the manager needs the task completed, instead of merely wanting it done, the employee feels that the task is worth accomplishing.

Contrast that with a classic pointy-haired manager who spits out orders without being personally involved. An employee just sees the manager as a conduit for orders that probably came from above them. There's no sense that the manager is in any way involved in the decision making process, or even cares about the outcome.

Of course, it's not enough for Jack to say that he needs it, he needs to provide justification and clarity. He does this in two ways: he briefly explains why, and he sets a clear time frame. Because he's built trust with the team (a subject of a separate post) he can briefly explain his reasons without fuss, and tell the employee when the task must be completed.

Here's Jack speaking to Chloe in Season 5:

Chloe, listen to me, I have a thumb drive that's going to help us find the sentox. I need you to data mine the files.

He makes a clear request 'data mine the files', he gives a clear reason 'going to help us find the sentox' and states that he needs it. In this case he doesn't state when, because it's clear from the context that 'when' is 'asap'.

So, how can you apply Jack's "I need it!" technique in the work place? You just need to remember the three step C T U plan whenever setting a task:

C is for Context: explain the context of the request so it's clear why you are asking for a particular task to be completed.
T is for Timeframe: make sure that the expected deadline or timeframe is clearly stated.
U is for Urgency: communicate your sense of urgency by specifying that this is something you need.


Barry Kelly said…
Jack Bauer is a facist! :)
Sean said…
Hey you're exactly right. JB is a top flight manager for the 21st century.
The Jack Sack said…
That's fantastic! What a goofy yet accurate post.
Laurie said…
Jack gets things done period!
Laurie said…
jack gets things done he doesn't waste time waiting on other people

Popular posts from this blog

How to write a successful blog post

First, a quick clarification of 'successful'. In this instance, I mean a blog post that receives a large number of page views. For my, little blog the most successful post ever got almost 57,000 page views. Not a lot by some other standards, but I was pretty happy about it. Looking at the top 10 blog posts (by page views) on my site, I've tried to distill some wisdom about what made them successful. Your blog posting mileage may vary. 1. Avoid using the passive voice The Microsoft Word grammar checker has probably been telling you this for years, but the passive voice excludes the people involved in your blog post. And that includes you, the author, and the reader. By using personal pronouns like I, you and we, you will include the reader in your blog post. When I first started this blog I avoid using "I" because I thought I was being narcissistic. But we all like to read about other people, people help anchor a story in reality. Without people your bl

Your last name contains invalid characters

My last name is "Graham-Cumming". But here's a typical form response when I enter it: Does the web site have any idea how rude it is to claim that my last name contains invalid characters? Clearly not. What they actually meant is: our web site will not accept that hyphen in your last name. But do they say that? No, of course not. They decide to shove in my face the claim that there's something wrong with my name. There's nothing wrong with my name, just as there's nothing wrong with someone whose first name is Jean-Marie, or someone whose last name is O'Reilly. What is wrong is that way this is being handled. If the system can't cope with non-letters and spaces it needs to say that. How about the following error message: Our system is unable to process last names that contain non-letters, please replace them with spaces. Don't blame me for having a last name that your system doesn't like, whose fault is that? Saying "Your

The Elevator Button Problem

User interface design is hard. It's hard because people perceive apparently simple things very differently. For example, take a look at this interface to an elevator: From flickr Now imagine the following situation. You are on the third floor of this building and you wish to go to the tenth. The elevator is on the fifth floor and there's an indicator that tells you where it is. Which button do you press? Most people probably say: "press up" since they want to go up. Not long ago I watched someone do the opposite and questioned them about their behavior. They said: "well the elevator is on the fifth floor and I am on the third, so I want it to come down to me". Much can be learnt about the design of user interfaces by considering this, apparently, simple interface. If you think about the elevator button problem you'll find that something so simple has hidden depths. How do people learn about elevator calling? What's the right amount of