Principle

Since I discovered PmWiki:SlideShow I will be able to convert wiki content directly to presentation, yet I should follow simple rules in order to be sure the message I want to convey does get across to properly generate a conversation on it.

Rules of presentation

  • as a presentation is a conversation, questions must be handled gracefully but can be "buffered"
    • ignore a raised hand re-route according to your desired way to make the talk
    • if you do not want remarks or questions during the presentation but if somebody is raising his or her hand, politely ask if he has a correction to make and if not, to hold this for the end of the section or the whole talk
  • focusing only on content is a mistake
    • if you have perfect content but a faulty protocol you can't use the network
  • technology != usage (habits, skills, goal, ...)
    • wiki! wiki! wiki! but efficient collaboration thanks to history management, simultaenous edition, etc
  • be inviting, never threatening
    • "Do you understand what I mean?" but "Am I making myself clear?"
  • if there is too much meat, it won't be digested properly
    • even though one wants to present as much as possible about a topic he or she is passionate about, there is only so much that can be said in a short period of time
    • consider the background of the public
  • your voice is the text
    • the rest are the slides, visuals, videos, sounds, ...

Bad examples and metaphor

never use example that could be more important to the audience than the topic you plan to talk about

  • if you talk about any of those more people fundamental, people will be very attentive but chances are they will be attentive on this new topic, not yours
    • one automatically compares the 2 topics, the one of your example and the one you want to explain. If they consider that one is more crucial than the other and does not depend on it, it is rational not to actually spend time on the first one.
    • consequently you invite people to hijack your presentation either passively by thinking about another topic or actively by asking a gradual serie of questions that will lead to what they consider be the most important topic
  • examples
    • religion
    • the judiciary system
    • politics
    • Microsoft vs. Apple
      • polemical emotional personal choices
  • except if the talk is precisely about how to reach it

A Presentation is still a conversation

Thus you must take Sophisms into account

Other tips to integrate

Interesting visual support

  • computer fire-power (yet doubtful content)
    • expressing scaryness

Those are nice pictures found over the web that could be used to get attention of the audience. Make sure to use the local mirror.

  • doing it wrong

Proposals

Strategic IT

Proposal to Franck, Sylvain, Dolaur, Duong, Nicolas... a "strategic IT : What B-School should teach the geeks".

  1. goal
    1. understand why IT practitioners have such an important role yet are too often managed in order to be purely executing and replaceable and what they can do (including quitting and starting up their own biz, in IT or not) to change it (if they want to)
  2. communication
    1. "strategic IT" but rather "Information Strategy" suggest by Sylvain
    2. How often to do you use software (in any form, from macro to kernel) for yourself (not the company that pays you) that you wrote (at least in part)?
  3. sources
    1. InformationRules
      1. Google Apple, Microsoft, Oracle, ... but from the framework user perspective, not the final user
      2. explore its bibliography
    2. http://www.tomsquest.com/blog/passionate-programmer-critique-du-livre/
    3. Programming
    4. HackersAndPainters
    5. http://manifesto.softwarecraftsmanship.org/
    6. recommendations on books about IT from a strategic and economic angle? (ideally for startups, not for the IT dept of a Fortune500)
      1. information rules
      2. innovator dilemma
      3. http://www.ted.com/talks/rory_sutherland_sweat_the_small_stuff.html
      4. http://www.insearchofstupidity.com/
      5. discussion with freenode/appletizer 23/06/2010 at 23:58
    7. books written by famous CTOs?
    8. legal aspect, Seedea:Seedea/Licenses
      1. large IT firm (including Google) legal departments publications
  4. key topics
    1. SaaS
      1. AWS including its payment method
      2. CloudCamp Paris in 2009 with Sylvain
    2. discussion on freenode/#startups 23/06/2010 at 23:34
    3. Strategy Lessons
    4. Code is Law by Lawrence Lessig, Harvard Magazine Jan-Feb 2000
    5. Programming Is the New Literacy by Marc Prensky, Edutopia 2008
    6. Architecture is Politics (and Politics is Architecture) by Mitch Kapor, Mitch Kapor's Blog, 2006
  5. guest speakers
    1. artistes
      1. http://les-algoristes.org/
    2. IT StartUp CEO
    3. Coop member
      1. Ouvaton coopérative de services internet
      2. http://forums.munci.org/ssii-en-cooperative-t3019.html
      3. http://forums.munci.org/-info-une-cooperative-d-independants-en-belgique-t5074.html
      4. https://secure.wikimedia.org/wikipedia/fr/wiki/Coopérative
    4. lawyers specialized in code
      1. FSF, ...
    5. mathematicians
      1. statistics used in political decisions, for the executive branch of their government
  6. organization
    1. guests speakers wouldn't be paid
    2. no sponsors
    3. gather in a place with bars around that have been warn, explain the locations and topics
      1. people indicate on a common media (SMS?) which talk they want to take part in
        1. the Nth largest group would go to Nth the largest bar
      2. start workshops and talks in those bars
      3. come back 1h after to sum up
      4. repeat for the whole afternoon or day
      5. closing talk in the central place
    4. Wikipedia:BarCamp

See also

To do

  1. locating associated presentation for each Events page
  2. contact (tweet?) the author of Cookbook:SlideShow if there is no edition done
    1. especially for Presentacular effects
  3. visioning button directly in the GroupHeader
  4. consider Cookbook:WikiStylesPlus
  5. seems to fail on PmGraphViz pages
    1. ex CausalReadingTree or Person
    2. should check if this also applies to Cookbook:MimeTeX, Processing, Cookbook:PmGraphViz or any other recipe that has to render content
  6. test with videos
  7. make a Seedea presentation
  8. merge with Presentations
  9. import older
    1. http://www.slideshare.net/Utopiah
      1. possible to get the outline thanks to their text extraction feature
    2. PPT files in Cloud:/
  10. find related services
    1. website screenshot
      1. http://browsershots.org/
      2. http://www.thumbalizr.com/
  11. local cache system from rendered content including
    1. results from related services (see above)
    2. PmWiki recipes (see above)
  12. pick the most sucessful presentation
    1. remove content and make a Template out of it
      1. translate it to other targeted languages
  13. find a way to package as a file offline
    1. else pre-load before doing the presentation
  14. check for special characters rendering problems
    1. unicode is safe but hard to use within the textarea
      1. check PmWiki unicode support, not just PmWiki:Internationalization
  15. http://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action.html
  16. http://fabien.benetou.fr/Events/MBEStartUpWeekend
  17. Slideology
    1. Slide:ology book brief by Nancy Duarte 2008
    2. Duarte Design's Five Rules for Presentations 2009
    3. Duarte Blog Duarte Design, Inc
  18. PresentationZen
    1. Presentation Zen: An Overview by Matt Helmke, 2009
    2. Authors@Google: Garr Reynolds 2008
    3. Presentation Zen by Fabian Crabus, 2007
  19. 10 slides Guy Kawazaki
    1. MBE08
  20. http://twitter.com/pierremorsa