The Shadow System

Every Catholic institution I have worked in or with has a shadow system.

The business manager's Excel sheet of major donors, carefully maintained for years, because the official CRM takes forty-five minutes to produce the view she needs for the pastor's Monday morning meeting... The DRE's personal address book of catechist contacts, kept because the parish management system makes it hard to search by anything other than registered household... The development director's handwritten index cards tracking each major donor family - the kids' names, which parent died when, what they say about the parish at the Christmas party - because the CRM has fields for giving history but no good place for the relational texture that is actually most of the work.

These are shadow systems. The Excel sheet, the personal address book, the Google Doc, the file cabinet, the stack of index cards - any system a staff member has built to hold the information the official system was supposed to hold, because the official system does not actually serve the work.

Most Catholic institutions treat the shadow system as a problem to eliminate.

The IT or tech team instinct says: consolidate everything into the official system, kill the shadow, standardize the data, enforce single-source-of-truth. The audit instinct says: shadow systems are a compliance risk, a data-protection risk, a continuity risk if the staff member leaves. The standardization instinct says: if everyone is doing their own thing, we have no visibility and no governance.

All three of those instincts are coming from a reasonable and important place. All three of them are usually wrong, in the specific way they get applied.

The shadow system is not a bug - It is the organization showing you where the real work is.

The business manager isn't maintaining the Excel sheet because she's resistant to the CRM. She's maintaining it because the CRM cannot do the thing she needs to do every Monday morning. The DRE isn't keeping a personal address book because she doesn't understand the parish management system. She's keeping it because the system was designed for sacramental records and household data, not for the relational, catechist formation work she's responsible for. The development director isn't tracking donors on index cards because he's old-school. He's doing it because the CRM has no good place to hold what actually matters in the donor relationship - the lived, pastoral texture of knowing these families over years.

Every shadow system in your institution is a staff member telling you, as clearly as they can without saying it out loud: The official system does not actually fit what I am being asked to do.

The right response to a shadow system is not elimination, it's investigation. Three questions.

1. What work is this shadow system actually doing?

Sit with the business manager and watch her Monday morning. What does she pull out of the Excel sheet? What question is she answering for the pastor? What does the pastor do with that answer? The shadow system is doing specific, important work. Name it. The work itself is the thing you're trying to understand, not the shadow.

2. Can the official system be configured to do that work?

Sometimes yes. The CRM might have the capability but no one ever built the view. The parish management system might have the search functionality but it's buried four menus deep. If the answer is yes, the move is clear: build the view, surface the functionality, train the staff member on how to get what she needs out of the official system. Then the shadow dissolves naturally, because it isn't needed anymore. Not because you killed it.

3. If the official system genuinely can't do that work, should the shadow system be formalized?

Sometimes the official system was never going to do what the staff member actually needs. The CRM wasn't designed for the relational texture of major-donor work. The parish management system wasn't designed for the catechist pipeline. In these cases, the shadow system isn't a workaround to be eliminated - it is a legitimate second system doing legitimate second work, and the institution's job is to formalize it. Give it a real tool (even if that tool is a well-designed spreadsheet shared on the parish server with proper backup and access controls). Document what it holds. Make sure someone else on the team knows how to use it when the staff member who built it is out. Treat it as a real system, because it is one.

What never works is attempting to eliminate the shadow system without doing one of those two things. Because the work the shadow system was doing doesn't go away just because you eliminated the approach. The staff member either goes underground with it (now the Excel sheet is on her personal laptop and the institution has worse data security than before), or she stops doing the work entirely (now the pastor doesn't get the Monday morning briefing and the development director loses the relational texture that was holding donor relationships together).

The institution ends up with worse data, worse mission execution, and a frustrated staff member who correctly reads the elimination of their shadow system as the institution not actually understanding what their work is.

This connects back to a Technology essay from a few weeks ago: The question before the system. In that essay I named four questions institutions need to answer before choosing a CRM or a database - who are we trying to reach, what do we need to know about them, how will we engage them, who owns the data. The shadow system is often direct evidence that those four questions were never answered, or were answered incompletely. The staff member built the shadow because the official system was configured for a different mission than the one she's actually being asked to execute.

Which means the shadow system is one of the most useful diagnostic tools you have. It tells you, with no filter and no political pressure, exactly where the official system failed to serve the actual work. Every shadow system in your institution is a free consulting engagement, if you're willing to treat it as information rather than as a problem.

This pattern isn't unique to Catholic institutions. Every mission-driven organization I've been in has shadow systems - nonprofits, foundations, family-held businesses, even enterprise technology teams. The reasons are the same. The dynamics are the same. The usual response - "eliminate the shadow" - is the same wrong instinct everywhere.

This is stewardship - of the staff member who built the shadow because she needed to do her job well, of the information the shadow system holds (which is often the most mission-critical information the institution has), and of the institution's capacity to actually understand its own work. Treating a shadow system as a problem to be eliminated is a form of institutional disrespect. It tells the staff member that her understanding of what the work actually requires matters less than the institution's attachment to the system it bought.

Treating the shadow system as an artifact to be understood - and sometimes formalized - is a form of respect for the person, for the work, and for the mission the system was supposed to serve in the first place.

After seeing this pattern across dozens of Catholic institutions and three decades of corporate ones, I keep coming back to this point:

The shadow system is the most honest artifact your institution produces. It shows you, with no filter, where the mission actually lives.

Everything else - the strategic plan, the mission statement on the website, the CRM dashboards the leadership team reviews quarterly - all of that is what the institution says about itself. The shadow system is what the institution actually does, revealed in the Excel sheet of major donors or the handwritten index cards or the Google Doc of catechist contacts that nobody in IT knows exists.

If you want to understand your institution's real operational life, don't start with the strategic plan. Start with the shadow systems.
In fieri. Ad alta.

Deacon Michael Halbrook

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 you have a shadow system in your institution and you want help understanding what it's telling you - whether to formalize it, build the official system around it, or something else - an Hour with Michael is a focused way to start. adaltaleadership.com/hour

Know a leader at an organization - a parish, diocese, foundation, Catholic school, or another Catholic organization - who should read this? Forward it to them.