01 / AI
Responsible AI in real work.
Map opportunities, consequences and knowledge dependencies before a tool or pilot becomes the answer.
Typical outputOpportunity-and-risk view, decision points and an implementable next step.
Understand first. Then change with purpose.
What must keep working when people or systems change?
A key colleague leaves. A supplier changes. AI enters a critical process. Albir helps you see what could be lost, decide what to protect and leave a result others can use.
For organisations with complex work — including public services and mission-driven teams.
QUESTIONS FOR HANDOVER2026
What is critical?NAME IT
Who can explain it?TEST IT
Where is the evidence?FIND IT
Who takes over?AGREE IT
Working with complex systems since 1999. The interfaces changed. The responsibility to understand them did not.
Since 1999Experience in business analysis and project management.
PaymentsProcesses, bank connectivity and SWIFT MT/MX.
Lieven BaatsDirect involvement in analysis and implementation.
ALBIR BVA Belgian company with clear contact details.
Three kinds of work
Where complexity meets responsibility.
The work starts from a bounded organisational question. Analysis, facilitation and implementation support are added only where they improve the result.
02 / KNOWLEDGE
Knowledge that survives change.
Make critical expertise, dependencies and evidence visible before departure, outsourcing or automation turns them into a hidden risk.
Typical outputKnowledge map with dependencies and priorities for continuity and transfer.
03 / DELIVERY
Change that connects the parts.
Bring business analysis, process, systems and professional judgement together in something teams can actually use.
Typical outputDecision note, pilot design or implementation roadmap.
A practical work cycle
Old-school craft. Modern systems.
Tools change. Understanding, framing, testing and a clear handover remain the foundations of the work.
01 / UNDERSTAND
See the real work.
Processes, exceptions, decisions, knowledge and constraints.
02 / FRAME
Bound the question.
One process, decision chain or dependency can be enough.
03 / TEST
Challenge assumptions.
Look for hidden dependencies, recoverability and evidence.
04 / HAND OVER
Leave capability behind.
Make the result usable, maintainable and open to challenge.
From question to work
A permit team loses its most experienced colleague.
Illustrative public-sector scenario — not a client case or a measured result.
01
Situation
The formal procedure is documented, but unusual files are resolved through one colleague’s experience. An AI summary can reproduce an answer without explaining why it was appropriate.
02
Bounded intervention
Select one decision chain and three exception files. Trace the sources, record the reasoning, name who can approve an exception and let a colleague reconstruct the decision.
03
Expected output
An exception map, a decision trail and a handover test. The team can identify what is recoverable and which gaps need an owner — without claiming that the whole service is assured.
About Albir
Small enough for direct responsibility. Broad enough to follow a problem across organisational boundaries.
Albir is an independent consultancy for complex change. The work follows the question across business analysis, systems, process, knowledge and implementation instead of forcing it into one discipline.
- Start from the real process, not from a technology category.
- Reuse existing evidence and professional practice.
- Make critical knowledge and decision points visible.
- Leave teams with something they can continue to use.
One concrete question?
Start there.
Two or three sentences about the situation are more useful than a polished transformation brief.