There Are No “Good People”

A lot of people are surprised when they discover that I don’t believe in “bad people.” I don’t believe there is such a thing as an irredeemable, fundamentally broken individual who just needs to exit the human race as quickly as possible.

“Not even Hitler?” the hypothetical objector exclaims, appealing to Godwin’s Law right out of the gate.

“No, hypothetical person,” I reply. “Not even Hitler.”

I’m raising this point in the midst of sexual assault scandals rocking everyone’s world as if we should be surprised that a culture that scarcely thirty years ago didn’t widely recognize sexual harassment, that to this day continues to ask victims of rape what they were wearing and whether they should have gone into the room with him, conditions its men to respect their own sexual urges over the self-sovereignty and safety of others.

“But I’m a good man,” cries Louis C.K., Bill Clinton, George H.W. Bush, Al Franken, George Takei, or whatever respected man is currently under discussion as having forced himself sexually against others.

Well that right there is your problem. The flip side of the notion that “bad people” don’t exist is that “good people” don’t exist either. There are just “people,” with all the mess of bias, emotions, desires, and other irrationalities.

I don’t mean to excuse any of the horrible things done by these or any other people. But whenever I give an apology with the claim, “I’m a good person”–or anytime I defend someone saying, “He’s a good person”–I’m implying there are “bad people” out there who are the ones who do these things, and the bad thing I did isn’t part of who I am. But clearly it is part of who I am. Because I’m the person who did it.

Of course, there are also people who think they’re the “bad people.” These people go home and love their spouses, children, or pets with complete selflessness. They give to poor people or help others avoid the mistakes they themselves made, often with the reasoning that “just because I’m a bad person doesn’t mean everybody else has to suffer.”

In a way, both these narratives exist because they save us energy. If I’m a “good person,” I don’t have to stop and think about what I’m doing, because by virtue of “being good,” I won’t ever do anything bad on purpose. If I’m a “bad person,” I don’t have to stop and think about what I’m doing either, because even if I try to do something good it will inevitably be corrupted by my “bad” nature.

The most terrible people in the world have almost always been “good people” by their own reckonings. Tyrants, slave traders, and genocidal maniacs have all reasoned that because they were essentially “good,” the actions they were taking must be justified.

It’s this kind of “goodness” that prevents us from making progress against racism, sexism, classism, and all the other dysfunctional “-isms” that plague our culture and keep crushing human lives under their weight. Your mom spouts vitriol about the Vietnamese family who moved in next door, but she’s a good person. Your buddy touches women inappropriately all the time but hey, he’s a good guy. Your boss would rather vacation in ever more remote tropical islands than lift a finger to help people less fortunate, but he’s always nice to you at work, so he’s a good person too.

Do you consider yourself a “good person?” If so, I recommend seeking treatment immediately before the condition worsens. Talk to a therapist or religious leader, and if they in any way imply it’s a simple thing to do, get a second, third, or fourth opinion as needed. Read Thich Nhat Hanh or Thomas Merton, follow the fantastic On Being podcast and blog, look in whatever texts you consider sacred for the words that are spoken to you and not the words that are spoken to others.

Give up being a “good person” or a “bad person” and work on becoming “good at being a person”–someone who has learned to accept his irrationalities and idiosyncrasies and limitations, who always acts with empathy, who considers the people affected by his actions before taking action. To quote Kendrick Lamar, “Be humble.”

I struggle to this day with the belief that I’m a good person. Sometimes I have to catch myself when I think that the things I believe or the lifestyle I embody mean that I’m a good person, incapable of doing wrong because it’s simply not in my nature. There are also times when I’ve been shaken to my core to think that I not be a good person–that I’m not capable of doing anything right, that I’m useless as a human being. It took me years of growth and practice to recognize and ingrain in myself that I was neither good nor bad. And as I began to leave behind rightness and wrongness (to allude to the Islamic mystic Rumi’s famous poem), I also began to find I was calmer, more focused, more energized by the change I could help to create in the world and less burdened by self-doubt.

This isn’t a quick process–it means dedicating yourself to learning how to be human the way you might dedicate yourself to learning guitar or glass blowing; and it means you have to keep practicing instead of depending on your inherent “goodness.” But it’s the one skill literally everyone needs. It’s the one skill that matters most to our collective future. And you can’t be an effective leader of your home, your business, or your country without it.

If you’re looking for help with this, please post in the comments below and I’ll try to provide some more resources.

Be What You Intend to Be

Much of what goes on in a traditional organization is unintentional. That is to say, it isn’t an action that someone has decided to take in order to contribute to the well-being of that organization and its stakeholders. It’s operating on default.

