New legislation affirms the governance and security responsibilities of all organizations doing business in the EU.

Today’s AI may be able to pass the Turing test, but I think we can all agree that doesn’t make it human. AI is a tool—a powerful one, but a tool nonetheless. And just like any tool, it can make our work easier, but it can’t do it for us.

Working with large volumes of data requires effective data management practices and tools, and two of the frequently used processes are data ingestion and ETL. Given the similarities between these two processes, non-technical people seek to understand what makes them different, often using search queries like “data ingestion vs ETL”.

If you have a legacy system with customized capabilities and valuable features but nearing end of life, refactoring the system is a potential choice for modernization. Insurance platform modernization usually involves one-to-one code migration, which can often be more costly and time consuming than expected and typically tends to miss some of the integration and data architecture modernization that is foundational for getting the full value of digitization.

My first attempt to understand accessibility and how to test it started back in 2016. I was working for a company where accessibility was already an important part of the process. I was asked to perform accessibility testing on the product to determine whether we could claim to be accessible. Since it was a new subject for me, I was quite confused. Where should I start? Should I be certified to provide a proper assessment? Do I need to request assessments from third-party companies?

We tested a product-led go-to-market motion last year. Here are the exciting results and learnings.

What is hyperautomation for insurance? It might sound like just another buzzword, but let’s peel back the layers to see how hyperautomation works. Imagine this: you go on a deep dive to evaluate your insurance company’s processes and operational models. You discover inefficiencies, lag times, and that your team manages transactions with disparate, often manual processes. It’s clear you need a new solution. And the solution you need doesn’t currently exist.