Customer vs. staff
In a properly designed AMS, when the customer goes online to your website to do business with you (e.g., join, renew, register for an event, buy a product), the website is interacting directly with the AMS. In other words, any data changes being made by the customer are going directly to the database with no staff intervention required. All modern AMSes work this way.
Because the database is being used by both staff and customers, there is an inherent tension for system design. On the one hand, the customer needs a very simple interface that allows her to quickly and easily take care of the business at hand. On the other hand, staff needs to have complete and total access to all data to manage any type of scenario that arises.
One trap that many associations fall into is trying to design the customer interface to manage as many scenarios (exceptions) as possible. This is a mistake. The customer interface should manage the most common interactions that occur and should make that process as efficient and simple ("idiot-proof") as possible. Anything that is exceptional should be managed by staff.
This is a great place to apply the 80/20 rule. Your customer interface should be able to manage 80% of the interactions and the remaining 20% is managed with staff assistance.
So look at your customer interface and ask yourself: Is it fast and easy to use? Have we tried to accommodate too many exceptions? Make the process for the customer as easy as possible and let staff manage all the hard stuff!
Wes's Wednesday Wisdom Archives
Action isn’t the same as progress
Action isn’t the same as progress I’ve written before that not taking action is an …
Start with the end in mind
Start with the end in mind Like so many, I probably first heard the phrase …
It’s quiet in here…maybe TOO quiet…
It’s quiet in here…maybe TOO quiet… One of the truisms of data management is that …
It’s ALWAYS about expectations
It’s ALWAYS about expectations The headline reads: “Tesla sets record for vehicle deliveries, an increase …
It’s hard to get UNangry
It’s hard to get UNangry I often emphasize to my clients the importance of testing …
Some history IS important!
Some history IS important! When I’m advising clients on data conversion (moving data from one …
“Many mickles make a muckle.”
“Many mickles make a muckle.” “Many mickles make a muckle.” – George Washington Apparently, this …
It’s easy to collect; it’s harder to manage
It’s easy to collect; it’s harder to manage The beauty of today’s highly configurable AMS …
Tell them why you want the data
Tell them why you want the data Because data is so easy to collect these …
Don’t get hung up on something minor
Don’t get hung up on something minor I’m a problem solver. I love to solve …