Organisational Culture logo

Organisational Culture

Community
fatihguner
organisational-culture

Audits organizational culture using Schein's three-level model: visible artifacts, espoused values, and basic underlying assumptions. Diagnoses gaps between stated values and actual behaviour to reveal the invisible beliefs driving organizational dynamics. Use when experiencing culture dilution during rapid hiring, planning M&A cultural integration, diagnosing why culture change initiatives fail, or auditing founder imprint on company norms.

Overview

Publisherfatihguner
Repositoryforeman
Skill nameorganisational-culture
Stars
63
Forks
10
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by fatihguner on GitHub. Read the source before you install it.

Installation

Install the Organisational Culture AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/fatihguner/foreman/tree/main/plugins/foreman/skills/organisational-culture
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/fatihguner/foreman.git /tmp/foreman
mkdir -p .claude/skills
cp -r /tmp/foreman/plugins/foreman/skills/organisational-culture .claude/skills/organisational-culture
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Organisational Culture in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Organisational Culture on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Organisational Culture is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.

Organisational Culture

What you see in an organisation -- the open-plan offices, the Friday beers, the branded hoodies -- is the tip of the iceberg. Roughly ten percent of culture is visible. The remaining ninety percent sits submerged: the unspoken beliefs, the unstated power hierarchies, the assumptions so deeply embedded that no one thinks to question them. Edgar Schein, the MIT professor who spent decades dissecting how organisations actually work, argued that most culture-change initiatives fail because they redecorate the tip while ignoring the mass below the waterline. The iceberg metaphor is not merely illustrative; it is diagnostic. Misread which level of culture you are dealing with, and your intervention will achieve nothing -- or worse, provoke the immune response that organisations mount against superficial change.

Schein's framework identifies three distinct layers, each progressively harder to observe and exponentially harder to alter. Understanding these layers is not an academic exercise. For founders, it is the difference between building a company that scales with coherence and one that fractures under the weight of its own contradictions.


The Framework

Layer 1: Artifacts (The Visible Surface)

Artifacts are everything you can see, hear, and touch when you walk into an organisation. Office layout. Dress code. Meeting rituals. The language people use in Slack channels. The way decisions get announced. These are tangible, immediately observable -- and profoundly misleading if interpreted without context.

A startup with a foosball table and no dress code might appear egalitarian. The reality could be a cult of personality where the CEO's whims override all process. Artifacts are symptoms, not diagnoses.

Common artifacts include:

  • Physical environment and workspace design
  • Published values and mission statements
  • Rituals, ceremonies, and recurring events
  • Stories and legends told about the company's origins
  • Organisational charts and reporting structures
  • Technology choices and communication tools

Layer 2: Espoused Values (What People Say Matters)

One level below artifacts sit the declared beliefs, strategies, and philosophies. These are the values on the website, the principles recited during onboarding, the strategic priorities invoked in board meetings. Espoused values represent what the organisation claims to be.

The critical question: do espoused values match actual behaviour? When a company proclaims "we value work-life balance" while promoting only those who answer email at midnight, a gap has opened between Layer 2 and Layer 3. This gap is where cynicism breeds and trust erodes.

Diagnostic indicators of alignment (or misalignment):

Espoused ValueAligned BehaviourMisaligned Behaviour
"Innovation"Budget for experiments, tolerance of failurePunishing failed projects, rigid approval processes
"Transparency"Open financials, candid all-handsInformation hoarding, surprise layoffs
"Customer first"Support team empowered to actSupport metrics optimised for speed over resolution
"Meritocracy"Promotions track resultsPromotions track tenure or political skill

Layer 3: Basic Underlying Assumptions (The Invisible Bedrock)

The deepest layer consists of unconscious, taken-for-granted beliefs. These assumptions are so ingrained they feel like objective reality rather than cultural choices. They govern how people perceive problems, define truth, relate to time, and think about human nature.

Schein identified several dimensions of basic assumptions:

  • Relationship to environment: Does the organisation believe it controls its market, or must adapt to it?
  • Nature of truth: Is truth discovered through debate, authority, or data?
  • Human nature: Are people fundamentally trustworthy (Theory Y) or requiring supervision (Theory X)?
  • Nature of relationships: Is hierarchy natural, or should all voices carry equal weight?
  • Time orientation: Does the culture privilege the past (tradition), present (agility), or future (vision)?

These assumptions are rarely articulated. They surface only when violated -- when a new hire from a different culture does something that provokes an emotional reaction disproportionate to the action itself. That disproportionate reaction is the clearest signal that a basic assumption has been touched.

