Today’s insurance companies need to respond quickly to market shifts and environmental changes. Pod-based engineering is a nimble solution.
Between intense market competition, rapid digital development cycles and the chaotic impacts of climate change, insurance carriers need to be nimble, rapidly adjusting their product offerings and messaging to better meet customer needs and maximize their profitability.
Yet insurance has historically been an extraordinarily siloed business. Underwriting, claims, finance and actuarial experts must all align on proposed changes to insurance products. Crossing those organizational boundaries to do something innovative and new can be impossibly time-consuming. To make matters worse, carriers are often working with somewhat outdated claims and policy systems, which further hamper innovation and speed. Data reporting structures are often broken, and feedback loops are long.
Pod-based engineering, a software development strategy centered on small cross-functional teams, can be a compelling method to overcome both organizational and technical hurdles in the insurance business, and rapidly accelerate the deployment cycle. In fact, it’s fair to say that the most effective way to truly ensure swift deployment in the insurance business is through pods.
Traditional engineering workflows function like assembly lines: One specialist at a time adds their contribution to the product, then passes it onto the next specialist. In the context of insurance, a product launch might require separate sign-offs from marketing, sales, underwriting, claims, actuarial and compliance. While product launches demand such a high degree of control for good reason, product performance can suffer as the same lengthy approval cycles slow down monitoring and enhancements, impacting the ultimate success of the product launch.
With pod-based engineering, small multi-disciplinary teams work together to quickly adjust small pieces of a product. Rather than developing a Version 2.0 sequentially and releasing it all at once, pod-based engineering allows cross-functional teams to tweak small elements of Version 1.0 one at a time, adopting the changes that add value and quickly reversing the changes that underperform until a much-improved Version 2.0 emerges. (Those familiar with scrum, full-stack, agile and shift left engineering will notice some distinct similarities to the pod-based approach.)


