IIBF Strategic Management & Innovations common mistakes
IIBF Strategic Management & Innovations · Understand the traps and how to avoid them.
Writing SWOT as four disconnected bullet lists - strengths, weaknesses, opportunities, threats - and then stopping, without ever pairing an internal factor with an external one to produce a strategic option.
Most candidates learned SWOT as a brainstorming grid in school or in generic management courses, so under time pressure they reproduce the grid as a memory dump, believing that filling all four boxes earns marks. The exam actually rewards the TOWS crossover: SO, WO, ST and WT strategies that state what the firm should do, and a bare list contains no decision.
What to do instead
Before writing, force each item through a crossover sentence: 'Our strength X lets us capture opportunity Y by doing Z' and 'Our weakness P makes threat Q dangerous, so we must do R'. Answer in the TOWS order, not the SWOT order: options first, factor lists only as supporting evidence. Practise three past-case companies this way until the crossover becomes automatic.
Applying Porter's Five Forces as a synonym for 'competition' - naming rival banks only and then treating the analysis as complete, or substituting PESTLE macro factors for industry-level forces.
Candidates blur the level of analysis: PESTLE describes the macro environment while Five Forces describes the structure of a specific industry and its profit pool. Because regulation and technology dominate banking, it feels natural to dump them into the forces model, and because rivalry is the most visible force, the other four get skipped - so buyers, suppliers, substitutes and new entrants are never analysed.
What to do instead
Anchor each tool to its level: PESTLE = macro factors the firm cannot influence; Five Forces = industry structure the firm must position within. Write one sentence per force, always naming the specific actor (deposit customers as buyers, IT vendors and talent as suppliers, fintech lenders and capital markets as substitutes, a new payments bank licence as entry). Then state the profit implication and one positional move.
Describing a bank's business model innovation as a product or channel feature - for example answering an open banking or platform question with 'launch a better mobile app' - and never identifying which business model element actually changed.
Candidates default to the visible customer interface because it is easiest to describe, and they lack a structured vocabulary for value proposition, revenue model, cost structure, value network and customer segment. Feature lists feel concrete and safe, whereas stating 'we shift from net interest income to fee-based platform revenue' requires committing to an economic claim that could be marked wrong.
What to do instead
Use the Business Model Canvas as a checklist and, in every answer, explicitly name the block(s) that change: value proposition, revenue model, cost structure, key partners, channels. Then state the financial consequence - margin mix, capital intensity, customer acquisition cost - and one capability the bank must build. If the answer cannot name a changed revenue or cost line, it is a product answer, not a business model answer.
Labelling any new fintech entrant or new technology as 'disruptive innovation' and using incremental, radical, architectural and disruptive as loose synonyms, without testing the market-entry logic.
The word 'disruptive' is used in the popular press for anything new, so candidates absorb a colloquial meaning. The academic construct has a precise and counter-intuitive test - entrants start at the low end or in non-consumed segments with a simpler, cheaper, lower-margin offer and move upmarket - and that test contradicts the intuition that disruption always means a superior product at the top of the market.
What to do instead
Apply the test before using the label: does the entrant begin with an offer that incumbents' best customers reject as inferior, and does it improve fast enough to move upmarket? If yes, it is disruption and the incumbent's correct response is a separate unit, not a premium-tier upgrade. If it is simply a better product for existing profitable customers, call it radical or architectural innovation. Write one sentence justifying the label every time.
Treating digital transformation as digitisation - describing branch-to-app migration, paper-to-paperless flows or a new chatbot, and concluding that the bank has 'transformed', with no analysis of process redesign, data architecture, operating model or economics.
Channel migration is the most visible and most easily measured change, and it is what candidates see in their own banking experience. Transformation requires claims about cost-to-serve, decision rights, product modularity and the data platform, which are harder to state and easier to get wrong, so candidates retreat to the safe surface layer.
What to do instead
Answer on three explicit layers: customer experience (what changes for the customer), operating processes and data (what the bank must re-engineer - straight-through processing, real-time decisioning, cloud core), and business model (who pays whom and how margins shift). Give one metric per layer, such as digital-to-assisted transaction ratio, cost-income ratio effect, and fee versus interest share of revenue.
Making unsupported technology claims - 'AI will improve efficiency and reduce risk', 'blockchain will make transactions transparent' - with no named use case, no data or infrastructure dependency, no control or model-risk discussion, and no regulatory anchor.
Emerging-technology questions feel like general-knowledge questions, so candidates write plausible-sounding benefits and stop. They have not built a per-technology reference card tying each technology to one concrete banking use case, one failure mode, and one supervisory expectation, so they cannot go deeper than the marketing claim.
What to do instead
For each technology - machine learning, distributed ledger, APIs and open banking, cloud, RPA, generative AI - memorise a three-line card: specific use case (e.g. ML for early-warning credit signals), the dependency or risk (data quality, explainability, third-party concentration), and the control or regulatory anchor (model governance, outsourcing and cloud expectations, data localisation, KYC/AML obligations). Write those three lines, not adjectives.
Answering an execution question with a formulation toolkit - recommending a fresh SWOT, a new mission statement or another environmental scan - when the scenario already contains a chosen strategy that is failing to land.
The frameworks taught earliest and revised most are formulation frameworks, so they are the first thing retrieved under pressure. Candidates also underestimate how much of execution is structural and managerial rather than analytical, so they reach for a familiar analysis instead of addressing organisation design, resourcing, incentives and monitoring.
What to do instead
Read the directive verb first: if the question says implement, execute, deliver or make it happen, do not propose any new analysis. Work through the execution levers instead - structure and decision rights, resource reallocation, budget and funding, process and capability, incentives, and the monitoring cadence - and state what changes in each. One sentence per lever beats a page of re-analysis.
Stating execution goals without measurable targets or a cause-and-effect chain - 'improve customer service and increase digital adoption' with no baseline, no target, no timeline, no owner, and no distinction between lead and lag indicators.
Candidates describe intentions rather than a control system, because specifying a metric exposes a commitment that can be disputed in marking. They also rarely use the Balanced Scorecard properly, so they cannot distinguish an outcome they want (lag) from the driver they can act on this quarter (lead).
What to do instead
Convert every goal into a metric statement: baseline, target, date, owner. Then present a mini strategy map with one objective per Balanced Scorecard perspective and a lead-to-lag link - for example staff capability in credit analytics (learning) drives faster sanction turnaround (process) which drives cross-sell ratio (customer) which drives return on assets (financial). Finish with the review cadence and what triggers a corrective action.
Answering change-management scenarios with generic prescriptions - 'communicate effectively, provide training, get leadership buy-in' - with no named model, no sequencing, and no analysis of which specific stakeholder group will resist and why.
Generic phrases are remembered from induction programmes and feel safe because they are almost never wrong in the abstract. Candidates avoid naming Kotter's steps, Lewin's unfreezing or a stakeholder map because they fear sequence errors, but the result is an answer that could be pasted into any organisation and therefore scores no diagnostic marks.
What to do instead
Name the model and use its sequence explicitly: create urgency, build a guiding coalition, form a vision, communicate it, remove barriers, generate short-term wins, consolidate, anchor in culture - mapped to the case's specific actors. Add a stakeholder table with each group's interest, likely resistance reason (loss of discretion, workload, status, competence) and the tailored intervention. Address resistance as a design problem, not a communication problem.
Prescribing transformational leadership for every leadership scenario and ignoring situational contingency - including compliance-driven or crisis situations where the task demands clear direction, standards and transactional reinforcement rather than inspiration.
Transformational and charismatic leadership are taught as the 'higher' or more desirable forms, so candidates treat them as the universally correct answer. They overlook that transactional leadership, directive styles and situational leadership by follower readiness are the better fit for turnaround, regulatory remediation, fraud control or a demoralised, low-capability team.
What to do instead
Match style to conditions before writing: state follower readiness and task urgency, then choose. Crisis, regulatory breach and low-capability teams call for directive and transactional elements - clear standards, monitoring, contingent rewards; capable and motivated teams facing renewal call for transformational and empowering styles; distributed expertise calls for servant or shared leadership. Name the contingency variables explicitly rather than asserting one best style.