oral Presentations

1. Cardinal Rule: KISS

2. Know What you are trying to accomplish

A. overall purpose?
B. Message you wish to deliver?
C. What do you want your audience to Do?
D. Impression of you?

3. Know your audiences

A. Who all are they? ( Multiple Types )
B. Knowledge in the subject area?
D. How you want to change them?

4. Plan your presentation

A. Explore content, then be selective
B. Decide on main point
C. Walk the ridgeline, build a tree
D. Add depth, but cautiously

5. Build your talk, build your visuals

A. Core of talk is your visuals
B. Keep them simple -- less is better
C. Allow adequate time for each visual
D. Make structure of talk explicit

6. Live Demos

A. High risk, high payoff
B. Don't show everything
C. Prepare sample data ahead of time
     Not too much, not too little
D. Test, test, test
E. Practice, practice, practice

7. Look around

A. Example presentations
B. Guidelines and tutorials
     E.g., A Strategic Method for Writing

8. Example System talk

A. Introduction / Overview

Problem or Need
Nature of the Solution (i.e., your system)
Main function (2 or 3)
Overview of talk

B. User's mental model

How does the user think of the system?
Main Function
Example screen shots

C. Demo

Live!
Selective -- interesting function, not routine
Previously prepared data
     Not too much, but not too little

D. Lessons Learned

What was harder/easier than expected Technically?
Any especially slick code?
Team or organizational issues?
What would you do differently?
What would you do if had more time, more resources?

oral Presentations

1. Cardinal Rule: KISS

2. Know What you are trying to accomplish

A. overall purpose?
B. Message you wish to deliver?
C. What do you want your audience to Do?
D. Impression of you?

3. Know your audiences

A. Who all are they? ( Multiple Types )
B. Knowledge in the subject area?
D. How you want to change them?

4. Plan your presentation

A. Explore content, then be selective
B. Decide on main point
C. Walk the ridgeline, build a tree
D. Add depth, but cautiously

5. Build your talk, build your visuals

A. Core of talk is your visuals
B. Keep them simple -- less is better
C. Allow adequate time for each visual
D. Make structure of talk explicit

6. Live Demos

A. High risk, high payoff
B. Don't show everything
C. Prepare sample data ahead of time
Not too much, not too little
D. Test, test, test
E. Practice, practice, practice

7. Look around

A. Example presentations
B. Guidelines and tutorials
E.g., A Strategic Method for Writing

8. Example System talk

A. Introduction / Overview

Problem or Need
Nature of the Solution (i.e., your system)
Main function (2 or 3)
Overview of talk

B. User's mental model

How does the user think of the system?
Main Function
Example screen shots

C. Demo

Live!
Selective -- interesting function, not routine
Previously prepared data
Not too much, but not too little

D. Lessons Learned

What was harder/easier than expected Technically?
Any especially slick code?
Team or organizational issues?
What would you do differently?
What would you do if had more time, more resources?

oral Presentations

1. Cardinal Rule: KISS

2. Know What you are trying to accomplish

A. overall purpose? B. Message you wish to deliver? C. What do you want your audience to Do? D. Impression of you?

3. Know your audiences

A. Who all are they? ( Multiple Types ) B. Knowledge in the subject area? D. How you want to change them?

4. Plan your presentation

A. Explore content, then be selective B. Decide on main point C. Walk the ridgeline, build a tree D. Add depth, but cautiously

5. Build your talk, build your visuals

A. Core of talk is your visuals B. Keep them simple -- less is better C. Allow adequate time for each visual D. Make structure of talk explicit

6. Live Demos

A. High risk, high payoff B. Don't show everything C. Prepare sample data ahead of time Not too much, not too little D. Test, test, test E. Practice, practice, practice

7. Look around

A. Example presentations B. Guidelines and tutorials E.g., A Strategic Method for Writing

8. Example System talk

A. Introduction / Overview

Problem or Need Nature of the Solution (i.e., your system) Main function (2 or 3) Overview of talk

B. User's mental model

How does the user think of the system? Main Function Example screen shots

C. Demo

Live! Selective -- interesting function, not routine Previously prepared data Not too much, but not too little

D. Lessons Learned

What was harder/easier than expected Technically? Any especially slick code? Team or organizational issues? What would you do differently? What would you do if had more time, more resources?

A. overall purpose?
B. Message you wish to deliver?
C. What do you want your audience to Do?
D. Impression of you?

A. Who all are they? ( Multiple Types )
B. Knowledge in the subject area?
D. How you want to change them?

A. Explore content, then be selective
B. Decide on main point
C. Walk the ridgeline, build a tree
D. Add depth, but cautiously

A. Core of talk is your visuals
B. Keep them simple -- less is better
C. Allow adequate time for each visual
D. Make structure of talk explicit

A. High risk, high payoff
B. Don't show everything
C. Prepare sample data ahead of time
Not too much, not too little
D. Test, test, test
E. Practice, practice, practice

A. Example presentations
B. Guidelines and tutorials
E.g., A Strategic Method for Writing

Problem or Need
Nature of the Solution (i.e., your system)
Main function (2 or 3)
Overview of talk

How does the user think of the system?
Main Function
Example screen shots

Live!
Selective -- interesting function, not routine
Previously prepared data
Not too much, but not too little

What was harder/easier than expected Technically?
Any especially slick code?
Team or organizational issues?
What would you do differently?
What would you do if had more time, more resources?