← Workplace culture

Culture · diagnosis & change

Handy’s four organisational cultures

Understand where authority comes from: personal influence, defined roles, specialist expertise or professional autonomy.

Charles Handy · 1978 · Gods of Management · Original editorial explanation
Handy’s four organisational cultures — simplified model sketchPower · central influence · Role · defined authority · Task · relevant expertise · Person · professional autonomy. Editorial interpretation, after Charles Handy (1978 · Gods of Management).Power · centralinfluenceRole · definedauthorityTask · relevantexpertisePerson · professionalautonomyADM HR · ORIGINAL INTERPRETATIONCharles Handy · 1978 · Gods of Management
Original simplified sketch after Charles Handy (1978 · Gods of Management). Read the explanation for assumptions and limitations. Download SVG ↗

The core idea

Handy’s four types describe different organising logics. Power culture concentrates influence around a central person or group. Role culture relies on defined responsibilities and formal authority. Task culture assembles expertise to solve problems. Person culture places the participating individuals at the centre, with the organisation serving their work. His Gods of Management associates these with Zeus, Apollo, Athena and Dionysus. An employer may combine several logics across activities; these are interpretive categories, not personality diagnoses or stages through which every business must pass.

Source and attribution [1]

Using it in practice

Follow an actual decision from request to resolution. Identify who can authorise it formally, who can block it informally, whose knowledge matters and who bears the consequences. Compare this with the organisation chart. Choose a specific bottleneck before proposing a new structure. A useful HR intervention might clarify delegated authority, create a project role with real decision rights or agree shared obligations among independent specialists. Make the trade-offs explicit rather than announcing a universally superior culture.

An example, not a reported case

Worked example · illustrative

A hypothetical security contractor has formal operating procedures and detailed post instructions, yet every staffing exception needs the founder’s personal approval. That is evidence worth exploring through role and power lenses. It is not evidence that all security companies work this way. HR maps recent requests, identifies routine decisions that can safely be delegated and agrees an escalation boundary. A pilot checks response time, consistency, staff understanding and whether informal vetoes still override the published process.

What to watch for

A strong leader is not automatically evidence of a power culture, and detailed rules do not prove that they govern practice. Person culture is not a polite label for selfishness. Professional autonomy can coexist with duties to colleagues and clients. Avoid using these categories to dismiss employees as the wrong cultural fit; assess relevant conduct and job requirements instead.

Power: inspect dependence

Ask what happens when the central decision-maker is absent. A short route to authority can make coordination quick, but a growing business may accumulate queues and uncertainty. Write down which decisions need central judgement and which can be delegated. Check whether staff trust the delegation or continue seeking informal permission. Succession and continuity deserve attention as well as speed.

Role: make responsibilities usable

Test a routine handover between functions. Does each person know what they own, what evidence they need and when to escalate? Rules can support fairness and reliability, but gaps between roles can leave a customer or colleague stranded. Agree a named owner for exceptions. Review the process with the people who use it before adding another approval step.

Task: give expertise a route to action

A project team needs more than a collaborative label. Agree the problem, success measures, resource commitments and who resolves disagreement. Make expertise visible without allowing the loudest specialist to dominate every decision. Decide how project learning returns to normal operations. Otherwise a successful temporary team may leave no lasting improvement once its members move on.

Person: negotiate shared obligations

In a professional partnership or specialist collective, discuss which choices remain individual and which require common standards. Our suggested exercise asks members to list what they need from the organisation and what they owe to others in return. Clarify quality, information sharing and conflict resolution. Autonomy is more sustainable when the boundaries of mutual responsibility are understood.

A mixed-culture diagnosis

Map each important activity separately: frontline delivery, senior approvals, project development and professional practice. Record evidence for more than one lens when appropriate. Revisit the map after a change in scale or leadership. The useful outcome is a clearer arrangement for real decisions, not a colourful label applied to the whole workforce.

Map where authority really comes from

For a recent decision, identify whether influence came from a central person, formal role, relevant expertise or the autonomy of professionals. Compare the formal organisation chart with actual practice. A company may rely on role-based procedures for operations while senior decisions depend heavily on a founder. That combination is a possibility to investigate, not an automatic description of every security company or small business. Ask what happens when the usual authority is unavailable.

Diagnose the tension between two cultures

Imagine a project team organised around expertise needing approval from a rigid functional hierarchy. The issue may be unclear decision rights rather than poor collaboration. Identify which decisions require formal control and which can sit with the project. Conversely, a strongly personal professional culture may struggle with shared service commitments. Describe the specific conflict and negotiate an operating arrangement instead of asking everyone to become one preferred type.

Design a boundary that makes the mixture work

An illustrative solution might preserve mandatory operational checks while delegating a defined improvement budget to a task team. State the scope, escalation triggers and evidence required. Ensure the central leader does not informally override the agreement without explanation. If exceptions are common, review the design. A hybrid culture works through clear relationships and credible behaviour, not through a declaration that the organisation is both entrepreneurial and controlled.

Use the model without ranking people

Power, role, task and person describe patterns of organising; they are not employee personalities or moral grades. Ask what each pattern enables and what it makes difficult in this context. A role culture can provide consistency and clarity, while excessive rigidity can obstruct response. A power culture can act quickly, while dependence on one person can create fragility. Use those trade-offs to guide a change, and verify whether the proposed arrangement improves real decisions.

Find where authority actually operates

Take a recent decision and trace who could approve it, who supplied expertise and whose objection changed the outcome. Compare that route with the formal policy. A role-based operation can still rely on one owner’s personal approval, while a project team may use task authority within strict regulatory boundaries. Record which organising logic serves the work and where it creates delay or uncertainty. The purpose is not to rank cultures from old-fashioned to modern, but to understand their practical consequences.

Work through a tension between cultures

Imagine an expert project team that promises a client a rapid service change, but operations require a controlled implementation process. Calling one side bureaucratic and the other reckless will not resolve the tension. Agree which standards are non-negotiable, which decisions belong to the project and where specialist review is necessary. Then test a real handover. If every exception still needs the founder, the issue may be concentrated power rather than the written procedure. Review decision clarity and rework after the change.

Take it into your next conversation

Three useful questions.

  1. What observable evidence supports this interpretation?
  2. Whose experience differs from the dominant story?
  3. What small change could we test, and how would we know it helped?

Related terms

Go to the evidence

Sources & attribution

Further reading: Hani Nabeel (2025), Culture Analytics: An evidence-based approach to company culture, First edition, Chapters 3 and 13; PDF pp. 38–39, 190–191 and 214. Edition & reading notes ↗

[1] Charles Handy, Gods of Management: publisher overview ↗

The core idea is an original summary of the cited work. Application notes, examples and sketches are our interpretations, not quotations or reproductions of the authors’ figures. Publisher records may require access to read the full original work.

Compare all eight culture models → · Read the practical playbook →

Application guidance expanded on 26 September 2026. These practical suggestions and invented examples are editorial explanations; further-reading sources are not the original authors of the historical models unless expressly identified. Original overview review dates are retained.

Published 2026-09-20 · Reviewed 2026-09-22. Editorial approach

Keep exploring

A little more context.

Culture · diagnosis & change01

Schein’s three levels of culture

Move from visible routines to the beliefs beneath them, and investigate why stated values and daily decisions can diverge.

Edgar H. Schein7 min
Culture · diagnosis & change02

Deal and Kennedy’s culture model

Explore how the stakes of decisions and the speed of learning about their outcomes shape working habits.

Terrence E. Deal7 min