This article was prepared with AI using the sources below. Read those sources for their original context.
Translated from the Dutch article. The original publication date is retained.
EDAY’s organiser announced a contribution by Ahold Delhaize CTO Gerhard van der Bijl about human and machine intelligence. An announcement of practical examples is not an independent measurement of their outcomes.
For a practical example, ask how the sequence was chosen: which problem came first, what data was available and why this application was built. Use the answers to sharpen your own decision questions.
The process first, then the tool
Do not turn a story about AI in a large organisation directly into a purchasing decision. First ask which process was examined, which data was used and how results were measured.
For a smaller team, start with a defined task. Describe the existing work and intended change before choosing software. Also record unknown constraints and access requirements.
Pressure on teams is no excuse
Make room to report errors in a trial. Agree who reviews reports, how a workflow is stopped and who decides when to resume it. That makes control in your process concrete without untested claims about stress research or other sectors.
I am not saying you need a culture programme. I am saying you should ask one question with every automation: does the employee using it feel able to report a problem? If not, the automation is not ready yet.
What you can do this week
Take one recurring task that takes a lot of time. Think about order confirmations, invoice checking or answering the same five questions by email. Write down who does it, how long it takes and exactly which steps are involved. Do this by hand on one A4 sheet. You now have a description of your process. Without it you do not know what you are automating, and therefore what you are measuring.
- Choose one task that recurs weekly and involves a lot of repetitive work.
- Write the steps in ordinary language, without system names.
- Record who currently does the task and where things go wrong.
- Decide which step a person must keep doing and which a tool can take over.
A process you can describe and test is a useful starting point. A speaker or event alone does not establish that the same application fits your business.
Sources
- CTO Ahold Delhaize naar EDAY 2026 ↗ · Emerce
