CIMA E3 common mistakes
CIMA E3 · Understand the traps and how to avoid them.
Writing generic PESTEL or SWOT lists that name factors (for example "economic uncertainty" or "strong brand") without linking each factor to a specific consequence for the organisation's strategy, competitive position, or value chain.
Candidates memorise framework headings from introductory material and treat the model as the answer rather than as a thinking tool. Under time pressure, listing is faster than analysis, so the habit is reinforced by practice.
What to do instead
For every framework point, force a three-part chain: factor, so-what implication, and strategic response or risk. Practise by taking any PESTEL item and writing two sentences: the mechanism by which it affects the organisation, and what management should therefore do differently. If a point cannot produce a so-what, delete it.
Answering the question asked in a past paper or the textbook rather than the one on the page, for example producing a full Ansoff matrix when the requirement is to evaluate one specific growth option against a stated objective.
Revision is often organised around model names, so the candidate recognises a trigger word ("growth", "acquisition") and retrieves a prepared block instead of parsing the verb (evaluate, recommend, assess) and the scope qualifiers.
What to do instead
Before writing, underline the command verb, the object, and any limiting words ("for the next three years", "given the funding constraint"). Restate the requirement in one sentence in the margin and check every paragraph against it. Build a personal list of command verbs with the depth of response each demands.
Presenting stakeholder analysis as a power/interest grid with names plotted but no conclusions about whose expectations will shape the chosen strategy, which conflicts exist, or how each group should be managed.
Mendelow's matrix is easy to reproduce and feels like a complete answer, so candidates stop at classification. They also avoid the judgement step because it feels subjective and risky in an exam.
What to do instead
After plotting, add a short paragraph per quadrant stating the management approach and the specific concession or communication it implies. Then state which single stakeholder could block the recommendation and what mitigates that. Practise converting a grid into three sentences of advice.
Treating culture, structure, and leadership as background description ("the company has a hierarchical culture") rather than as causes that explain why a chosen strategy will fail or succeed in implementation.
Cultural and organisational topics are perceived as soft and less examinable than financial analysis, so candidates describe the current state and move on without connecting it to the strategy being evaluated.
What to do instead
Use a fixed bridge sentence pattern: current cultural or structural feature, therefore this implementation action will be resisted or enabled, so the recommendation must include this specific change lever. Link every cultural observation to a named implementation barrier and a named intervention such as reward redesign or a change agent network.
Producing a balanced scorecard or KPI set that mixes lagging financial measures with vague aspirations ("improve customer satisfaction") and omits targets, timeframes, and the causal links between perspectives.
Candidates recall the four perspectives but not the logic of the model, which requires a strategy map showing how learning and growth drives process, then customer, then financial outcomes. Without that logic, measures are chosen by association rather than by purpose.
What to do instead
Always build the causal chain first, then attach one or two measures per perspective with a target and a review frequency. Test each measure against the question: would a manager know what action to take if this number moved? Remove any measure that cannot answer that.
Recommending a strategy without evaluating alternatives against explicit criteria, so the answer reads as a single assertion rather than a reasoned choice among options.
Time pressure pushes candidates to pick the first plausible option and defend it. Many also confuse evaluation with listing advantages and disadvantages of one option rather than comparing options on consistent criteria.
What to do instead
State two or three criteria up front (for example fit with capability, financial feasibility, risk, stakeholder acceptability), then assess each option against the same criteria in a compact table or structured paragraphs, and finish with a justified recommendation plus the main risk. Rehearse this structure on any strategy question.
Ignoring the organisation's actual resources and competences when proposing a diversification or market entry, so the recommendation could apply to any company in the industry.
Candidates learn generic growth routes and industry recipes, and lack a habit of auditing internal capability before selecting a route. Case detail about distinctive skills or assets is read as context rather than as the constraint that should drive the choice.
What to do instead
Before recommending, write one line naming the threshold resources needed to succeed in the target market, and one line naming what the organisation actually has. Where there is a gap, either recommend building or acquiring the capability or reject the option. Make this gap analysis a mandatory step in every strategy recommendation.
Confusing corporate-level and business-level strategy, for example proposing a competitive pricing tactic when the question concerns portfolio composition, or proposing divestment when the question concerns how to compete in one market.
The levels of strategy are taught as a taxonomy but rarely practised as a filter, so candidates answer at whichever level their prepared content sits.
What to do instead
Label the question's level explicitly before answering: corporate (scope, portfolio, parenting), business (competitive advantage in a market), or operational. Then select only tools appropriate to that level, and check that each recommendation changes something the level's decision-makers actually control.
Writing long descriptive case summaries and industry background in the opening paragraphs, consuming time and word count that should carry analysis and recommendation.
Candidates fear missing marks for knowledge and believe restating the scenario demonstrates understanding. It also delays the harder analytical work.
What to do instead
Cap context to two or three sentences that establish only the facts you will later use. Adopt a discipline of never restating a fact without immediately adding its implication. In practice, time yourself to reach the first analytical judgement within the opening short paragraph.
Failing to integrate ethical, sustainability, and risk considerations into the strategy recommendation, treating them as a separate section appended at the end.
These topics are revised as standalone areas with their own frameworks, so candidates bolt on a paragraph about ethics or risk rather than letting those factors shape the option choice itself.
What to do instead
Add risk and ethical acceptability as standing evaluation criteria alongside financial and capability criteria, so they influence which option is recommended. For each recommendation, state the principal downside, its likelihood and impact, and the mitigation or monitoring control. This converts an appended section into part of the argument.