More demos is not better

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

Some context, please

April 21, 2021

Some context, please A pet peeve of mine: A report about associations (e.g., marketing benchmarks report) where […]

Eventually automated emails get ignored

April 14, 2021

Eventually automated emails get ignored During the discovery and development phase of implementing a new […]

The challenge the AMS providers see

April 7, 2021

The challenge the AMS providers see Over the years I’ve asked AMS providers what they […]

Be careful about “solutioning” too quickly

March 31, 2021

Be careful about “solutioning” too quickly One of the great things about software developers is […]

What’s our next action?

March 24, 2021

What’s our next action? As you can imagine, I spend a lot of time in […]

Don’t automate for the sake of automation

March 17, 2021

Don’t automate for the sake of automation I’m the laziest person in the world. I […]

Don’t forget about what got better

March 10, 2021

Don’t forget about what got better Negativity bias is the tendency to focus on only […]

Give a little at a time rather than taking away

March 3, 2021

Give a little at a time rather than taking away I’m sure there’s research somewhere […]

First, you gotta have the data

February 17, 2021

First, you gotta have the data When I work with clients on a new AMS […]

Work on your relationship with your AMS vendor

February 10, 2021

Work on your relationship with your AMS vendor It is no coincidence that my most […]

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top