ICAB PL Business Strategy common mistakes
ICAB PL Business Strategy · Understand the traps and how to avoid them.
Writing a PESTLE or five-forces list with no implication drawn, so the answer stops at description and never states what the analysis means for the case organisation's choices.
Candidates memorise framework headings and treat naming all six PESTLE factors or all five forces as the deliverable, because that is what revision notes reward; under time pressure listing feels productive and safe.
What to do instead
After each framework point, force one sentence beginning 'This means the organisation should...' or 'This raises the risk that...'. Before writing, decide the two or three most decision-relevant factors and give them depth, explicitly dismissing the rest as minor rather than listing everything.
Treating 'the industry is competitive and growing' as an opportunity or threat, rather than identifying a specific external change with a specific consequence for this organisation.
Candidates conflate generic industry description with environmental analysis, and lack practice in converting a fact into a directional implication with a named beneficiary or victim.
What to do instead
Use a strict three-part test for every opportunity or threat: the external change, the mechanism by which it affects the organisation, and the direction (favourable or adverse). Delete any point that cannot pass all three parts.
Choosing a strategy and then presenting only the benefits, with no evaluation of alternatives or criteria for the choice.
The case question often asks 'recommend a strategy', and candidates read that as 'describe one strategy'; evaluating alternatives feels like hedging and takes time they have not budgeted.
What to do instead
Always generate at least two genuine alternatives plus a do-nothing or status-quo option, then compare them against explicit criteria such as fit with capabilities, risk, financial return and stakeholder acceptability. State the criteria before applying them so the recommendation is visibly reasoned.
Recommending diversification or a new market entry without testing it against the organisation's existing resources and capabilities.
Ambitious growth options sound impressive and candidates believe a bold recommendation scores better than a cautious one, so they skip the resource-fit check that would expose the gap.
What to do instead
For every recommended option, produce a short capability-fit table: what the option requires versus what the case shows the organisation possesses, and how any gap will be closed and at what cost. If the gap cannot be closed credibly, downgrade or reject the option.
Describing the implementation plan as a list of activities with no owners, sequence, resources, milestones or success measures.
Candidates run out of time and compress implementation into a paragraph of verbs, and many have never practised writing a plan that could actually be executed.
What to do instead
Use a fixed template for implementation: initiative, accountable role, dependencies and sequence, resources and cost, milestone date, and the measure that shows it is working. Even three initiatives done to this template outperform ten unsupported activities.
Ignoring the funding and cash-flow consequences of a strategic recommendation, treating cost as a single number rather than a profile over time.
Strategy syllabi emphasise direction and positioning, so candidates treat finance as another subject; they also lack confidence doing quick arithmetic under exam pressure.
What to do instead
For each recommendation, state the investment required, when the outflows occur, when benefits begin, and the payback or breakeven point in rough terms. Show the arithmetic briefly so the marker can follow it, and flag any funding source or constraint.
Treating culture and stakeholder resistance as a single sentence about 'managing change', with no diagnosis of who will resist, why, and what specifically will be done.
Candidates know culture matters but have no analytical tool ready, so they default to a generic closing paragraph that adds no marks.
What to do instead
Map stakeholders by interest and influence, state the likely source of resistance for each key group (loss of status, competence, workload, ideology), and pair each with a named intervention such as involvement in design, piloting, retraining or changed incentives.
Assuming the existing organisational structure and reporting lines will absorb the new strategy unchanged.
Structure is treated as background context in the case rather than a variable the candidate can change, so structural misalignment is never surfaced.
What to do instead
Ask explicitly whether the current structure creates the coordination the strategy needs, and if not, propose the structural change (for example a product or customer axis, a coordinating role, or changed decision rights) with its own costs and transition risks.
Presenting a balanced scorecard or KPI set that measures activity rather than strategic outcomes, with no baselines or targets.
Candidates list measures they can remember rather than deriving them from the specific strategy in the case, and they omit baselines because the case rarely supplies them.
What to do instead
Derive each measure from a stated strategic objective, and for each give a baseline (or state the assumption if the case is silent), a target, a frequency and an owner. Drop any measure that would not change behaviour if it moved.
Writing about governance and risk in generalities, naming 'the board oversees risk' without identifying the specific risk, its likelihood and impact, or the control and responsible owner.
Governance feels like common sense so candidates do not prepare a structure for it, and risk registers are unfamiliar as an exam artefact.
What to do instead
Use a compact risk table: risk event, cause, likelihood, impact, mitigation, owner. Then link the top two or three risks back to the recommended strategy so governance is shown operating on the actual decision rather than described in the abstract.