Organizational Culture
Organizational Culture
What is organizational culture?
- Shared values, beliefs, and ways of behaving
- The unspoken rules of 'how we do things here'
- A force stronger than strategy
What organizational culture really changes is the judgment calls people make when the boss isn't around. In a situation the manual doesn't cover, when an employee decides within seconds whether to 'escalate this or just handle it and move on,' culture is what guides that decision. That is why culture is the reason the same system produces different results at different companies. Roll out an identical performance management system, and at one company feedback conversations increase, while at another it turns into a rating-sorting exercise. Culture explains the difference.
Culture and organizational climate are different things. Climate is the current mood, and it can swing within a quarter after a leadership change or a bonus payout. Culture is the accumulated result of who you hire, who you promote, and who you let go, so it takes at least two to three years to move. One more thing: company-wide average scores are almost useless. The sales division and the development division are effectively different companies, and a diagnosis only becomes meaningful when you break it down by division and job level. If the executive average and the entry-level average differ by more than 20 points on the same question, that gap itself is the most important finding.
When you decide to change culture, there are only a few points you can actually touch. Who benefits in promotions and evaluations, how bad news is handled in meetings, and what a new hire sees and learns in the first month: these three places are practically all there is. Slogans never reach them. By contrast, a single list of promotions sends a stronger signal than 100 slogans. The moment members confirm 'this is the kind of person who does well here,' every other message gets reinterpreted to fit that conclusion.
The most common mistake in practice is substituting perks and events for culture. You can switch everyone to first names and hold a town hall every quarter, but if approvals still run through five levels and the team lead who objected in a meeting gets passed over in the next promotion round, employees learn that words and actions don’t match. What is left is not improvement but cynicism. In particular, if a culture initiative is handed to an HR task force alone and executives only lend their names as sponsors, six months later all that remains is one report and the reaction 'Here we go again.' Culture is proven by what leaders let slide, not by a mission statement.
Anna ChoExpert in organizational culture, coaching, emotion management, and CS consulting
John KimInstructor John Kim, CEO of Nanum Consulting and author of B2B Marketing DesignThe best-known framework comes from organizational psychologist Edgar Schein, who described culture in three levels: artifacts (surface), espoused values, and underlying assumptions (deep). It has since become a core concept in organization development.
Consider a hypothetical case. Company A makes industrial components, with 420 employees and annual revenue of KRW 120 billion (≈ US$89,780,000). Over the past year it received 17 client complaints, and 12 of them involved defects the shop floor already knew about. Despite a quality manual of more than 300 pages, problems never made it upward, so the CEO ordered a six-month organizational culture diagnosis.
- When the head of organizational development interviewed 28 people across three divisions (production, quality, and sales), 9 of them gave almost the same answer: 'Because when I report a problem, the first thing they ask is why we didn’t stop it sooner.'
- At a management meeting, the CEO asked, 'Of the employees who reported a problem first over the past three years, how many were promoted?' Two days later, HR came back with the answer: zero.
- The head of production turned the first 15 minutes of the weekly meeting into a 'what almost slipped past us this week' share, and went first with a case where they had delayed a line-stop decision by two days.
- The quality director created a no-blame policy for anyone who reports a problem within 72 hours and added an 'early reporting' item worth 10% of the team leader evaluation score.
- Six months later, voluntary problem reports rose from 4 to 23 a month, client complaints fell from 17 to 6, and quarterly rework costs dropped from KRW 88 million (≈ US$65,800) to KRW 31 million (≈ US$23,200).