Ironically, unintentional behavior can often be the result of trying to clamp down on unintentional behavior. On the other hand, it can just as easily be the result of leaving people isolated and expecting them to do their best work without any assistance or support.

The road to a more intentional organization is one described ideologically by business greats from Warren Buffett to Richard Branson. Here is the idea as verbalized by Steve Jobs:

It doesn’t make sense to hire smart people and then tell them what to do; we hire smart people so they can tell us what to do.

Taken to its logical conclusion, this idea is counter to the operation of a traditional organization. Traditionally, decisions get made and orders pushed down the chain of command; results come back up and get pieced into something like the final result that the person at the top of the chain wanted.

Counter-intuitively, the result of the traditional approach is that much of what happens in the organization is unintentional. People who wait for orders don’t make the best use of their own time; and the people above them, who don’t have the perspective of each individual’s point of view, don’t make the best use of their time either. People fulfill their immediate expectations without a view of what’s good for the whole. What’s more, managers often don’t communicate all their expectations, and the results reflect the holes in each subordinate’s understanding of the tasks assigned to him.

Becoming intentional means, at least in part, understanding myself, acknowledging and accepting what I am, and developing upon my strengths. As in the Cherokee proverb of the two wolves, I become better by feeding what is good within me. It’s not a choice I make when I’m faced with a hard question, it’s a choice I make by the way I condition myself to face the hundreds of little choices throughout the day.

The same is true of an organization: I have to feed what is best in my organization and what is best in the individuals within it.

This is one reason organizations that focus on facilitation can be much more effective than traditional organizations. Instead of “managing” in the traditional sense, leaders help people to do and become their best, guiding their individual work toward the ultimate good of the organization as a whole and helping to connect it to the work of others.

What this means for a leader is that I am first of all responsible to my people rather than for them. (Responsibility for my people is still important, though it’s mostly externally-facing: followers want leaders to have their backs.)

Whereas a traditional organization is merely, as Emerson put it, “the lengthened shadow of one man,” an organization of facilitation is an attempt to leverage the power of community toward a common goal. That makes the intent of each individual important to the whole. Each level is intentional about its own goals and behaviors, and each subsequent level is there to help the previous level attain its goals and bind efforts together.

Here are a few risk factors for unintended behavior, and what you can do about them:

  • Fear. When people are afraid of something, they tend to either destroy it or hide it. I have never seen either of these behaviors yield positive results in an organization. If the people working with you act fearfully, address it head-on. Learn what they are afraid of. Dig into the root cause, too–few people are afraid of disappointing a customer so much as they’re afraid of what might happen to them. If you start to notice a lot of people having similar problems, you have a systemic fear on your hands–usually one that has to do with trust within the organization–that requires a change.
  • Inconsistent culture. People are more willing to take personal risks if they feel anchored and supported. That has partly to do with knowing that the people around them have their back–even people who may be on a different team, or come from a very different background. Your hiring practices and cultural guidelines need to be spelled out so that the people you hire are people you’d choose to weather a crisis, not just people who would have fun together at happy hour. More than that, everyone in your organization needs to be telling the same story and believe in the same destiny.
  • Too much process. Process can be a good thing if done correctly–if the process represents a best practice, serves the people, and is capable of evolving. But if you need a process to mitigate risk, that means you already have unintended behaviors–and adding a process could make the issue worse, as people attempt to short-cut or circumvent the process in order to get their work done. (Ask yourself: Is the process an invention or a control?) Pare down or eliminate any processes that get in the way of doing good work, and instead focus on gaining buy-in from your ostensibly reliable (you did hire them, right?) employees as to how to avoid putting your community at unnecessary risk.
  • Over-management. If responsibility for my efforts always goes up to my manager, my natural human response is to fight against that control mechanism. I might give up on doing anything that isn’t assigned to me, I might deliberately procrastinate or slack off, or I might start looking for other jobs. (The top cause of burnout isn’t over-working, it’s lacking control over or engagement with your work.)1 A quote from a study in the Indian Journal of Industrial Relations: “Burnout can be minimized/avoided if individuals develop a high level of involvement in their jobs and they are able to identify themselves psychologically with their jobs.” Adding controls and oversight to prevent me from doing anything but the work I’m supposed to be doing will provoke a desire to rebel against them. Try cutting out levels of management and finding ways to prevent micromanagement, or better yet, train your “hierarchy” to be a facilitating structure instead of a managing structure. If you have good people, you won’t need to control them; and if you stop controlling them, you’ll find out pretty quickly who’s good and who isn’t.

