Consider the priorities of functionalities that you want to implement
in your Siebel application. Siebel comprise many areas of
functionality, even if you bought licenses for a limited range of
functionality you may well have access to a lot of useful standard
functionality. But how and where do you start? There are many best
practices that you may well glean valuable information from, best
practices established both by Siebel and by the implementators you work
with. Boiling them down into useable statements, may help you
tremendously in getting your Siebel project from start to finish in the
best way possible. You may beg to differ on these best practices and
opinions, and you are welcome to do so – they are intended to provoke
thought, and careful consideration, which should help you realize your
company’s goals with a Siebel implementation without any grief.
- Use
the Vanilla Functionality first – then decide how and if you need to
change areas of the application to better suit your needs. There are two
options here;
- Change Siebel
- Change how you do your business
Both
options have merit, sometimes you cannot change Siebel to do what you
want without breaking the application in places, or making it difficult
to upgrade at a later stage. Sometimes you cannot change how your
company does things.
- Limit the amount of functionality that
you expose to your users from the beginning. But make sure that super
users have access to functionality areas not yet used in production –
for safety – just do it in your UAT. Doing this should help ensure that
your users do not loose sight of new functionality that can be added to
the application.
- Get your users on board. There is no excuse on
this, you need to educate you users, you need to nurse them, and you
need to let them have time to develop an understanding for the
application, this way your investment in software and configuration is
not lost. If you do not get your users to embrace the application – just
forget it then.
- Listen to the users, it goes almost without
saying – if you get them onboard, they see improvements to the
application and you dismiss all of them, then you’re going to loose the
support of the users. Always balance the development to make sure that
you provide functionality required by management and by users. Remember
there may be differences in what management and end-users want the
application to do.
In Manzana we live on our customers’
success, and our ability to scope, develop, implement and rollout
solutions that cover the above points and more. And the results speak
for themselves. Our customers are satisfied, their employees are
satisfied, and resources have been freed for more important tasks. Look
at the Customer Success to see some quotes from customer installations
that Manzana have built.
Further we pride ourselves in not just
being an implementator of Siebel, we also use Siebel actively in
Manzana. So our experience also comes from our own daily use of Siebel.
Look for the Download Section, there’s a small free utility that will test your Siebel COM objects.
Thanks for your time!
Henrik Ohm Eriksen, CEO
Manzana
If
you are considering a CRM or Siebel solution or just want to ask a
question, then send us an email and we will get back to you asap. If you
would like to inquire on hiring Manzana Services please do not hesitate
to contact us, either by email or phone.
And also, we highly recommend you visit the Siebel Inc. homepage at www.siebel.com