Organizational Culture 101: A Practical How-To For Interaction Designers

Organizations are tenuous phenomena; they can fall apart at any time. To navigate the landscape of organizational culture interaction designers need a set of practical tools, language & knowledge drawn from the world of cultural anthropology.

It’s happened to all of us. We walk into what we think is a Web redesign project, only to find we have unwittingly ignited the fires of WW III in our client’s organization. What begins as a simple design project descends – quickly – into an intra-organizational battle, with the unprepared interaction designer caught in the crossfire.

What is it about design projects that seem to attract such power struggles? Contrary to what you might think, being stuck in the middle of an internecine battle is actually an opportunity to effect meaningful change on your client’s organization. But it requires a set of practical tools to negotiate these battles and a more sophisticated language and knowledge to exploit these events to create meaningful change.

The Glue Inside Organizations: Taken-for-Granted Assumptions

Organizations are tenuous phenomena; they can fall apart at any time. It’s quite extraordinary, actually, that organizations don’t spontaneously disintegrate regularly. Organizations have no force of law or violence. They cannot force their members to remain within them. Their members are autonomous adults and can leave, reject, or even revolutionize the organization at any time. Yet organizations endure, held together by taken-for-granted patterns of social interaction.

These patterns of interaction are exactly what the organization must have to survive. Everyone must share what sociologists Berger and Luckman call a “common stock of knowledge” – like using “bandwidth” synonymously with “time” – for an organization to function properly. We could not waste time at every meeting explaining what “bandwidth” or “DTC” or “short selling” mean. Instead we rely on this common stock of knowledge; newcomers must be inculcated with this knowledge for the organization to function.

This common stock of knowledge is exactly what keeps an organization together. The sum of this knowledge is often called “organizational culture.” IBM, for example, would not have the same stock of knowledge as, say, Zappos. What is taken for granted at Patagonia is not the same as what is taken for granted at Ford. Organizational culture is key to keeping an organization intact. Without this sum of knowledge, members of the organization would spend too much time trying to figure out what to do or say in given situations.

An organization simply could not function without its members knowing what to do, say and wear day-to-day. Interestingly, organizations that send out the “dress code memo” are actually reinforcing this argument. If its members are routinely wearing shorts and flip-flops to work, this suggests that the “common stock of knowledge” supports this kind of clothing. The “dress code memo” usually causes tension, derision, and – paradoxically – greater social glue among the casually dressed members of the organization.

Knowing what to do or say in any given moment gives us comfort. It is less stressful. It is efficient. It is even pleasant. Organizations must have a critical mass of its members in this comfort zone to continue to function. In other words, organizational culture must be firmly cemented with a large enough number of its members for an organization to endure.

The downside of culture: change is hard

Culture is, by definition, resistant to change. We like to know what is “appropriate” or normal in everyday situations and the more we engage in these behaviours, the more “normal” they become. The French father of sociology Emile Durkheim even had a word for not knowing what to do: “anomie,” or the lack of norms. Modern life was plagued with anomie, Durkheim argued, causing alienation and confusion.

Organizational cultures like to stay the same, even when it seems irrational. In her painstakingly detailed analysis of the Challenger crash, Diane Vaughan showed that NASA’s major failure was not technical at all. Rather, it was systematic denial which lead to a distortion of the real risks involved in using rubber O-rings on a cold morning. NASA’s organizational culture systematically downplayed certain kinds of information because it threatened the way the organization currently functioned. In a sense, it was the organization’s attempt to endure which paradoxically sowed the seeds of its own demise.

Understanding organizational cultures

Interaction designers are accustomed to discerning individual preferences, particularly for interactivity. But they may not be as well versed in understanding cultural preferences. Anthropology offers us a very clear framework for mapping cultures against key values.

Florence Kluckhohn’s “value orientation model” describes culture as a set of values. To that end, she suggested that cultures have five key elements to them.

Figure 1: F.R. Kluckhohn’s Value Orientation Model