The only way you’re going to get more than a handful of people to be fully engaged in accomplishing a goal is to get them to buy into that goal and work toward it on their own motivation. In other words, hire good people and let them tell you what to do. Think of it this way: As long as I hold the power to fire my leader, what do I lose by being a servant?

What reservations do you have about making this kind of change? Did I miss something? I’m looking forward to getting your reactions in the comments.

References   [ + ]

1.  A quote from a study in the Indian Journal of Industrial Relations: “Burnout can be minimized/avoided if individuals develop a high level of involvement in their jobs and they are able to identify themselves psychologically with their jobs.”

How Emergence Works in Organizations

Emergence isn’t about collecting a bunch of fine people and letting them do what they want with no structure of any kind. In fact, emergence needs structure–just not the same kind of structure traditional organizations use.

Functionally speaking, the traditional top-down structure is a method of augmenting one person’s ideas with the minds and bodies of others–like a human Voltron.

Voltron with an overlay of an org chart

This is familiar to our way of thinking–a reflection of Industrial Age ideals of order, rationality, and efficiency. But Voltron is ultimately a machine, and as we enter the Second Machine Age, organizational structures that mimic machines are going to fall by the wayside: they are less efficient than actual machines, and less adaptive (in an evolutionary sense) than organic communities.

Consider the example of Microsoft’s .NET versus the open-source Ruby On Rails: the closed, controlled, heavily planned product has consistently lost market share for years, while the decentralized, agile developer community has turned out a consistently more popular and more useful product. In terms of external incentives and long-term planning, Microsoft should have the better product. Instead, Microsoft is planning to make .NET open-source because of the spectacular failure to keep up. The organic community has unequivocally trumped the traditional model.

Let’s take another stab at that organization chart. Take the person at the top and place her instead in the middle. Connect her to all her sources of information, her co-workers, the people who report to her, the people to whom she reports. Do the same for each of those people to whom she’s connected, outward until everyone in the organization is accounted for, and connect each of them with their points of contact to the outside world. What you have now much more resembles a neural network:

Map of the neural network of a mouse

This isn’t an aspirational image, it’s a reflection of reality–a reality that the former image attempts to control and confine into a linear hierarchy. For comparison, here is a map of Twitter employees using the platform:

Network map of Twitter employees

Seeing an organization in this way–as it organizes itself, and not as the linear design into which we try to squeeze it–reminds us of the first principle of emergent structure: the number and quality of connections improves emergent behavior.

This isn’t a call to increase the number of networking events at your business. Human beings will create connections on their own if given the right environment.

Consider Google’s practice of mixing functional groups on the floor. While this would be anathema to a linear hierarchy–I would have to walk to another part of the building to talk to a co-worker–at Google, the people around you may become your co-workers. Some businesses have replicated the design without taking into account the hierarchy and culture, resulting in marginal improvements at best, and often employee frustration. (Even at Google the practice is not without its drawbacks, but it is an intentional culture play.)

The quality of the connections is likewise based on trust; the traditional organizational structure makes trust unnecessary, and by making it unnecessary, undermines it. This leads to a second principle of emergent structure: where traditional organizations depend on chain of command, emergent structure depends on social contracts.

A social contract is, at its most basic, an agreement held in common between any number of people, either written or implied. Top-down structures choose policies and impose them. Leaders of adaptive organizations make a case that a policy is in the best interest of the organization, and modify it based on the needs and applicability to a particular population. We all agree that we need to follow a certain regulation or we will face prosecution, therefore we promise to follow that regulation and hold one another to it.

In this way, instead of imposing a rule that employees follow like the speed limit (seven miles per hour over isn’t really speeding, you know), employees are accountable to one another for their actions. We all know we have made the promise with one another; when I violate the promise, I have broken my promise with everyone in the organization.

Social contract underpins the entire structure of a culture. When I expect that I have ownership over my work and it won’t be taken away from me and given to someone else, that is an implied social contract. When I expect that I can do my work every day without fear of sexual harassment, that is (usually) a written social contract.

Social contract also defines the leadership of an organization. A person can be an owner if he has enough money, and he can be a manager if he has enough connections, but he can only be a leader if he has people willing to follow him.

Finally, in addition to good connections and social contracts, emergent structure requires process. This may seem to contradict what I’ve said so far, except that human processes are approximate–they are always applied using judgment and a “feel” for the particular situation.

Human process is an interesting phenomenon. Machine processes can be made to take variables into account, but machines don’t make judgments. And machines don’t vary processes in ways they haven’t been explicitly programmed to learn, i.e., they don’t introduce personal experience or personal interpretation. Emergent behavior in an organization depends upon human experience and variability, working against an established process, to produce unexpected outcomes. Only processes that are documented and followed can be improved. Everything else is folk knowledge, which is improved by rare individuals and passed piecemeal to others.

