Woman writing on board

Transformation @ Work

Episode 34: The Ripple Effect: How Data Architecture Decisions Permeate Across Your Organization

Woman writing on boardTransformation at Work podcast backgroundtransformation at work icons on dark grey

Transformation @ Work

Episode 34: The Ripple Effect: How Data Architecture Decisions Permeate Across Your Organization

Woman writing on boardTransformation at Work podcast background

Transformation @ Work

Episode 34: The Ripple Effect: How Data Architecture Decisions Permeate Across Your Organization

Dan Waldner

Vice President of Financial Services
Gerent

Dan brings years of technology to his current role at Gerent, with over half of that time spent in the Financial Services. In his previous role, he owned Salesforce for the enterprise, running a total of four organizations, and 5K+ users in 16 countries. That hands-on experience gives him profound insights into how Financial Services institutions can meaningfully adopt and utilize Salesforce to transform day-to-day operations.

Shane Hayes

Product Lead, Financial Services
Gerent

Shane brings almost 30 years of experience in technology, and 12 years in the Salesforce ecosystem, to his current role at Gerent. He has a particular passion for solutioning and architecture, as well as for helping to deliver and deploy the Salesforce infrastructure that businesses need to thrive.

No decision within a financial institution happens in a vacuum. Even the smallest change can potentially ripple out and impact other arms of the organization, for good or for ill. This is doubly true for your average banking institution, where dozens, or even upwards of a hundred disparate systems and data models are used daily to manage data. All it takes is one disruption in the complex spider-web of systems to cause major pain points, compromised data, and potential disaster. This makes careful planning especially crucial during Salesforce implementation: team leaders need to be aware of the ways in which changing one system may impact the broader institution as a whole.

No decision within a financial institution happens in a vacuum. Even the smallest change can potentially ripple out and impact other arms of the organization, for good or for ill. This is doubly true for your average banking institution, where dozens, or even upwards of a hundred disparate systems and data models are used daily to manage data. All it takes is one disruption in the complex spider-web of systems to cause major pain points, compromised data, and potential disaster. This makes careful planning especially crucial during Salesforce implementation: team leaders need to be aware of the ways in which changing one system may impact the broader institution as a whole.

In this episode of Transformation @ Work, we look at how a strategic approach to Salesforce deployment can help team leaders reimagine their data flows and create more cohesive data architecture for their organization.

Key Insights

03:00: Examining the current state of data architecture within financial institutions: a “spider-web” of interconnected data models and systems

05:12: The potential pitfalls that come with making changes in a highly interconnected data structure

09:38: How early data architecture decisions can snowball over time into substantial tech debt

13:47: Reimagining the data architecture within an institution to better address the needs of employees and members

17:29: How working with an experienced technology partner can help team leaders built more efficient data architectures

green background

Ready to reinvent the future?
Let’s chat!

Get Started
green background

Want to get involved?

More episodes

More episodes

Follow Us