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

Measuring customer service

February 16, 2022

Measuring customer service When I work with clients on AMS selection, one question that often […]

Iterate or innovate?

February 9, 2022

Iterate or innovate? When moving to a new association management system, there is often an implicit […]

Who is in control?

February 2, 2022

Who is in control? Speaking with a client once about their database project, the client […]

Sometimes Staff Has to do the Work

January 26, 2022

Sometimes staff has to do the work… As a child, I was attracted to computers […]

Documentation and the Great Resignation

January 19, 2022

Documentation and the Great Resignation Unless you’ve been living under the proverbial rock, you’ve heard […]

Data Management Strategy

January 12, 2022

Data Management Strategy Do you know what your data management strategy is? If you have […]

It’s always about trust

January 5, 2022

It’s always about trust When I work with clients on almost any data management project, […]

You can’t outsource buy-in

December 16, 2021

You can’t outsource buy-in One factor consistent with all of my most successful projects is […]

Use it or lose it!

December 8, 2021

Use it or lose it! I’m referring here to the data you collect. If you […]

“If I could only do one thing…”

December 1, 2021

“If I could only do one thing…” Managing data throughout your organization can be overwhelming. Do […]

Leave a Comment

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

Scroll to Top