In the race to modernize, many insurers have found their progress slowed by the size, scale and scope of large transformation programs. From core systems to data warehouses, and from cloud platforms t...
The path forward is clear: embrace and implement architectures that reinforce Agile principals and create a much better foundation for a dynamic enterprise of the future. Part 1 of this series disc...
An organization can never become truly Agile until it creates an overall enterprise architecture that is specifically designed to be Agile. “Any organization that designs a system (defined more bro...
It’s an old lament. While creating an enterprise or application architecture is great for a conceptual understanding of something, it would be even greater if that architecture could be used directly ...
Open source libraries, once shunned as risky and not ready for prime time, are now used extensively across major corporations, including insurers. The reason is simple: In time- and resource-constrain...
In the modern computer era of the last several decades, industries including auto, banking, and, of course, insurance have developed and re-developed their core processing systems many times over. Tha...
Many insurers may not be able to adopt blockchain in time to retain a competitive advantage, so it’s imperative that every company has a blockchain game plan—and the sooner, the better. If you’re a...
For technology employers, the recruiting game is fierce, especially for smaller firms that compete with industry giants such as IBM, Google, Amazon, Microsoft, Accenture and Cisco. How do smaller cont...
This article serves as a primer for identifying the different types of consulting companies out there, and how to find the best consulting fit. (Photo credit: D-M Commons.) Like the Swiss army knives,...
Most insurers have a business technology ecosystem that has grown and advanced over years and decades. These are combinations of older and newer systems, legacy and modern data stores, and integration...
Technical Debt—also known as Design Debt or Code Debt—is a concept in software development that reflects the implied cost of additional rework caused by choosing an easy solution now instead of using ...
In Part One of this series, the focus was on the advantages and disadvantages of creating a separate and distinct team for any project’s integration work, as opposed to having integration work as part...