This kind of adherence to and improvement of process depends wholly upon social contracts and quality connections: I must know that I am not documenting my changes to the process on behalf of some uncaring management four levels above me, I’m keeping rigid documentation on behalf of people like myself in the organization who are doing their best to cover for one another and keep things moving.

This is why I encourage you to abolish the idea that there is a “top” or “bottom” to your organization. The goal is to have a structure where everyone finds the most appropriate place for as long as that place is appropriate, not a structure where everyone struggles to climb as high as they can. In order for this to work, we also need to rethink the role of leadership in such an organization–because it is still critically important–and what that leadership is attempting to do.

I’m eager to get your thoughts on all this. Did any of this sound like an organization where you’ve worked, either under the traditional model or under a more adaptive approach? Have you seen leaders embrace the “neural network” of organization and truly try to engage all their members in uniquely meaningful ways?

Hiring for a Unique Culture

Culture is an emergent phenomenon. It exists between the people who make up that particular culture, and evolves based on their interactions–the mythology, folk knowledge, and traditional practices they create and pass between themselves. If you hire based on skill alone, your internal culture will look pretty much like the rest of your industry, because it will be populated with the same kinds of people.

Unlike the Industrial Age, hiring today isn’t picking up a part to put into an already-designed machine to make the machine run. Hiring into an emergent environment only happens when the candidate fits both the current culture and the future culture. Emergent strategy depends on the people within the organization working with and off of one another to yield unplanned results.

Here are a few tweaks to your hiring practices that may yield better results:

  1. Don’t appeal to everybody. Many organizations just want to be liked by everyone. They want to be the place where any individual out there would love to work. Don’t do that. Your organization is unique, and you want people who fit that collective vision and identity. Netflix asserts very clearly that its culture isn’t for everyone, but that is precisely what makes its culture all the more appealing to those who do fit. Figure out now why people wouldn’t want to work in your organization, and you’re on the way to creating a unique and powerful culture.
  2. Fill blind spots, not roles. Roles are a collection of responsibilities and skills that fit a pretty standard definition. Blind spots require a more complete understanding of your team and organization. Simply put, a blind spot is something you need that you don’t have, at the broadest definition that is required (e.g., do you really need someone with three years of Trello experience or do you just need someone who’s comfortable with agile project management?). A blind spot may be a specific competency, like a specific piece of technology, or it may be a tweak to the chemistry of the current team–for example, a more outgoing individual that will facilitate communication between the more introverted members of a remote team. It strips away the expectations that come with hiring someone into a particular role, allowing the new hire to integrate more organically with what’s already going on in your team for the first few months until they have a rhythm going.
  3. Advertise your vision, not your requirements. Anyone who isn’t excited by your specific vision doesn’t belong to your culture. And don’t just advertise the vision of your company. If possible, state succinctly but with enthusiasm what your vision is for the team and even for the specific role. A less-skilled candidate who is energized by the collective vision will be twice as valuable as a more skilled candidate who just wants a new job. And bear in mind that a long list of qualifications belies a search for an interchangeable part. If you want your candidates to get excited about a position, pare it down to your vision and the key blind spots you’re trying to fill. Leave room for the candidate to surprise you.
  4. Interview thoroughly. The hiring process I’ve seen averages two interviews. Google suggests no more than five–and then actually goes on to interview candidates five times, looking for factors including raw skill, problem solving ability, and cultural fit. In an adaptive organization, you’re going to want to take advantage of four or five interviews in order to thoroughly vet the skills, the personality, and the chemistry with the current environment.
  5. Weigh potential. Today the pace of change in technology and the economy means being able to learn what’s needed for the future is more important than having what’s needed in the present. Your people will not only need to adapt as things change, but they will need to create change themselves. And then they will need to live into that change. If the candidate doesn’t have what’s needed to adapt to whatever his role will be in three years, he may not be the best fit.
  6. When in doubt, leave them out. Don’t hire a candidate unless they leave you no other choice–by which I mean, she is such an excellent fit for your organization that you couldn’t bear to let her take another job. Turn away business before hiring someone who doesn’t add to your culture. Adaptive organizations thrive based on the number and quality of connections between employees. Hiring someone who isn’t going to improve your internal network is poison to your long-term goals.
  7. Enlist your recruit’s help. Zappos offers a $2,000 bonus for new hires to quit. The idea is that a new hire will take the money if they don’t feel that they are a good fit for the culture or they don’t believe in the long-term potential of working with the company. In the long run, the occasional $2,000 quitting bonus saves the company a lot of money on people that might otherwise be a drag on the culture. A new-hire quitting bonus might not work for you, but you should still look for ways you can work with a new hire to ensure he’s the right person, and part ways amicably if he’s not.

