I've sales agents and bean counters who are attempting to sell custom remaking to clients, that is fine. However when an intricate change request is available in which i send back a sizable estimate for, they get confused. Frequently they return at me with "Why can't you simply add another column?" which by another, they mean twelve approximately custom posts PER client.

To date all I'm able to return with is "We are attempting to keep your database well stabilized" meaning absolutely nothing to them. I let them know I can produce a system of tables that enables each client to define their very own group of custom fields, however that can take more money and time than "just adding a couple of posts". Not to mention they would like to get their cake and eat it too.

So how do i make sure they are understand?

I let them know I can produce a system of tables that enables each client to define their very own group of custom fields, however that can take more money and time than "just adding a couple of posts".

I believe you need to push this method for your bosses since customizability is clearly an element much sought after. Stress that the individually personalized (instead of generalized, limited customizability) system for every client implies that patches and updates must be produced for everybody client (resulting in longer roll-out occasions and greater costs) that non-standardized installations imply that HelpDesk tickets will require considerably longer to shut (resulting in dissatisfied clients and greater costs) etc.

Quite simply sell temporary discomfort for long-term gain by showing that the price of their solution far exceeds the price of your solution.

Salesmen are focussed on making the purchase. That is what will get them their commission. They do not worry about what uses. Bosses, however, are focussed on cost. Target your bosses as well as your bosses sell towards the salesmen.

The easiest way I have found would be to show the best way to produce a new feature from what they are requesting that you simply could not add with just a couple of personalized posts. Features are superior to custom remaking, especially when you are able charge someone for this.

Try to create a good business situation for the side before getting in to the technical stuff.

Ah.. just a little understanding is really a harmful factor.

Try that one:

You: Which companies did we neglect to target?
Sales: Acme Industries, OCP Corp, blah blah blah
You: Well.... why can't you simply make a few more calls?

The solution obviously is sales is not that easy. Neither is software development. Unless of course they really want hrs of explanation when it comes to architecture and maintenance I would recommend they believe in judgement like a software developer.

This is actually the problem here, trust. You need to show them they're exhibiting deficiencies in rely upon your capabilities by looking into making these claims.

You are able to let them know that the poorly designed database implies that in the long run:

  • it will require longer to allow them to retrieve their data - can they wish to wait and wait?

  • it will likely be harder and take more time to create queries to create reviews - again, when they need that question tomorrow, do they would like to find out it's still being done?

  • it will likely be a nightmare to keep, with error prone queries more prone to be written.

If they are sales agents and bean counters, they will certainly comprehend the almighty dollar (pound, euro, etc.). Are you able to demonstrate the time spent to keep these extra posts does not justify the additional sales?

Be cautious here and make certain your argument is sensible. I have found myself resistant previously to doing custom remaking more because I did not wish to ugly up my pretty little domain model than since it would actually be that hard to maintain. A good analysis can help you determine why you are fighting off the personalization.

Remember - the end result is you need to keep clients happy to be able to remain in business. We thoughtful designers can occasionally lose sight of this within our mission to create things maintainable and straightforward.

Google "technical debt" Demonstrate to them the outcomes.