More demos is not better
When I work with clients on selecting a new system, I try very hard to limit to three the number of systems that make it to the demo stage. (We'll typically consider five or six systems prior to demos, but here I'm talking about demos specifically.) My clients will sometimes ask: "Shouldn't we be demoing more than three products?"
There are several reasons for limiting the number of demos, including:
- Demos are "expensive" from a staff time perspective. Multiply the the number of hours you're sitting in a demo times the number of staff in the demo. For some of my clients this could mean 15-25 staff hours (or more!) for one demo. You may not see it, but there is a price for having many demos.
- The more demos you have, the more confused staff will actually get. Even the best note-takers are likely to miss details about a given product, and after watching four or more demos, keeping track of which product does which thing becomes increasingly difficult. So more demos actually create more confusion, not more clarity.
- Research demonstrates that the more options we're presented with, the less likely we are to make a decision. I've encountered many associations who reached out to me for help because they had looked at so many different products that they were overwhelmed and couldn't make a decision.
You should be doing your due diligence and narrowing down your choices before you have actual demos. You want to look at systems that look like solid matches on paper before you ever demo them. This way, when you're doing demos, you're looking at systems that are legitimately good options for your organization.
Wes's Wednesday Wisdom Archives
Once you know, what will you do?
Once you know, what will you do? I’ve yet to meet a client who didn’t […]
If it’s not in your AMS, why not?
If it’s not in your AMS, why not? I like to tell my clients they’ll […]
Why checkboxes and tags are awesome and dangerous
Why checkboxes and tags are awesome and dangerous One of the most common functions in […]
Don’t miss obvious engagement data
Don’t miss obvious engagement data What I’ve experienced with my clients over the years is […]
All data requires active management
All data requires active management It’s a simple fact of data management that is often […]
Documentation is critical for consistency
Documentation is critical for consistency There are so many reasons why documenting your data management […]
Consumer demands change and technology changes
Consumer demands change and technology changes When I work with clients on the selection of […]
Why I write
Why I write Thirty years ago, I started a new job as director of membership […]
DAN – The Data Analytics Network
DAN – The Data Analytics Network I’m a huge fan of users groups (both internal […]
Process before technology
Process before technology In a conversation with a client recently, I was reminded (yet again) […]