CIMA E1: Naming a Handy Culture Type Isn't the Answer

Ask a CIMA E1 candidate to read an organisational culture scenario and most will land on the right answer within seconds: "that's a role culture" or "this is clearly a power culture." The classification itself is rarely the problem. What costs the marks is what happens next — or rather, what doesn't happen next. The script stops at the label instead of using it to answer the question that was actually asked.

This is one of the most common and most avoidable mark losses in CIMA E1 scenario questions, and it is worth understanding exactly why it happens, because the fix is straightforward once you see the pattern.

Handy's four culture types, briefly

Charles Handy's typology is the standard lens CIMA scenarios use for organisational culture, and it splits organisations into four broad types.

• Power culture — control sits with a small central figure or group, often the founder. Decisions are fast because few people need to be consulted, but the organisation is highly dependent on that central figure and can struggle with succession.
• Role culture — authority follows job title and formal procedure, not personality. It suits stable, predictable environments but tends to be slow to respond when the environment changes quickly.
• Task culture — work is organised around projects and teams pulled together for their expertise. It is flexible and good at problem-solving, but can be expensive to run and harder to control.
• Person culture — individuals see the organisation as existing to support their own professional practice, common in partnerships of specialists such as barristers' chambers or some consultancies. Management structures are typically weak because no one accepts being managed easily.

Every E1 candidate learns this list. It is not the differentiator between a pass and a fail — the differentiator is what a candidate does with it.

The classification trap

A typical scenario describes an organisation, and the question asks something like: "discuss the implications of the organisation's culture for its ability to respond to the proposed change." A candidate reads the scenario, correctly spots a role culture — perhaps a long-established manufacturer with rigid departmental hierarchies and a thick procedures manual — and writes a paragraph confirming that this is, indeed, a role culture, citing the textbook features: bureaucracy, job descriptions, hierarchy, rules.

That paragraph, on its own, answers a question nobody asked. The verb in the requirement was "discuss," not "identify." Marking schemes for this type of question typically allocate identification a small number of marks and application the majority — so a candidate who stops at classification has done perhaps a quarter of the available work, however confidently and correctly it was done.

Why this keeps happening

Culture models are usually revised as classification exercises — spot the type from a description — because that is the easiest way to check the theory has been learned. Candidates then arrive at the exam having practised recognition far more than the second step: reasoning from the type to its consequences for the issue in the scenario. Under time pressure, the brain defaults to the skill rehearsed most, which is naming the type rather than analysing it.

Turning identification into application

The fix is a habit, not new knowledge. Once a culture type has been identified, force the answer to address the actual question by asking: "so what does this mean for the issue in front of me?" For a role culture facing a change proposal, that means explaining that formalised procedures and layered sign-off will slow implementation, and that the change will likely need more explicit structure and phased milestones rather than relying on informal buy-in. For a power culture, the useful application is rarely "decisions are fast" in isolation — it is what fast, centralised decision-making means for the specific risk in the scenario, such as succession planning or a lack of challenge to the founder's judgement.

A simple discipline for exam pressure: never let a sentence identifying a culture type stand alone. Follow it immediately with one starting "this means," "as a result," or "this creates a risk that," tied directly to the scenario's specific organisation and problem — not a generic textbook consequence lifted from a revision card.

Practising the right skill

Because this weakness is a habit rather than a knowledge gap, it needs to be practised as a habit. When working through past scenario questions, resist the urge to move on once the culture type is correctly named — write out two or three sentences of implication for that exact scenario before checking the model answer. Comparing your implications against the marking guidance, rather than your classification against it, is what closes this gap. The same "classify, then apply" trap shows up elsewhere in the qualification too — the E2 Mendelow stakeholder mapping mistake is built on exactly the same underlying error, just with a different model.

Frequently asked questions

Do I need to memorise Handy's culture types word for word?

You need to recognise the four types from a scenario description and know their typical features well enough to identify them quickly, but memorising definitions is only the starting point. Marks are concentrated in explaining what a given type means for the specific issue the question raises, not in reciting the definition itself.

What if a scenario seems to show a mix of culture types?

That is common and is not a problem to resolve by forcing a single label. State which features are present, note that organisations can display characteristics of more than one type, and then apply the implications of each relevant feature to the scenario's issue rather than picking one type and ignoring evidence for another.

Is this mistake specific to culture questions, or does it show up elsewhere in E1?

It shows up wherever E1 uses a model to describe an organisation — structure, stakeholder analysis, and the shape of the finance function are all vulnerable to the same "correct label, no consequence" pattern. The underlying fix is the same in every case: treat the model as a way into the analysis, not as the answer itself.

Naming a Handy culture type correctly shows you know the theory. Explaining what that culture type means for the actual problem in the scenario is what earns the marks attached to it. Build the "so what" step into every practice question you attempt, and it will become automatic well before exam day. For a structured route through this and the rest of the E1 syllabus, including further practice on applying organisational models to scenario questions, see Learnsignal's CIMA E1 Managing Finance in a Digital World course, and for a deeper look at the culture framework itself, Learnsignal's guide to Handy's model of organisational culture is a useful companion.