Filling your organization with effective people who fit with the people around them and are excited about a common vision is the basis of any good culture, not just in an adaptive organization. But because of the importance of emergence in adaptive organizations, getting the mix of people right for your culture is a crucial requirement for success.

EDIT: Reader Brian Gorman offers two additional points to consider: “Having spent more than four decades living in the world of organizational change, I would add two more to his list. 1. Hire for the culture that you want, not the culture that you have. 2. Hire for resilience; you need people who can learn new skills, and shift their mindsets, as your organization continues to change.” I would add a caveat to the first that anyone you hire needs to be able to work in the culture you have today, or she’ll be out the door as soon as she can–which makes finding adaptable people all the more important during a period of change.

Which of these points do you find is most important or illuminating? Are there any important points about hiring for culture that I’ve missed? Do you disagree with my points? I look forward to discussing it with you in the comments.

Do This, Not That: Market Versus Social Norms

Dan Ariely makes a distinction between market norms and social norms in the fourth chapter of Predictably Irrational. He touches briefly upon the way that employers mix their messages, dangerously breaking social contracts and making things about money when they are attempting to lead a socially-driven organization.

As the book documents, operating on market norms (i.e., thinking about the money I’m getting in return for the activity I’m doing) can damage productivity even when compensation is considered adequate. But worst of all, it can damage relationships when we assumed we were operating on higher terms–social norms like trust, reciprocity, and friendship. And we can’t mix the two: once we perceive that our efforts are being valued according to market norms, that’s the mindset we use for the entire interaction.

The next era of commerce will not be kind to organizations that depend on market norms, except as perhaps a back end, business-to-business protocol. For the most part, those things that are driven by competition, price, and data can be outsourced to computers and become a secondary function of people-facing businesses, businesses that use humans for those things humans are uniquely capable of accomplishing.

If you’re still using market norms to run your business, it’s best to start weeding them out now, before they relieve you of all your self-motivated people and leave you with half-hearted key-punchers.

Here are a few “do this, not that” guidelines for common business practices:

  1. Pay healthy salaries, don’t track hours. Some businesses require hour tracking, but to the extent that it’s possible your people shouldn’t identify the time they put in with dollar amounts. Doing so puts them in a market mindset: Am I getting enough money to be worth what I’m doing? Paying healthy salaries instead removes market questions from their minds, and has the potential to make the rare transformation of money into a social contract: the business is a community that takes care of your needs, rather than an employer compensating you for your activity. This is the genius behind Netflix’s policy to pay employees as much as they would pay to keep them: there’s no need for employees to ever negotiate salary or think about how much their work is worth, so they operate on a basis of trust and social contract rather than constantly competing with the employer for a fair wage. Even better if employees have direct deposit, where the money simply appears in their accounts as if by magic.
  2. Appeal to social contract, don’t talk about money. It should go without saying that you should never bring up the fact that you’re paying an employee, or use money as a bargaining chip for a change in behavior. They’re already aware that a threat to their position in the community is a threat to their livelihood. Focus on the social contract rather than the monetary transaction. Are they letting down their co-workers? Are they hurting their ability to make a difference in the organization? Talk about those things. If you have to mention money, it’s already a lost cause. (If they’re the ones bringing money into it, you might as well address their concerns–they’re already thinking in market terms. Take it as a form of feedback on your ability to keep market norms out of your business, and consider whether the issues raised might affect other people as well.)
  3. Make your people financially secure, don’t cut costs at their expense. If your employees have to be worried about paying the rent, covering bills, and eating, then they are already thinking about their jobs in terms of market norms. If you’re going to employ someone, make sure you’re ready to pay enough that they don’t have to be concerned about the basics of life. That includes health care, child care, and retirement. Ariely and James Heyman report that people who perceived themselves as paid inadequately lost as much as a third of their productivity at a very simple mechanical task (forget creative problem solving), and that’s without factoring in any worries about feeding their children. And if Costco is any indication, paying a living wage is a clear path to sustainable business.
  4. Share successes, don’t pay bonuses. This is a tricky one: Traditionally, bonuses are the way you share successes. But paying bonuses can create a clear line between the actions of an employee and the money, turning the action into market-regulated action rather than social-regulated action. There are different ways of accomplishing essentially the same thing. One is to reframe the concept of compensation entirely, as with my post on taxation. If employees interpret the amount they earn not as a payment from you but as something they are accomplishing with you, it may be possible to avoid activating market norms. Another way is to award the bonus as an in-kind gift–but this is fraught with pitfalls. Having the employee choose the gift causes the employee to think about the monetary value; choosing the gift for the employee puts one in danger of choosing something the employee doesn’t want or need; and having co-workers choose may invite comparison and market-norm thinking among the co-workers.
  5. Show loyalty, don’t dig moats. There are already a lot of financial obstacles to leaving a job. Creating new ones causes your people to think about the job in terms of their financial need instead of thinking about the social contract. Instead, you should make it as easy as possible for them to leave–and challenge yourself to convince them they shouldn’t. To the extent your people feel that they are with you by choice and not by necessity, they will be more likely to act on social norms instead of market norms.

