Charles handy’s theory of organisational culture

Charles Handy’s theory of organisational culture describes four broad patterns in how organisations work: power, role, task and person culture. Each offers a different way of understanding where authority sits, how decisions happen and what holds people together.

The model is useful for discussing workplace behaviour, but it is not a diagnostic test. Most organisations combine several patterns, and identifying a culture type does not establish whether an organisation is effective, fair or a good place to work.

One important clarification: Handy’s fourth type is usually called person culture, not “people culture”. It describes an organisation that exists primarily to serve its individual members, rather than simply one that cares about employee wellbeing.

What does handy’s model explain?

Organisational culture concerns the shared assumptions, expectations and everyday practices that shape how work gets done. You notice it in whose opinion carries weight, what happens when someone challenges a decision and which behaviours receive recognition.

Handy’s framework helps people explore these patterns through four contrasting types. The ACCA overview of organisational culture explains the model in a management context.

The central questions are straightforward:

• Does influence come mainly from a powerful individual or central group?
• Do formal roles and procedures determine what happens?
• Does expertise carry authority when solving a particular problem?
• Does the organisation primarily support the independent work of its members?

These questions are more useful than asking everyone to choose a single label for their employer.

The four organisational culture types

Power culture: influence sits at the centre

In a power culture, authority is concentrated around a central person or small group. Handy’s familiar image is a web: influence extends outwards from the centre through relationships and personal trust.

Decisions may depend more on access to influential people than on formal procedures. A founder-led business can show this pattern when the owner personally approves recruitment, spending and changes to services.

Potential strengths: decisions can be quick, priorities can be clear and the organisation can respond rapidly when the central leader has the necessary information.

Potential difficulties: work can stall when that person is unavailable. Staff may hesitate to challenge decisions, while opportunities can appear to depend on personal relationships rather than transparent criteria.

Power culture is not simply another name for hierarchy. A highly hierarchical organisation may instead rely on formal roles and rules, making role culture a better description of particular decisions.

Role culture: authority comes from the position

In a role culture, responsibilities, procedures and reporting lines organise the work. Authority belongs primarily to the role someone holds, rather than to their personality or informal influence.

The traditional image is a Greek temple, with its pillars representing functions or departments. People are expected to understand their responsibilities and follow agreed processes.

Potential strengths: clear responsibilities can support consistency, accountability and dependable service. This is particularly valuable where errors could affect safety, public money or legal compliance.

Potential difficulties: decisions can become slow when several approvals are required. Teams may protect departmental boundaries or treat an unfamiliar problem as someone else’s responsibility.

Role culture is not inherently inefficient. The practical question is whether procedures protect something important or merely add unnecessary work.

Task culture: expertise supports a shared objective

In a task culture, people come together to solve a problem or deliver an outcome. Influence depends substantially on relevant knowledge and contribution, rather than solely on seniority.

Often pictured as a net, this pattern can appear in project teams bringing together specialists from different functions.

Potential strengths: people can combine expertise, adapt their approach and work across departmental boundaries. Someone relatively junior may lead an aspect of the work because they understand it best.

Potential difficulties: competing projects can stretch the same specialists. Accountability may become unclear, and teams can pursue their own targets without considering the wider organisation.

Task culture does not mean having no structure. Effective project work still needs decision rights, resources and a clear definition of success.

Person culture: the organisation serves its members

In a person culture, individuals are central and the organisation exists primarily to support their professional activity. A shared arrangement among independent practitioners may resemble this pattern more closely than a conventional employer.

For example, professionals might share premises and administrative support while retaining substantial control over their own clients and work. Not every professional partnership operates this way, so the actual arrangements matter.

Potential strengths: members can retain professional independence and considerable discretion over their practice.

Potential difficulties: collective decisions can be difficult when individual preferences conflict. Members may resist central direction or disagree about shared investment and responsibilities.

A supportive employer is not automatically a person culture. Wellbeing, inclusion and professional development can be priorities in any of the four types.

Why organisations usually have mixed cultures

An organisation can display all four patterns in different places. Its finance function may rely on role-based controls, a service improvement project may work through task-based collaboration, and strategic decisions may remain concentrated in a small leadership group.

Patterns can also shift with circumstances. During an urgent incident, authority may temporarily become more centralised. Once the immediate risk has passed, decisions may return to established roles or collaborative teams.

This mixture is not necessarily a problem. Different activities need different safeguards and degrees of discretion. Trouble often arises at the boundaries: a project team expects to make quick decisions, while the function responsible for approving its spending expects a documented business case.

Rather than saying “we are a task culture”, ask: “For this activity, who actually decides, on what basis, and with what consequences?”

It also matters whose experience you hear. Senior leaders may experience considerable freedom while frontline staff experience close control within the same organisation.

Worked example: an FE college introducing a new course

This is an illustrative scenario, not a report about a named college.

An FE college wants to introduce a new adult course developed with local employers. Curriculum staff, employer engagement colleagues, learning support and finance need to agree the delivery plan.

