The decision feels rushed.
You have committed budget or are about to, and something feels off — but nobody can say exactly what without leaving the room.
The decision to run them was driven by panic, not strategy. I trace back to that, then make sure what follows actually lands.
If you have committed budget to a digital programme — or are about to — and something feels off about how the decision was made or how delivery is progressing: that is the right moment to call.
I work where technology decisions meet business consequences – from the first hard questions and vendor selection to making sure what gets built is what was actually needed.
The answer is rarely to start over, and rarely to spend more. It is usually a matter of finding where the brief broke down and fixing the handover. That tends to be faster and cheaper than either side expects.
I put digital programmes back on track when the budget has been committed but the outcomes are not landing as expected. When that happens, the answer is rarely to start over and rarely to spend more. It is usually a matter of finding where the brief broke down — and fixing the handover before the next phase compounds the problem.
I sit between business and delivery – from the first hard questions and vendor selection to making sure what gets built is what you actually need. AI is part of that toolset where it speeds up understanding and decision‑making; it does not replace the ownership of those decisions.
In practice, that means three modes of engagement: taking the CDO seat on an interim or fractional basis to stabilise or re‑align a programme; owning a specific phase such as a diagnostic, vendor selection, regulatory feasibility review, or a go/no‑go before a pilot; or working inside a programme as the bridge between business decision‑makers and the technical team. The scope depends on where you are and what you actually need.
In regulated markets — fintech, lending, payments — compliance needs to be in the room from day one, not discovered after the first rejection. Licensing requirements, data‑handling obligations, and regulatory constraints shape the architecture, the timeline, and the budget; taking a platform through an AFM licence application in the Netherlands is one of the cases on the track record.
Some calls come before a programme starts; most come after it is already in trouble. Either moment is the right one — the earlier, the cheaper the fix.
You have committed budget or are about to, and something feels off — but nobody can say exactly what without leaving the room.
The vendor was selected before the scope was finalised. The programme now bends around the contract instead of the other way round.
Business and IT are giving clean explanations of why the gap exists rather than making equally clear decisions to close it.
Six months in, the scope looks nothing like what you agreed at kick‑off. Nobody can point to the decision where it changed.
Delivery is behind and the conversation has shifted from fixing it to assigning responsibility for the delay.
You are entering a regulated market and compliance has not been in the architecture conversation yet.
The programme is technically delivered. It just is not changing the business outcome it was justified on.
The original decision is being quietly revisited. Nobody wants to give that sentence a slide of its own.
No deck. No prep. Just thirty minutes. If there's a match, I'll follow up with a brief note on what I'd look at and a suggested scope.
Book a call