Find what will derail the program before the program starts.
Before an ERP, digitalization, or major technology investment, verify ownership, capacity, data, governance, dependencies, and change readiness while there is still time to fix them.
Runs on the Galactus assessment platform: anchored questions, evidence-based scoring, and red flags that override averages. See how our assessments work
44 anchored questions · 6 scored domains · the two program killers tested explicitly
Already decided and want the decision validated? See the Independent IT Second Opinion
The mandate starts with the decision, owner, time window, and evidence that could change the answer.
Scope, exclusions, evidence access, and uncertainty are made explicit before conclusions are presented.
Sven leads the work directly and closes with clear ownership, decisions, and next actions.
Test before mobilizing
The program is tested before budget, people, and credibility are committed to a plan the organization may not yet be able to carry.
01 / Frame
A Readiness Check is useful before an ERP, digitalization, or major platform program turns assumptions into commitments. It tests whether leadership, scope, capacity, data, and governance can support the promised plan.
02 / Test
Executive sponsorship, decision rights, standardization choices, key-user capacity, data quality, dependencies, vendor readiness, and change impact are examined against the actual program rather than a generic maturity model.
03 / Decide
Leadership receives a clear verdict with the evidence and conditions behind it. Weak foundations are not softened into an average score, and a vendor timeline is not treated as proof that the organization is ready.
04 / Prepare
When the program should not start yet, the output identifies what must change, who must own it, and which conditions must be demonstrated before budget, people, and executive credibility are committed.
Decision dossier
The useful boundary is visible before the work begins: the decision, the evidence, what is excluded, and what happens next.
Whether to proceed, pause, re-scope, or repair specific foundations before committing budget and executive credibility.
Decision ownership, governance, capacity, process maturity, data readiness, architecture and integration dependencies, security, vendor readiness, change impact, and delivery controls.
Software selection, implementation partner selection, detailed solution design, or acting as the program assurance office unless separately agreed.
Business case, scope, roadmap, governance design, resource plan, data and integration inventories, risk and dependency logs, vendor material, and stakeholder interviews.
The result identifies go, conditional go, or no-go conditions and the actions that must be owned before mobilization.
Timing
2-3 weeks
Delivery owner
Every mandate is led directly by Sven Van Roosenbroek. Specialist involvement, when needed, is made explicit in scope.
Commercial model
Fixed fee based on program scope and stakeholder coverage.
Thirty minutes is enough to establish fit, the right depth, and the next responsible step.