3.2 Culture and Values in Project Environments (ICB4 4.3.5)

3.2 Culture and Values in Project Environments (ICB4 4.3.5)

[!NOTE] ICB4 Competence Context: Competence element 4.3.5, Culture and values, resides within the Perspective competence area of the IPMA Individual Competence Baseline (ICB4). This competence requires project managers to assess, respect, and align with the cultural paradigms and ethical standards of the host organization, the project team, and the wider society. It emphasizes that technical delivery methods fail whenever they conflict with the prevailing cultural values and tacit assumptions of the organization.

Culture has famously been described as "the way we do things around here." In project management, culture dictates how decisions are made, how risk is perceived, how transparently bad news is communicated, how authority is respected, and how team members collaborate across departmental and national boundaries. Project managers who ignore organizational and national cultures encounter invisible friction, unvoiced resistance, and demotivated teams. Conversely, project leaders who skillfully diagnose culture can shape a high-performing project micro-culture, foster psychological safety, and ensure long-term societal sustainability.

---

Deconstructing Organizational Culture: Edgar Schein's Three-Level Model

One of the most rigorous and widely cited frameworks for analyzing organizational culture was formulated by MIT Sloan Professor Edgar Schein. Schein defines culture as:

"A pattern of shared basic assumptions that the group learned as it solved its problems of external adaptation and internal integration, that has worked well enough to be considered valid and, therefore, to be taught to new members as the correct way to perceive, think, and feel in relation to those problems."

Schein conceptualizes organizational culture across three distinct levels, analogous to an iceberg, ranging from tangible, visible manifestations down to unconscious, deeply buried mental models.

+---------------------------------------------------------------------------------+
|                      Edgar Schein's Three Levels of Culture                     |
+---------------------------------------------------------------------------------+
| LEVEL 1: ARTIFACTS & BEHAVIORS (Visible Surface)                                |
| • Architecture, office layouts, dress codes, rituals, ceremonies, jargon        |
| • Written project templates, status dashboards, technology tools               |
| • Easy to observe, but difficult to interpret without deeper context            |
+---------------------------------------------------------------------------------+
| LEVEL 2: ESPOUSED VALUES (Conscious Strategies & Goals)                         |
| • Published mission statements, corporate values, codes of ethics               |
| • Stated project delivery philosophies ("We embrace agile experimentation")    |
| • May reflect aspirational ideals rather than actual day-to-day practices       |
+---------------------------------------------------------------------------------+
| LEVEL 3: BASIC UNDERLYING ASSUMPTIONS (Unconscious Core)                        |
| • Taken-for-granted beliefs, perceptions, human nature assumptions              |
| • Unspoken truths: "Never deliver bad news to executives", "Silos protect us"  |
| • Invisible, automatic, non-negotiable; the true driver of real behavior        |
+---------------------------------------------------------------------------------+

Level 1: Artifacts and Behaviors (The Visible Surface)

Artifacts include all the tangible, visible, and audible phenomena that one encounters when stepping into an organization:

• Physical Environment: Open-plan collaborative spaces vs. closed executive corner offices and cubicle rows.
• Language and Symbols: Internal acronyms, jargon, corporate branding, and humor.
• Myths and Rituals: Stories told about past heroic project managers, annual award ceremonies, or post-mortem blame sessions.
• Project Artifacts: Formal risk logs, Kanban boards, Gantt charts, and governance gate checklists. Limitation: While artifacts are readily observable, outsiders frequently misinterpret them unless they understand the underlying values and assumptions that generated them.

Level 2: Espoused Values (The Conscious Ideals)

Espoused values encompass the organization's declared philosophies, stated strategies, shared goals, and official codes of conduct. Examples include corporate slogans such as "Customer Obsession", "Safety First", or "We Celebrate Failure as a Learning Opportunity." The Dissonance Trap: In many organizations, there is a substantial chasm between espoused values (what people say they value) and values-in-use (the values that actually guide real decisions). If a company's leadership publishes an espoused value of "Total Transparency", yet publicly berates a project manager who accurately reports a red schedule variance, the espoused value is exposed as hollow rhetoric.

Level 3: Basic Underlying Assumptions (The Unconscious Core)

At the deepest level lie basic underlying assumptions: unconscious, taken-for-granted beliefs, habits of perception, and mental models that have become so thoroughly institutionalized that members view them as indisputable reality. Examples include:

• "Disagreement with senior management is dangerous to one's career."
• "Only billable engineering hours count; project governance is bureaucratic waste."
• "Marketing always overpromises, so engineering must build in secret buffers." When project change initiatives attempt to impose new practices (e.g., agile transparency) that conflict with these deeply rooted underlying assumptions (e.g., risk-aversion and fear of punishment), the underlying assumptions invariably prevail, suffocating the change.

---

Corporate Culture Typologies and Project Alignment

To tailor project governance and communication structures effectively, project managers must identify the overarching corporate culture archetype of their host enterprise. Two prominent models provide critical insight for the IPMA Level D exam.

