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

The “S” stands for “Standard”

October 9, 2019

The “S” stands for “Standard” In a conversation with a past client, we were discussing […]

Is that meaningless data?

September 25, 2019

Is that meaningless data? I’m not a big quotes guy, but one of the few […]

Be aware of unintended consequences

September 18, 2019

Be aware of unintended consequences I’ve written before that every decision involves a trade-off. When […]

Positive change is harder to see

September 11, 2019

Positive change is harder to see Humans are wired to see negative change because we […]

MVP: Minimum Viable Product

September 4, 2019

MVP: Minimum Viable Product In product development there is a concept known as MVP, or […]

You always need a reason for collecting data

August 28, 2019

You always need a reason for collecting data When you ask for data from someone […]

If you’re unhappy, speak up!

August 21, 2019

If you’re unhappy, speak up! My clients will often ask me something along the lines […]

Does it advance the mission?

August 14, 2019

Does it advance the mission? Because associations are mission-driven, everything you do should be seen […]

How should you start a new data project?

August 7, 2019

How should you start a new data project? When you’ve got a new data project […]

A Data Integrity Report…for Reports!

July 29, 2019

I’ve written elsewhere about the value of data integrity reports. But one of the most […]

Leave a Comment

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

Scroll to Top