- Software Project Delivery
-
-
Analysis
Project Delivery
Design
Development
Software Testing
- Unit Testing: Is It Worth the Effort?
- Test and Automation Strategy: A Deep-Dive Into an Essential Solution for Your Daily Agile Practices
- Software Testing and Quality Assurance: A Modern Analysis of Its Internal Dynamics and Impact on Delivery
- Stress and Performance Tests for Online Systems: How to Prepare, Execute, and Analyse Their Results
Support
-
- Business Management
-
-
Soft Skills
Organizational Culture
- Organizational Culture: The Edgar Schein Model
- Operational Excellence in 7 Quotes From Its Founding Fathers
- Cultural Transformations and Resistance to Change: Understanding the Risks to Your Organization’s Growth
- Organizational Culture, Transformation, and Change: FAQ
- Human Groups as Complex Systems: Structure, Organization, Power Distribution, and Dynamics
Processes
- Decision Making In a Professional Environment: Techniques and Pitfalls
- Principles of Operational Excellence in Software Development
- Engineering Superior Production Processes: A No-Nonsense Guide for Everyone
- Thoughts on Six Sigma for Developing Your Software Engineering Processes
- Process Management, Improvement, and Redesign: The Essential Guide for Boosting Your Performance
- C++ or Java: What You Need to Consider Before Making Strategic Technical Decisions
- Technical Risk Management and Decision Analysis — Introduction and Fundamental Principles
-
- Science &Technology
- Book Reviews
-
-
Business Books
- Book Review: The 7 Habits of Highly Effective People
- Book Review: The Toyota Way – 14 Management Principles From the World’s Greatest Manufacturer
- Book Review: Organizational Culture and Leadership
- Book Review: Six Frames for Thinking About Information
- Book Review: The Six Sigma Way — How GE, Motorola, and Other Top Companies are Honing Their Performance
General Interest
- Book Review: Thinking Fast and Slow
- Book Review: Sapiens — A Brief History of HumanKind
- Book Review: Fooled by Randomness — The Hidden Role of Chance in Life and in the Markets
- Book Review: The Black Swan — The Impact of the Highly Improbable
- Book Review: QED – The Strange Theory of Light and Matter
- Book Review: The Greatest Story Ever Told So Far — Why Are We Here?
- Book Review: Programming the Universe — A Quantum Computer Scientist Takes on the Cosmos
-
- FAQs
- Subscribe
1. Overview
In this article, we try to examine and answer the most common questions on organizational culture.
The ideas and concepts are derived from Edgar Schein‘s seminal work which can be found in his 1990 paper or fantastic book on Orgazniational Culture and Leadership.
2. Organizational Culture FAQ
Organizational culture is a set of hidden rules and assumptions that govern the behavior of an organization.
These rules and assumptions allow the organization to respond to external pressures (such as competition) and internal integration pressures (like dealing with conflict).
An influential model of organizational culture is the one developed by Edgar Schein.
If an organization faces existential threats, it might need to change its culture. This is also known as organizational cultural transformation. These are usually painful and can either lead to the survival of the organization or its decline and fall.
Leadership influences organizational culture at every stage of its lifetime.
Organizational culture emerges and develops based on the actions/responses of the founding fathers during the early stages of the organization’s life. These initial responses are then confirmed by subsequent events and become assumptions that are rarely questioned.
During the organization’s midlife, leadership maintains the existing culture by influencing and managing the integration of new members and replacing those who moved on.
In times of crisis, transformation leaders are brought from outside the organization to manage the change. Outsiders are not emotionally attached to the existing cultures and are ready to drive the changes through the turmoil.
Organizational behavior is defined by the organization’s response to both internal and external challenges.
The way it deals with integration issues, like conflict and challenges to its leadership and external issues such as competition, changing customer requirements, disruptive technologies, determine an organization’s behavior.
The Greek philosopher, Heraclitus, once said: “change is the only constant”. This applies equally well to organizational culture.
New members coming in, old leaders moving out, new threats, and new challenges are all part of the natural forces that compel organizations to change.
Two examples of organizational culture (derived from Edgar Schein’s book on organizational culture and leadership) are as follows.
Organization A believes in internal competition, prefers centralized control, and trusts that responsible people with good will can solve problems.
Organization B believes in individualism, truth through conflict, personal initiatives, creativity, innovation, and individual responsibility.
Edgar Schein developed one of the interesting theories on organizational culture.
His idea is based on the assumption that a group of people working towards a specific objective over a shared history will develop shared knowledge (which he refers to as assumptions).
These assumptions govern all aspects of the group’s interactions. These are rules dictating the inclusion or exclusion criteria from the group, agreement on the nature of time and space, development of intimacy, love, and affection, distribution of power and status, rewards and punishments, and finally managing the unmanageable (such as religion and politics).
One particular model of organizational culture was proposed by Edgar Schein in his 1990 paper on the topic.
Schein proposes a model built around a group that has shared a sufficiently long and shared history. Their common experience in the face of internal and external threats and under the influence of their leaders allowed them to form some assumptions and gather around specific values. These assumptions and values manifest themselves through observed artifacts (such as office setup) and subtle behaviours such as dealing with internal conflict.
Organizational culture is the invisible hand that governs the behaviour of a particular group, in this case, either the organization as a whole or its subgroups.
Organizational culture is responsible for two aspects of an organization’s dynamics, both of which are vital to the performance and even survival of the organization.
The first is maintaining the cohesion of the group in the face of internal pressure. The dominant culture governs the inculturation of new members, management of conflict, allocation of status and power, and distribution of rewards and punishments.
Another aspect of an organization’s culture dynamics is surviving external threats and staying in the game. Organizational culture is thriving if it allows its regeneration and renewal through transformation. This capability will enable it to adapt and survive disruptive changes in its environment.
Cultural clashes 43% and General organizational resistance to change 42% have been repeatedly cited in the State of Agile Report as the top detractors from Agile adoption by participating organizations.
The State of DevOps Report also showed the same signs despite the proven benefits of both methodologies.
Individuals can show resistance for several reasons, especially if it adversely impacts their current status and privileges and challenges the concepts that placed them where they are.
The traumatic and anxiety-ridden experiences that it has to go through while it unlearns its previous assumptions and learns new ones can explain organizational resistance to change.
Organizational culture is a cognitive construct that allows groups trying to achieve a common objective to cope with internal and external pressures.
In this manner, it is neither positive nor negative. It can be viewed as a tool for dealing with the challenges posed by the environment.
Perhaps a better adjective for organizational culture might be healthy vs toxic. A healthy culture allows the group to grow, perform, and more crucially, survive disruptive changes.
A toxic organizational culture stifles growth, impedes progress, and endangers people’s morale and mental wellbeing.
From Edgar Schein’s book: “Whether or not a culture is ‘good’ or ‘bad’, ‘functionally effective’ or not, depends not on the culture alone, but on the relationship of the culture to the environment in which it exists.”
The strength of an organizational culture derives from how strong its values and assumptions are held by its members.
This in turn derives from two factors:
A) How traumatic were the experiences from which the culture emerged
B) How much anxiety-reduction capabilities it holds
B) The dominant personalities of its founders
Quoting Edgar Schein from his book on Organizational Culture and Leadership: “If a basic assumption comes to be strongly held in a group, members will find behavior based on any other premise inconceivable”.
The characteristics (or levels) of organizational culture in Schein’s model are:
A) Artifacts
B) Espoused Beliefs and Values
C) Underlying Assumptions
The Artifacts encompass the visible organizational structures and processes. These could be the office’s layout or whether a high or low voice is used for communications. Artifacts usually are hard to explain without additional knowledge.
Espoused beliefs and values are the strategies, goals, philosophies (or espoused justifications that allow members of the organization to make sense of why they are doing things in a certain way).
Finally, the underlying assumptions are the unconscious thoughts, feelings, and axioms that motivate the group’s behavior.
A successful management of cultural transformations will depend on three factors:
A) Cultural transformations cannot kick-off without enough data made available and which indicates that changes in the environment have occurred, and that these changes jeopardize the strategic goals of the organization.
B) The organization needs to have enough psychological safety to recognize the possibility of a successful transformation without having to compromise its image and reputation.
C) Change Managers or Transformational Leaders, possibly from outside the organization, are likely to be needed to carry the change over as they will not have the same trouble unlearning some of the, now sacred, assumptions on which the culture was built.
3. Featured Articles

