Mind the gap: done isn't delivered
Every team knows the moment work is done. Far fewer know how long it takes before anyone actually benefits from it. Features wait for a release, updates wait for the next maintenance round, and fixes wait for a slot in the calendar. For years that gap was simply the cost of doing business. Now it has become one of the biggest risks we carry, and one of the biggest opportunities we leave on the table.
Between the moment something is done and the moment it’s delivered lies a gap that most of us have learned to live with. We plan around it, negotiate it with clients and accept it as part of how the web works.
That acceptance is getting harder to justify. Security releases are arriving at a record pace, and the time between a vulnerability becoming known and being exploited keeps shrinking. At the same time, the effort it takes to close the gap has dropped dramatically. What once needed a dedicated team and a large budget is now within reach of almost anyone. With AI, a fix can be written in minutes; the harder part is becoming comfortable shipping it just as fast.
So why does the gap persist? Part of the answer lies in our tools, including in Drupal itself, where some of the basics of continuous delivery are still harder than they should be. Part of it lies in habits, contracts and expectations that made sense when delivery was slow and expensive. And part of it lies in a question this year’s theme invites us to ask: in a world where machines can do more of the routine work, where do humans add the most value?
This talk explores what it would take for our community to close the gap together: as developers, as module maintainers, as agencies and as the organisations that rely on Drupal. It’s a story of where we are, what’s changed, what we haven't solved yet, and why the next step may be smaller than we think.
Alexander Varwijk is Technical Product Lead at Open Social, a Drupal-based SaaS platform for online communities used by organisations such as the European Commission, the United Nations and Greenpeace International. In ten years there, he grew from developer to leading a product team, and helped the company make the move from consultancy to product company. He combines a background in engineering with a passion for product and business, and he loves finding and solving problems at the intersection of the three. Alexander is a regular speaker at DrupalCon and other events, and he contributes to the Drupal ecosystem, from asynchronous Drupal to the GraphQL and OAuth2 modules.