For me, 65 miles per hour is fast and so is jogging, but you could swim as fast as you like and I’d still tell you you’re slow – I’m pretty good.
For me, what’s important is the ‘definition of fast’ in the user’s eyes.
For a recruitment CRM to be fast, we need to take into account a number of things.
- What are the users allowed to see?
- What permissions do they have?
- What workflow do they need?
- What database are they looking at?
OK, so now ‘fast’ also sounds complicated, but it doesn’t need to be with Voyager.
Let me give you an example.
Voyager Professional was one of the first windows based applications in the market, I was selling it at a time when fax machines were still popular….
OK, so the much-loved and widely used recruitment CRM is now a bit dated, and whilst customers can still upgrade to Voyager Infinity as part of their contract, everyone agreed that Professional was fast – really fast, and we needed to retain that with the newer versions too.
Looking up a record on Voyager Professional was so fast it was almost instant. Input ‘Smith’ and the candidate results literally appeared as you typed the letters.
What customers overlooked was that it only looked at a very small subset of data. It looked at ‘Candidates’ or ‘Clients’ and not both. Users also overlooked the huge amount of time they spent adding CV’s manually to the database, and posting the jobs on job-boards that generated them in the first place. The world has changed a lot since then.
Our newer, shinier solution Voyager Infinity is light-years ahead of the first Voyager solution, and still people are asking for ‘faster’.
If you feel your recruitment CRM provider doesn’t understand what you mean when you tell them it’s slow, then feel free to drop us a line for a chat.
Maybe your ‘fast’ is my slow.
Blog written by Paul.Thompson@VoyagerSoftware.com