The difficulty: the project group believes it has permission to develop the course, but decisions repeatedly return to separate departmental approval routes. Nobody is certain who can approve a timetable change or additional support costs.

Using Handy’s model: the development work resembles task culture because it depends on combining expertise. Funding checks, safeguarding responsibilities and quality assurance require clear role-based accountability. The issue is not that either pattern is wrong, but that the boundary between them is unclear.

A practical response: the college gives the project a named sponsor and records:

• Which decisions the team can make within its agreed resources.
• Which decisions need finance, quality or safeguarding approval.
• Who resolves conflicts between departmental priorities.
• When approvals must happen before recruitment begins.

The team can then design the course collaboratively without assuming that collaboration overrides formal responsibilities.

What to review: track time spent awaiting decisions, late timetable changes and whether learners’ support requirements are addressed before delivery. Ask staff whether they understand their responsibilities. The HSE Management Standards on role provide a useful reference for role clarity and conflicting expectations.

These observations would show whether the revised arrangements help. Calling the college a “task culture” would not.

Worked example: a growing training provider

This is also an illustrative scenario.

A small training provider has grown beyond the point where its founder can personally oversee every operational decision. Managers still seek the founder’s approval for routine purchases, trainer cover and adjustments to delivery plans.

The difficulty: decisions wait when the founder is teaching or meeting clients. Managers are accountable for delivery but are unsure how much discretion they really have.

Using Handy’s model: the approval pattern resembles power culture. Personal oversight may have helped when the organisation was smaller, but it now creates a bottleneck. This is a working explanation to investigate, not proof that the founder’s leadership is ineffective.

A practical response: the provider reviews recent delayed decisions and separates them into categories. Routine decisions move to named managers within agreed spending and quality boundaries. Higher-risk decisions retain senior approval. A short decision record makes the new responsibilities visible.

The founder also changes their own behaviour. When someone seeks unnecessary approval, they refer back to the agreed delegation rather than quietly taking the decision back.

Managers receive coaching in the responsibilities they are taking on. Delegation without the necessary skills, information or time would simply transfer the pressure.

What to review: compare approval delays, delivery problems and managers’ confidence before and after the change. Check whether staff can raise concerns without going through personal connections. The aim is dependable delegation, not replacing every informal relationship with bureaucracy.

How to apply the model in your workplace

Use Handy’s framework to structure a conversation about a specific problem, rather than to label the whole organisation.

Start with observable behaviour

Choose an issue such as slow approvals, inconsistent induction or repeated project disagreements. Gather recent examples of what happened, who made decisions and where work stopped.

Avoid vague statements such as “our culture resists change”. Ask what people did and what conditions shaped their response.

Listen across roles and teams

Include managers, frontline staff and people affected by the process. Compare formal policies with everyday practice: the person named as responsible may not be the person everyone actually consults.

Treat differences in experience as information, not as evidence that one group misunderstands the organisation.

Identify a pattern, then test another explanation

Discuss which aspects resemble power, role, task or person culture. Allow more than one answer.

Then consider alternatives. Is the approval delay really about centralised authority, or is the approving manager covering two vacancies? Is limited collaboration a cultural issue, or do staff lack shared planning time?

Make a small change and review it

Choose a practical adjustment: clarify a decision, remove a duplicate approval or create protected time for cross-team work. Agree what improvement would look like and check for unintended effects.

The CIPD factsheet on organisational culture and climate offers wider context for understanding workplace culture beyond a four-type framework.

Limitations and common misunderstandings

The four types are not diagnostic facts. An observation may be consistent with a type without proving that the organisation belongs to it. Do not present an informal workshop score as a validated cultural assessment.

There is no universally best type. Task-based collaboration can help a development project, but it does not remove the need for clear financial or safeguarding accountability.

The model does not explain everything. Workload, incentives, resources, discrimination and employment conditions need examination in their own right. A culture label cannot substitute for investigating a specific concern.

Culture is not the same as structure. An organisational chart shows formal reporting lines, not necessarily who has influence in practice.

A label cannot predict engagement or performance. Whether people thrive depends on their actual working conditions and experiences. The model alone cannot establish that a particular culture caused an outcome.

Summary and next step

Handy’s four cultures offer a useful vocabulary for discussing authority, coordination and professional independence. Their value lies in the questions they prompt, not in sorting employers into fixed boxes.

Start with one recurring workplace difficulty. Map how decisions currently happen, listen to the people involved and test one practical improvement. Keep the cultural label provisional and judge progress through observable changes.

Sources and further reading

• ACCA: Organisational culture, a professional explanation of culture frameworks, including Handy’s four types.
• CIPD: Organisational culture and climate, wider guidance on understanding and developing workplace culture.
• Health and Safety Executive: Management Standards, role, practical guidance on clear responsibilities and avoiding conflicting roles. This supports the application discussion, rather than validating Handy’s typology.