Charles Handy's Four Cultural Archetypes

British organizational behaviorist Charles Handy popularized four distinct cultural types, each linked to a mythological archetype:

1. Power Culture (Web / Zeus):
   • Structure: Centralized web with power concentrated in a central key leader or small inner circle.
   • Operating Style: Relies on personal loyalty, direct phone calls, rapid intuitive decisions, and minimal formal bureaucracy.
   • Project Management Reality: Formal project documentation (WBS, Gantt charts) is rarely valued by leadership. Project success depends on maintaining direct personal contact with the central figure and aligning with their immediate priorities.
2. Role Culture (Temple / Apollo):
   • Structure: Classical bureaucracy organized by functional pillars and formalized hierarchies, supported by stable rules and procedures.
   • Operating Style: Functions through strict job descriptions, standardized processes, and formal committees. Predictable and stable.
   • Project Management Reality: Highly structured environment where stage gates, formal change control boards, and detailed documentation are mandatory. However, cross-functional projects often struggle with slow decision cycles and functional silo protection.
3. Task Culture (Matrix / Athena):
   • Structure: Dynamic, project-based network where multi-disciplinary teams assemble to solve specific problems and achieve tangible goals.
   • Operating Style: Authority is distributed based on expertise and technical capability rather than hierarchical rank. Highly adaptable, collaborative, and results-focused.
   • Project Management Reality: The ideal corporate environment for project management. Teams enjoy high autonomy, work collaboratively, and embrace iterative delivery, though they may experience friction over resource allocation between competing projects.
