3 ms·
I'm scoring this at about 55% good material, which gets an upvote. The problem, in my opinion, is that some of this advice is simply broiler plate, motherhood,
by DanielBMarkham 18y ago
I'm scoring this at about 55% good material, which gets an upvote.
The problem, in my opinion, is that some of this advice is simply broiler plate, motherhood, and apple pie goodness.
Yes. Google can demo their product with one screen and a text box. Got the next Google? Then don't worry so much about your demo. Writing the next Space Shuttle flight system? I'd like to see more than a screen with flight numbers on it. (Probably take a lot longer than 5 minutes too). Sure -- write succinctly. Have a great opening screen from your software that draws the viewer in.
Don't show trivial bits? Hey, that's great advice. Care to tell me what's a trivial bit? I've been pouring blood, sweat, and tears into this puppy: everything is important. Once again, the general point of reduce your depth of presentation to important points for the listener is all goodness. But you'd better know the 2 or 3 little things that's going to put a twinkle in the eye of your viewer. Guess what? It's different every time.
I liked the article overall, though.
One of the best questions was in the comments. Is it okay to use pre=canned video to show your app? Suppose for pacing purposes you want to record your demo and then put it inside an annotated powerpoint. Anything wrong with that? I know I've tried that during training sessions on a couple of occasions and it actually went very well -- freed me up from doodling with the keyboard and let me focus more on my audience.