Showing posts with label Interdependence. Show all posts
Showing posts with label Interdependence. Show all posts

April 11, 2011

Optimizing Culture For Performance

Interdependence

Strategy + Business (Spring 2011) has an interview with Edgar Schein, the MIT sage of organizational culture.

In it, he describes why it is so hard to change this.

In my experience, organizational culture is key to success.

Why do we want to change organizational culture to begin with?

Sometimes it becomes dysfunctional and can get in the way of performance.

Sometimes, leaders think they can simply change a culture, but Schein disagrees. He says that you cannot simply introduce a new culture and tell people to follow it--"that will never work."

"Instead you have to...solve business problems by introducing new behaviors."

However, you cannot solve problems or even raise concerns where "in most organizations the norms are to punish it."

Schein states that "the people with the most authority...must make the others feel safe"--to speak up, contribute, and even make mistakes.

Schein goes on to call for people "to work with one another as equal partners"--breaking down the traditional organizational boundaries--so that we stop telling people, so to speak, that "you're in my lane" or "that's above your pay grade."

He goes a step further, stating that the healthiest work cultures are interdependent, meaning that people actively try to help one another solve problems.

What an enormously powerful idea, that everyone has something valuable to contribute. Every opinion contributes to the dialogue--and all employees are worthwhile.

That is my definition of a healthy culture, for the organization and its people.

Share/Save/Bookmark

November 21, 2008

Collaborative Enterprise Architecture

One of the ways that traditional enterprise architectures often goes awry is when the enterprise architects hole up in their ivory tower to plan and govern. Typically, this results in the rest of the organization ignoring the plans and the architects, both of which soon become shelfware.

The only way for enterprise architecture to genuinely succeed is for the architects to climb down from their ivory tower and work hand-in-hand with the business and IT subject matter experts to build a user-centric enterprise architecture that speaks to the genuine needs and culture of the organization and its people.

Enterprise architecture needs to be a collaborative initiative where difficult problems get identified and resolved by vetting issues, best practices, and solutions among organizational stakeholders. In this user-centric model, the architects and business and technology stakeholders build an proverbial alliance and work together to develop and maintain architecture plans that are valuable to and actionable by the organization. The architects provide the leadership, structure, principles, and processes to guide the architecture development, and the stakeholder, subject matter experts contribute and vet the content with the architect staff. Neither group can be truly effective without the other.

In a broader sense, the concepts of user-centricity and collaboration that enable an enterprise architecture to succeed at the organizational level can be applied at higher levels (e.g. globally) to solve the most challenging problems we face in the world today.

The Wall Street Journal, 7 November 2008, ran an interesting editorial by Will Marshall, the president of the Progressive Policy Institute.

In this opinion piece, Mr. Marshall calls for “a new progressive internationalism” for America. He argues that rather than go it alone, America should build international alliances to tackle the difficult problems and build a way forward. He says that “Alliances don’t tie American’s hands, so much as extend our global reach.”

In other words, America can’t function as traditional enterprise architects solving the world’s problems out of an ivory tower, but rather we need to work with other nations around the world jointly tackle these.

But aren’t we smart and innovative and capable in America. Why can’t we just solve the problems on our own (the ivory tower approach)?

Marshall states: “In today’s increasingly interdependent world, no nation is strong enough to go it alone. We need other countries’ help to solve problems of the global commons like today’s financial crisis, terrorism, climate change, the depletion of natural resources, pandemics and poverty.”

Similarly, enterprise architects can’t solve our organizations’ problems alone. Architects cannot have the breadth nor depth of subject matter expertise, nor the where-with-all to implement even the best laid plans without the stakeholders that stand to benefit.

Now certainly there are times of peril or when decisions need to be made quickly that someone has just got to “make the call” and there is no time to collaborate, fully vet the issues or build consensus, but this should be the exception rather than the rule, since collaboration trumps going it alone far more often than not.


Share/Save/Bookmark