I've been working at a SaaS startup of about 50 employees, and I'm the only data professional. This is a company that experienced rapid growth in recent years, but has relied heavily on ORMs in software development, and sees data as a byproduct of its software.
The design of the data model in the RDBMS has been largely driven by application/technology needs, rather than business needs.
I've been trying to introduce business-driven data architecture, which involves normalizing our relational data models, but in order for an object-oriented application to work with such, it would require that it accesses our data only through the database's external layer (views, functions, procedures, etc).
There have been concerns in the organization that, if we were to implement this layer, I'd be the only person able to maintain it, thus creating a knowledge silo.
While I can understand that argument, I don't see how we're going to achieve our goals with highly denormalized, tech-driven data models on an RDBMS.
Has anybody had similar experiences that you could share, and how you've handled them?