Understanding and Managing Technical Debt
1. Overview Technical debt is a concept first coined by Ward Cunningham, one of the co-authors of the Agile manifesto. When recounting the story, he explains how he used the metaphor of financial debt to explain why they needed to refactor part of an existing codebase for a product they were developing. Somehow, the businessContinue reading “Understanding and Managing Technical Debt”

Technical Risk Management and Decision Analysis — Introduction and Fundamental Principles
1. Overview I could not find a better way to start an article on Risk and Risk Management than by quoting the opening lines of Donald Lessard and Roger Miller’s 2001 paper that, briefly but lucidly, summarizes the nature of large engineering endeavours. It goes like this: This article leans heavily on three handbooks thatContinue reading “Technical Risk Management and Decision Analysis — Introduction and Fundamental Principles”

Complexity and Complex Systems From Life on Earth to the Universe: A Brief Introduction
1. Overview Dealing with complexity is an integral part of our lives, even if we do not realise it. An organisation can be modelled as a complex system from the scale of megacorporations right down to the smallest teams. The architecture of software solutions can be equally complicated, and megaprojects and implementations are certainly involved.Continue reading “Complexity and Complex Systems From Life on Earth to the Universe: A Brief Introduction”
Book Review: Programming the Universe — A Quantum Computer Scientist Takes on the Cosmos
Synopsis Most physical theories adopt a mechanistic view when examining natural phenomena where any system can be modelled as a machine whose initial conditions and dynamics govern its future behaviour. In this book, Programming the Universe — A Computer Scientist Takes on the Cosmos, Professor Seth Lloyd proposes a radically different approach centred around aContinue reading “Book Review: Programming the Universe — A Quantum Computer Scientist Takes on the Cosmos”

From Abstract Concepts to Tangible Value: Software Architecture in Modern IT Systems
1. Overview Software design and architecture are two very elusive concepts; even Wikipedia’s entries (ref. architecture, design) are somewhat fuzzy and do not clearly distinguish between the two. The Agile manifesto’s statement on architecture and design is especially brief and raises more questions than answers. The most common definition of software architecture is as follows:Continue reading “From Abstract Concepts to Tangible Value: Software Architecture in Modern IT Systems”

Business Requirements and Stakeholder Management: An Essential Guide to Definition and Application in IT Projects
1. Overview The complexity of business requirements in IT projects has experienced exponential growth due to pressures by increasingly sophisticated client preferences, novel technologies, and fierce competition. Consider, for example, the case of financial payments. In the mid-80s, most payment transactions occurred inside bank branches, and only the biggest banks offered services on ATM orContinue reading “Business Requirements and Stakeholder Management: An Essential Guide to Definition and Application in IT Projects”
Loading…
Something went wrong. Please refresh the page and/or try again.