ICAB AL Strategic Business Management common mistakes
ICAB AL Strategic Business Management · Understand the traps and how to avoid them.
Writing a generic PESTLE or Five Forces list with no link to the case organisation, so each bullet could apply to any firm in any industry.
Candidates memorise framework headings and treat the model as the answer rather than as a lens; under time pressure they dump the template and move on without applying it.
What to do instead
For every factor, force a two-part sentence: the external trend plus its specific consequence for this organisation's margins, demand, or strategic options, and rank factors by impact so the analysis concludes with the two or three that actually matter.
Treating resources and competences as the same thing, listing 'strong brand' or 'skilled staff' as a competence without showing how activities combine into a capability that delivers value.
The resource-based vocabulary is familiar but the distinction between inputs and the routines that deploy them is subtle, and exam answers reward visible framework labels.
What to do instead
Build a two-column table separating resources (what the firm has) from competences (what it does well repeatedly), then test each competence against VRIO or the threshold/distinctive split and state explicitly which one underpins competitive advantage.
Recommending a strategy without evaluating alternatives, so the answer jumps from analysis to a single preferred option with no criteria, trade-offs, or rejection of rivals.
Candidates run out of time on analysis and rush the choice section, or they believe naming one strong option demonstrates decisiveness.
What to do instead
Generate at least three genuinely different options, appraise them against explicit criteria such as suitability, acceptability and feasibility (or SAF/risk/return), and justify the rejection of each discarded option in one sentence.
Describing implementation as a list of tasks ('communicate, train, monitor') with no sequencing, ownership, resourcing, or treatment of resistance and culture.
Implementation feels like common sense so it attracts shallow prose, and candidates underestimate how much of the marks sit in change management and organisational design.
What to do instead
Structure the answer around a named change model (for example Lewin, Kotter, or a cultural web), assign each step an owner and timeframe, and address stakeholder resistance and structural fit explicitly rather than as an afterthought.
Confusing governance with day-to-day management, describing the CEO's operational duties when asked about the board, or failing to distinguish executive from non-executive roles and board committees.
The separation of direction, oversight and execution is conceptually slippery, and candidates default to describing leadership behaviour they know from case studies.
What to do instead
Anchor answers in the agency problem: state who directs, who monitors, and who executes, then map the specific case facts onto board composition, independence, audit and remuneration committees, and disclosure obligations.
Treating stakeholders as a single undifferentiated group, or listing them without assessing power, interest, or the ethical tension between competing claims.
Mendelow's matrix is memorised as a diagram but rarely applied, and candidates avoid ethical judgement because it feels subjective in an exam.
What to do instead
Plot named stakeholder groups on power and interest, derive a tailored engagement approach for each quadrant, and where claims conflict state the ethical principle (utilitarian, rights-based, justice-based) used to resolve it and why.
Producing a risk register of generic risks with no likelihood, impact, or link to the strategy being recommended, and no discussion of controls or residual risk.
Risk is often revised last and answered from memory rather than from the case, so the register floats free of the strategic decision under discussion.
What to do instead
Tie each risk to a specific strategic option, score likelihood and impact, identify the control or mitigation, and state the residual exposure and who owns it, distinguishing strategic, operational, financial and compliance risk.
Calculating ratios correctly but stopping at the number, with no interpretation of what the movement means, why it occurred, or what management should do about it.
Candidates treat the calculation as the deliverable and fear that interpretation is speculative, so they leave marks for analysis on the table.
What to do instead
Use a comment structure of result, cause, consequence and action for each metric, and compare against a benchmark, prior year, or budget so the figure carries meaning rather than standing alone.
Describing digital technology in vague terms ('invest in AI, improve the website') without connecting it to a business model change, capability gap, or measurable benefit.
Digital topics feel novel and candidates lack a structured way to move from technology to value, so they produce buzzword lists.
What to do instead
Frame each digital initiative as a change to a specific business model component (customer channel, value proposition, cost structure, revenue stream), identify the capability and data required, and state the expected benefit and the risk of disruption.
Ignoring the question's command verb and case constraints, writing everything known about a topic rather than answering what was asked within the organisation's stated resources and timeframe.
Under exam pressure candidates regurgitate prepared notes, and skimming the stem means the scenario's budget, market, or regulatory limits are missed.
What to do instead
Underline the command verb and the case constraints before planning, allocate marks proportionally to each part, and close with a short recommendation that explicitly respects the stated constraints and answers the verb asked.