A culture’s value orientation to nature, for example, can be one which values being in harmony with nature. Japan’s penchant for miniaturist design, for example, may be explained by its value of living in harmony with nature.

An organization’s orientation to time may hold the key to understanding why your design project is mired in the mud. How the organization collectively values the future has significant implications for interaction designers, which after all are the harbingers of a thing called “change.” Toyota, for example, exemplifies an organization that values “becoming” or ever aspiring. Such an organization values “new-ness” as inherently worthy.  The French wine-making industry, by contrast, values the past (to a fault, if recent market-share figures are an indicator of success). Reverence for tradition, celebrating its members’ long tenures, and elaborate discussions of past examples are key indicators of a past-oriented organization.

Interaction designers should pay close attention to how their client’s organization values activity.

An organization’s orientation to social relations is also important for interaction designers. The typical interactive agency (or management consultancy for that matter) values individualism. Sociologist Alice Lam calls this kind of organization an “ad hocracy,” which is highly innovative and creative. But such organizations are also very vulnerable to its knowledge walking out the door when the latest “rising star” takes her talent and knowledge with her to the next organization.

By contrast, Lam argues, banks are collective in their orientation. They value consensus above all. This may make decision-making maddeningly slow but it also preserves the organization. It ensures that all members of the organization share in the common stock of knowledge and thereby maintains the organization itself. Interactive agencies may be highly innovative, but they are also highly volatile. Banks may not be innovative but they are stable.

Interaction designers are accustomed to discerning individual preferences, particularly for interactivity. But they may not be as well versed in understanding cultural preferences.

Interaction designers should also pay close attention to how their client’s organization values activity. Some organizations care nothing for what may become of a certain project, if only that something is happening. This kind of organization values “doing.” But perhaps more common to Western organizations is the implicit value on “becoming.” German sociologist Max Weber became famous for his analysis of “the protestant work ethic,” which is really an exposition on the Calvinist value of “becoming.” To be a competent Protestant, Weber argued, one must always be aspiring to work harder, accumulate more and above all, delay gratification. This spirit is so key to capitalism that Western, capitalist organizations may all implicitly value this notion. In such cases, interaction designers may find themselves in the midst of an ever-aspiring organization that wants “best in class” wireframes and project plans but seems strangely unconcerned with a relative lack of actual progress.

Interaction designers finding themselves in the middle or an intra-organizational war may be working with an individualistic organization that values competition above all else. This is common to sales-driven organizations, that offer individual incentives and bonuses to their members.

Organization Design: How To Incorporate It Into Interaction Design Projects

Before you start a design project, evaluate your client’s organization. This need not be a detailed research project but an intuitive ethnographic craft. Stakeholder interviews provide a great opportunity to gather insight about the values of your client’s organization. A colleague and I used to call this stage “business ethnographic gathering,” or BEGging. Do ask about business requirements and goals. But pay attention also to what is valued.


Does your client spend an inordinate amount of time talking about the ways things have been done in the past? This may reveal a past-orientation. Honour that client’s value of the past. Celebrate past successes. Build “rituals of reverence” into your design process, where the organization’s members can savour the beauty and grandeur of their organization’s venerated history. Carefully frame innovation as putting icing on an already delicious cake. Above all, do not attack foundational elements directly. This is akin to throwing away the Mona Lisa.


Does your client take you into “confidence” frequently and reveal that everyone else in his organization “doesn’t get it”? Does he discuss how he would like to best his rival department? This client’s organization is individualistic and competitive. Consensus is still needed for collaborative design but this kind of organization makes collaboration difficult. For such a client, frame collaboration as an opportunity for him to be a “champion of innovation,” which all the individual glory thereto. Encourage him to be a “hero” for the organization and construct a narrative that allows him to be “victorious” but only if he becomes a collaborative, transformative leader.


Does your client’s organization have many symbols of future plans? Perhaps the walls are plastered with posters of its “next generation” goods or services. Perhaps your client spends much time talking about her future “vision” and how she wants to “inspire” her colleagues and her customers. The value here is placed on “becoming,” and not necessarily on “doing.” Your challenge as an interaction designer is actualizing her vision. The idea with this kind of culture is to create some material reality out of the constant visioning, but at the same time allowing the client organization to engage in this imagination process continually. Allow them to savour future “dreams” in concrete form.

