Go to Top
(800) 851-2530

To Change A Culture, Change The System

Just before the holiday break, I broached the subject of systems. And given the current management rage focusing on the power of distinctive corporate culture as the key enabler of constant innovation, it's worthwhile to think how systems and culture intertwine.

My friend Michael Shrage likes to talk about "innovation ecosystems," and in a recent talk he made the point that "culture trumps strategy." So let's think through this a bit.

The best and most consistent innovators have the ability to think through all the conditions and connections required to allow a given solution to fit seamlessly into the everyday beat of those who will use it. That kind of thinking is systems thinking.

It’s the ability to provide solutions within the current context, or providing a new one along with the solution.

I happen to believe that systems thinking isn’t natural, intuitive, or easy. And nowhere in our formative years do we get schooled in systems thinking. But it can be learned.

SYSTEMS THINKING

Thomas Edison was a systems thinker. He had to be to turn his invention into an innovation. He knew his little invention--the light bulb--wouldn’t change the world on its own. He knew, because incandescent lighting had already been developed, on the other side of the Atlantic. He knew the gas lighting industry (the existing system) held the real power, and a light bulb alone wasn’t going to dethrone it. He knew the real solution was about providing on-demand light and power to everyone.

And that required a whole new ecosystem to provide the proper context in which the light bulb could flourish.

In under three years and mostly with his own money, Edison built the entire electric power system. He designed, engineered and manufactured everything down to wiring: constructing power stations to convert steam power to electricity, digging and laying miles of wiring, insulating the wires to prevent damage and discharge due to moisture, and connecting the conduits in a workable network. He built and installed electric motors in the various types of machinery that would use the new power source, along with all the infrastructure needed to support the use of electricity, like meters, fuse boxes, lamp holders, switches, and sockets.

But here's the thing: we aren't all Edisons. We're not that good at systems thinking. All you have to do is read the headlines and tune in to a late-night talk show every now and again. The lack of systems thinking can be downright funny.

I still remember how United Airlines’s $700 million high-tech automated baggage system became the butt of jokes as it delayed the opening of the Denver International Airport well over a year and then regularly chewed up or lost luggage. The system featured miles of underground track with cart-to-computer communication via radio frequencies, and promised to revolutionize the airport experience. Television crews covering the debut split their sides as they watched carts overshoot luggage onto the tracks and get sliced up by other carts.

After a rather painful ten years and nearly a billion dollars in operating costs, United’s Chief Operating Officer was quoted as saying, “We have come to the conclusion that going to a manual approach is best.”

Some stories aren't so funny, though. And what strikes me is how in the near-perfect vision of hindsight, "culture" is often blamed for the most devastating of disasters and tragedies.

It's been a decade since The 9/11 Commission Report cited the most important failures as being “lack of imagination” and “cultural asymmetry,” explaining that “To us, Afghanistan seemed very far away. To members of Al Qaeda, America seemed very close.”

Really? Wasn't is more that a small, highly-organized, well-funded, and extremely inventive organization successfully accomplished a goal because their systems and structures were properly focused to do so, while the U.S. intelligence systems and agency structures were simply no match, because they were at that time designed primarily for enforcement, not prevention.

It's also been a decade since the Columbia exploded over Texas, followed by the report of the Columbia Accident Investigation Board which blamed “broken safety culture,” “can-do culture,” and “perfect place culture” as being behind the neglect of early warning signs and clear equipment failures discounted as “in-family” events.

Really? Wasn't is more that NASA’s key processes were inherently biased to operate on inputs designed to produce the desired output: lift-off?

Here's the interesting thing: in both cases, the remedies revolved around bolstering systems and structures. They were NOT aimed directly at "culture."

In the case of 9/11, the commission recommendations were to “routinize” and “put in place systems” and “provide a framework” for analyzing improbable scenarios. That sounds like systems thinking. They suggested having a “coordinating mechanism” to ensure intelligence goals are met. The cabinet-level Department of Homeland Security was formed. And that sounds like structure.

