BCS Written Management common mistakes
BCS Written Management · Understand the traps and how to avoid them.
Writing a generic essay on the strategic planning process (mission, SWOT, objectives) without applying it to the scenario organisation, so the answer could be pasted into any question.
Candidates memorise textbook frameworks and reproduce them under time pressure, believing coverage of the model earns marks, when the mark scheme rewards application to the given context and judgement about trade-offs.
What to do instead
Before writing, spend two minutes extracting three or four facts from the scenario (sector, size, stated objective, constraint) and attach each framework element to one of them; for every model point, add a sentence beginning 'In this organisation, this means...' and finish with a recommendation the scenario's decision-maker could act on.
Producing a budget or investment appraisal with correct arithmetic but no commentary on assumptions, sensitivity, or the qualitative factors behind the numbers.
Quantitative questions feel safe and candidates spend disproportionate time on calculation, treating the narrative as optional decoration rather than the assessed judgement.
What to do instead
After each calculation, write a short interpretation paragraph: state the key assumption, show what happens if a variable moves by a plausible margin, and name one non-financial factor (reputation, staff morale, regulatory exposure) that could overturn the numerical conclusion.
Describing a project methodology (critical path, earned value, stage gates) in the abstract without diagnosing the specific failing project in the scenario or proposing a recovery plan.
Project questions often include technical vocabulary that triggers recall of definitions, and candidates answer the vocabulary rather than the managerial problem posed.
What to do instead
Structure the answer as diagnosis, cause, action: identify the symptom in the scenario, trace it to a control or governance weakness, then set out three sequenced corrective actions with owners and timing, using technique names only as evidence for the diagnosis.
Treating change management as a list of models (unfreeze, change, refreeze; urgency, coalition, vision) with no analysis of resistance sources or stakeholder positions in the case.
Change models are easy to recall and appear comprehensive, so candidates list them sequentially instead of using one model as an analytical lens on the specific situation.
What to do instead
Choose one model only, map the scenario's named groups onto its stages, and for each group state the likely source of resistance (loss of status, workload, uncertainty) with a matched intervention such as consultation, piloting, or visible sponsorship.
Answering governance and ethics questions with pure assertion ('the board should provide oversight', 'staff must act ethically') without citing mechanisms, codes, or consequences.
These topics feel like common sense, so candidates write principles rather than the concrete structures that make principles operative, and run out of substance.
What to do instead
Convert every principle into a mechanism: name the committee, the reporting line, the register, the declaration process, the escalation route, or the sanction; where a professional code applies, state the specific obligation and what breach would look like in the scenario.
Listing risks in a register without assessing likelihood and impact, naming an owner, or linking each risk to a response type and a monitoring trigger.
Candidates equate identifying risks with managing them and stop at the brainstorm stage, which earns only the lowest band of marks.
What to do instead
Use a compact table format in the script: risk, cause, effect, likelihood, impact, rating, owner, response (avoid, reduce, transfer, accept), and the indicator that would signal it materialising; add one sentence on residual risk after the response.
Ignoring the word limit distribution, writing a long answer to the first question and leaving the final question answered in note form or omitted entirely.
Candidates write chronologically and let early momentum consume time, often because they have not rehearsed timing or decided question order in advance.
What to do instead
Allocate minutes in proportion to marks, write the strongest question second (after a short warm-up), and keep a visible clock checkpoint: if a question's time is up, close it with a bulleted conclusion and move on, since a completed outline outscores an unfinished essay.
Discussing information systems strategy as a technology purchase decision, omitting data governance, security, legacy integration, and benefits realisation.
Candidates without technical backgrounds default to vendor selection and cost, missing the strategic and control dimensions the syllabus actually tests.
What to do instead
Frame every IS answer around business alignment: state the strategic objective the system serves, then address data ownership and quality, access control and security obligations, integration with existing systems, and how benefits will be measured after go-live.
Writing about people management in purely motivational terms, ignoring performance management, legal obligations, and the link between HR practice and organisational objectives.
Behavioural topics invite anecdotal or humanistic writing, and candidates underuse the contractual, statutory, and measurement dimensions that carry marks.
What to do instead
For each people issue, address three layers: the individual (capability, motivation), the managerial system (objective setting, appraisal, feedback, development), and the organisational and legal context (policy, consultation, fairness, record-keeping), then recommend an intervention at each layer.
Failing to reach a decision in the final section, ending with 'it depends' or a summary of points already made instead of a justified recommendation with implementation steps.
Candidates fear committing to a position that could be marked wrong, so they hedge, but the assessment rewards reasoned judgement rather than neutrality.
What to do instead
Reserve the last paragraph for a clear recommendation, give two reasons tied to the scenario evidence, acknowledge one counter-argument and rebut it, then state the first three actions, the responsible role, and the measure of success.