In this case, frame your need for concrete deliverables and milestones as “best in class project methodology,” or an “innovative service delivery process.” Convince her that being a “next-generation organization” is about constantly materializing her visions. Show her prototypes. Bring her evidence of the first-mover’s advantage. And above all, show her current, existing evidence of how innovative companies continue to produce innovations instead of simply thinking about it.

When Culture Isn’t Enough

Even sociologists tire of organizations that are continually dysfunctional. As an interaction designer, you can learn to recognize when these organizations are beyond the power of one designer. If the organization has a critical mass of values that are antithetical to your own, then it may be time to move on. Even better, however, is to use the value-orientation model to pre-screen potential clients. We may not all have the luxury of picking and choosing only the clients we want but using a systematic approach beforehand will surely reduce the number of wars we unwittingly ignite within our client organizations.

Sam Ladner

Sam Ladner currently runs her own firm, Copernicus Consulting Group. She specializes in uncovering insights for organizations designing products, services, or processes. She holds a PhD in sociology from York University. She blogs at

19 comments on this article

  1. Pingback: Twitter Trackbacks for Johnny Holland - It’s all about interaction » Blog Archive » Organizational Culture 101: A Practical How-To [] on

  2. Pingback: Organizational Culture 101: A Practical How-To For Interaction Designers LZ power

  3. Pingback: Twitted by meghnaj

  4. Pingback: Organizational Culture 101: A Practical How-To For Interaction Designers wear

  5. Pingback: Organizational Culture 101: A Practical How-To For Interaction Designers- Forex4Trader

  6. Pingback: Organizational Culture 101: A Practical How-To For Interaction Designers GF power

  7. Pingback: Organizational culture 101: a practical how-to for designers « Design Research

  8. I believe this article is valuable for Web Designers, Designers, and Interaction Designers alike. Clients are Clients so please pre-screen, pre-screen, pre-screen

    There are many dysfunctional companies out there that do not communicate internally. So if the CEO has hired you to do a redesign without consulting management you will definitely have a hard time getting cooperation from employees who feel left out.

    So note to self, find out before you start what the situation at the company is.

  9. Pingback: Putting people first » Organizational Culture 101: a practical how-to for interaction designers

  10. I’m delighted by the specificity of your characterization of these organizations and the suggestions you offer. They remind me of design patterns for specific situations – any chance that there’s a larger body of culture-specific design patterns?
    As a student with no experience in consulting and less with big corporations, I find it hard enough to deal with new cultures as I migrate every few years.
    This makes a great prompt for what behaviors to look at and what part of the design solution to augment.

  11. Pingback: Twitted by letterpress_se

  12. Pingback: All This ChittahChattah | ChittahChattah Quickies

  13. Good reading and see a few central themes in this for all UX professionals and that is to a) Be the glue b) Facilitate this through design and c) Let them own the vision as its being delivered.

    Easier said than done but like the underlying approach.

    The hard part is navigating the waters inside an organization and it takes the senior people to help find ways to work together and support it constantly.


  14. Pingback: Company Culture Day? Bunka-no-hi, not bunkum … « Don’t Compromise!

  15. Pingback: Twitted by valeskaUX

  16. Zune and iPod: Most people compare the Zune to the Touch, but after seeing how slim and surprisingly small and light it is, I consider it to be a rather unique hybrid that combines qualities of both the Touch and the Nano. It’s very colorful and lovely OLED screen is slightly smaller than the touch screen, but the player itself feels quite a bit smaller and lighter. It weighs about 2/3 as much, and is noticeably smaller in width and height, while being just a hair thicker.

  17. Pingback: german sociologist

  18. Pingback: Our Bookmarks: Sep 7 - Sep 13 | Border Crossing Media

  19. Pingback: Material world «