How the Layers Interact

Change flows downward with great difficulty. A founder can redesign the office (Layer 1) overnight. Rewriting the values statement (Layer 2) takes a quarterly offsite. Shifting basic assumptions (Layer 3) requires years of consistent leadership behaviour, critical incidents handled visibly, and patient reinforcement.

Conversely, diagnosis flows upward. To understand Layer 3, observe the patterns in Layer 1 and the contradictions between Layer 1 and Layer 2. The gap between artifacts and espoused values is the most reliable indicator of what the organisation actually believes.


Prompts

Prompt 1 -- Culture Audit:

Conduct a three-level culture audit for my company using Schein's framework. At the Artifacts level, I will describe our office setup, communication norms, meeting practices, and visible rituals. At the Espoused Values level, analyse our stated mission, values, and strategic principles. Then help me identify the Basic Underlying Assumptions by probing for gaps between what we say and what we do. Company context: [describe company stage, size, industry, and any recent cultural tensions].

Prompt 2 -- Misalignment Diagnosis:

I suspect a gap between our espoused values and our actual organisational behaviour. Our stated values include [list values]. Recent incidents suggesting misalignment include [describe incidents]. Using Schein's model, help me diagnose which basic underlying assumptions are driving the contradictory behaviour, and propose interventions at each of the three levels.

Prompt 3 -- Culture Integration for M&A:

We are acquiring [describe target company]. Using Schein's three levels of organisational culture, help me map the cultural differences between our two organisations. For each level (artifacts, espoused values, basic assumptions), identify potential collision points and recommend an integration strategy that addresses each layer explicitly.

Prompt 4 -- Founder Culture Imprint:

As a founder at [stage], I recognise that my personal behaviours are imprinting onto the company culture. Using Schein's framework, help me audit which of my assumptions, habits, and decisions are becoming embedded as basic underlying assumptions. Identify which imprints are serving the company well and which may become liabilities at scale.


Use Cases

Series A SaaS Company Experiencing Growing Pains A 45-person B2B SaaS startup has doubled headcount in eight months. The founders notice that new hires "don't get the culture" -- they schedule unnecessary meetings, escalate decisions that should be made autonomously, and default to formal communication. A Schein analysis reveals that the company's basic assumption -- that competent adults make decisions without permission -- was never articulated; it was transmitted osmotically when the team was fifteen people. The fix operates at all three layers: codify the assumption into explicit values (Layer 2), redesign onboarding rituals to demonstrate autonomous decision-making (Layer 1), and have leadership visibly reinforce the assumption by publicly celebrating independent judgment (Layer 3 maintenance).

Growth-Stage Fintech After a Compliance Crisis A payments company with 200 employees suffers a regulatory penalty. Leadership declares a "compliance-first culture" and introduces new processes, reporting lines, and training (Layer 1 and Layer 2 changes). Six months later, the same risk-taking behaviours persist. Schein's framework reveals that the basic assumption -- "move fast, regulators are slow" -- was forged during the company's scrappy early days and reinforced by the promotion of individuals who embodied it. Surface-level changes cannot override Layer 3 assumptions. The intervention requires replacing key role models, restructuring incentives, and having the CEO publicly acknowledge past assumptions that no longer serve the company.

Pre-IPO Enterprise Company Merging Two Engineering Cultures Following an acquisition, two engineering teams with fundamentally different assumptions about quality (one ships fast and iterates; the other ships only when perfect) must integrate. Artifacts conflict immediately: different code review practices, different deployment cadences, different definitions of "done." Mapping each team's three layers reveals that the conflict is not about process -- it is about basic assumptions regarding the nature of professional excellence. Resolution requires surfacing both assumptions explicitly, negotiating a shared assumption appropriate to the combined entity, and rebuilding processes and rituals from that new foundation.


Anti-Patterns

  1. Redecorating the Iceberg Tip. Installing ping-pong tables, rewriting the mission statement, or launching a "culture committee" without addressing underlying assumptions. These initiatives generate cynicism when employees observe that actual behaviour remains unchanged. Artifacts-only interventions are the most common and most futile form of culture work.

  2. Assuming Culture Is What the Founder Says It Is. Founders often conflate their intended culture with the actual culture. Schein's framework demands empirical observation, not aspiration. The culture is what people do when no one is watching, not what the deck says.

  3. Treating Culture as Monolithic. Large organisations contain subcultures -- engineering, sales, operations -- each with distinct assumptions. Applying a single cultural analysis to the entire company produces a fiction. Map subcultures independently, then identify where they align and where they collide.

  4. Skipping Layer 3 in Due Diligence. M&A due diligence routinely examines financials, technology, and talent. It almost never examines basic assumptions. The result: post-merger integration failures that no amount of process harmonisation can fix, because the two organisations hold incompatible beliefs about how work should be done.

  5. Expecting Speed. Layer 3 assumptions take years to form and years to change. Leaders who announce a "culture transformation" with a six-month timeline are confusing artifacts with assumptions. Genuine culture change is measured in leadership generations, not quarters.


