Yvan Veldeman

Official documents, on your phone

MyGov.be — the federal wallet app for iOS and Android, under the strictest requirements a government application carries.

Situation

The documents that prove who you are and what you are entitled to are still things a citizen requests, carries or prints. The EU Digital Wallet is the federal answer to that: a mobile app, iOS and Android, that holds official government documents on the citizen's own device.

Constraint

An app holding proof of identity is a target the day it ships. The security and privacy requirements were the strictest that apply to a government application: privacy and security by design.

Agile · Proxy product ownership · iOS & Android · Security & privacy by design

Getting a government to plug itself in

Onboarding local and central entities to a single citizen portal.

Situation

Mijn Burgerprofiel is the one place a Flemish citizen sees their government data, permits and official documents. That promise only holds if the entities behind it actually connect — hundreds of local and central bodies, each with its own systems, budget cycle and appetite for change.

Constraint

None of them reports to the programme. Onboarding is a matter of persuasion, sequencing and making the integration cheap enough to say yes to — not of issuing a plan.

Decision

No onboarding process existed yet. Developing one was the first part of the job — a repeatable route to take an entity through, instead of arranging every connection from scratch.

Agile · Stakeholder management · Public sector integration

A new Collect&Go, built a country away

End-to-end delivery across an external supplier and a wide integration surface.

Situation

Colruyt's Collect&Go needed a new website. Development sat with an external supplier in the UK; the integration surface into Colruyt's own systems was wide, and the internal stakeholder list was long.

Constraint

Distance and org boundary in the same project: the people building it were neither in the building nor in the company, while everything it had to talk to was.

Vendor management · Risk management · Systems integration

One map for all of Flanders

Geopunt — the Flemish geoportal, Google Maps for Flanders — built from nothing as a programme of nine projects.

Situation

AGIV, the Flemish government's geographic information agency, set out to build www.geopunt.be: one public map where the region's geographic data could actually be looked at. Nothing of it existed yet, and it mattered enough to the agency to be run as a programme rather than a project — nine of them, four project managers, agile from the first day rather than converted to it halfway.

Constraint

A map of a region is made of other people's data. Almost nothing the programme needed belonged to it — the sources sat with other administrations and with parties outside government altogether, and the building of it was spread across several suppliers at once. So the programme ran on stakeholder management, internal and external, and on multi-sourcing management; neither of those is a phase you finish.

Decision

Treat those two as the work rather than as overhead around it, and take the proxy product owner role as well as the programme one — because the decisions that settle what a map shows are product decisions, and pushing them out to a committee is how a programme this size stops moving.

Result

Geopunt was delivered and is public. Because it mattered strategically to AGIV, the programme did not stop at the portal: it ended up changing the agency's own processes and organisation — which is the more interesting half, and the half nobody scopes at the start.

Agile · Programme management · Stakeholder management · Multi-sourcing · Proxy product ownership

geopunt.be

Twenty-one services, one page

A self-built control plane for the virtual private servers I run.

21

services on one page

Situation

Everything I build for myself runs on one Hetzner box: trading dashboards, a video knowledge base with RAG search, paper-trading engines, a market scanner, and the databases behind them. Twenty-one services, split across applications, background workers, infrastructure and databases.

Decision

One page, no navigation. Every service states its port, its status and how long it has been up; host CPU, memory, load average and uptime sit across the top; favourites pin above the rest. A web terminal, the Docker image list and a file browser are built in, so a fix does not need a second tool. The page refreshes itself and says when it last did.

Result

Managing all my services got a great deal easier at a glance.

×

Make AI Work

A Claude course for small teams, built as an app — three install paths, 18 modules, 87 ready-to-run recipes.

18

modules

87

recipes

3

install paths

Situation

Small business owners hear constantly what AI can do and get a fraction of it. The gap is rarely the model; it is knowing which workflow to run, in the software they already pay for.

Decision

Not a video course — an application. Three install paths sit across the front: Claude Desktop for the full eighteen modules, a Chrome extension that drives the browser, and an add-in that puts Claude inside Sheets and Excel. Each has its own setup steps and marks its own progress. Behind them: eighty-seven copy-paste recipes grouped by business function, twenty-eight setup guides, a prompt builder, and a scenarios route for someone who wants to skip the course and solve today's problem. Aimed at one-to-ten-person teams, explicitly not at developers.

×

course.linkflow.be

A readiness check for the AI Act

An assessment instrument for mid-sized companies, in three reading depths, with its own legal currency on the page.

3

reading depths

Situation

A mid-sized company has no in-house counsel and no appetite for the Official Journal. The news said the AI deadline had moved, most people read that and stopped reading, and the obligations that were already enforceable — the ones carrying the largest fines — were never postponed at all.

Decision

Three reading depths over one body of content — basic, practical, legal — so all three readers use the same page at their own level instead of being sent to different ones. A dated line in the header states which text it was checked against and when, so its currency is a claim on the page rather than an assumption in the reader's head. Four cards carry the live position: what is enforceable today, what actually moved and to when, the next deadline with a running count, and the maximum exposure. Then a guided assessment, with a worked example for anyone who wants to see one filled in before starting their own.

×