We probably need to change the way we select our PV database systems. You also do not go buying a car with a home drawn blueprint in your hand. It is impossible to expect from the business users to have to describe a PV application’s all much needed functionality in its totality from scratch on their own. You also do not start describing a car by having four wheels, a steering wheel, an engine, and a chassis and then break it down to details. You kind of assume that the leading car manufacturers do know what a car needs to entail and are able to deliver the bundle of functionality you need from it.
You could though check some references of the car manufacturers you are looking at, what quality certifications they have, see how their cars are authorized for sale, check their crash tests, read some reviews from professional testers, or simply browse some blogs to see what people think of the companies and their products. But do you do this? Most probably not. You rely on the common understanding which brands are considered to be decent mid-range manufacturers and you trust them as long as they are legally represented in your country.
But will you be able to stand up to the question did you evaluate this or that critical functionality of the product during the evaluation to make sure it meets all your requirements? Have you checked the Follow-Up features for example to see if they can really schedule your three attempts and fire your targeted questionnaires appropriately so that your FU is end-to-end automated and handled within the system? You could have tried. You could have compiled a long list of questions and could have spent hours in demos and reviewing vendor responses to figure out if the FU features are 100% mature and are going to work for you. But what is with the other 300 important elements of your PV database application?
You will take your PV system candidate for a spin though. A vendor demo environment will be your showroom car and the short road trip nearby the dealership will give you a pretty good impression how the cars feels to drive, how it handles and you will be able to try out and see many of the key features of the vehicle on the road. You will be able for example to turn on the lane, distance and speed limit assistant, but you will not be able to definitely say if the drive assistance functions will be truly comfortable in all aspects over a multi-thousand-kilometre-long ride as well.
Like with a car dealer the vendor demo and sales team will have a time window for you. The dealership closes at five and you will not be really able to spend unlimited time with an unlimited list of questions which the dealer him/herself might not be able to answer at all. It is not polite to interrogate, there is a common-sense level of detail of your interest which can be catered at the dealership in a standard sales process. Very similar to how your vendors will work, regardless how wicked your procurement process might be.
And what you also do not do when buying a car is look at the manufacturer’s development roadmap. It would probably not even be disclosed to you even if you specifically asked for. The firms use their innovative plans in messaging and raising brand awareness. They might build and take concept cars to car shows, but these plans are usually not discussed in the sales process at your local dealership. The purchase is based on what the car can do here and now. You rarely even factor in the amount of innovation that should be coming in the vehicle line of your choice when signing the deal.
- I like this feature, is it already available or coming?
- It is available.
- In the version we are going to go live with?
- No, in one of the upcoming ones.
- So, it is coming.
- It is on our roadmap.
- So, when will it be available?
- Let me discuss with our product team and get back to you on this.
If the above discussion is familiar to you, you might have been part of a selection and procurement process of an IT tool for your Pharmacovigilance function. Come on, you cannot base your decision on the uncertainly around all the innovative new features. You will not be able to get time guarantees on when these will arrive in the upcoming product versions. Even less will you be able to assure that they will be delivered in a mature state or even truly get to know their current capabilities.
Even vendors are neurotic about these situations when their true innovative roadmap is being scrutinized. They fear all other merits of their tools and offerings will be disregarded and innovative automation will be the number one deal breaker in the heavy competition of the leading vendors, who are very different as companies and have very different approaches to the product development as well as to innovation itself.
So, unless you need to buy something really cheap, and a mid-range car is usually not that cheap, the choice becomes very preferential. You need to look at your history you have with the brand, your previous experience and all what you know about their cars. You need to ask yourself the questions, do I like their products and approaches generally or am I up for something new. A good old German brand will not compare to a Tesla. You will have tradition and legacy with moderate pace of innovation, while on the other hand you are sitting into something you are not yet very comfortable with. Will you reach your destination in both options? Yes. Will the ride be different? Yes, but it is about your liking.
Do not be married to your current vendor though, always ask the question: Will my life be better in another car from a different manufacturer? Does it matter if they have a traditional dealership nearby, where I know the guy, who sold me my past few cars already? Do you trust new millennial brands with their different approaches and claiming to break the status quo or you want legacy, and cosy conservatism? And if you say new ways are nice but let them grow and mature remember you can still give your current brand another go and keep assessing the ambitious newbies and be ready to switch over in 3-5 years.
As the history of long un-touched on-premise PV systems fades in our memory we also need to perceive our data in the relevance of here and now. As migrating between systems of different data structures have become very common, and with the transaction-based SaaS Cloud model vendors have set the scene for a dynamic customer strategy. That means that unless you are tired of being continuously in “project implementation mode” you could theoretically be continuously evaluating the competing systems and switching in-between platforms as frequently as in every 2 years to keep getting the maximum benefit out the offering financially and functionality wise.
Maybe it is the beginning of a new era, which might also force vendors to focus on their offerings, to sell current capabilities and not worry about losing a client so much, because a good brand will reattract customers even if they have set out to drive other cars for a few years.