Why good technology projects fail in parishes
A parish spends £4,000 on a new website.
A good agency is chosen. They have real WordPress expertise, genuine Catholic experience, a decent portfolio. A volunteer is nominated to run the site; she used to work in marketing before her children were born. Training is booked. A launch date is agreed. At the PPC meeting before the launch, Father says some warm words about the exciting new direction for the parish. Everyone claps.
Six months later:
The website has three posts on it. Two of them are from launch week. The third is the Easter Mass schedule, which is now out of date.
The volunteer has moved to another parish because her husband changed jobs.
The parish secretary has her Friday mornings back, which she was quietly glad about, and has not said so aloud.
Father, when asked, says he thinks it is going well.
Nobody can find the password.
The £4,000 is gone.
Every parish secretary reading this is nodding. Every priest who has been in the same parish for more than five years has seen some version of this. The specific numbers may differ. The pattern does not.
This piece is about why this keeps happening, and why the way most people think about preventing it is wrong.
The temptation to blame something specific
When faced with this pattern, the instinct is to blame something concrete.
The agency picked the wrong CMS. The volunteer was flaky. The priest did not really back the project. The parish secretary was quietly resistant. The training was inadequate. The CMS was too complicated.
All of these are sometimes true. None of them is the real answer.
The real answer is that the parish never actually changed. And the parish never actually changed because nobody had ever sat down and thought honestly about what it takes for a parish to change.
The website was built. The training was delivered. The launch happened. But the human system around the website did not adapt, because nobody had sat down to adapt it, because the project was treated as a technology project when it was really a change project.
The £4,000 paid for the website. It did not pay for the change that would have made the website useful. And the change, it turns out, was the thing that actually mattered.
Why parish change is not corporate change
A parish is not a company. Five things make this true, and each of them matters for why the £4,000 website failed.
The primary unit is relationship, not process. In a company, a manager can change a process and expect compliance because paycheques depend on it. In a parish, nobody’s paycheque depends on using the new website. Change happens through trust, and trust does not run on project timelines.
Most of the people doing the work are volunteers. The volunteer who was nominated to run the website was a volunteer. She could leave, and did. A company can hire a replacement. A parish cannot simply replace a volunteer; it needs another volunteer to say yes, and the saying yes is not automatic.
The parish has been here longer than the project has. The parish secretary has been running communications informally for seven years. She knew what the previous system did well. Nobody asked her. The new website was built without incorporating her knowledge, and so it did not solve the problems she was actually solving. When she quietly stopped using it, nothing stepped in.
The stakes are pastoral, not commercial. When the website failed, the cost was not lost revenue. It was that bereaved families could not find the funeral coordinator’s number. That newcomers could not find Mass times. That the website that was meant to help the parish was, quietly, making it slightly harder to serve its people. Pastoral harms compound over time in ways the balance sheet does not show.
The spiritual life of the parish continued throughout. The project was not the main event. The Mass was the main event. The sacraments were the main event. The pastoral care of the sick and bereaved was the main event. The project asked the parish to prioritise the change over the mission for three months, and the parish, correctly, did not.
These are not complications to be managed around. They are the actual conditions under which parish change happens. The £4,000 website failed because it ignored all five.
What should have happened instead
The same project, conducted with invitation and patience, would have looked like this.
Before the £4,000 was spent, a “what already works” audit. Conversations with the parish secretary, the previous website volunteer, the long-serving ministry leaders. Understanding what the current arrangement was doing well and what it was not. Two to four weeks of genuine listening.
Before the agency was briefed, a change proposal drafted collaboratively. Not by the agency or the priest alone. By a small group including the parish secretary. The proposal would have named what the change was meant to achieve in pastoral terms, not technical terms, and it would have honoured what the current arrangement was already doing well.
Before the launch date was set, consultation with the Parish Pastoral Council and the finance committee. Not to rubber-stamp a decision already made. To shape the decision before it was final. Time allowed for reflection. The parish given the opportunity to say “wait, we are not ready.”
Before the volunteer was nominated to run the site, a commissioning conversation. About scope. About authority. About what the parish was promising her in support, and what she was promising in return. A written role description. A named review date. A clear sense that she was not alone.
Before the launch, a pilot. Three or four originators using the new system in parallel with the old one. Learning what was working, what was not, what needed adjusting. Not a soft launch; a genuine listening exercise.
After the launch, a named six-month review. The priest checking in with the volunteer. Adjustments made based on real use. A clear handover at the end of the project phase from the agency to the parish.
The cost of this approach: roughly the same in money. More in time. The project would have taken eight months or a year, not eight weeks. The agency would have had to be paid differently, perhaps in phases rather than a lump sum.
The outcome: a website still being used three years later, by a volunteer who is still in place, with a parish secretary who feels part of the system rather than bypassed by it.
The honest sales pitch
True Light Digital is a communications agency. We are in the business of building things for parishes.
We are also in the business of saying no to projects that are structured to fail.
A parish that asks us to build a £4,000 website in eight weeks with a generic spec and a volunteer nominated but not yet committed is a parish we will gently redirect. Not because we do not want the work, but because the work, structured that way, will produce the scene at the opening of this piece.
We would rather say no to a project than take a parish’s money for something we know will not last.
This posture is costing us some work. It is also, we think, the only posture that can honestly serve parishes over time. Agencies that take the £4,000 and deliver in eight weeks are the agencies whose work you see failing in other parishes. You have probably seen a few of them yourself.
Where to go next
If the scene at the opening of this piece is familiar, the Pillar 3 cornerstone (Invitation & Patience) explains the full framework of how parish change actually works. It is the intellectual anchor for everything this piece touches on.
The “What Already Works” Audit (W3) is where any genuine parish change project should begin. Before a proposal, before a brief, before a pound is spent.
The Three-Seasons Pacing Guide (T7) is the practical companion that helps priests, PPC chairs, and agencies structure projects at parish pace rather than corporate pace.
The Change Proposal Template (T3) is what the proposal itself should look like when it is eventually drafted.
And the reflection guide Invitation, Not Buy-In (R3) is the piece that helps anyone trained in corporate change management (agencies, diocesan staff, PPC members with management backgrounds) recalibrate for parish work.
All free. All aligned. All together, enough to run a genuinely successful parish digital project without paying anyone a penny for the thinking.
A closing thought
The failure was not a technology failure. It was a change failure.
And change, done well in a parish, is not harder than change done badly. It is just different. Slower. More human. More honouring. More durable.
It is the work. And it is available to any parish that is willing to slow down enough to do it.
This piece is part of the Pillar 3 series within the True Light Digital Formation framework. For the full cornerstone essay on which it is based, see truelight.digital/formation/invitation-and-patience/.