EXIN BCS International Diploma in Business Analysis Oral Examination common mistakes
EXIN BCS International Diploma in Business Analysis Oral Examination · Understand the traps and how to avoid them.
Answering the oral examiner's question with a memorised definition of a technique (for example reciting the textbook description of a SWOT analysis or a business activity model) instead of applying it to the candidate's own submitted project, so the answer never mentions their stakeholders, their evidence, or their decision.
Candidates prepare by revising the syllabus and assume the oral is a viva on theory. The exam actually probes the reasoning behind the candidate's own work, and under pressure people fall back on the definitions they rehearsed rather than the case they lived through.
What to do instead
Before the exam, build a one-page 'project map' for each submitted piece of work: the situation, the stakeholders, the technique used, the options considered, the decision taken, and the outcome. Practise answering every likely question by starting with 'In my project...' and only then naming the technique. Record yourself and check that each answer contains at least one specific fact from your own work (a number, a named role, a date, a document).
Describing what was produced (a requirements catalogue, a process model, a business case) without explaining the judgement behind it: why that technique rather than another, what alternatives were rejected, and what trade-offs were accepted.
Candidates confuse 'what I did' with 'why I did it'. The oral is assessing professional judgement, and describing deliverables is the easy, safe part of the story. Many candidates have never been asked to justify their method choice, even at work.
What to do instead
For each artefact you submit, write down two rejected alternatives and the reason each was rejected. Practise the sentence pattern: 'I chose X because..., I considered Y but rejected it because..., and the risk I accepted was...'. Aim to have this ready for every technique in your submission, not just the ones you are proud of.
Giving a generic answer about stakeholders ('I consulted the business users') instead of naming specific stakeholder groups, their interests, their influence, and how the candidate handled a conflict between them.
Stakeholder analysis is often done superficially on real projects, so candidates genuinely have thin material to draw on. They also fear naming real people or organisations, so they blur the detail until the answer is meaningless.
What to do instead
Prepare three stakeholder stories in advance, each with a named role (not a real name), their interest, their power or influence, the tension involved, and the action you took. Anonymise the organisation rather than the analysis. Rehearse one story about a stakeholder who resisted and how you moved them, since conflict questions are near-certain.
Treating the oral as a solo presentation, delivering a long uninterrupted monologue and not picking up on the examiner's follow-up probes or signals to go deeper or move on.
Candidates over-prepare scripts and fear silence, so they keep talking. They also misread the oral as a performance to be delivered rather than a structured professional conversation with an assessor who is testing the limits of their understanding.
What to do instead
Practise answering in 60 to 90 seconds and then stopping. Learn to hear a follow-up as an invitation, not a criticism. In mock sessions, have a colleague interrupt with 'why?' three times in a row; train yourself to answer each 'why' with new substance rather than restating the previous answer more loudly.
Failing to connect the submitted work to the wider business analysis lifecycle: for example presenting a requirements elicitation piece with no link to the business situation that triggered it, or a business case with no link to how benefits would be measured after delivery.
Candidates submit work from a narrow slice of a project and never saw the upstream or downstream context. The oral expects them to show where their work sat in the end-to-end process and how it fed the next stage.
What to do instead
Draw a simple lifecycle strip (business situation, investigation, requirements, solution options, delivery, benefits) and mark where each submitted piece sits. For each piece, write one sentence on what came before it and one on what it fed. If you genuinely did not see a stage, say so and explain what you would have needed from it.
Handling 'what would you do differently?' by defending the original decision or giving a vague 'nothing major', rather than showing reflective practice with a concrete alternative and its likely consequence.
Candidates hear the question as an attack on their competence. Reflective practice is a genuine skill that many analysts have not been asked to demonstrate formally, and admitting a weakness feels risky in an assessment.
What to do instead
Prepare three honest lessons learned in advance, each with the specific trigger, what you would change, and what you believe the effect would have been. Frame them as professional judgement, not confession: 'I would have run a workshop rather than interviews because the conflicting views only surfaced when people were in the same room.'
Being unable to state the actual benefit, cost, or measure behind a business case or requirements prioritisation, answering with 'it was approved by the board' or 'the business wanted it' instead of the underlying figures and rationale.
Many analysts inherit business cases they did not write, or work in organisations where numbers are owned by finance. They therefore never internalise the economics and cannot defend the recommendation when probed.
What to do instead
Reconstruct the numbers yourself before the exam: the cost, the expected benefit, the measurement approach, the payback period, and the biggest assumption. Where you cannot know a figure, be explicit about the assumption and how you would test it. Examiners accept 'I did not own that number, but I challenged it by asking...' far more readily than a blank.
Using the oral to argue that the exam technique or the submitted work was constrained by the employer ('we don't do that here', 'my organisation doesn't allow modelling'), effectively blaming the context instead of showing what the candidate did within it.
Candidates feel their real-world work is being judged as substandard and become defensive. Blaming the organisation is a way to protect the submission, but it reads as an absence of professional agency.
What to do instead
Reframe constraints as decisions: 'The organisation did not fund full process modelling, so I prioritised the three processes with the highest error rates and documented the rest at a higher level, accepting the risk that...'. Show the trade-off you made and the risk you consciously accepted; that is exactly what the assessor is looking for.
Failing to prepare logistically and structurally: arriving without knowing which techniques are in the submitted work, being unable to locate a specific artefact the examiner refers to, or not being able to summarise the submission in a two-minute overview.
Candidates focus all preparation on knowledge and none on their own submission. If the work was completed months earlier or written by a team, their memory of it is hazy, and the oral quickly exposes gaps in ownership.
What to do instead
Re-read your own submission end to end at least twice in the final week and annotate it with the reasoning behind each section. Prepare and rehearse a two-minute overview covering context, role, techniques, and outcome. Keep a single index page listing each artefact, the technique it demonstrates, and the three questions you expect on it.
Answering questions about professional ethics or conduct (for example pressure to sign off incomplete requirements, or handling conflicting stakeholder interests) with a purely procedural answer, ignoring the ethical dimension and the candidate's own accountability.
Ethics is often treated as a soft topic that will not be examined, and candidates have no rehearsed example. They default to describing process steps because that feels safer than making a values-based judgement.
What to do instead
Prepare one real or realistic ethical dilemma from your experience: the pressure, the options, the person you consulted, the decision, and the consequence. Rehearse stating your professional position plainly and naming the relevant principle (for example honesty about uncertainty, or independence of judgement) without hiding behind procedure.