Likewise, in the case of NASA, when the near-miss of the 2005 Discovery mission reminded everyone of the agency’s shortcomings, new administrative leadership promised to refocus the organization by resetting priorities and measures, realigning programs and processes, and restructuring.

I don't think it's such a big secret why culture is the favorite culprit named for a lack of creativity and innovation. It pulls together all the most visible company dynamics: management styles, budget policies, political practices, office environment, interpersonal relationships, and decision speed.

BIG COMPANY SYNDROME

But there’s a deeper root cause related to the system and structure from which the culture springs: what my friend and former Toyota Group VP Bob Bennett once explained to me as "Big Company Syndrome."

It's prevalent in large corporations with weak or loosely defined systems and structures, can be deadly if gone untreated, and goes something like this:

Constant, company-wide innovation is not something requested, managed or measured at the organizational level. Therefore the desire for personal reward and recognition drives an informal system intended to produce a promotion and bonus, which results in a strong program mentality. Meaning, sell a program up and request more capacity and resources in the form of bodies and budget, regardless of whether it adds value. Approval is granted because it produces a favor owed and supports the boss' own career ambitions. Objectives now become focused on meeting budget projections. Company expenses then rise faster than sales, and add further complexity. That limits organizational effectiveness, requiring even more work to execute the program, leading to yet further requests for more resources. When costs swell, senior management puts the squeeze on to stem the tide. Speedbumps get erected, often in the form of additional project approvals and heavy-handed governance. Valuable ideas get iced along with circumspect programs. Eventually, the ability to flex, react and innovate is lost.

Now, compare that to a design studio or entrepreneurial outfit, both of which organize themselves around customer-focused goals, projects and processes, not functions. Projects have a clear start and stop, so resources are mobilized to match the need.

But over a certain size, the entrepreneurial structure grows up and gives ground to the Big Company Syndrome…IF you let it.

Can the Big Company Syndrome be turned around? Is there a way to recreate the creative shop experience and entrepreneurial spirit to ensure constant innovation even when the Big Company Syndrome has a strangle hold on the organization?

Yes, through strong systems and solid structures focused on creating the right social context. YOu do NOT attack "culture" directly, for the simple reason that people will hold on even tighter to the culture you're trying to change.

Stay tuned for a future post. For now, the message is this: to change a culture, focus on the system.

2 Responses to "To Change A Culture, Change The System"

  • Shrikant Kalegaonkar
    Tuesday, January 7th, 2014 - 12:19 PM

    Dear Mr. May,

    Through the books I’ve recently read I’ve come to see culture as an output, a result or an emergent property of a system. Furthermore, just like all outputs, it cannot be managed directly, as you pointed out in your post. The only way to manage outputs is to change the inputs to the system and/or change the system.

    I believe we’re wired to focus on outputs and sort good from bad. And, why not? For most of our evolution we’ve never had any control of our environment. We’ve been a part of the system. In that context it’s perfectly natural for us to comment on culture and sort it into good or bad. However, just as you can’t inspect quality into a product as Dr. Deming pointed out, you can’t improve culture by calling out its positive or negative attributes.

    In the case of the modern organization, perhaps you can select the type of people to minimize cultural diversity. (Cultural diversity here refers to mindset, drive, focus, etc.) But in my experience, with the way that process (i.e. interviews) works right now, it amounts to shots in the dark. Better to setup a system that is robust to the variation in its human resource to yield a cohesive culture.

    System design requires designers (leaders) who have a vision for the system. They must understand the context for their system and then design their system to produce the desired result. These are all learnable skills, but so few bother. It’s hard work. There’s no instant pudding. But who’s got the time?!

    Best regards,
    Shrikant Kalegaonkar
    Twitter: @shrikale

  • A Reflection on Culture | Iterations
    Tuesday, January 7th, 2014 - 1:04 PM

    […] like all outputs, it cannot be managed directly, as Matthew E. May points out in his post “To Change A Culture, Change The System.” The only way to manage outputs is to change the inputs to the system and/or change the […]