Lately I have been reading a lot of articles on Return on Investment for projects in Sales and Information Technology. More often than not these techniques describe ways on how to implement or adapt new technologies, methodologies and ways of working.
A question that comes to my mind when I am wrapping my head around it is whether or not there was actually a real need for it. Has anybody in the situation asked: “Is this investment even worth it?”
New and more isn’t always better
After my initial response: “of course, anything is possible” I made sure to also ask about the core purpose of the API, and after some discussion it became clear that it would have been a complete waste of money.
What you need to know is that an API for this kind of system would have resulted in expenses of up to 5 figures, it would have been even harder to find the relevant information for all parties and it would have only created an overflow of information for a work-group who’s people are only involved minimally in the process of our target department. Sure, connection and communication is key. But so is correct filtering of data that is redundant for certain employees.
Consult with Result
In the course of fact finding we narrowed down the necessary information that should have been delivered by the API from one system to the other, omitted its significance for later use, and developed a very short but effective process that helped their people to communicate the necessary information in a different way. A quick set-up in the reporting structure of their CRM system with a dedicated delivery time made it possible for this company to 1) enhance their information flow and communication, and 2) save them tens of thousands on an implementation that only would have made things worse.
Generally you should always ask yourself and also your customers a question that is usually a little frowned-upon, but extremely necessary: “Why?” Digital Touchpoints in between systems can be very helpful in most cases. However, if the task that needs to be carried out is so small that the new technology itself is worth more than the saved workload, consider that designing a short process instead could be much more effective in the long run.
Co-Founder & Director Information Services