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.
Take it into your next conversation
Three useful questions.
- What observable evidence supports this interpretation?
- Whose experience differs from the dominant story?
- What small change could we test, and how would we know it helped?
Related terms
Go to the evidence
Sources & attribution
[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 →
Published 2026-09-20 · Reviewed 2026-09-20. Editorial approach