I have watched two versions of the same technology failure in Catholic institutions.

The first was a parish that bought a system that turned out to be too hard to use and did not actually fit the work. Someone had championed it. Someone had seen it demoed. The decision got made and the check got signed. Six months in, the business manager was running donor lists in a spreadsheet because the system took forty-five minutes to produce a report she needed in five. The $10,000 purchase was still on the books. Nobody was using it.

The second was a diocese that did everything right in the selection. They ran a real discovery process. They brought in stakeholders from parishes. They engaged people in the decision, demoed options together, negotiated with vendors as a group, and chose a system everyone had bought into. The implementation went in. The training happened. The system worked.

And then, slowly, it stopped working.

Not because the technology failed. Because next Tuesday there is a new parish secretary in a rural parish who has never heard of the system, does not know it is available to her, does not know why it was chosen, and does not know that the diocese already has the tool for her situation. She will spend her first six weeks either building her own workaround in Excel or searching for a different tool. Multiply that by a dozen staff transitions a year across the region, and the diocese's $150,000 investment and eighteen months of discovery slowly bleeds users faster than it can onboard them.

Two different failures, the same underlying mistake, in two different places on the timeline.

The first institution skipped the question before the system. The second institution answered it well and then failed to answer the question after the system.

Here is the question before the system. It turns out to have four parts:

1. Who are we trying to reach?

This needs to be a real, named set of people with real, named characteristics. Registered households. Lapsed Catholics in a specific zip code. Donors above a specific threshold. Volunteers in a specific ministry. Parents of sacramental prep students. The more specific the answers, the easier every subsequent decision becomes. Institutions that cannot answer this question concretely will choose systems that promise to reach everyone, which in practice means they are optimized for no one.

2. What do we need to know about them?

A CRM is a database of what you know about the people you are trying to reach. If you have not named what you need to know, you cannot design the database, and you certainly cannot choose software to hold it. Common answers include contact history, giving history, sacramental records, ministry involvement, household relationships, communication preferences. Less common but more useful answers include things like when did we last talk to this person about anything other than money and what did they say the last time we asked them what they needed. The specificity here determines whether the system becomes a working tool or a filing cabinet.

3. How will we engage them?

Email, mail, text, phone, in-person at Mass, through small-group ministries, through specific events. Each channel has its own operational implications - who sends, who writes, how often, with what authority. An institution that chooses a system before answering this question will discover six months later that the system supports a workflow nobody actually runs, while the workflow everyone actually runs has to happen in a parallel tool.

4. Who owns the data?

Not legally - operationally. Who is responsible for keeping the information in the system accurate, complete, and current? Who runs the deduplication process? Who closes out deceased parishioners? Who merges records when a family moves between parishes in the diocese? If the answer is "everyone" or "the system does it automatically," the data will degrade to unusable within eighteen months. If the answer is a specific person with authority, the system will stay healthy indefinitely.

Answer these four questions, and the system choice almost makes itself. Skip them, and no system will save you.

But here is where the diocese in the second scene comes back in.

Answering the four questions well is necessary. It is not sufficient. The institution that gets the four questions right and still fails - and I have seen several - fails on a fifth question that most institutions never think to ask.

5. Who owns this when the people who answered the first four have moved on?

Technology implementations in Catholic institutions are not just projects. They are permanent new operational realities. The parish secretary who starts next Tuesday needs onboarding into the system, into why it was chosen, and into the fact that her situation already has a tool. The new business manager in the next parish needs the same. The DRE who comes in after the current one leaves needs the same. Every single staff transition across the organization is a point at which the implementation can quietly erode, and most institutions have not assigned the ongoing work of catching it.

This is not a technology problem. It's a change-management-as-operational-discipline problem. The methodologies for sustaining a technology implementation across staff transitions are well-known in corporate contexts - some combination of onboarding checklists, named system owners at each location, periodic refresh training, ongoing feature and success messaging to stakeholders, and a feedback mechanism for people hitting friction. In most Catholic institutions, none of that exists after the implementation go-live. The project team disbands, the vendor transitions out, and the system is left to float on the assumption that whoever is in a seat will know what to do.

I spent eighteen years in enterprise consulting at Adobe, including leading up to 100-person and larger global teams doing exactly this work for companies that spend millions on their technology stacks. The companies that get sustained value from their technology are not the companies with the best systems. They are the companies that treat the implementation as a beginning, not a finish line. The ones that fail - and the ones that look exactly like the Catholic institutions I have been inside - are the ones that treat the go-live date as the end of the work.

This is stewardship - of the donor dollars that bought the system, of the staff hours that went into choosing it, of the parish secretary who starts next Tuesday and deserves to inherit a working tool, not a mess, of the institution's capacity to actually do its mission with the resources it has been given. Technology discipline is not a corporate skill being imposed on the Church. It is the specific application of stewardship to the systems that increasingly carry the Church's operational life.

Two more patterns are worth bringing up here as well:

The shadow system - the Excel sheet, the personal address book, the Google Doc that lives alongside the "official" system because the official system does not actually serve the work. More on that in a future essay.

The strategy-shaped-as-database - the institution that treats choosing a CRM as if it is the strategic decision, when the actual strategy was never named in the first place. That will also hit a future essay.

For now, the point is more simple. The question before the system is four questions. The question after the system is a fifth. The institutions that answer all five keep their systems working, and the ones that answer four and skip the fifth watch their investments slowly disappear.

Most institutions never think to ask the fifth. Which is why most institutions, two years into their expensive new system, are quietly back on spreadsheets.

In fieri. Ad alta.

If you want to see where your institution actually sits across mission, technology, and organizational effectiveness, Where You Stand is a free fifteen-question diagnostic. adaltaleadership.com/diagnostic

If your institution is in the middle of a system decision - or living with the consequences of one - and you want help naming what question actually needs answering first, an Hour with Michael is a focused way to start. adaltaleadership.com/hour