EUCs Are Part of How Banks Actually Work

EUCs Are Part of How Banks Actually Work

ARTICLE

EUCs Are Part of How Banks work

EUCs in banking persist because core platforms rarely keep up with how work actually moves. The banks that manage this well aren't trying to eliminate these tools; they're learning to govern them.

By Dami O. | 06/14/26

End User Computing Tools fill the gaps

In banking circles, End User Computing tools or EUCs are often framed as a risk to eliminate rather than a reality to manage. Spreadsheets, Access databases, Power Apps, and local scripts are typically grouped under “EUC risk,” discussed through remediation plans, inventories, and controls. The implied assumption is that with enough discipline, EUCs would not exist. That framing misses the real reason they persist.

Banks are complex environments where data moves across desks, systems, and regulatory expectations that change faster than core platforms can adapt. When practitioners need answers quickly, they build practical solutions to fill the gaps formal systems leave behind. That is how EUCs emerge. Not as workarounds born of negligence, but as necessary tools tied directly to how work gets done. Pretending these tools should not exist does not reduce risk. It pushes critical activity into places leadership cannot see or support.

What I saw working with GSIBs

My own perspective on this comes from working with GSIBs addressing MRIAs. In that context, EUCs were not fringe tools. They were central.

Teams responsible for data lineage, controls, and regulatory responses were expected to answer detailed questions quickly and accurately. In practice, the official tools often fell short. Vendor data governance platforms lacked the flexibility, interdependency views, or real‑time feedback practitioners needed. Internal tools were rigid, slow to adapt, or simply didn’t model the work as it was actually done.

The most valuable contributions I often made came from buildingwell governed EUCs

These were not wild spreadsheets passed around by email. They were structured, controlled tools. Inputs validated row by row in real time. Clear ownership. Traceable logic. Explicit links to upstream data. Practitioners could move fast and with confidence.

Why forcing everything into tools doesn’t work

A common response to EUC risk is to mandate usage of centralized platforms. In theory, this sounds reasonable. In practice, it often fails.

When tools don’t reflect how people actually work, they create friction. Practitioners still need to do the work, so they rebuild the missing pieces elsewhere. Now the risk hasn’t gone away, it’s just gone dark.

3rd party vendor platforms often assume a world where definitions are settled, workflows are linear, and change is rare.

The environments responding to regulatory findings don’t look like that. They need flexibility, iteration, and speed.

A better way to think about EUCs

The more effective banks we’ve worked with don’t ask how to eliminate EUCs. They ask how to govern them intelligently. That starts by accepting a few realities. Some EUCs are exploratory and low risk. Others are material and deserve tighter controls. Not everything needs enterprise‑grade engineering, but important things need more than good intentions.

Governance becomes practical when EUCs consume data from authorized sources, rather than defining truth themselves. When transformations live upstream and EUCs focus on inspection, analysis, and decision support. When ownership is explicit and lineage is traceable. In that model, EUCs stop being uncontrolled systems and start being governed interfaces.

The role companies like ours play

This is where firms like ours fit naturally. We don’t approach EUCs as something to stamp out or blindly rebuild. We approach them as artifacts of real work. They tell us where official systems fall short and where value is actually created. Our role is to help banks put structure around that reality. To turn fragile EUCs into governed ones. To decide what should stay flexible, what needs guardrails, and what truly belongs in a more durable architecture.

In many cases, the fastest, safest path forward isn’t a rewrite. It’s strengthening what already works, while reducing key‑person risk and improving traceability. That mindset has served our banking clients well, especially in the context of regulatory scrutiny. Not because it ignores risk, but because it addresses it where it actually lives.

EUCs reflect real work in banking

Govern them thoughtfully to reduce risk

Where accuracy matters most
that's where we work

We work anywhere documents carry risk, financial impact, or compliance requirements.

What you're probably
wondering

Quick answers to the most common questions

What are End User Computing (EUC) tools in banking?

End User Computing tools in banking include spreadsheets, Access databases, Power Apps, local scripts, and similar tools built by practitioners to do their work. They emerge when core systems cannot adapt quickly enough to changing regulatory requirements, data questions, or operational needs. EUCs exist because banks are complex and work still has to get done.

Why do EUC tools persist despite bank governance and risk controls?

EUC tools persist because they fill real gaps left by enterprise platforms and vendor systems. When official tools are rigid, slow to change, or poorly aligned with how work actually happens, teams create practical solutions to meet deadlines and regulatory expectations. Treating EUCs as something to eliminate often drives activity underground rather than reducing risk.

How can banks reduce EUC risk without eliminating flexibility?

Banks reduce EUC risk by governing EUCs intelligently instead of trying to remove them. This means sourcing data from authorized systems, keeping transformations upstream, defining clear ownership, and ensuring traceability. When EUCs are used for analysis and decision support rather than as sources of truth, banks maintain speed and flexibility while improving control and regulatory confidence.

Governing EUCs Without Disrupting How Banks Work

Governing EUCs Without Disrupting How Banks Work

ARTICLE

Governing EUCs without disrupting how banks work

