Arjan van Wieringen

A team that works, but not together

The team delivered, but everyone worked on their own. Problems stayed unspoken, one strong voice set the direction, and nobody felt really in control.

I started open discussions where every opinion counted, including when that meant disagreeing with the loudest one. Mistakes became something to talk about instead of something to hide. I made a point of noticing good work and celebrating it.

When the team had shown it could deliver, we dropped the meetings that no longer earned their time. Towards the rest of the organisation, I made clear that I stood behind the team.

Result: A team that talks openly, gets things done, and that other teams like to work with.

Delivering with AI agents

I was hired for three months to build a feature. Working with AI coding agents, it was done in three weeks.

That speed is not a trick of the tools. It comes from a codebase and a way of working that let agents do useful work safely. I help teams set that up for themselves.

Result: Three weeks instead of three months.

An architecture that outgrew its first job

I designed the full-stack architecture for a new application. It scaled so well that the organisation decided to move its legacy application onto the same platform.

Result: One platform instead of two, with the legacy application fully moved over.