1. Oral Presentations & Graphics Review

2. Step I: Identify Core Message & Audience
What’s my core message?
i.e. What do I want the audience to remember?
Made to Stick: Core Intent
Who is my audience?
What do they care about?
How much do they know about this topic?

3. Oral Pres. 1: Graphics Review
Review of project that is underway
Model: formal review with upper management
What is the vision & motivation for this project?
Clear & compelling?
Baffling or nonexistent?
How is it progressing?
Team executing well, good progress
Some difficulties, team has credible plan to overcome
Progress poor, team recovery plan unclear
Made to Stick: Core message / intent?
Project is worthwhile and team can deliver it

4. Oral Pres. 1: Graphics Review
Audience
CI (not yours)
Represents upper management or client
Assigns your grade
 Impress!
Your peers
Made to Stick: Avoid the Curse of Knowledge
Assuming audience knows what you know
Assuming audience knows why something is important
e.g. deep dive into tricky code detail  bad!

5. Extreme Curse of Knowledge
Field Castro three-hour speech on Che Guevara’s application of dialectics
— to an audience of 6-year-olds [Miami Herald]

6. Step 2: High Level Plan & Outline
High level plan: key points?
What’s interesting to your audience?
What will show your team & project well?
e.g., might focus on:
Fast Response
Detailed but usable
Adapting to environment: night mode
Brainstorm as a team!

7. 4 content slides  approx. 4 min.
Step 2: Outline
Slide skeleton
What slides & who owns each
Assign owners
Separator slide
 ~0 min.
Introduction
GIS from Roman times to today
Generation GIS
Response Time …
Basic Usability
Design Philosophy
Screenshot1 -…
Screenshot2 - …
Focus Group Feedback
Environmental Adaptation
Night Mode!
Conclusion
Bob: 2 min
Sue: 2 min
Iterate!
4 content slides  approx. 4 min.
Nancy: 4 min
Sue: 1 min
Bob: 1 min

8. Why Do an Outline? Creating good slides time consuming
Faster to refine plan now than after slides made
Wasteful to make 25 slides and throw 15 away
Assign ownership of slides to individuals
Get parallel development going
Commitments clear
Similar to design / project management process
Shawn Malhotra: 10% time high-level plan, 10% detailed plan, rest iteration

9. Step 3: Create Slides Be Visual! Made to Stick: Simple
Audience cannot read & understand complex slides
More reading  less listening to you
But put key points on slides
Very succinctly!
Some audience visual: retain more by seeing
Helps presenter – your (brief) notes are on the slide

10. Not visual  not concrete
Night Mode
Too wordy: not simple
Who cares? Why did you do this?
Our night mode reduces brightness but maintains the colour contrast
All setcolor calls have an extra indirection to obtain the brightness-scaled color
t_color brightness_scaled[NUM_COLOURS];
// Scale to 30% brightness for night mode
update_brightness_scaled (0.3);
setcolor (brightness_scaled[BLUE]);
// now draw normally
Inappropriate for audience – CI representing client or upper management
Not visual  not concrete

11. Night Mode Who cares? Why did you do this? 16 point font  too small
Reduces brightness for nighttime use
Not centered  visually unappealing

12. Specific references & tests  credible (but could be better sources)
Night Mode
60 minutes for full eye adaptation to dark [
Bright screen at night  distracting
“Despite 60 percent less traffic on the roads, more than 40 percent of all fatal car accidents occur at night.”
Michael Pines, Law Office
Told me why!
Colors & road widths chosen to reduce brightness, but maintain contrast
Tested with 5 individuals  preferred to google maps
Still too wordy
Specific references & tests  credible (but could be better sources)

13. Different why / make me care  story
Night Mode
Different why / make me care  story
Better night vision  safer driving  night mode!
Colors, line widths etc.  reduce brightness
But maintain contrast
4 / 5 people preferred to google maps
Less wordy  simple
Less chance of reading in presentation

14. Night Mode Better night vision  safer driving  night mode!
Colors, line widths etc.  reduce brightness
But maintain contrast
4 / 5 people preferred to google maps
Good or distracting?
Team 300 – Maps are our passion! Betz & Tallman

15. Step 4: Practice Stand up, speak out loud
Screen where it would be in presentation
Remote clicker if you can
Time yourself
Work to get a smooth, but natural-sounding delivery
Slide hard to speak to  edit/refine (step 3)
Too long? Change outline to cut content (step 2)
Most teams try to fit too much in
Iterate!

16. Questions?

17. AdaptaMap: Safety through Environmental Adaptation
Questions?

18. Handling Q & A

19. Tips Clarify the question if necessary Be succinct
“I think your question is whether … Is that right?”
Be succinct

20. To Do Before CI meeting next week CI will discuss outline with team
Make a presentation outline
E.g. title of each slide
Make one complete slide
CI will discuss outline with team
Each team member will present the slide
Great opportunity for feedback