Showing posts with label Culture. Show all posts
Showing posts with label Culture. Show all posts

Many cultures

You must, as a 21st Century human, participate in many cultures.  Your business definitely does as well. Not only that, but in my opinion, in the case of your business, it actually should have many (or at least multiple) cultures. Just so you know, I have colleagues who vociferously disagree with that last bit -- who think that a business should have one culture that is pervasive throughout every aspect of the business. So let me explain my position on this disagreement.

First of all, what do we mean when we say "a culture"? Here's a pretty good definition that matches the way I use the term: "a set of ideas, beliefs, and ways of behaving of a particular organization or group of people". (By the way, I found this by using one of my favorite sites -- www.onelook.com.)

Ideas, beliefs, and behavior of a particular organization or group. This is not a wishy washy, touchy feely matter. Hard-nosed business people take culture very seriously. Here's what Lou Gerstner says about his time as the CEO of IBM: “In all of my business career, I would have always said that culture is one of the five or six things you worry about if you're a leader. You worry about markets, and competitors, and financial assets and strategy. And somewhere on the list is culture. What I learned at IBM is that culture isn’t part of the game. It is the game.” (Gerstner, 2002). So, yes, your business is a particular organization, and there is probably a recognizable “corporate culture”.

Another example I observed personally of cultures at work was the regional telephone company where I worked for a few years, not too long after the breakup of AT&T.  Prior to divestiture, it was common for people to refer to the unified, national telephone company as "Ma Bell".  This sounded to my outsider's ears as a relatively meaningless cliche.  But looking at the company from inside, in a time of great turmoil, that phrase took on real, and poignant, meaning.  One of the people I worked most closely with was a 3rd generation Bell employee.  Her father's name was carved in a granite wall in the lobby of the headquarters building, as one of dozens of heroic employees, who had made a life-saving rescue from a flooded river.  He had been a District Manager, and following in his footsteps, she later also became a manager of a local office.  She would tell the story about how part of her actual responsibility was to check up on an employee after a couple of days of absence.  And how her responsibility included a personal visit, to take groceries to the home of the sick employee.  By the time I heard such stories, the company was well down the path of culture change, from the parental guardian of community and employees, to a marketplace competitor with more "modern" perceptions of its role in the marketplace

Elements of a corporate culture include: norms of behavior, guidelines for handling various types of situations, styles of dress (even uniforms), manner of conducting working interactions, ceremonies and manner of celebrating.  A corporate culture generally originates from the personalities of the founders, as well as founding stories or creation myths that get passed down and elaborated over time.

However, there are other sources of cultural elements, aside from the unique corporate culture that the founders have passed down.  The primary sources of these additional cultural elements are the professional disciplines that are required to run a business.  Think about accounting.  Think about sales.  Could there be any more distinctive cultures (ideas, beliefs, behaviors) than the risk-alert accountant, the bean counter, vs. the star salesperson who takes whatever risk is necessary to close the deal?  Or how about sales vs. engineering?  "If we can sell it, those guys can make it work."  

But remember, I said that your business should have multiple cultures.  Behind those stereotypic images, there are very good reasons to support a dynamic tension between a culture of risk-taking, and a culture of risk mitigation.  A culture that deals in excitement and enthusiasm in the marketplace, balanced by a culture of delivery of robust, high-quality products and services.  These, and many others, are necessary.  But what's equally necessary is to maintain balance among them.  This is a key challenge for you as a business leader.

Understanding cultural factors can give you the ability to predict how various interventions and stimuli will be received by organizations.  And cultural practices can actually be designed, especially if you can find the expert consultant who can do just that. An example is Sara Moulton Reger's technique -- patented, practiced, and written up in her book Can Two Rights Make a Wrong: Insights from IBM's Tangible Culture Approach.
Perhaps you already know you are dealing with cultural element that are out of a healthy balance.  Remember, some dynamic tension is actually healthy, but constant conflict can also be destructive, and an unhealthy drain on energy.

To get back to the hub list of healthy business factors, click here.
To get back to the discussion of businesses as living systems, here.

Many languages

How often do you find that people in your business seem to be talking past each other?  Or, to put it a different way, how often does it seem that you keep going around and around with people who can never seem to agree, even though it appears that they have the best intentions, and have the good of the business at heart?  Maybe this is because they are actually speaking different languages, even though it appears that they are all speaking "English"!

