Why using new technology does not need to blow your mind or your budget
If you have ever moved between two systems, like a CRM or AMS, you know firsthand how complicated the switch can be. But using new technology does not need to make your head spin or your wallet groan. In this article, we will walk you through three ways to adopt technology using the KISS (‘Keep It Simple Stupid’) standard to make your next technological adoption simpler and start generating value from it faster. When you are ready to supercharge your sales team, make sure to check out 'The Ultimate Guide of Building a Tech-enabled Sales Team' to get started.
The KISS Methodology
KISS, an acronym for keeping it simple, stupid, is a design principle noted by the U.S. Navy in 1960. The KISS principle states that most systems work best if they are kept simple rather than made complicated; therefore, simplicity should be a key goal in design, and we should avoid unnecessary complexity. We have associated the phrase with aircraft engineer Kelly Johnson. The term "KISS principle" was in popular use by 1970. Variations on the phrase include: "Keep it simple, silly", "keep it short and simple", "keep it simple and straightforward”, "keep it small and simple", "keep it simple, soldier", "keep it simple, sailor", or "keep it sweet and simple".
The KISS method also works when buying new software. We broke down how to do that in this article.
Applying KISS to Technology
- Application Program Interfaces (APIs) are the gold standard for connectivity between two separate pieces of software. But if you have ever used software that was originally built before 2015, chances are it does not have an open API to connect to other systems. So what is one to do? The best option may be to choose a simpler integration route and leave the complexity of completing an API integration down the road. Yes, that is right. If you want to make adopting software streamlined, you may need to ignore APIs. The trade-off is a bit more manual work, but you can reap big dividends immediately without requiring a one-off or custom integration.
- Using your data can be as simple as exporting it in a report out of your main software and into other systems as necessary. You can look to build custom reports which will send a .csv file full of information to your inbox regularly, streamlining this. This is a great way to work with insurtechs during pilots and keep the complexity low. Chances are, any information you need to get back into your primary system can easily be imported.
- Before APIs came batch file transfers. This older version of APIs allows you to transfer entire files of information (such as a whole excel spreadsheet at once) between two systems automatically. If you are working in an older - dare we say legacy - software, you may move information between your systems this way. Using a batch file method will often rely on a Secure File Transfer Protocol (SFTP) site, such as SharePoint or Dropbox as an intermediary. Getting up and running on an SFTP site is easy and chances are you already have one in place. This commonly used way of exporting and importing information between two systems is a great way to get your next pilot or implementation up and running.
The Brick Wall Rule
If you are evaluating a project or a pilot and the barriers to using your data seem insurmountable, it can feel like beating your head against a wall. If you have ever been involved in a project around your AMS or CRM, then you know this firsthand. The next time you feel this strange and familiar sensation, take a step back and consider other options to get your data flowing between different systems. Because keeping it simple will prove to be your best friend time and time again.
