• The Department of Doing

    Jeff
    Pfeffer and I published The Knowing-Doing
    Gap: How Smart Companies Turn Knowledge Into Action
    about 7 years ago. It is a book about why smart companies and
    people sometimes don’t do things that they know they should, and how to
    overcome impediments to organizational action including using smart talk as a
    substitute for organizational action, precedent, fear, flawed metrics and
    incentives, and dysfunctional competition. We’ve both been heartened by people
    who have contacted us over the years to tell us how they have used the ideas to
    spur action.  After all, as we say in the
    book, just reading and talking about getting things done isn’t enough, you
    actually have to do it.

    As
    such, I was delighted do get an e-mail from Richard Hollingum, who runs a
    company called The Department of Doing
    based in Devonport, New Zealand. Richard
    wrote me,“I set up the Department of Doing 6 years ago
    and we work with some amazing clients all over the world, and preach the power
    of doing. As they say "Doing requires Doing Something". Your book
    fits so much with what we stand for. I spent too many years sitting on
    committees, board meetings where decisions were made, consensus was agreed and
    still nothing happened. So out of sheer frustration I set up DOD.It is the best
    thing ever did. So liberating, so much fun and makes the hard work all the more
    rewarding.”

    This
    is music to my ears and I am looking forward to learning more about his company
    when he visits California
    in March for the TED Conference. Check out the attached “The Directives of
    Doing” that Richard sent me, a code of conduct for people in his company.
    Wonderful stuff, like, Never say “That’s not my job.” The
    business world is full of organizers, planners, facilitators, and managers.  It doesn’t need any more. At The Department of
    Doing, we only want doers. We are about making stuff, and making stuff happen.
    We are about taking client’s problems and making them go away. That’s or job.”

    P.S.
    I also loved Richard’s reply when I wrote him back that I would be delighted to
    meet with him: “You’re on!!! Consider it Done. Let’s
    talk real soon. Take care. Gotta dash, real busy doing.
    He sounds like quite
    character!

    Download dod_leaflet_stamp_directives.pdf

  • The No Asshole Rule: Early Reviews

    My publisher was kind enough — and I believe wise enough — to send out about 35 advance copies of The No Asshole Rule to influential bloggers, and in fact got these copies to bloggers at least a month before anyone from the traditional press.  A couple of early reviews have already appeared, both of which are thoughtful and supportive.  Check out what Brayden King and Kent Blumberg have to say.  I especially like Kent’s comment — I guess it is more of a question — where he wonders whether the book should have been called "The One Asshole Rule" rather than "The No Asshole Rule,"  a good question (if you read the book), but it is too late to change now (Thank goodness!  There is a point where every author has to let a book go, and I am past it… or they never get done.).

    Brayden and Kent: Thanks for your thoughtful comments.

  • Teams as a Double-Edged Sword

    I’ve
    been really impressed with the quality of the comments and the constructive
    debate that was sparked by my last post on Fighting
    the War for Talent Right.
    As I went
    back and read the post and the smart comments, I realized that I had
    unwittingly implied a dangerous half-truth: That doing things in a tight team
    is just always better than having them done by a collection of individuals who throw their work into some kind of common “pot,” but don’t interact much.
    Sociologists talk about this as the difference between a group with strong
    “interdependence” versus one that has little or none at all.

    If
    you look at research on teams by social psychologists and organizational
    researchers it turns out that Freud got it right about 100 years ago: Groups
    bring out the best and worst in human beings. One my mentors is J.Richard Hackman, who has spent about 40 years studying
    what drives group effectiveness. I
    worked on a team effectiveness project that Richard led in graduate school,
    that resulted in a book he edited called
    Groups That Work
    , and for a complete and more recent summary of his
    perspective see his Leading
    Teams.
      About 10 years ago, I recall
    Richard expressing annoyance because the then best-seller
    The Wisdom of Teams
    was being used as a justification for herding people
    into tight-knit teams, on theory that teams outperform individuals.

    It
    turns out that if you look at team effectiveness research, the lesson is that if you can get the
    conditions right, teams will outperform a loss collection of individuals on a wide range of tasks. But
    there is also striking evidence that a bad team will bring out the worst in
    people as well, and if you can’t get the conditions right it, it might be
    better to organize them along the lines of a group dental practice, where they
    share the same building, perhaps a common receptionist and a few other
    resources, and each do their own thing. A similar lesson emerges from experimental research on the differences
    between decisions made in groups versus individuals. A series of studies show
    that mean level of decision quality is about the same, but there is much wider
    variance in decision quality in groups
    compared to individuals. In other words,
    groups either to a really good or a really bad job of making decisions – I
    believe that Max Bazerman’s book on Managerial
    Decision-Making
    reviews this research.

    The
    upshot of this research is that if you have well-functioning team – or if you
    want to hire one, to return to my last post – then it is worth doing all you
    can to keep them together and to building trust and a shared point of view. But
    if you have bad group, where peopleagree that few things are worth doing
    well, don’t believe in learning, is rife with fear and so on, the best you can
    do (if you can’t disband them… sometimes a wise move) might be to reduce the
    interdependence between them, to organize their work so they don’t see much of
    each other, don’t have to work closely on tasks, and – applying the group
    dental practice model – at least aren’t dragged down by each other.


    Now, I confess, this is not the optimal
    approach, and I love talking about great teams and top performance and
    all that, but the fact is, there are times when –- at least for the forseeable future – it is a great
    victory if you can move a team from being downright bad to being simply
    mediocre. The other implication of this
    research is that if you are leading – or part of – and effective “group dental
    practice” that taking steps to tighten the links between people carries a
    high risk of making things worse rather than better, especially if you don’t have the
    resources, time, and power to do it right.

    So,
    teams aren’t a panacea; they are more like magnifying glasses or multipliers
    that bring out the best – and worst – in people.

    P.S. If you
    want to see a strong argument that
    individuals matter more than teams or organizations, see Locke, Edwin, A.,
    Diana Tirnauer, Quinetta Roberson, Barry Goldman, Michael E, Latham, and
    Elizabeth Weldon (2001). The
    importance of the individual in the age of groupism
    . In Marlene E. Tuner’s
    Groups at Work.Mahwaw, NJ:
    Earlbaum, 501-528. We try to show that this the authors take their argument too far in  Hard Facts, but
    this article is charming and well-argued.

     

  • Fight the War for Talent Right: Bring Aboard Intact Teams and Networks

    Tom
    Davenport and Larry Prusak wrote a wonderful book a couple years back that is
    called What’s
    The Big Idea
    .
    One of their most
    clever observations was that, if you start digging into the waves of management
    fads, you can see that the emphasis tends to shift among three different
    themes: efficiency, innovation, and people.  They showed how, even though all three themes
    matter to all organizations, at any given time, one and sometimes two of these
    themes seems to be in vogue, while the other one or two are in the background.

    If
    you think back over the past 8 or 9 years, it works pretty well. So, after the
    dot.com bust it was all efficiency all the time – layoffs and outsourcing. Then it was innovation and innovation is
    still hot (but doesn’t feel quite as hot as it did about 6 months ago), and I
    am starting to see signs – look at the cover of the current Economist – that people are starting to move toward center stage.

    Econ

     If
    you read this issue of The Economist,
    if you consider standard HR practices for recruiting, hiring, evaluating, and
    compensating employees, if you listen to most HR consulting firms, and if
    you look at how employee records are organized in enterprise software you will
    see that the – usually unspoken but pervasive – assumption is that a focus on
    people means a focus in hiring the most talented individuals. Indeed, talent is the word people like to use
    talk about good people, a word that conjures up images of superstar actors and
    athletes. Certainly, having talented
    individuals is important. But focusing on individuals alone – as the HR mindset
    seems to do, in an automatic mindless way without ever questioning the
    assumption – is a dangerous half-truth. It blinds managers and executives to a
    growing body of literature that shows performance is heavily dependent on
    having people who are experienced at working together and who work together for
    a long time. Just look at that Economist’s
    cover, at how implies a search for that lone beautiful pearl, one that is fixed
    in its hardness and beauty. This analogy
    mirrors the talent mindset and its fixation on individuals.

    I
    thought of this when Boris
    Groysberg
    sent me a Harvard Business
    Review
    article that he published earlier in the year with Andrew McLean and
    Nitin Nohria.  It is called “Are Leaders
    Portable,” and it examines what happened to 20 former General Electric
    executives who were hired as CEOs between 1989 and 2001. The article focuses on
    what they call annualized abnormal returns. In English, this means: How did the
    company do in the three years after the new CEO from GE was hired compared to
    market as a whole and similar firms?  The
    main finding of the article – which I don’t think the article quite comes out
    and says – is that these GE CEOs did a lot of damage, perhaps more harm than good. For example, they show that the 11 CEOs who
    “matched” their new companies were associated with a 14.1% positive return,
    while the 9 who didn’t match were associated with a -39.8% return. I actually doubt that the CEO’s alone had
    this much effect, as more controlled research shows that leaders of large firms
    usually have much weaker
    effects on performance
    , but the number of firms that apparently weren’t
    saved by an executive riding in from GE is instructive.

    One
    of the most interesting findings – and a challenge to HR’s obsession with practices
    aimed at individuals rather than teams or networks – was that GE executives who
    brought along 3 or more GE alumni to join their teams had “annualized abnormal
    returns” of 15.7% above average; while those that hired one or none from GE had
    -16.7%. Groysberg and his colleagues
    call this past experience working together “relationship human capital,”
    horrible language from economics. Other researchers call it “prior joint
    experience,” which isn’t much better. But whatever you call it, while HR practices turn attention to individual
    stars, study after study shows when people have experience working together –
    and have learned who knows what, how to read those little signals that people
    send off, and can communicate ideas quickly and efficiently – their teams and
    organizations perform better. The list
    of studies is long and uncover consistent findings. My Stanford colleague
    Kathleen Eisenhardt
    found – in a large longitudinal study of new
    semiconductor firms – that those firms that were founded by people who had
    worked together before were more likely to survive and be financially
    successful, and such positive effects got stronger as the firms got older. Exhibit one in this industry is Intel, which
    was founded by the “traitorous eight,” a group of executives who fled from
    Nobel Prize winner (and racist) William Shockley to start their own firm, which
    included Gordon Moore and Andy Grove. Similar findings has been replicated in studies of start-ups funded by
    venture capital firms, surgical teams that do coronary bypasses, airplane
    cockpit crews, and product development teams. The only study I know that challenges this pattern showed that, after
    about 4 or 5 years of working together, the productivity of product development
    teams starts to slow if they don’t start moving out some old members and moving
    in some new ones.  But productivity gets
    higher and higher in these teams every year until about the fifth year.

    The
    implication of this research is pretty clear and shows the limits of modern HR
    practices, assumptions, and even the enterprise software systems that they
    use. If you are going to hire some
    “talent,” don’t focus on just landing that lone star – focus on hiring as much
    of his or her team, or network, as possible. You win the war for talent by bringing aboard talented sets of people, not
    talented solo acts. Indeed, if you recall my earlier posting about the hazards
    of mergers and acquisitions, I showed how the
    typical merger fails,
    but I used the example of Cisco to show how when the
    focus is on acquiring small companies and on going through great effort to
    weave the people into the culture – and I would add now, keeping their
    relationships in place – it can be quite effective. Some of the most effective companies – Google
    appears to be an example – do this informally. People who are hired by Google are often pulled from intertwined
    networks and groups that have worked together in the past. In fact, speaking of Google, if you look at
    the history of the company, the two founders started working together when they
    were doctoral students at Stanford, as did the founders of Yahoo! Paul Allen and Bill Gates met each other –
    and started working on computer stuff – in high school, as did Steve Wozniak
    and Steve Jobs.

    Call
    it whatever you want, but as the war for talent seems to be heating up again,
    companies that fight it right will spend less time looking for solo stars and
    more time looking for dynamic duos, teams, and networks of people that have
    worked together in the past and want to work together more in the future.  And perhaps it is time for modern HR practices
    to catch-up with the evidence.

  • Alinea: A Weird Idea That Works

    As I was waiting around the British Air lounge in San Francisco on my way to Germany, I read a story in the October issue of Gourmet Magazine that pronounced Alinea in Chicago as the best restaurant in the U.S.  It brought back memories of the meal that I had there with David Kelley of IDEO and d.school fame, just about a year ago.  I am not sure it is the best place I ever ate, but they did create an astounding experience and were without pretension at all.  Our little room — with about  5 tables — not only had a couple of dedicated waiters it also had its own sommelier, who explained each wine we had. And it really was weird food, As David put it, if he would give Alinea a 10 for his weirdest meal, his next next weirdest meal would be no more than a 6.  How weird? Well, I saved the menu from October 6th 2005 (which they say changes constantly), and the 12 courses (each just two or three bites) started with what described as olive oil — but was domino-sized disc frozen at 100 degrees below zero.  I also recall a lobster Cheeto (almost as good as regular Cheeto) that came with one dish, and the final dish was a spoonful of dry caramel.  They had things like fish, lamb, pork and bison (which was excellent), each weird and delightful in its own way. The greatest thing about the experience was the staff, who — with great knowledge and just the right touch of silliness — gave us a mini-lecture about what we were eating, how it was prepared, and how to eat it for each course(many dishes did not use traditional utensils…like the five little stuffed hearts of palm that were each placed on little pedestals that you picked-up and then used as launching pads or I guess like shot glasses to toss the food into your mouth). I sent the 29 year-old chef and owner Grant Achatz a copy of Weird Ideas That Work — I never heard back from him, but the title certainly fits the place. 

    If I had to choose a place to go for my last meal, I would still probably pick the French Laundry in Napa, but Alinea might be second. The only thing that I recall that wasn’t wonderful was a house made
    sweet wine that reminded my of a bad imitation of Mogen David concord
    grape wine.

    The experience also stands out because David and I spent the next day at a McDonald’s research and development lab near  Chicago that has several full-sized working McDonald’s kitchen and restaurant. It is called the Core Innovation Center and it is a place where they constantly experiment with new technologies, configurations, and service solutions — you can read a bit about it in this Economist story.  We made our own burgers for lunch the next day and ate them standing-up in the kitchen, while talking to the inventor of an amazing burger-cooking machine that used a kind of conveyor belt to remove frozen burgers from one compartment and then cook them in another compartment, cranking them out a rate of one every few seconds — which we then assembled with our favorite toppings.  As David said, each meal was equally enjoyable and the contrast between the two made each seem so wonderful.

  • Firefox Crop Circle

    Now that is metacool! Check it out at Diego’s blog.

  • Why I Call Them Assholes: Updated

    I recently did a video "book brief" for BNET about The No Asshole Rule and received a few strong complaints about the title — the strongest in a long time. I responded, but I also thought that I would update my original blog posting on the topic. I have received some complaints now and then since the book was published, as you can see in my Publisher’s Weekly piece and this wonderful letter to the San Francisco Chronicle. But as I have written here, I am mostly shocked by how few people object to the term, and by some of the places — like this bible study class — that use the word openly.  Nonetheless, as I am getting more push back on the title than I have in awhile, I thought I would re-run a post that I put-up last October, before the book was published, on "Why I Call Them Assholes."  I’ve edited it just slightly. In particular, check-out the comments from readers; they are wonderful. Here goes:

    I confess that I have received surprisingly few
    complaints about publishing a book titled The
    No Asshole Rule
    (or if you speak German, Der
    Arschloch-Faktor
    ).  One of the most surprising things about the
    experience of writing the book, selling it to publishers, and now talking about
    it to various people, is how few complaints I’ve received about the somewhat
    dirty title.
    Perhaps the most serious complaint was from the Harvard
    Business School Press (HBSP), whose editors wanted to publish the book as long as I
    changed to a more respectable title — something I declined do. Jeff  and I have had a fantastic
    experience with HBSP on our current book,
    Hard Facts, Dangerous Half-Truths, and Total Nonsense
    , and I would
    recommend them to any business author. But I found their negative reaction to the title a bit amusing because
    my original essay on the rule (called “More Trouble Than They Are Worth") was
    published in their sister publication the Harvard
    Business Review
    , and it contained the word “asshole” 7 or 8 times. In their defense, the Harvard brand is one
    that smacks of respectability and even a touch of stuffiness. And as I told them when they tried to get me
    to change the title, if I was in management at the Harvard Business School
    Press, I wouldn’t publish a book with “Asshole” in the title either, as even if
    it sold well, it would be bad for their brand image.  So off I went to other publishers, and I’ve
    been delighted with Warner Business Books.

    I haven’t had many complaints since.  I have done media interviews where they requested
    that I use the word “jerk.” When I did a radio
    interview with Ron Reagan
    , he let me use the word “a-hole.” Just recently, though, I had a complaint that
    really got me thinking about why I use the word, and if it is a wise and civil
    thing to do. A couple weeks ago, BusinessWeek published a “centerfold”
    story
    about my perspective on brainstorming and a list of eight brainstorming
    tips based on my research and experience with creative teams. In the story,
    they (without censoring the title) were kind enough to say that my next book is
    The No Asshole Rule: Building a Civilized
    Workplace And Surviving One That Isn’t
    . The story provoked a most thoughtful e-mail from one reader:

    One thing
    caught my eye, though:  If it isn’t too late, get a new title for your
    upcoming book.  Vulgarism has no place in serious business.  It
    weakens your ideas and diminishes your credibility.  Maybe you could
    brainstorm with some of your colleagues and come up with a better one.

    This critique got me
    thinking about why I was using this “vulgarism.” Was I just being cute? Was I
    doing it to sell books? Certainly, I
    plead guilty to that charge — it would be a lie to deny that. Was I doing
    it because I am a vulgar person? That
    might be true too, but the other books and articles that I write rarely contain
    dirty talk.

    There are two main reasons why, at least for me, no
    other word works as well for describing these demeaning and mean-spirited
    people.  The first reason has to do with authenticity
    and the second follows from my goal of affecting what people actually think about and
    do in organizations.

    To start with authenticity, when I tangle with
    nasty person, I don’t think “what a jerk” or “what an abusive person.” The first thing that comes to mind is “what
    an asshole.”  That is also the word that
    nearly everyone I know uses to describe these creeps, even though they may
    later censor it. In The No Asshole Rule, for example, I describe a law firm that actively
    enforces what they call a "no jerk rule" in media reports, but when I talked to a senior partner, he confirmed
    that, they call the people that they screen out “assholes” rather than
    jerks.  And just the other day, my wife
    was talking with an attorney who specializes in labor law litigation, and this
    attorney was amused to hear the title of my forthcoming book because so many potential clients that
    she turns away are really complaining about working for assholes, not about
    sexual harassment or discrimination.  This
    attorney reported that “asshole” is the word that her potential clients often use
    and nearly always really mean — and she turns most away because it probably
    isn’t unlawful to be an equal opportunity asshole in most places, despite all
    the damage they do.

    Finally,
    another sign that that this phrase is authentic from both an intellectual and
    emotional standpoint came, to my surprise, in an email that I received
    from an accomplished researcher who studies emotional abuse in the
    workplace. As I say the book, she wrote,
    “Your work on the ‘no asshole rule’ has certainly resonated with my colleagues
    and me. In fact, we often speculate that
    we would be able to predict a large proportion of variance in job satisfaction
    with one ‘flaming asshole item.’ Basically, if we could ask whether your boss is
    one, we would not need any other [survey] items. …. Thus, I agree that while
    potentially offensive, no other word quite captures the essence of this type of
    person.”

    We teach our Ph.D. students at Stanford in the Center for
    Work, Technology and Organization
    who do ethnographies of the workplace
    that using foul language is sometimes necessary for providing accurate and
    realistic descriptions of what people say and how they feel. I believe that –
    in terms of both descriptive and emotional accuracy – other words are simply
    inferior for describing how persistently demeaning people act and, especially,
    the feelings they unleash in their victims.

    My second argument is that, since my aim is to help
    people understand how to spot these demeaning creeps, understand the damage
    they do, and how to build civilized organizations that screen-out, reform and
    expel nasty people, I should use language that people will remember and spread.
    After all, as Chip and Dan Heath show so
    brilliantly in their forthcoming book Made
    to Stick
    , no matter how good an idea is, if it isn’t “sticky,” if it isn’t
    something that people talk about, recall persistently, and gets them excited,
    then it can’t have any impact on what they do.  Chip and Dan show how “sticky ideas” are
    embedded in Simple, Unexpected, Concrete, Credentialed, Emotional Stories that
    Stick – which boils down to SUCCESS, one of the few “evidence-based acronyms”
    I’ve ever seen. I won’t lead you through
    a detailed march through these seven standards, but I do think that the phrase “The
    No Asshole Rule” fits their standards for a sticky idea better than, say, the “no
    nastiness,” “no bully,” or no “psychological abuse” rule – particularly because
    it is more emotional and more concrete than other phrases, it easier to weave
    into stories that “stick” with people, and it provokes an array of depressing,
    funny, and touchy stories from other people as well.

    Again, perhaps I am just trying to justify or
    glorify my vulgar language or crass desire to sell books, but I believe that
    these other arguments about authenticity and stickiness are sound too – – with
    all due respect to the thoughtful person who gently chastised me in that e-mail.

    P.S. Another reason that, at least for me, that no other word works as well that when I am acting like a nasty creep (I plead guilty, it does happen), I don;t say to myself "Gee Bob, you are acting like a jerk." I say to myself "You are acting like an asshole. Stop it."  So — again to be authentic — this is what I call myself when I’ve been bad to help gain a bit of self-control, not some sanitized word. 

  • The No Asshole Rule at SuccessFactors

    I wrote a post a few months back on The No Asshole Rule Reaches New Heights, which described how CE0 Lars Dalgaard enforced the rule at SuccessFactors, a global softwate companies with headquarters in San Mateo, California.  You may recall that he has employees sign contracts in which they
    commit to not acting like assholes.  I’ve got an update:  The rule
    seems to be working and is part of the company’s current success. Check out Succcesfactors list of five founding principles that Dalgaard spelled out when he started the company in 2001 — "No Assholes" is number 5.  Now that is my kind of CEO!  This story has lovely implications for entrepreneurship. I’ve had at least half-a-dozen entrepreneurs tell me that they used the no asshole rule as one of their founding principles, but all told me that — although they used the word "asshole" when talking about who they wanted to hire, fire, and so on — they used more polite language to describe it in written materials or just talked about it rather than writing it down. I applaud Mr. Dalgaard for his courage and plain talk. 

    I also love how Dalgaard measures the company’s current success. I quote:


    As of September 2006 we have made a dent into this goal by achieving:

  • Real usage by 2 million employees worldwide
  • Real usage by employees in 139 countries and 18 languages
  • Growth 3 times that of our nearest competitor
  • Near 100% customer referenceability
  • Dramatically low employee turnover
  • Employing no assholes
  • Now that is a balanced scorecard!  And one that is short enough that it doesn’t suffer from the Otis Redding Problem

    UPDATE ON OCTOBER 2nd: I pasted the above text in blue on Sunday October, 1 from the SuccessFactor site. So it said "Employing no assholes" just yesterday.  But it seems that someone at SuccessFactors has decided that the word "asshole" is a bit too much. As Stan points out in his comment below, it now says "jerks."  I bet Lars still calls them assholes, but someone with less courage has talked him into a bit of censoring.  My hunch — and this is a hunch based on no other information– is this is the kind of thing that people do when they start "prettying-up" a company to sell it or go public. I could be wrong, but let’s see what happens in the next few months — or days.   In any event, I still have to give them credit for straight talk for the first five years, even if they are losing a bit of courage now.

  • Assholes in HR

    I got an interesting note from "Suzie" about how the people in HR Departments. Here is an excerpt  from what she wrote me:

    My
    company was moving our office to another city, and the head of HR sent out
    information about moving. He did not include the address or directions and also
    didn’t include the email address of the person he told us to contact if we had
    questions. I replied to suggest it would help all the employees to provide this
    so  we wouldn’t have to individually look up the information (wasting a
    lot of time). A few minutes later an HR manager who reports to him came to my
    cubicle to explain that I could look on Mapquest and how to use the company
    phone directory. Basically I felt like I was reported for  suggesting an
    efficiency. I’ve pretty much found many people in HR are assholes.

    Suzie’s
    conclusion that she was "reported for suggested an efficiency" is
    something that every person in every HR department should read and think about
    closely — this is the kind of organization that quality guru W. Edwards Deming
    railed against and the kind that  Harvard Business School’s Amy Edmondson has shown undermines psychological safety, which  drives out learning and error correction.

     I have a lot of respect and sympathy for people who work in Human Resources departments.  Unfortunately, however, this isn’t the first time I’ve heard stories like this
    about people in HR.  I won’t defend their behavior but it does seem to
    me that many organizations put HR staff members in positions where it
    is a lot easier — and safer — to act like rigid assholes instead of
    actually helping people to their job. HR people have tough jobs, as they deal with some of the contentious issues in organizations, hiring, performance evaluations, pay equity, benefits, and the messy problems of dealing with problem employees of all stripes. To make matter worse, in too many companies, no one notices them when they do their jobs well, but when things go wrong, they get in trouble. So, although companies talk about people being their most important asset, people in HR are often treated as the least powerful department, and ironically, treated by other senior executives as among the company’s least important human assets.

    This lack of power and constant fear of getting in trouble often leads HR executives and staff to become very bureaucratic and to say no to requests to take actions that will actually help employees do their jobs.  Charles O’Reilly’s and Jeff Pfeffer’s Hidden Value shows how this mentality even arose at Southwest Airlines in the 1980’s, where the old HR Department was known as the "police department." Ann  Rhoades (who went on years later to be founding  head of HR at JetBlue) was brought in to  turn the department around  — she threw away the 300 page book of rules, renamed it the "people department,"  and brought in people who had line experience. Ann especially brought in people from marketing because, to paraphrase Libby Sartain who followed Ann in the position (and is now EVP of HR at Yahoo!) , people in HR always say "no" because they are so afraid of getting trouble and getting fired, while people in marketing say "yes" because they want their clients to be happy.  The People Department’s job at Southwest is to do whatever it takes to make their clients — Southwest employees — happy and more effective.

    I suggest that other HR managers take a cue from Suzie and Southwest. If you are in HR, do people think you are assholes who will punish them for making suggestions?  If you are a senior executive, do you treat people HR so badly that it is safer for them to act like assholes rather than to actually help your people do their work?

  • BusinessWeek, d.schools, and Creating Infectious Action

    The new BusinessWeek has a "special report" on "Design Schools" and identifies the "Best D-Schools" in North America, Europe, and Asia. Co-author Jessi Hempel talked to several of us at the Stanford d.school about the story, and I was delighted that we were on the list and even more delighted that they elected to simply list top schools rather than to do some kind of ranking from best to worst, as I think that this "category" is too new and there are too many differences among the different kinds of school  — so trying to rank the single course taught by the Harvard Business School to the MIT Media Lab to the California College of Arts doesn’t seem reasonable.  I think their perspective — that these schools all try to produce people who can do creative work — is the right take, that certainly is what we try to do at the Stanford d.school. The twist I would add is that we don’t so much try to teach people to be creative individuals (although that is certainly one goal), our main mission is to produce people who are skilled at contributing to the process of creative collaboration.

    I also was pleased to see that the opening main story on The Talent Hunt started off with a description of the Firefox project, which was part of the class that Diego Rodriguez and I taught on Creating Infectious Action — which we’ve written about on both our blogs.  We love coverage and we realize that there probably wasn’t space to the name all students, but I want to give special thanks to John Lilly and Asa Dotzler from Mozilla, coach Debra Dunn, and to the four students who worked on www.firefoxies.com — which was mentioned in the article, Thomas Niss, Xiao Wang, Corrine Putt, and Brian Witlin. More evidence that sex sells — note also that those pictures sometimes are censored a bit before they are posted, as the website is rated PG!

    Meanwhile, Michael Dearing, Perry Klebahn, Liz Gerber, Alex Ko and I are teaching a new d.school class this term called Clicks-n-bricks: Creating Mass Market Experiences.  The first day of class was Thursday and the first assignment is to "improve the theme park experience, especially for non-English speakers."  We have buses of students off to visit local theme parks this weekend. I can hardly wait to hear what they discover and what design changes they suggest. I attach the description of the first assignment for the curious — as you can see it is a very simple and broad description and, if you think about it, a mighty tough problem!

    Download clicksnbricks_first_assignment.pdf