EXIN BiSL Foundation common mistakes
EXIN BiSL Foundation · Understand the traps and how to avoid them.
Treating BiSL's three process layers (steering/governance, management, execution) as if they were the same as the three domains (business information management, information management, functional management) and assigning a process like 'information portfolio management' to the wrong axis.
BiSL uses two different groupings - process clusters/levels (sturende, richtinggevende, uitvoerende processen) and domains (bedrijfsinformatiebeheer, informatiemanagement, functioneel beheer) - and candidates who learned the acronyms by rote confuse the two axes because both are often drawn as three-part diagrams.
What to do instead
Build a two-axis grid: rows = the three process levels (governance, management, operational/execution), columns = the domains. Place each named process in exactly one cell and rehearse why. For example, establish that portfolio and strategy processes sit at the governance level within business information management, while day-to-day user support sits at the execution level in functional management.
Confusing the roles of the business information manager, the information manager, and the functional manager - for instance stating that the functional manager decides the information strategy or that the business information manager handles incident tickets.
The role names sound interchangeable in translation, and candidates map them onto familiar IT job titles from their own organisation, which rarely match BiSL's division of responsibility.
What to do instead
Memorise each role by its core question and its main counterpart: business information manager owns the demand side and the relationship with business strategy; information manager translates that into information provision and the information plan; functional manager keeps the information systems usable for users day to day. Write one sentence per role describing what it decides, then test yourself by asking 'who decides X?' for ten sample decisions.
Answering questions about the relationship between BiSL and ITIL or ASL by claiming BiSL replaces or overlaps fully with them, instead of positioning BiSL as the demand-side complement to supply-side frameworks.
Candidates often come from an IT service management background where ITIL is the only reference model, so they force BiSL processes into ITIL categories or assume the exam treats them as competitors.
What to do instead
Learn the demand/supply split explicitly: BiSL covers the business information demand and information provision, ASL covers application management, ITIL covers infrastructure and service delivery. Practise hand-off questions - which framework owns change coordination, which owns the user organisation - and note that the interfaces, not the overlap, are what the exam tests.
Misidentifying which processes belong to the governance (sturende) level versus the management (richtinggevende) level, e.g. placing 'information portfolio management' at management level or 'information lifecycle management' at governance level.
The Dutch-derived level names translate inconsistently into English study material, and candidates rely on intuition about what sounds 'strategic' rather than learning the fixed process list.
What to do instead
Create a flashcard set with each process name on one side and its level plus a one-line purpose on the other. Group them by the question each level answers: governance asks 'where are we going and what is it worth', management asks 'how do we organise and plan it', execution asks 'is it working today'. Review until you can sort all named processes without hesitation.
Treating the BiSL process model as a strict sequential waterfall - assuming a process cannot start until the previous one is formally closed - and answering 'sequence' questions accordingly.
Diagrams in the syllabus are drawn left to right, which invites a linear reading, and candidates without process-modelling experience default to a waterfall mental model.
What to do instead
Study the stated relationships between process clusters and note where cycles and feedback loops are intended. When a question asks about ordering, look for the trigger or input named in the question rather than assuming a fixed chain. Practise with scenarios describing an urgent demand arriving mid-planning cycle and reason about which process responds first.
Giving generic answers about 'aligning IT with the business' where the question asks for a specific BiSL product or deliverable, such as the information plan or the information provision plan, and their distinct contents.
BiSL's value proposition is often summarised in alignment slogans, so candidates learn the slogan and never learn the named products, then cannot match a product to the process that produces it.
What to do instead
List the key products per process with their purpose, owner, and intended audience. Distinguish clearly between plans that describe what information the business needs and plans that describe how information provision will deliver it. Rehearse by taking a product name and stating which process creates it and who consumes it.
Assuming BiSL is only relevant to large enterprises or only to the IT department, and selecting answers that restrict its scope to central IT functions.
Candidates transfer assumptions from their own workplace, where information management sits inside IT, and the framework's business-side orientation is under-emphasised in casual summaries.
What to do instead
Anchor on the framework's premise: BiSL addresses the demand side of information provision and places responsibility with the business organisation, not the IT supplier. For scope questions, ask 'who owns the information requirement?' and choose the answer that keeps that ownership in the business domain.
Confusing the purpose of the information manager's planning cycle with project or programme management, and answering that BiSL prescribes how IT projects are run.
Planning terminology overlaps with project management vocabulary, and candidates with a PM background map BiSL planning processes onto project stages.
What to do instead
Keep the boundary explicit: BiSL governs the demand, the information provision and the user organisation's use of information; project execution methodology is outside its scope. When a question mentions project delivery, identify whether it is asking about the demand-side input to the project or the delivery mechanics, and answer from the demand side.
Skipping the Dutch-origin terminology and answering on the basis of English translations alone, then failing questions that hinge on a term whose translation is ambiguous, such as the distinction between information provision and information management.
The framework was developed in the Netherlands and several core terms have no single settled English rendering, so candidates who never see the original terms cannot disambiguate them.
What to do instead
Keep a bilingual glossary: for each core term record the original term, the English rendering used in your study material, and a one-line definition. Where two English words are used for the same concept, note the equivalence so a question using either wording is recognised.
Memorising process names without being able to state, for a short scenario, which process would own the activity described - resulting in answers that name a plausible-sounding but wrong process.
The exam is scenario-driven and rewards functional understanding, while most candidates prepare by rereading lists of process names, which builds recognition but not application.
What to do instead
Switch to scenario practice: write ten short workplace situations (a new regulatory reporting requirement, a recurring user complaint, a supplier contract renewal) and for each identify the owning process, the responsible role, and the product produced. Compare against the framework definitions and correct mismatches, repeating until the mapping is automatic.