A possible starting point

It is hard to tell whether it is the fault of Odoo or the policy of the respective partner. Perhaps it is just one’s personal view on one’s own development or a reflection of what all the projects have in common when you take them over. Maybe it has to do with the fact that, when you receive them, some of the requests or specifications already contain precise functional descriptions. Or maybe it is only a question of a partner’s maturity once he gets involved.

We are quite familiar with this kind of approach from past experience. Quite often, decision-making bodies are present during the workshops, either discussing supposedly missing functions or planning processes and their optimization at the very beginning of an implementation. One of the reasons for these discussions is that the clients are familiar with the processes of the previous system that they regard as the “standard” and are now looking for a new and better “previous system” that covers the standard in the well-known way.[1] Consequently, they now face a situation where implementations, if successful, are more than a little bumpy, consume a lot of support for „remedies“ and, in retrospect, are very difficult to scale.

[1] In a previous blog, we have already discussed our views regarding the definition of the term „standard“, what it is and what it is not.

Our approach

Our approach is quite different, since we align the daily working steps with Odoo. Sometimes this is easier said than actually done. It is not necessarily due to simple habit, but to the fact that in some respects Odoo has a very intelligent and simple approach as well as a novel perspective. Using both actually optimizes efficiency without necessitating subsequent adjustment. However, there a many users who are still looking for their familiar functions and well-known processes in the new tool.