It can be difficult to manage the financial needs of the business while operating on social norms, but undermining the social norms can quickly undo all the effort you’ve placed into creating them. If you start by thinking of your organization as a community, a family, or a nation, you will be on more solid ground. And when in doubt, leave the money out of it.

Interlocking Shields: The Importance of Constructive Conflict

Any organization that’s trying to become more innovative has to adopt one universal management skill: constructive conflict.

Constructive conflict doesn’t mean conflict resolution. It means allowing conflict to happen, even encouraging it, and focusing it into a creative, constructive exercise.

Conflict is important because it challenges beliefs and assumptions. It reveals the limits of our vision and draws out feelings and opinions that need to be dealt with. Well-executed conflict can result in more robust ideas and more complete buy-in; it also prevents territorialism and resource allocation inefficiencies from people overstating their needs, and allows us to air grievances before they develop into grudges. For these reasons, conflict doesn’t go away in a good business environment.

Conflict occurs when people have different information, different values, or different needs; constructive conflict facilitates synthesis of these differences:

  • Synthesizing information allows decisions to proceed with a more holistic view.
  • Synthesizing values allows each stakeholder to understand other stakeholders’ concerns and determine whether they are important to the matter at hand.
  • Synthesizing needs helps make decisions and compromises that will benefit the business overall and not just the stakeholder acting on his or her own.

Conflict avoidance, on the other hand, short circuits innovation by preventing the interaction of diverse viewpoints and areas of knowledge. Providing a framework for conflict to happen makes collaboration possible. All the platforms and incentives and leadership messages trying to push collaboration can be sabotaged by not knowing how to create positive conflict.

Although constructive conflict is a skill, we can start by creating a solid foundation for conflict. This begins with shared purpose and shared values: if people are working toward the same end, resolving the conflict becomes a matter of how best to achieve that end instead of a contest of ends.

We can also more clearly define roles. This is a particular challenge for less-hierarchical organizations: a manager, for example, becomes a role rather than a position of absolute authority. Yet as I’ve discussed previously, “domain” is critical to the development of individuals. Defining and using domain in very clear-cut ways helps those involved in a conflict to understand the perspectives of one another, and reduces the scale of conflict to border disputes while eschewing hostile takeovers.

Finally, constructive conflict and trust feed into one another. If you have established trust, it will help to draw out conflict and create constructive outcomes. If you create successful conflicts, it will strengthen the bond of trust.

How to Use Your Diversity

We intuitively know there’s value in diversity: the Mission Impossible team, the A-Team, Ocean’s Eleven, the Guardians of the Galaxy.

But in business the tradition has been to focus on things that can be tabulated: years of experience, education level, predefined skill sets–and usually to fill the abstract concept of a “position.” In this context, “diversity” is a buzz word that means “someone who looks different”–different clothes, different rituals, different language–but someone who is still plugged into the same ways of thinking.

It’s not that such people don’t add diversity. But the value of their diversity is often suppressed in favor of the appearance of diversity. The game, while at the office at least, is conformity.

The value of diversity comes with different modes of thinking. Any given person can see a problem from multiple angles, but never from all angles. Having and utilizing real diversity, then, depends on being able to bring out the difference in perspective and put it to work in combination with other perspectives.

From a recruiting perspective, this means hiring to fill the blind spots. A blind spot is different from a role, and it behooves a manager to understand where blind spots may exist in a team.

From a management perspective, this means practicing constructive conflict. Constructive conflict is a way not only to allow but to encourage dissenting opinions in such a way that final solutions benefit from very different ideas.

Finally, it means management that is able to see the value in other perspectives. Much of the value of these perspectives may not be rational, but that doesn’t mean there isn’t reason behind them. Finding tools to judge these perspectives, and to incorporate them together, is critical to effective management of diverse teams.

