What are the main demo mistakes described as "Demo Crime Files" in Robert Riefstahl’s framework?

The main demo mistakes described as "Demo Crime Files" are featuring crimes, alienation crimes, chameleon crimes, presenting crimes, and team crimes. Featuring crimes involve demoing feature by feature instead of solving real problems, alienation crimes involve confusing or frustrating prospects by using internal language instead of the prospect’s language, chameleon crimes involve failing to adapt to the customer’s environment, data, or terminology, presenting crimes involve breaking connection with the audience through poor delivery, unclear flow, or missed context, and team crimes involve winging a demo with multiple presenters and no game plan.

What is a "featuring crime" in a sales or solutions demo?

A featuring crime in a sales or solutions demo is demoing feature by feature instead of focusing on solving real problems for the prospect. A featuring crime shifts attention to a checklist of capabilities rather than showing how the software creates business impact for the customer.

How does the post define "alienation crimes" during a demo?

The post defines alienation crimes as confusing or frustrating prospects by speaking the vendor’s language instead of the prospect’s language. Alienation crimes occur when a presenter uses internal jargon or concepts that do not match how the customer thinks about their own business.

What are "team crimes" in multi-presenter demos?

Team crimes in multi-presenter demos are mistakes that happen when multiple presenters run a demo without a clear game plan. Team crimes typically show up as an uncoordinated flow, handoffs that feel improvised, and a lack of preparation across the demo team.

The Demo Crime Files: Are You Guilty?

Q: According to the post, can these demo "crimes" be fixed, and if so, how?

According to the post, the demo crimes described in the "Demo Crime Files" can be fixed through awareness, preparation, and practice. The post states that most Solutions Engineers have committed these mistakes, sometimes without knowing, but that deliberate effort in recognizing and addressing them can significantly improve demos.

in short

The post summarizes the "Demo Crime Files" concept from Robert Riefstahl’s book "Demonstrating to Win!" and applies it to the work of Solutions Engineers. The post describes five categories of demo mistakes: featuring crimes (showing features instead of solving problems), alienation crimes (using internal jargon that confuses prospects), chameleon crimes (failing to adapt to the customer’s environment and terminology), presenting crimes (losing audience connection through poor delivery and structure), and team crimes (uncoordinated multi-presenter demos). The post emphasizes that most Solutions Engineers have committed these mistakes but that they can be fixed through awareness, preparation, and practice. The post ends by asking readers to reflect on their own demo pet peeves and habits they have unlearned to improve their demos.

In the book Demonstrating to Win! by Robert Riefstahl, there's a chapter recommended for every Solutions Engineer: The Demo Crime Files. These aren't just bad habits; they're momentum-killers that derail great software from landing with business impact.

Featuring crimes. Demoing feature by feature instead of solving real problems.

Alienation crimes. Confusing or frustrating prospects by speaking our language, not theirs.

Chameleon crimes. Failing to adapt to the customer's environment, data, or terminology.

Presenting crimes. Breaking your connection with the audience through poor delivery, unclear flow, or missed context.

Team crimes. Winging it with multiple presenters and no game plan.

Most of us have committed these, sometimes without knowing. The good news? They're fixable with awareness, preparation, and practice.

What's your biggest demo pet peeve in these categories? Or, what habit did you unlearn that made your demos dramatically better?