By Stage

StageFocusKey Difference
Early TractionFounder imprint auditCulture is being formed now, largely from the founder's unconscious assumptions. This is the highest-leverage moment to be intentional.
GrowthArticulation and codificationAs headcount exceeds Dunbar-adjacent numbers (~50-150), osmotic culture transmission fails. Assumptions must become explicit values, and values must become visible artifacts.
ScaleSubculture managementMultiple teams, geographies, and functions develop distinct subcultures. The task shifts from building culture to managing cultural coherence across diverse groups.

At early traction, the primary risk is accidental culture -- the founder's unexamined habits becoming organisational doctrine. At growth, the risk is dilution -- rapid hiring overwhelming the cultural carriers. At scale, the risk is fragmentation -- subcultures diverging until the organisation loses coherence.


Output Template

markdown
# Organisational Culture Audit: [Company Name]

## Layer 1: Artifacts (Observable)
- **Physical environment:** [Describe workspace, layout, remote/hybrid setup]
- **Communication norms:** [Tools, formality, response time expectations]
- **Rituals and ceremonies:** [All-hands, retrospectives, celebrations]
- **Symbols and stories:** [Origin myths, hero narratives, cautionary tales]
- **Decision-making patterns:** [Who decides, how fast, with what process]

## Layer 2: Espoused Values
- **Official values:** [As stated on website/internal docs]
- **Strategic principles:** [As communicated by leadership]
- **Alignment assessment:** [Where behaviour matches values / where it diverges]

## Layer 3: Basic Underlying Assumptions (Inferred)
- **Relationship to environment:** [Control vs. adapt]
- **Nature of truth:** [Data vs. authority vs. debate]
- **Human nature assumption:** [Trust vs. verify]
- **Relationship orientation:** [Hierarchy vs. egalitarian]
- **Time orientation:** [Past / present / future]

## Gap Analysis
| Espoused Value | Observed Behaviour | Inferred Assumption | Gap Severity |
|----------------|-------------------|---------------------|--------------|
| [Value] | [What actually happens] | [What this reveals] | High/Med/Low |

## Recommended Interventions
### Layer 1 (Quick wins):
- [Artifact changes]
### Layer 2 (Medium-term):
- [Values clarification / realignment]
### Layer 3 (Long-term):
- [Assumption-level work required]

## Risk Assessment
[Key cultural risks if no action is taken]

Related Skills

  • Tuckman's Team Stages -- Team development dynamics operate within the cultural container Schein describes; understanding both reveals why some teams thrive and others stall.
  • Radical Candor -- A feedback culture is an artifact sustained by espoused values, which only works when basic assumptions support psychological safety.
  • Psychological Safety -- Edmondson's framework addresses the Layer 3 assumption about whether interpersonal risk-taking is safe; culture change initiatives fail when this assumption remains hostile.
  • Kotter's Change Model -- Kotter's eight steps provide the process methodology for altering culture; Schein's three layers explain why each step is necessary and where resistance originates.
  • Team Culture and Dynamics -- Translates Schein's organizational-level theory into team-level practice, helping leaders build and sustain culture within their immediate sphere of influence.
  • Leading Through Change -- Culture transformation is the deepest form of organizational change; this skill addresses the leadership behaviors required to shift Layer 3 assumptions over time.

Frequently asked questions

What does the Organisational Culture AI skill do?

Audits organizational culture using Schein's three-level model: visible artifacts, espoused values, and basic underlying assumptions. Diagnoses gaps between stated values and actual behaviour to reveal the invisible beliefs driving organizational dynamics. Use when experiencing culture dilution during rapid hiring, planning M&A cultural integration, diagnosing why culture change initiatives fail, or auditing founder imprint on company norms.

Why use Organisational Culture on TypingMind?

Because you install it once and use it with any model. Organisational Culture is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Organisational Culture in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/fatihguner/foreman/tree/main/plugins/foreman/skills/organisational-culture. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Organisational Culture?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Organisational Culture?

As many as you like. As long as a model supports skills, you can use Organisational Culture with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Organisational Culture AI skill free?

Yes. It is published on GitHub by fatihguner under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