One final point: Diversity of perspective must be unified by unity of purpose. Last week, I described founding myth in terms of shared origin, shared values, and shared destiny. These are critical to the development of a diverse community.

Living the Myth

Once you have your founding myth, what do you do with it? You can’t exactly distribute an epic poem to your people. Do you have to update your internal training materials?

Fortunately, this isn’t necessary. Most of ancient Rome couldn’t even read, but that didn’t mean they didn’t identify themselves with the founding story of Romulus and Remus.

Your founding myth will become the centerpoint of your shared identity, but it should become a story your people tell intuitively, not because they’ve memorized it off a sheet of paper. Many cultures tell their myths through holidays and religious practices–but another way of looking at it is that the myth is told through the activities that establish the culture’s identity. What activities that establish your organization’s identity?

If your response is, “Almost everything my organization does,” you’re starting to get the idea. The story is told every time two or more people assemble in the name of the organization. So the challenging process is not in telling the story at all, but in changing the story that’s being told.

  1. Believe the myth. Have you created something you believe, or is it something you wish were true? If it’s the latter, you’d better head back to the drawing board. There has never been a story that existed outside of a human mind. The founding myth must be believed into existence–by way of its influence over actions and motivations. But the founding myth is not magic. It will help to guide decisions and create community, and it will help the culture of your organization to hold together and move in the same direction. But it will only work if it’s based in reality, and it is genuinely believed by the people in the organization. Belief starts with you.
  2. Share your beliefs. If you believe the myth, you will find it working itself into your everyday language. The ideas and beliefs will be embodied in your presentations, your conversations, the way you lead your meetings. You will reference your shared past, call upon your shared values, and look forward to your shared destiny, sure as a Pentecostal preacher on a Sunday morning.
  3. Pay attention to the response. How your people receive and react to the story you’re telling will indicate changes you may need to make. You may have blind spots where the facts as you see them don’t match up with the experience of others, and have to revise your myth. You may have pain points where you will have to change the way your organization operates in order to align with your myth. Do people disagree with the conclusions you reach? Do you experience resistance to initiatives? Do people seem like they’re going through the motions without really understanding the purpose? If your myth is told well and aligns with what everyone is doing, your people will act with purpose; if your myth isn’t aligned with reality, your people will be annoyed at being asked to keep up a compulsory fiction.
  4. Revise. Pay attention to the way people respond, and you’ll start to see where you might have to make changes to your myth, and where you might have to make changes to your business. In all likelihood, you will need to do both. How will you know the difference? There aren’t any hard-and-fast rules, but as a general rule of thumb, if the negative or lackluster response is widespread, you probably need to revise your myth. If the poor response is concentrated in the core areas of your business–the people who best know your organization’s purpose–you probably need to revise your myth.
  5. Keep it up. Don’t let growing pains get you down; there will be people who don’t agree with your vision exactly, and while you should listen to them, you shouldn’t always revise your myth to please them. If you have a consensus within your organization–not just at the executive level (if applicable), but the organization as a whole, including all major divisions–then you will simply have to accept the fact that some people will take more time to get on board, and some people will never get on board and probably need to find a different community.

You will notice that both the story and the business will have to change. (I hope you are expecting for your business to change, since it’s the whole point of this exercise.) But after a few iterations, you should find a comfortable guiding myth.

And then you will have the privilege of encountering the great truth, “It works until it doesn’t.”

What I’ve written this week could be the content of an entire set of books, but these principles should at least give you some ideas about how to approach the enhancement of your organization’s story and the development of its community. And if not, I’m always willing to be wrong. I look forward to hearing your observations and experiences in the comments.

Writing Your Founding Myth

Yesterday we examined the existing story of your organization. Today we’re going to explore how we can nudge that story into place to create a founding myth–the story that underlies the identity of any company, nation, team, or collective.

As much as Americans may disagree about the particulars, most of us have a shared respect for our founders and place emphasis on the values of liberty and equality. Today, this story includes the long fight to end slavery and grant equal rights to minorities. This is our founding myth: a particular telling of our history, with emphasis on the values that form our identity and the heroes who championed those values.

A large chunk of the Hebrew Bible contains what could be called Davidic mythology: from foretelling David’s kingship long before his birth, to calling upon his bloodline well after his death. The patron, YHWH, brought the people out of Egypt and into a new land, established the identity and values of the culture, and provided a model and hero in the form of King David. This myth sustained the identity of Israel and the Jewish people through multiple exiles, through Greek and then Roman occupations.

