n order to make products accessible to specific audiences sometimes
designers make decisions that other audiences disagree with.
Many small business users have trouble understanding that data is
stored in a database, let alone the possible relationships between
entities.
BCM decided that their particular schema would make it easier for
more users to use a CRM tool. Other CRM products have different
schemas or allow the user to choose their own schema.
It is similar with cars. Most people buy cars with automatic
transmissions
because the default makes it easier for them to drive. Other users
prefer stick shifts because they get better gas mileage or want more
control. There are models for both. And there are very few (zero?)
models with both automatic and manual transmissions, or user
configurable gear ratios.
I'm sure that if Microsoft saw a compelling reason to "correct" this
design limitation, they would have done so by now. Instead they are
making their bets in other areas, focusing on making other CRM
tasks easier for small businesses. In many cases that requires
making choices that will keep some businesses from adopting
BCM. Presumably, losing those customers is offset by those
they gain. SBA, intended for a similar audience, was released
after BCM and after you made your criticisms known. SBA also
decided on the same many contacts to single company schema.
To many users, the real problem is that BCM Contacts are only
intended to represent customers. BCM does not handle vendors,
employees, contractors, and other types (SBA does). For those
types, having a contact assigned to multiple accounts is a
common pattern. When BCM adds those contacts, BCM will fit with
even more users.
Whether BCM has made the right choices will be determined by
the market.
mrtimpeterson via OfficeKB.com wrote: