When it comes to software development (and Business Intelligence as well), tailoring is our Dada.
As you know, we don't really like ready-made solutions that don't really meet the customer's needs
And then charge for features that are not needed because they are part of the overall solution.... Finally, to twist the neck of business processes to fit them into an unsuitable data model, even less.
But how to design and develop a tailor-made solution efficiently and cost-effectively.
Addressing the customer's need
By tackling the client's need, of course. By studying it precisely, by dissecting it and by creating the database model that will be sufficiently evolving to meet the needs not yet identified. This is where good design methods remain the most relevant and there is nothing like a good relational database. Especially if the latter is based on a modern, powerful, customisable and scalable application baseor framework.
Experience and new technologies
It also means capitalising on several years of development (more than 10 years for the youngest members of our team) and concentrating on the best technologies without spreading ourselves too thin. And thus rely on high-performance technological building blocks.
The right way for a publisher
But isn't that the ideal path for any publisher?
Of course, yes. But why do some succeed with talent, others less so?
One answer may lie in the fact that some people think they are satisfying the customer by trying too hard to say yes and by thinking too much about the order . In reality, the obsession with the order makes them miss the essential point: the customer's real need. If the need is not understood, then it is necessary to go back to the drawing board, as many times as necessary. Finally, if the misunderstanding persists, you have to know not to go in a direction contrary to the philosophy of the product. If you do, you run the risk of dissatisfying the customer and seriously distorting the product and ultimately devaluing it. Whatever the case, listening to the customerremains essential and if the customer questions the product, then it must be changed. That's our job, isn't it?
What do you think?