As you can tell from my short telling of these two stories, founding myths have important characteristics that help to shape a community:

  1. Shared origins. Your shared origins might stretch back to the founding of the organization, particularly if it was founded last week or last year. Or it might only stretch back to a particular turn in the organization’s history. I began working at KPMG in 2005, shortly after a tax-shelter scandal that resulted in a deferred prosecution agreement with the government. The narrative at the time hinged on that event: we were going to become the firm with the most integrity and the highest-quality work. Sure, we could have traced our origins to the 1800s and the four partners that make up the letters of the name, but that wasn’t the story we were telling; that wasn’t the firm we were trying to be. Our story was of a new beginning, of a murky past and a better future.
  2. Shared values. It’s no coincidence that the greatest philosophers, scholars, and scientists of ancient Greece lived and worked in Athens, the city of Athena. Out of all possible patron gods, its founders chose the goddess of wisdom–not the god of war to have a powerful military, the goddess of fertility to have abundant farmland, or the god of the forge to have unparalleled industry. The story of Athens defined the city’s key value, and elevated that value above many other perfectly good values. If you lead an organization, I urge you to pick one value above all others that is of special importance to this group of people. Then make sure it is embodied in your founding myth.
  3. Shared destiny. It’s never enough to simply share a past. In order to build a community, people have to believe in a shared future that follows from that past. Your shared destiny is the natural result of the values that call you out of your origins; the message is that all that is needed for you to go from where you were to this bright future is to embody your values. Often this destiny is something you know can be achieved because in your founding myth it has been achieved before: George Washington’s presidency, David’s kingship, Steve Jobs’ release of the iPhone. But if your organization is too new to have past successes, or if you’re overseeing a major shift in culture and values, focus on the promise of the future you are trying to achieve.

Through all of these, the operative word is “shared.” You can’t dictate a new future from on high; it has to be something that each person in your organization can believe, a destiny and a set of values that each individual wants to execute. Be aware that this may also be a way to cull your membership; those who aren’t interested in being a part of your shared story may not belong in your community.

Of course, the one thing this story is missing is a character. The character is a champion. The story isn’t about the champion–not really–but the champion breathes life into the ideas. She emerges from the shared past (like everyone else), embodies the shared values (like everyone can), and creates a shared destiny (by virtue of her embodiment of those values).

George Washington was a simple land owner who embodied the values of liberty and equality, led the military forces of rebellion, and eventually became the first President of the United States. David was a humble shepherd who embodied the values of piety and wisdom, overcame both the Philistines and the forces of Saul, and became the first in a long line of kings. Neither of these men were perfect even in the myths–in fact, being an ordinary, flawed human being is important. But because they embodied the shared values, they brought about a bright destiny for all their people.

You might in fact be the champion of your organization’s founding myth, like Jack Welch was at GE. But the myth isn’t about you, it’s about the collective identity.

Once you’ve laid out what you want your founding myth to be, you will need people to buy into it. But recognize that your founding myth is what the people in your organization believe it is. It’s the story they tell, not the story you tell. The closer your myth is to the story people are already telling, the better you will be able to convince them. But remain open to the possibility that your story will need to go through several revisions before everyone’s on the same page.

What Is Story Good For?

In my post “How To Gather Your Community” I discussed the importance of your organization’s story. When I say “organization,” I don’t just mean your company as a whole. Each department, branch, or working team in a larger organization has a story as well. Nor do I just mean businesses. Unions, churches, nations, tribes–every human organization of any kind has its own kind of mythology that defines its identity.

Yet even though we have a story for every organization in our lives, the function of story seems to be poorly understood. An organization will often try to tell “stories” instead of its own story. These can be useful–for example, user stories help to clarify the experience of using a product. But they are no substitute for a clear understanding of your organization’s own narrative.

Your organization’s story is more powerful and more important than any strategy or mission statement. An organization will play out the story its people believe.

Everyone in your organization already believes a particular story about it. Take a look at The Office–either the British or the American version will do. The boss has constructed a narrative that the company is on the up-and-up and the employees are rallying to the banner. The employees believe their story is one of a company in decline and a boss in denial. Which of these stories is the company playing out?

For the company in The Office (Wernham Hogg/Dunder Mifflin) to turn around, the very first thing it needs is to look at its facts and find a reasonable, value-driven, forward-looking narrative–a founding mythology with a bright future.

Once the organization has a narrative, it needs to act out that narrative. The larger an organization gets, the greater the tendency to try something small and new without radically changing anything. But unless you act upon your new story, you’re just writing fiction. People will believe the narrative that’s playing out, not the narrative you’re telling.

Nor is it enough for the leadership alone to act out a new narrative. Each employee needs a place within the narrative that she is energized to act out.

I’ll be exploring each of these steps this week.