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

Simpler and Faster is Better

August 24, 2022

Simple and Faster is Better Earlier this week I was fortunate enough to attend a […]

Patience and grace

August 17, 2022

Patience and grace A past client of mine recently told me: “You inspire confidence and […]

Sometimes you just have to try it and see what happens

August 10, 2022

Sometimes you just have to try it and see what happens The single greatest key […]

Training and testing

August 3, 2022

Training and testing I’ve written before that the best form of training follows this process: […]

How to save a “failing” project

July 27, 2022

How to save a “failing” project It is not unusual for me to receive a […]

How to avoid the “IT black hole”

July 20, 2022

How to avoid the “IT black hole” Going all the way back to my days […]

The “People” are important!

July 13, 2022

The “People” are important! I’ve written a lot about people, process, and technology over the […]

Always look for the MVP

July 6, 2022

Always look for the MVP I first wrote about minimum viable product (MVP) just three […]

The longer you take, the longer it will take

June 29, 2022

The longer you take, the longer it will take It may sound like a tautology, […]

Data is for action

June 22, 2022

Data is for action When deciding whether or not to collect a piece of data, […]

Leave a Comment

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

Scroll to Top