Wednesday, April 30, 2008

Architecting a great demo

by alec on April 30, 2008

David Spark has a great piece up titled The worst product demonstration I’ve ever seen.  It’s full of good advice on fit and finish around demos.  I enjoyed his critique.  One of the things that I would add to his comments is that you have to focus on the architecture of your demo. If you treat your demo as an interactive product sheet, then you’ll have a good foundation for a truly effective pitch.

After winning a DEMOgod award in 2006, Howard and I built a slide presentation that we delivered at BarCamp Ottawa to describe that architecture.  Here’s how to knock your audience off their seats in 6 minutes or less (notes taken by Jay Goldman at BarCamp).

Architecture of a great demo

Hook

  • 0:00 to 0:20
  • State the problem (sometimes it feels like the whole world wants your attention)
  • Engage the audience (we can’t help you with the co-worker who wants to sit in your office and chat)

Position

  • 0:20 to 0:30
  • My product is…

Prove

  • 0:30 to 5:15
  • Blow the crowd away with three big ideas
  • Awesome! (killer feature 1)
  • Awesome! (killer feature 2)
  • Doesn’t suck (it’s easy, it’s inexpensive, etc.  remove the one big objection people might have)
  • This has to be the main focus of the presentation – show the entire product in detail

Close

  • 5:15 to 5:45
  • Synchronized blast to phones throughout the audience
  • Smart closing lines

Pitfalls

  • Trying to be too funny
  • Some company did a terrorist sketch that wasn’t funny and no one remembers who they were – just the dreadful sketch
  • It’s not about you and it’s not about your company – it’s about the DEMO
    • One DEMO that could have been great was about an in-car entertainment centre but they spent the first three minutes on market position and on showing connectors on the back of the box
  • Timing is everything
    • 5:45 is only a :15 second
  • Listen to your advisors
    • Speed to cool is key – how quick can you get to the cool stuff?
  • Practice, Practice, Practice
    • iotum practiced about four times a day for two weeks before to get it totally slick

{ 4 comments }

Squawk Box April 30 – Trust

by alec on April 30, 2008

This morning we talked about trust, in two different contexts.

First, yesterday AOL announced their AOL Open Voice API to allow software developers to be able to connect their applications to AOL’s network.  But given the disaster that the AIM Phoneline Developers program was, why should software developers trust AOL now?

Luckily, we had Dan York on the line.  He had spent the time to dig into the AOL Open Voice API, and discovered that it really wasn’t an API to speak of at all.  AOL has simply opened their SIP Proxy’s to 3rd party applications.  It’s in fact, no different than any of hundreds of other SIP termination services out there.  And as Ken Camp pointed out, because you can’t buy incoming service from them, what they’re offering is a half a phone service.

So if you’re a developer, here’s one more option for you for terminations.  It’s odd that AOL thinks this is newsworthy.

And the second trust topic was social media.  Forrester analyst Jeremiah Owyang published a piece titled Who do People Trust? It ain’t bloggers this morning, about the implications of social media for marketers.  Suffice it to say,  he thinks that most companies are focusing on the wrong thing.  We had a good discussion about trust in marketing, although prevailing opinion was that this is a topic that keeps coming up.  As one person said “it’s novel for Jeremiah because he wasn’t around the last 4 times this meme went around”.

On the line: Jim Courtney, Randall Howard, Dan York, Ken Camp, Jonathan Jensen, Mark Hewitt, Steve Sokol, Jeanette Fisher, David Spark, Moshe Maeir, Adam Somer, Ian Hood, Bill Volk, Mike Pruyn, Sheryl Breuker, Kyoko Kataoka, Andrew Hansen, and Linda Saytes.

Enjoy the podcast!

{ 5 comments }

AOL announces AOL OpenVoice API. CAVEAT DEVELOPER.

April 30, 2008

AOL announced Tuesday that it has opened the API to AIM Call Out, a move designed to let programmers more easily build products that tap into AIM for making calls over the net. The API is freely available, and applications built with it can let people call using AOL’s network to bypass the ordinary telephony [...]

Read the full article →
Alec on LinkedIn Alec on Twitter Alec on Facebook Calliflower on Youtube RSS Feed Contact me