Claudio Perrone - Outstanding Presentations

2,052
-1

Published on

Published in: Education, Business
0 Comments
11 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,052
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
11
Embeds 0
No embeds

No notes for slide
  • Find a compelling dramatic story in which your area/product/technology plays a key role and structure your presentation around that story
  • Corporate politics.Lack of shared values.Weak communication skills.These, and many others, are reasons why most IT projects fail.IT project success rate 1994: 15%IT project success rate 2004: 34%In 1994, 75% of projects failed to meet customer expectations, 30% never see the light of day. 50% are 200% over budget.Most projects are challenged on the basis of lack of “soft skills”, not hard skills.We tend to worry so much on our technical skills, that we tend to forget this “tiny aspect”. Our employers forget this too, so maybe this is a problem.
  • How do you see the world around you?
  • Claudio Perrone - Outstanding Presentations

    1. 1. Storytelling <br />techniquesfor crafting<br />Outstanding Presentations<br />Claudio Perrone<br />
    2. 2. How relevant are presentations to your career?<br />
    3. 3. In late 2007, I was leading a happy life<br />
    4. 4. One day, my phone rang…<br />
    5. 5. I was offered to speak at a BIG conference<br />
    6. 6. On the one hand,it was a fantastic opportunity<br />
    7. 7. On the other hand, public speakingscared me to death<br />
    8. 8. Year: 1997Location: C.E.R.N.<br />
    9. 9. I trained 15 scientists for a week<br />
    10. 10. They skinned me alive<br />
    11. 11. I’ll never forget that experience…<br />
    12. 12. There was no way I was going face another possible humiliation<br />
    13. 13. Besides, I could brain-damage people with PowerPoint<br />
    14. 14. What would you do?<br />
    15. 15. 1<br />Move Beyond<br />Bullet Points<br />
    16. 16. In Feb 2008, I joined the revolution<br />
    17. 17. “<br />Simplicity <br />is the ultimate<br />sophistication<br />--- Leonardo Da Vinci<br />
    18. 18. Despite my efforts, my firstdry-run was a disaster<br />
    19. 19. I had strong images, but lack of structure confused the audience<br />
    20. 20. At first, I created a “logical” outline<br />Main Point: Agility + Communication + Creativity lead to success<br /> 1. Supporting detail: Agility<br /> 2. Supporting detail: Communication<br /> 3. Supporting detail: Creativity <br />Summary: Agility + Communication + Creativity lead to success<br />
    21. 21. Then, I discovered BBP!<br />
    22. 22. Let’s “script” the first 5 slides<br />Screenwriting techniques for crafting outstanding presentations<br />The downturn threatens the future of many individuals and organizations<br />You are an entrepreneur, meeting an investor for the first time<br />I suggests…<br />Move beyond bullet pointsUnleash the Power of StoryTame your story to persuade<br />You’d love them to invest <br />in your great idea<br />Investors can be so<br />hard to persuade<br />
    23. 23. Let’s see how they “play”<br />Action!<br />
    24. 24. The downturn threatens the future of many individuals and organizations <br />
    25. 25. You are an entrepreneur, meeting an investor for the first time<br />
    26. 26. Investors can be so HARDto persuade<br />
    27. 27. You’d love them to invest in your great idea<br />
    28. 28. I suggest...<br />Move beyond bullet pointsUnleash the Power of StoryTame your story to persuade<br />
    29. 29. …And Cut. Well done! (you’ll add the cool pictures another time)<br />
    30. 30. But wait…<br />What if Spielberg showed up?<br />
    31. 31. Dude,<br /> you are telegraphing.<br />Your “story” has no drama.<br />
    32. 32. How about this?<br />telegraphing<br />vs.<br />dramatic irony<br />vs.<br />dramatic tension<br />
    33. 33. 2<br />Unleash the Power of Story<br />
    34. 34. Enter a new world<br />
    35. 35. Why Story?<br />People make choices based on emotions <br />(and use data to justify them)<br />
    36. 36. What’s a good story idea?<br />Someone<br />wants something badly<br />and goes after it <br />against great odds<br />[character]<br />[desire]<br />[obstacles]<br />
    37. 37. Story revolves around conflict<br />Antagonist<br />Nature<br />Society<br />Self<br />Protagonist<br />vs.<br />
    38. 38. Story has good structure<br />Outer journey<br />
    39. 39. Often, there is a character inner journey<br />WA=C<br />W: Weakness (psychological and moral)<br />A: Action (and struggle to accomplish it)<br />C: Changed Person<br />
    40. 40. Let’s see the “highlights” of a past presentation<br />Action!<br />
    41. 41. Most IT projects fail<br />Will yours?<br />
    42. 42. Once upon a time I was a successful software developer…<br />
    43. 43. My technical skills made me feel invincible<br />
    44. 44. Until one day…<br />
    45. 45. …I entered a world of deception<br />
    46. 46. It was Hell from day 1<br />
    47. 47. What would you do?<br />
    48. 48. I choked<br />
    49. 49. …but then, I decided to fight back<br />
    50. 50. This is what I tried:<br />2<br />Effective <br />Communication<br />3<br />1<br />Deliberate<br />Creativity<br />Agility<br />
    51. 51. 1<br />Agility<br />
    52. 52. …but the project was still at risk<br />
    53. 53. 2<br />Effective Communication<br />
    54. 54. 3<br />Deliberate Creativity<br />
    55. 55. So, what happened to the project?<br />
    56. 56. Amazingly, it succeeded<br />
    57. 57. Lessons learned...<br />“<br />We moved from the Flintstones era to the future.<br />“<br />--- an end user<br />I was part of something. I belonged.<br />--- a developer<br />
    58. 58. …And Cut!<br />
    59. 59. Agile Tales Walk-through (1/3)Setup<br />Setting <br />(+Hook)<br />Character flaw (“naivety”)<br />Setup<br />(ordinary world)<br />Inciting incident<br />
    60. 60. Agile Tales Walk-through (2/3) Development<br />Enter special world<br />Dilemma<br />Complication<br />Refusal of the call<br />Action / <br />Resolution<br />Turning point <br />(will he succeed?)<br />Action /<br />Resolution<br />New complication<br />
    61. 61. Agile Tales Walk-through (3/3) Resolution<br />Dramatic question (restated)<br />Aftermath<br />Climax<br />Theme<br />
    62. 62. How do you craft your own story?<br />
    63. 63. 3<br />Tame <br />Your Story<br />
    64. 64. I used to rewrite a story ~30 times<br />
    65. 65. Not anymore<br />
    66. 66. I use a 7-steps process<br />
    67. 67. Step 1: Research (Create a Data Dump)<br />
    68. 68. Step 2: Prepare<br />Subject<br />POV<br />Listeners<br />Action<br />Benefit<br />
    69. 69. Step 3: Fill and cluster content<br />
    70. 70. Step 4: Identify Story Ideas<br />
    71. 71. E.g. Reverse Benefits<br />Features <br />Model<br />View<br />Controller<br />Benefits<br />Separation of concerns<br />Easier page lifetime model<br />Testability<br />Reversed Benefits<br />No separation of concerns<br />Complex lifetime cycle<br />Hard (or no) testability<br />E.g.: Candidate Scenario 1<br />After the latest disastrous crash, team has 3 weeks to “fix” a web application which is almost impossible to test<br />
    72. 72. Step 5: Create a dramatic outline<br />Complication: Claudio fears public speaking<br />Development:<br />1. Claudio moves beyond bullet points<br />2. Claudio unleashes stories<br />3. Claudio tames stories<br />Resolution: Claudio conquers fear<br />
    73. 73. Step 5. Dramatic outline II (saga)<br />Major Complication: Claudio fears public speaking<br />Semi-Major Complication: Claudio kills with PowerPoint<br /> Development 1,2,3<br />Interlinked Complication: Spielberg challenges Claudio<br />Semi-Major Resolution: Claudio moves Beyond Bullet Points<br />Semi-Major Complication: Spielberg challenges Claudio<br /> Development 1,2,3<br />Interlinked Complication: Stories consume Claudio<br />Semi-Major Resolution: Claudio embraces stories<br />Semi-Major Complication: Stories consume Claudio<br /> Development 1,2,3<br />Semi-Major Resolution: Claudio tames stories<br />Interlinked Complication: Claudio fears public speaking<br />Semi-Major Complication: Claudio fears public speaking (restated)<br /> Development 1. Claudio pursues emotion<br /> Development 2. Claudio welcomes obstacles (carpe diem)<br /> Development 3. Claudio finds own voice<br />Major Resolution: Claudio conquers fear<br />
    74. 74. Final Thoughts<br />
    75. 75. “<br />Be yourself.<br />Everyone else is already taken.<br />--- Oscar Wilde<br />
    76. 76. Thank you!<br />Claudio Perrone<br />claudio@agilesensei.com<br />www.agilesensei.com<br />www.twitter.com/agilesensei<br />

    ×