CIMA E1 Organisational Structure: The Matching Mistake That Loses Marks

Ask a CIMA E1 candidate to describe an organisational structure and most will happily reel off the advantages and disadvantages of functional, divisional and matrix structures from memory. That is not where the marks are. E1 questions on organisational design reward candidates who can read a case-study scenario, pick out what it actually signals about the organisation's size, product and market diversity, and need for coordination, and then match that evidence to the structure it points towards. Defaulting to whichever structure you find easiest to write about, regardless of what the scenario describes, is the single biggest reason candidates lose marks on this topic.

This post runs through the three core structure types, the scenario signals that point to each one, a worked mini-example applying the logic to a short case, and the exam-technique trap of listing generic pros and cons without linking them back to the organisation in front of you.

The three core structure types

Functional structure

A functional structure groups people by the specialist activity they perform: finance, marketing, operations, HR, and so on, each reporting up through its own departmental head. It suits organisations offering a single product or a narrow, closely related product range, because it allows deep specialisation and clear lines of technical authority. The trade-off is that it can create silos between departments, slow down decisions that need input from several functions, and make it harder to hold anyone accountable for the profitability of a specific product or market, since no one function owns the whole customer relationship.

Divisional structure

A divisional structure splits the organisation into self-contained units, typically by product, by market, or by geographic region, with each division holding its own functional resources (its own finance team, its own marketing team, and so on) and its own manager accountable for that division's performance. It suits larger organisations with genuinely diverse products or markets, because each division can be run and measured as close to a standalone business, and divisional managers can respond quickly to the conditions in their own market. The trade-off is duplication of resources across divisions, some loss of the economies of scale a single centralised function would offer, and the risk that divisions compete with each other rather than cooperate.

Matrix structure

A matrix structure overlays two reporting lines at once, most commonly function and project, or function and product, or function and geography. Staff report both to a functional manager and to a project or product manager. It suits organisations that need to pull specialists from different functions together for a defined piece of work, such as project-based consulting or new product development, because it gives flexibility and strong cross-functional coordination without permanently reorganising the whole business. The trade-off is dual authority: staff can receive conflicting instructions from their two managers, accountability can become blurred, and the structure demands more time spent on communication and conflict resolution than either a functional or divisional structure would.

Matching scenario signals to the right structure

E1 case studies rarely say outright which structure an organisation uses or should use. Instead they describe facts about the organisation, and the exam technique is to read those facts as signals.

Worked mini-example

Consider a short case: a technology group operates three distinct product lines — cloud software, hardware devices, and IT consulting — sold into twelve different countries with very different customers, competitors and profit drivers in each line. Senior management have said they want each product line's manager to be accountable for that line's own profitability, and they are frustrated that decisions about hardware pricing currently get delayed while they wait for sign-off from a central product committee that also handles software and consulting.

The signals here are clear: multiple distinct product lines, each with different market dynamics, and an explicit management wish for accountability at the level of each line, plus evidence that a centralised structure is currently slowing decisions down. That combination points to a divisional structure organised by product line, not a functional structure. A candidate who instead wrote a generic answer about the benefits of functional specialisation would be answering a question the scenario did not ask.

Now add one more detail to the same case: within the consulting product line, staff from IT, finance and HR need to be pulled together temporarily for each individual client engagement, then reassigned to the next one once it ends. That detail, specifically about the consulting division, signals a matrix arrangement within that division, even though the group as a whole is best described as divisional. Good E1 answers pick up on this kind of nuance rather than forcing the whole organisation into one label.

The exam-technique trap: generic advantages and disadvantages

The most common way candidates lose marks on this topic is writing a technically correct list of advantages and disadvantages of, say, a matrix structure, without ever tying any of them back to the organisation described in the scenario. A statement like matrix structures can cause confusion over who has authority earns very little on its own. The same point applied to the case earns considerably more: because consulting staff would report both to their functional head and to a client engagement manager, there is a risk that competing instructions from each create exactly the kind of delay senior management are already trying to eliminate in the hardware division.

Before you write a single advantage or disadvantage, name the specific feature of the organisation you are applying it to. If you cannot point to a sentence in the scenario that your point relates to, it is bookwork rather than application, and E1 marking guides consistently reward application over bookwork on organisational design questions.

Exam technique checklist

• Read the scenario for size, product/market diversity, and coordination needs before deciding which structure to discuss.
• Match, don't default: do not reach for the structure you find easiest to write about if the evidence points elsewhere.
• Remember a real organisation can be a hybrid — broadly divisional with a matrix arrangement inside one division, for example — and identifying that nuance is worth marks.
• Every advantage or disadvantage you state should be anchored to a specific fact from the case, not written as a standalone bookwork statement.
• Where the scenario describes a problem (slow decisions, duplicated costs, conflicting instructions), treat it as a diagnostic clue pointing to the structure change the question wants you to recommend.

Organisational design is a recurring theme across CIMA E1 Managing Finance in a Digital World, and it sits alongside other people-and-organisation topics where the same application-over-bookwork rule applies. If this kind of scenario-matching trap sounds familiar, it is worth also reading about the Handy's culture types mistake, where candidates make an almost identical error by naming a culture type without linking it to what the case study actually describes.