Redundant applications get a bad rap. Between wasted spend, low adoption, and operational inefficiencies, you’d think eliminating all redundancies would be the answer. Think again. In this episode, Ben Pippenger explains when application redundancy may be ok, factors to consider in your strategy, and best practices to consolidate your software.

Have a question you’d like answered on SaaSMe Anything? Submit yours here.

Key Takeaways

[00:08 - 01:08] Introduction, Ben has a lot of streaming subscriptions, addressing redundancy
[01:11 - 01:47] What is application redundancy, and what are the biggest culprits?
[01:47 - 02:22] Why is app redundancy so prevalent?
[02:22 - 03:05] The difficulties of resolving redundancies
[03:04 - 03:36] Determining the right amount of redundancy for your organization
[03:36 - 04:33] Considerations for tackling organization redundancy, the scope of the problem
[04:33 - 05:04] Features and functionality, app preferences and favoritisms
[05:29 - 06:04] Steps to rationalize the redundant apps in your stack
[06:04 - 06:18] Understanding app value and their ROI and importance to business objectives
[06:18 - 06:42] Anecdotal data and feedback about apps from end users
[06:40 - 07:03] Identify what you can eliminate, consolidate, and replace
[07:03 - 07:20] Utilization usage rates in understanding what to remove
[07:18 - 07:47] The big takeaway on redundancy

SaaSMe Anything is the bi-weekly podcast that brings clarity to the chaos of SaaS, hosted by your resident SaaS expert and Zylo co-founder Ben Pippenger. Connect with Ben on LinkedIn here.

How Much Application Redundancy Is Ok?

SaaSMe Unfiltered: The SaaS Management Podcast