Choose customer functionality over staff functionality.
Because our websites (customer-facing) and databases (staff-facing) are now intertwined and completely integrated, we may come upon situations where database design requires us to choose between making use of the system easier for the customer or making it easier for the staff. In 99% of the cases, you should choose customer over staff. Here’s why:
- Our first job is to help our customers buy, whether it’s membership, events, products, or services. Anything that makes it more difficult to buy will dampen our sales. That’s bad.
- We can’t “train” our customers on how to use our systems if they are poorly designed. If we have to train them, we’ll lose sales (see #1 above). But we can train staff on how to work around less-than-perfect design on the staff side.
- You have far more customers to please than staff!
Hopefully you can choose BOTH, but the next time you have to make a choice between a better customer experience and a better staff experience, choose the customer!