Learn how governing EUCs effectively means building guardrails that work with how banks actually operate, not against it. Flexibility and control are not mutually exclusive, and the best EUC strategies treat them that way.

By Dami O. | 06/14/26

Govern EUCs with Flexibility

Once you accept that End User Computing tools are part of how banks actually work, the next question becomes more interesting. How do you govern them without removing the flexibility that made them necessary in the first place?

This is where many EUC conversations stall. The default response is usually control through restriction. Lock down access. Centralize everything. Force usage of a single platform. On paper, it sounds clean. In practice, it rarely holds. A better approach to governing EUcs starts by rethinking what EUCs are allowed to be.

EUCs are not systems of record

One of the most useful shifts we’ve seen is separating where truth is defined from where work happens.

EUCs should not define authoritative data. They should not be the place where core business logic quietly lives. That role belongs upstream, in governed data platforms.

EUCs are often the most effective effective interface for analysis, validation, and decision‑making.

That duality is not a contradiction, it’s a design opportunity.

The Lakehouse as an authorized redistributor

Modern Lakehouse architectures make this separation easier than it used to be. When a Lakehouse is treated as the system of record, its role doesn’t end with storage. It becomes the authorized redistributor of curated data products.

Instead of allowing EUCs to pull arbitrary tables or rebuild logic independently, teams consume certified datasets. Clear grain. Defined metrics. Documented ownership. Versioned outputs.

This matters from a governance perspective. You can trace where data came from without needing to police every spreadsheet formula.

An EUC becomes a governed consumer rather than an uncontrolled source.

Importantly, this doesn’t mean users need to query the Lakehouse directly or abandon their tools. It means the Lakehouse establishes boundaries that EUCs operate within.

Guardrails don’t have to slow people down

One reason EUC controls fail is that they’re implemented as barriers instead of channels. Blocking Excel access or forcing complex tooling on unready teams doesn’t eliminate EUCs. It just makes them harder to see.

We’ve seen better outcomes when banks provide sanctioned ways to consume data. Approved connectors. Reusable templates. Clear guidance on what’s acceptable and what isn’t.

Power Apps that read from curated APIs instead of SharePoint lists standing in for databases.

Excel models wired to certified datasets. Power BI semantic models backed by Lakehouse data. When the approved path is easier than the unofficial one, behavior changes without enforcement.

Proportional governance actually works

Not all EUCs deserve the same level of scrutiny. Banks that govern EUCs effectively do so proportionally. Low‑risk, exploratory tools stay light. Material EUCs that support regulatory reporting, risk metrics, or controls get stronger oversight.

That oversight doesn’t have to look like a full SDLC

It usually means clear ownership, documented intent, versioning discipline, and lineage back to trusted inputs. The key is that decisions are based on impact, not on the existence of an EUC itself.

Where this breaks down

Problems emerge when EUCs are expected to either disappear or behave like enterprise applications. Neither expectation is realistic.

EUCs struggle when they’re asked to scale endlessly. SharePoint starts acting like a database. Logic becomes tangled. Performance degrades. At that point, the EUC has done its job. It has shown where the work actually lives.

The mistake is treating that moment as failure instead of a signal. That’s when a workflow transitions into a more durable architecture, not because policy demands it, but because the reality of use does

The role companies like ours play

This perspective shapes how we work with banking clients. We don’t start EUC conversations with a mandate to rebuild. We start by understanding how practitioners are actually working today and what those tools are already telling us.

Which EUCs are exploration layers on top of trusted data. Which ones are compensating for missing functionality. Which ones have outgrown their original purpose. From there, we help banks decide what needs structure, what needs guardrails, and what needs to move upstream. Often, the most effective path is strengthening the boundary between the Lakehouse and the EUC, not eliminating the EUC itself.

That was especially true in the context of regulatory findings. Well‑governed EUCs made lineage clearer, remediation faster, and practitioner confidence higher than forcing everything into rigid platforms that didn’t reflect the work.

Realistic EUC governance for modern banks

Control risk without slowing down work

Where accuracy matters most
that's where we work

We work anywhere documents carry risk, financial impact, or compliance requirements.

What you're probably
wondering

Quick answers to the most common questions

How can banks govern EUCs without limiting flexibility?

Banks can govern End User Computing tools by separating where data is defined from where work happens. Core data and business logic should live in governed platforms, while EUCs are used for analysis, validation, and decision-making. This approach preserves flexibility while reducing risk, instead of relying on restrictive controls that slow teams down or push work underground.

What role does a Lakehouse play in EUC governance?

A Lakehouse acts as the system of record and the authorized redistributor of trusted data. EUCs consume certified datasets with clear definitions, ownership, and lineage rather than rebuilding logic independently. This makes EUCs governed consumers of data instead of uncontrolled sources, improving traceability without forcing users to abandon familiar tools.

What does proportional EUC governance look like in practice?

Proportional EUC governance applies oversight based on impact, not on the mere existence of an EUC. Low-risk, exploratory tools remain lightweight. Material EUCs that support regulatory reporting, risk metrics, or controls receive stronger guardrails such as clear ownership, documented intent, versioning, and lineage. This keeps governance practical and aligned with how banks actually work.