Who does the work

This theme is, in its own way, hopeful. The Church is not waiting to be rescued. In many places, it is already changing how the work gets done.

A new role, appearing on its own

In several districts, quite separately from one another, the same answer has emerged: paying someone to carry the load. An operations manager, a district administrator, a property officer – often part-time, often someone with experience from outside the Church – employed to absorb the admin and compliance that would otherwise crush a minister or fall to no one at all.

Where this role exists, the relief is real. Work that once took local volunteers days, and a good deal of worry, can be done in minutes by someone who knows the systems.

The people who want to help – but not like this

Alongside this, we heard about a large group of willing people who want their church to have a good digital presence, but who will not, or feel they cannot, be the one to build it. The gap is rarely about ability. It is about confidence, and a quiet reluctance to be made responsible for something new.

One digital volunteer went into a church expecting to talk about social media, and "ended up leaving having told them to make an email address for the church." The fallback, people told us with a smile, is always the same: "someone will have a grandchild."

The people we must not leave behind

We also heard, clearly, about faithful church members in their seventies and eighties who hold real responsibilities and may have no email address at all. They are not a problem to be solved. They are part of the Church. When something moves online and they cannot follow, the load shifts to the few who can – or a message is printed out and carried, by hand, to the next chapel.

Why it matters

Whatever the Church builds has to be designed for the people who will actually use it – the new paid operators, the once-a-week volunteer, and the member who has never been online – all at once. Adoption is not a step that comes after the building. It is the whole point of it.

Where this points

Two things follow. Build for the real range of people doing this work, not an imagined confident user. And invest as much care in helping people take something up – patiently, person to person – as in building the thing itself.