4. Person Culture (Cluster / Dionysus):
   • Structure: An association of autonomous, highly skilled individual professionals (e.g., barristers' chambers, specialized medical practices, university faculties, architectural cooperatives).
   • Operating Style: The organization exists solely to serve the individual needs and independence of its members, rather than members serving a collective corporate goal.
   • Project Management Reality: Project managers have zero command authority. Leading a project requires extensive consensus-building, personal diplomacy, and demonstrating how the project benefits each individual expert's practice.

Cameron and Quinn's Competing Values Framework

Kim Cameron and Robert Quinn established the Competing Values Framework, mapping organizational cultures across two dimensions: Flexibility vs. Stability and Internal Focus vs. External Focus:

• Clan Culture (Collaborative & Family-Like): High flexibility, internal focus. Emphasizes mentoring, consensus, employee development, and shared participation. Project managers lead as facilitators and coaches.
• Adhocracy Culture (Dynamic & Entrepreneurial): High flexibility, external focus. Emphasizes innovation, risk-taking, cutting-edge agility, and creative experimentation. Project managers lead as visionary change agents.
• Market Culture (Competitive & Results-Driven): High stability, external focus. Emphasizes competitive advantage, hitting measurable KPIs, speed to market, and profitability. Project managers lead as hard-driving results orchestrators.
• Hierarchy Culture (Structured & Process-Governed): High stability, internal focus. Emphasizes formal rules, standardization, risk elimination, and operational predictability. Project managers lead as rigorous administrators and compliance monitors.

---

Cross-Cultural Project Dynamics: Geert Hofstede's Six Cultural Dimensions

In modern globalized, virtual, and multicultural project environments, project managers regularly collaborate with distributed team members, international clients, and offshore suppliers. Dutch social psychologist Geert Hofstede developed the most comprehensive empirical model of national culture, identifying six core dimensions that explain systematic variations in societal values and behaviors.

+---------------------------------------------------------------------------------+
|                     Hofstede's Six Cultural Dimensions Overview                 |
+---------------------------------------------------------------------------------+
| 1. POWER DISTANCE (PDI)         | Hierarchical deference vs. Flat equality      |
| 2. INDIVIDUALISM (IDV)          | Personal autonomy vs. Collective group harmony|
| 3. MASCULINITY (MAS)            | Assertive competition vs. Nurturing quality   |
| 4. UNCERTAINTY AVOIDANCE (UAI)  | Rigid rule adherence vs. Comfort with ambiguity|
| 5. LONG-TERM ORIENTATION (LTO)  | Future sustainability vs. Short-term quick win|
| 6. INDULGENCE (IVR)             | Spontaneous celebration vs. Strict self-control|
+---------------------------------------------------------------------------------+

Detailed Analysis and Practical Project Applications

---

Fostering Project Culture, Team Norms, and Psychological Safety

While a project manager must respect the broader corporate and national culture, they also possess significant latitude to build a purposeful project micro-culture. Because a project is a temporary organization with a distinct mandate, the project manager can consciously shape the team's internal values and working atmosphere.

Establishing Explicit Team Norms (Social Working Agreements)

High-performing project cultures do not emerge by accident; they are intentionally constructed through collaborative team charters and explicit working agreements established during project initiation:

• Communication Norms: Preferred collaboration platforms (Slack, Teams, Email), expected response windows, and core working hours for distributed team members.
• Meeting Hygiene: Mandatory agendas distributed 24 hours prior, punctuality, active participation, and banishing multitasking during standups.
• Decision-Making Protocols: Establishing when decisions will be made by project manager decree, consultative input, majority vote, or full consensus.
• Conflict Protocols: Explicit agreements that debate must focus on technical and structural problems, never personal character.

Amy Edmondson's Psychological Safety Framework

Harvard Business School Professor Amy Edmondson pioneered the concept of Psychological Safety, defining it as:

"A shared belief held by members of a team that the team is safe for interpersonal risk-taking—that one will not be punished, humiliated, or ostracized for speaking up with ideas, questions, concerns, or mistakes."

Psychological safety is the single greatest predictor of project team effectiveness, innovation, and risk identification. In an environment lacking psychological safety, team members hide errors, conceal emergent risks, and withhold creative ideas out of fear. Edmondson outlines four developmental stages of psychological safety:

1. Inclusion Safety: Team members feel welcomed, respected, and valued for their unique identity.
2. Learner Safety: Team members feel safe to ask clarifying questions, experiment, and admit what they do not know without appearing incompetent.
3. Contributor Safety: Team members feel empowered to contribute meaningful ideas and utilize their skills to make a difference.
4. Challenger Safety: Team members feel safe to challenge the status quo, voice dissenting opinions, and disagree with senior leaders when they observe impending risks.

+---------------------------------------------------------------------------------+
|                  Leader Behaviors that Build Psychological Safety               |
+---------------------------------------------------------------------------------+
| 1. Frame Work as a Learning Challenge | Acknowledge that the project involves   |
|                                       | technical uncertainty and complexity.   |
| 2. Model Vulnerability & Humility     | Say openly: "I don't know the answer;   |
|                                       | I need your technical expertise."       |
| 3. Destigmatize Mistakes              | Treat failed experiments as valuable    |
|                                       | learning data, not disciplinary events. |
| 4. Ask Powerful Open Questions        | Inquire: "What risks am I missing?" and |
|                                       | "What is our biggest blind spot here?"  |
| 5. Respond Appreciatively to Bad News | Thank team members who surface schedule |
|                                       | slips early: "Thank you for flagging." |
+---------------------------------------------------------------------------------+

Ethical Standards and the IPMA Code of Ethics

Project culture must be anchored in unshakeable ethical integrity. The IPMA Code of Ethics and Professional Conduct establishes five fundamental pillars that every certified professional must embody:

• Honesty and Transparency: Providing truthful, accurate, and complete reports on project progress, risks, and financial expenditures.
• Fairness and Equity: Treating all team members, contractors, and stakeholders with impartiality, prohibiting discrimination and bias.
• Mutual Respect: Valuing cultural diversity, personal dignity, and human rights across all interactions.
• Professional Responsibility: Accepting personal accountability for decisions, honoring commitments, and continuously advancing project management competence.
• Sustainability and Social Good: Minimizing environmental harm and maximizing positive societal contributions.

---

Aligning Projects with Societal Values, Sustainability, and CSR

Traditional project management focused narrowly on the Iron Triangle of project outputs: did the project finish on time, within budget, and according to functional scope? Under ICB4 competence 4.3.5, modern project governance expands beyond outputs to consider strategic outcomes, societal impact, and long-term sustainability.

Moving from Output to Sustainable Value

• Project Output: The physical bridge, software application, or restructured business process.
• Project Outcome: Increased traffic capacity, faster customer transactions, or reduced operational expenses.
• Societal Value: Reduced carbon emissions through traffic optimization, enhanced digital accessibility for underserved populations, and safe working conditions.

Corporate Social Responsibility (CSR) and ESG Criteria

Project managers must actively incorporate Environmental, Social, and Governance (ESG) criteria into project life cycle planning, procurement, and risk analysis:

• Environmental Criteria: Evaluating carbon footprint, minimizing toxic waste, selecting energy-efficient infrastructure, and adhering to circular economy principles (recyclability and sustainable decommission).
• Social Criteria: Enforcing fair labor standards, human rights safeguards, and non-exploitative working hours across the supply chain; ensuring local community engagement and public health protection.
• Governance Criteria: Preventing bribery, ensuring transparent competitive bidding in procurement, upholding intellectual property rights, and auditing financial integrity.

Aligning with the United Nations Sustainable Development Goals (SDGs)

Adopted by all United Nations Member States in 2015, the 17 Sustainable Development Goals (SDGs) represent a global blueprint for peace, prosperity, and ecological health. High-maturity project management organizations explicitly link project charters and business cases to relevant SDGs:

• Goal 9 (Industry, Innovation, and Infrastructure): Building resilient, future-proof digital and physical assets.
• Goal 12 (Responsible Consumption and Production): Utilizing sustainable materials, reducing construction scrap, and lifecycle product design.
• Goal 13 (Climate Action): Mandating energy-efficient technologies and climate risk resilience in capital projects.

By harmonizing internal project culture with broad societal values and ecological stewardship, project managers ensure that their projects deliver lasting, ethical, and sustainable value to the organization and the global community.