In order to get a handle on this, let’s descend into the deep world of philosophy.  Well, not so deep actually!  Only so deep that we find some surprisingly practical help.  This help comes from Ludwig Wittgenstein, who said that 'philosophers must leave the frictionless ice and return to the "rough ground" of ordinary language in use.[1] Here is a quote from Wittgenstein that gives some perspective on the situation as we find in almost all business contexts, at least beyond the solopreneur, where there is any division of work among specialists:  “Let us imagine a language ...The language is meant to serve for communication between a builder A and an assistant B.  A is building with building-stones; there are blocks, pillars, slabs and beams. B has to pass the stones, and that in the order in which A needs them. For this purpose they use a language consisting of the words 'block', 'pillar', 'slab', 'beam'. A calls them out; --B brings the stone which he has learnt to bring at such-and-such a call. -- Conceive of this as a complete primitive language.  … I shall also call the whole [of language], consisting of language and the actions into which it is woven, the 'language-game.' “

The point here is that this great philosopher recognized that workers create and communicate by their own specialized languages.  And, he has given us some terminology to use in communicating about these different vocabularies, and styles of communication.

One of my favorite examples of a colorful, business-specific language-game comes from the company we saw that embodied the "business dream".  This resort condominium exchange company had an amazing overloaded usage of the word “week”.  Far from the normal, everyday usage as 7 days of calendar time, for this company the week was their reason for existence.  Anyone who has ever bought into a timeshare plan in a resort location knows that they acquire the rights to occupy a particular facility during a particular time period during every subsequent year. 

One of my favorite language examples is from my few years working for a post-divestiture Regional Bell Operating Company.  I worked in the strategic IT planning organization, but I had the opportunity to ride in a van pool on a 90-minute commute each way to the headquarters offices.  It was during that time spent with employees from all over the business that I learned the many meanings of the term "central office".  One might assume that this term referred to the HQ office building where we were all headed.  But no, in these conversations, the term "office" was closely associated to the word "exchange".  This was the location where telephone switching equipment was housed, and served particular geographic regions.  By then, the equipment centers were largely cavernous, nearly empty (because of equipment miniaturization) vaults within massive concrete structures.  Central office meant that kind of building.  It also meant the equipment that served the region.  It also referred to the range of phone numbers served, designate by central office (CO) code.  One day I overheard, "I used to have an office in the central office", and I actually understood what this meant!  And I wondered, how does if feel to have an office in the Central Office?  My observation was that it was a point of pride – a kind of badge of honor, to work every day in such a hub of technology.  Which helped drive home the point of convergence between business culture, and various business language-games.

It is often the case that people in your business are able to make sense of different language-games, and how they use the same words in different ways, simply because human beings are very good at providing context to make sense of each other's usage.  But it becomes a whole different story when computerized information systems are introduced into the mix.  Computer technology has raised the bar on the need to clarify ambiguous and overloaded language.  Failure to really get clear on how different groups express their business issues can easily turn into health issues of time-wasting communication glitches, and even worse, glitches that are codified into computerized information systems.

In your business you are likely to encounter a predominance of certain categories of information than others.  Language models can reveal the importance of the same concept from one domain to another.  Models from two different companies indicate the importance of contractual agreements in the insurance business.  In fact, many insurance terms are classified under both the concept of agreement and the concept of product.  This is because a policy, which is a contract, is actually the basic product of the insurance industry.  Without contracts, there is no business.  This is contrasted with a model done for a cellular telephone company, where there are very few terms that refer to contracts.  Contracts are rather casual pieces of paper that are signed upon commencement of service, and as many as 40% never make it from the retail distributor back to the appropriate corporate file.  Service, billing, and collections proceed unimpeded, so that contracts are truly not a major issue.  These diverging models provide strong indication of the types of computer support needed by various businesses.

Experience with business language models generally evoke the positive reaction in business people.  There always seem to be significant insights, and great appreciation for this fresh view of language.  Wouldn't you be grateful that information systems professionals are willing to spend time to appreciate the unique meaning that infuses the language of your business?  

At the same time information systems professionals who have been exposed to this approach are almost unanimous in their positive reaction.  The most common reaction is “If only we had followed this approach on my last project!  It would have saved untold misunderstanding and rework.”  They recognize that detailed understanding of language avoids a number of common problems with information system development.  These problems include the cost of reworking inadequate requirements, the loss of credibility when delivered systems do match the needs of the business, the risk that projects will be so focused on the data processing “plumbing” that human communication and information needs will not be served, and the risk that analysts will drift off into a haze of abstractions that are too loosely coupled with the needs of the business.  The ultimate risk is that the form and operations of the business will be forced to conform to the resulting information system, instead of the other way around.

To get back to the hub list of healthy business factors, click here.
To get back to the discussion of businesses as living systems, click here.





[1] http://en.wikipedia.org/wiki/Ludwig_Wittgenstein