Diagnose before prescribing
Most failing programmes are misdiagnosed. The first weeks are spent reading the architecture, the contracts, and the incentives — not proposing technology.
About
Forty years spent inside systems that are not allowed to fail.
Josef Vemark advises governments, regulators, and financial institutions on the infrastructure citizens depend on without ever thinking about it: identity, payments, benefits, registries. The work began on mainframe financial systems in the early 1980s and has followed the same thread ever since — how large, old, politically exposed systems are modernized without interrupting the people who rely on them.
The remit is deliberately narrow. He is brought in when a programme is consequential, contested, or already in difficulty, and when the decisions that matter are structural rather than cosmetic: architecture, sequencing, vendor posture, and the compliance envelope the system must live inside.
How the work runs
Treat policy as architecture
Regulatory parameters are design inputs, not obstacles raised late. Systems built that way pass assurance the first time.
Ship in sequence
Statewide platforms fail on ordering far more often than on engineering. Sequencing decisions are the advisory work that matters most.
Leave the team stronger
An advisor who becomes load-bearing has failed. The measure is whether the client's own people can run the system afterwards.
Operational Philosophy
“High-stakes infrastructure demands a steady hand and a clear perspective. My approach is entirely pragmatic, built on decades of pattern recognition: cutting through bureaucratic and technical clutter to ship durable systems that must work, without exception. No unnecessary drama, just direct execution.”