Hi,
I just purchased Maximizer 9 for my recruiting business. Before I jump in and start adding info, would appreciate any startup advice, suggestions etc..
Thanks
Original Post
Replies sorted oldest to newest
1) Read the manual to get an idea of what you can do
2) Document your business processes at a very high level - do a scenario for recruiting step by step, just a couple of words or a single sentence for each; This is likely to result in less than 10 high level steps
3) Detail your business processes - list each sub-step for each of the high level steps in #2
4) Map your business processes to Max capabilities (this will drive UDF setup, Preferences settings, etc.)
5) Build a test database and enter a few records of each type (3-5 maximum)
6) Run a conference room pilot walking through each business proces from beginning to end
7) Document results, make required changes to Max, then enter lots of data and go live!
Max is extremely flexible. I don't know your level of experience with these types of systems and to you this may be Systems 101 and simple common sense. But based on my own experience doing this in advance, while Systems 101, is really beneficial.
- R
2) Document your business processes at a very high level - do a scenario for recruiting step by step, just a couple of words or a single sentence for each; This is likely to result in less than 10 high level steps
3) Detail your business processes - list each sub-step for each of the high level steps in #2
4) Map your business processes to Max capabilities (this will drive UDF setup, Preferences settings, etc.)
5) Build a test database and enter a few records of each type (3-5 maximum)
6) Run a conference room pilot walking through each business proces from beginning to end
7) Document results, make required changes to Max, then enter lots of data and go live!
Max is extremely flexible. I don't know your level of experience with these types of systems and to you this may be Systems 101 and simple common sense. But based on my own experience doing this in advance, while Systems 101, is really beneficial.
- R
Thanks Rooster. You are quite right and I will apply the process. I have been through several technology implementations in a previous life. Of course, I forget to apply the good points to myself..
As part of planning a couple areas are not clear ( I read the manual once so far). How many address books should I plan or can I structure one address book with multiple views ( candidate, customer...supplier.) Is there a group function at this level? . Is this a related entry?..
Here I go...
As part of planning a couple areas are not clear ( I read the manual once so far). How many address books should I plan or can I structure one address book with multiple views ( candidate, customer...supplier.) Is there a group function at this level? . Is this a related entry?..
Here I go...
>How many address books should I plan
Start with one. If, down the road, you find that you *really* need to split it into multiple address books you can do that and it is much easier than consolidating multiple address books into one.
>or can I structure one address book with multiple views ( candidate,
>customer...supplier.)
Maximizer address book entries include a system-defined field called "Category" specifically for that purpose.
>Is there a group function at this level?
"Category" can be searched on, sorted on, included in column setups (and hence column reports), etc., etc.
Start with one. If, down the road, you find that you *really* need to split it into multiple address books you can do that and it is much easier than consolidating multiple address books into one.
>or can I structure one address book with multiple views ( candidate,
>customer...supplier.)
Maximizer address book entries include a system-defined field called "Category" specifically for that purpose.
>Is there a group function at this level?
"Category" can be searched on, sorted on, included in column setups (and hence column reports), etc., etc.
I'll take the liberty to add my two cents - particularily to expand on Rooster's comments about "processes".
Either one will have established processes or not for their business. In either case, with the implementation of a CRM solution, the success or failure that a business eventually evaluates a CRM solution will hinge a lot on how well their processes have been integrated into the CRM solution.
That said, one has to give thought to the end user requirements. Sales staff will have different requirements from support staff and so on. By focusing on the end user requirements and working backwards one can increase their success rate. If the end user doesn't perceive the CRM solution is delivering the results they require then they'll likely not use it to it's fullest - falling back on old methods.
With this approach one will readily be able to evaluate ROI. As an example, an manual process that is now integrated and facilitated with the help of Maximizer may mean that staffing requirements have been reduced by 5 hours a week. That's 260 man hours a year. That saving along with the efficiencies introduced increase my ROI - and it's measurable.
Too often, IMHO, too much focus is placed on the bells and whistles of the CRM solution and not on the what one is trying to solve.
Anyways, I'm rambling now...
- Iris
Either one will have established processes or not for their business. In either case, with the implementation of a CRM solution, the success or failure that a business eventually evaluates a CRM solution will hinge a lot on how well their processes have been integrated into the CRM solution.
That said, one has to give thought to the end user requirements. Sales staff will have different requirements from support staff and so on. By focusing on the end user requirements and working backwards one can increase their success rate. If the end user doesn't perceive the CRM solution is delivering the results they require then they'll likely not use it to it's fullest - falling back on old methods.
With this approach one will readily be able to evaluate ROI. As an example, an manual process that is now integrated and facilitated with the help of Maximizer may mean that staffing requirements have been reduced by 5 hours a week. That's 260 man hours a year. That saving along with the efficiencies introduced increase my ROI - and it's measurable.
Too often, IMHO, too much focus is placed on the bells and whistles of the CRM solution and not on the what one is trying to solve.
Anyways, I'm rambling now...
- Iris
Iris,
Ramble on! The importance of considering the entire value chain,no matter how small or large a firm, is key to getting the requirements well thought out.
On of the areas I focus on in my recruiting /matchmaking practice is serving companies who embrace change. If we cannot get the needs clear up front and share them with all concerend to ensute "fit" those 260 man hours saved could turn into a loss.
So I am off to define my process and data requirements now and hope to have some good/tough how-to questions for maximizer and team.
I think Maximizer should publish what Rooster and Iris have to say in starting up booklet.
Thanks..
Sy
Ramble on! The importance of considering the entire value chain,no matter how small or large a firm, is key to getting the requirements well thought out.
On of the areas I focus on in my recruiting /matchmaking practice is serving companies who embrace change. If we cannot get the needs clear up front and share them with all concerend to ensute "fit" those 260 man hours saved could turn into a loss.
So I am off to define my process and data requirements now and hope to have some good/tough how-to questions for maximizer and team.
I think Maximizer should publish what Rooster and Iris have to say in starting up booklet.
Thanks..
Sy
I just wanted to reinforce what Gord says about going for a single Address Book. We started with three and eventually I convinced everyone we could use just one. It was a huge amount of work merging them (standardizing on UDF's, making data formats like phone numbers consistent, etc.) but it's been well worth it. All our information is in one place - easier to work with/report on, easier to manage/troubleshoot, etc. The end users and the IT folks love it - when you get both of those groups on the same side you know you're on to something!
Setting up multiple Address Books seems to be a very common mistake new users commit.
Think of it this way as well - splitting an Address Book up later will be easier than merging multiple Address Books into one.
- R.
Setting up multiple Address Books seems to be a very common mistake new users commit.
Think of it this way as well - splitting an Address Book up later will be easier than merging multiple Address Books into one.
- R.
Good question. One of the things I had problems with with max is that by default LOGGINGS are off, so nothing appear ex: you phone someone it dot not keep traces. So to fix that go into File Menu
Preferences
Logging
Check to BOTH on everything you see.
Good luck.
Preferences
Logging
Check to BOTH on everything you see.
Good luck.
Another focus I thought of last night was UDF planning. We have 2 divisions servicing very different markets. When we set up the first division we set up UDF's and added to them as needed, but didn't spend a lot of time planning the logic behind the structure. We took the time to do the planning for the second division and the difference is huge - searches are way more powerful. In the first division our people do broad searches and review the details of each entry returned to make sure they really fit the profile. In the second division they can drill right to what they're looking for.
- R.
- R.