dos&donts in technical writing

Upload: elgin-renz-timbreza-rocili

Post on 19-Feb-2018

220 views

Category:

Documents


0 download

TRANSCRIPT

  • 7/23/2019 dos&donts in technical writing

    1/121

    DOs and Don'ts

    in creating your

    Power Point Slides

  • 7/23/2019 dos&donts in technical writing

    2/121

    Efective PowerPointpresentations

    ExcitedBy

    Animations, sound

    and

    Clip art

    In PowerPoint?

    You

    Are

    ??

  • 7/23/2019 dos&donts in technical writing

    3/121

    Highlight ey points or rein!orce what the!acilitator is saying

    "hould #e short and to the point, include onlyey words and phases !or visual,rein!orcement

    $n order !or your presentation to %t on mostscreens, text and images should #e placedwithin &'( o! the PowerPoint slide) *his+action sa!e area is seen in the next slide)

    PowerPoint SlidePowerPoint Slide

  • 7/23/2019 dos&donts in technical writing

    4/121

    PowerPoint Presentation SkillsTips for Eective Presenting1. Do you really need to use PowerPoint

    $! its not a#solutely necessary to use PowerPoint in your presentation then -STOP !S"#$ "T%

    &. Stop using PowerPoint as your propt%(. )ut*lessly reduce t*e nu+er ofPowerPoint slides

    ,. !se iages in t*e PowerPoint slidesw*enever possi+le-. !se *eadline suaries only for tet slidesin PowerPoint

    /. Don't 0ust use PowerPoint slides as your*andouts. !se *idden PowerPoint slides for t*e 234session

    http://www.presentation-skills.biz/presentation-delivery/powerpoint-presentation-skills-tips-for-effective-presenting.htmhttp://www.presentation-skills.biz/presentation-delivery/powerpoint-presentation-skills-tips-for-effective-presenting.htmhttp://www.presentation-skills.biz/presentation-delivery/powerpoint-presentation-skills-tips-for-effective-presenting.htmhttp://www.presentation-skills.biz/presentation-delivery/powerpoint-presentation-skills-tips-for-effective-presenting.htm
  • 7/23/2019 dos&donts in technical writing

    5/121

    .ayout continuity !rom !rame to !rameconveys a sense o! completeness

    Headings, su#headings, and logos shouldshow up in the same spot on each !rame

    /argins, !onts, !ont si0e, and colors should #econsistent with graphics located in the same

    general position on each !rame .ines, #oxes, #orders, and open space also

    should #e consistent throughout

    PowerPoint 5ayoutPowerPoint 5ayout

  • 7/23/2019 dos&donts in technical writing

    6/121

    !sing PowerPointDo:1.Chec that you have #ooed all the e1uipment

    you need well #e!ore your tal)&.Plan what you want the audience to see and don2tcrowd the screen)(.3se an appropriate !ont)

    ,.3se a good colour contrast !or #acground andimage, and pro4ect it to chec)-.5ive handouts with details, which wouldn2t #eclear on the screen)/.6ehearse with all your visual material and the

    e1uipment you will #e using).Always have #acup in case o! disaster)

  • 7/23/2019 dos&donts in technical writing

    7/121

    Don't:1."how paragraphs or long sentences on thescreen)&.3se !ussy and distracting #acgrounds)(.7verdo punctuation8 very little is needed ina visual aid)

    ,.3se over9complicated diagrams, which theaudience won2t #e a#le to see clearly)-.3se unnecessary and distractingmovement on the screen)

    /.:atch the computer screen instead o! theaudience).Assume that you can use the e1uipmentwithout trying it out)

  • 7/23/2019 dos&donts in technical writing

    8/121

    :hat we;ll cover today

  • 7/23/2019 dos&donts in technical writing

    9/121

  • 7/23/2019 dos&donts in technical writing

    10/121

  • 7/23/2019 dos&donts in technical writing

    11/121

    *he outline

    >stor ndslide should

    have an outline

    =ollow outline !or your

    presentation

    Place main points on

    outline slide

  • 7/23/2019 dos&donts in technical writing

    12/121

    "lide layout

    3se point !orm, not completesentences

    /aximum o! six points per slide

    Avoid wordiness8 ey words only

  • 7/23/2019 dos&donts in technical writing

    13/121

    "lide layout

    *his page contains too many words !or apresentation slide) $t is not written in point!orm, maing it di@cult #oth !or your

    audience to read and !or you to presenteach point) Although there are exactly thesame num#er o! points on this slide as theprevious slide, it loos much more

    complicated) $n short, your audience willspend too much time trying to read thisparagraph instead o! listening to you)

  • 7/23/2019 dos&donts in technical writing

    14/121

    "lide layout

    "howing one point at a time will8

    !ocus attention on one point

    prevent reading ahead

    help eep your presentation !ocused

  • 7/23/2019 dos&donts in technical writing

    15/121

    "lide layout

  • 7/23/2019 dos&donts in technical writing

    16/121

    "lide layout

    "lide transitions should not #e distracting

    Be consistent with transitions never

    6andom

    :orst efects

    Checer#oard or Com#;

  • 7/23/2019 dos&donts in technical writing

    17/121

    =onts good

    3se diferent si0e to show hierarchy

    the title !ont is D9point

    the main point !ont is 9point

    this !ont is F9point

    3se a standard !ont lie Arial !se at least an 167point font and 8old

  • 7/23/2019 dos&donts in technical writing

    18/121

    =onts 9 #ad

    $! you use a small !ont, your audience won;t #e a#le to read what you have written

    CAP$*A.$"E 7G. :HEG GECE""A6) $* $"

  • 7/23/2019 dos&donts in technical writing

    19/121

    "pacing 9 #ad

    $! you have a set o! points space them out on the slide rather than in one corner

  • 7/23/2019 dos&donts in technical writing

    20/121

    "pacing 9 good

    $! you have a set o! points

    space them out on the slide

    rather than in one corner

  • 7/23/2019 dos&donts in technical writing

    21/121

    Colour 9 good

    3se a !ont colour that contrastssharply with the #acground

    3se colour to rein!orce the logic o!

    your structure

    3se colour to emphasise a point

    But only use this occasionally

  • 7/23/2019 dos&donts in technical writing

    22/121

    Colour 9 #ad

  • 7/23/2019 dos&donts in technical writing

    23/121

    Bacground 9 good

    3se a simple #acground

    3se #acgrounds that contrast withtextJimagery

    3se the same #acground consistentlythroughout your presentation

  • 7/23/2019 dos&donts in technical writing

    24/121

    Bacground #ad

    Avoid #acgrounds that are

    distracting or di@cult to read !rom Always #e consistent with the

    #acground that you use

  • 7/23/2019 dos&donts in technical writing

    25/121

    5raphs

    3se graphs rather than 4ust charts andwords

  • 7/23/2019 dos&donts in technical writing

    26/121

    5raphs

    January February March April

    Blue Balls 20.4 27.4 90 20.4

    Red Balls 30. 3!. 34. 3".

  • 7/23/2019 dos&donts in technical writing

    27/121

    5raphs

    Items Sold in irst uarter of "##"

    0

    "0

    20

    30

    40

    #0

    0

    70

    !090

    "00

    January February March April

    Blue Balls

    Red Balls

  • 7/23/2019 dos&donts in technical writing

    28/121

    5raphs

    20.4

    27.4

    90

    20.4

    30.

    3!.

    34.3".

    0

    "0

    20

    30

    40

    #0

    0

    70

    !0

    90

    "00

    January February March April

    Blue Balls

    Red Balls

  • 7/23/2019 dos&donts in technical writing

    29/121

    7ther !eatures 9 avoid

    Avoid sound efects in

    PowerPoint

    Em#edded programs

    and action #uttons !or

    advanced users

    6e!rain !rom trite clip

    art

  • 7/23/2019 dos&donts in technical writing

    30/121

    7ther !eatures

    choose pictures

    that highlight your

    point

    use a screen

    capture i!

    appropriate

  • 7/23/2019 dos&donts in technical writing

    31/121

    "pelling and 5rammar

    Proo! your slides !or8

    speling mistaes

    the use o! o! repeated words

    grammatical errors you might have mae

    Have someone chec your

    presentation

  • 7/23/2019 dos&donts in technical writing

    32/121

    7n the day

    5et there early

    Handouts

  • 7/23/2019 dos&donts in technical writing

    33/121

    Conclusion slide

    3se an efective and strong closing

    3se a conclusion slide

  • 7/23/2019 dos&donts in technical writing

    34/121

    Conclusion

    "tructure your presentation

    Ieep it simple K#acground, !ont, colourL

    /inimal content on slides 9 DJD

    Avoid pointless animations

    7nly use pictures i! they assist Ensure accuracy with content ande1uipment

  • 7/23/2019 dos&donts in technical writing

    35/121

    Muestions?

    End your presentation with a simple

    1uestion slide to8

    $nvite your audience to as 1uestions

    Provide a visual aid during 1uestion

    period Avoid ending a presentation a#ruptly

  • 7/23/2019 dos&donts in technical writing

    36/121

    /ae $t Big

  • 7/23/2019 dos&donts in technical writing

    37/121

    This is a good title size

    Verdana 40 point A good subtitle or bullet point size

    Verdana 32 point

    Content text should be no smaller thanVerdana 24 point

    This font size is not recommended for content. Verdana 2 point.

    9ont Si:e9ont Si:e

    T*e larger; t*e +etter. )ee+er; your slidesust +e reada+le; even at t*e +ack of t*eroo.

  • 7/23/2019 dos&donts in technical writing

    38/121

    Dont %

    9ont Si:e9ont Si:e

    What does this say? Garamond Font, Italic, Bold 12pt.

    T*is is very diFpt)

    Go one will #e a#le to read this) 5ill "ans =ont, Condensed Bold, >pt

    Com#ining small !ont si0es with #old oritalics is not recommended8

    "mall !onts are oay !or a !ooter, such as8

  • 7/23/2019 dos&donts in technical writing

    39/121

  • 7/23/2019 dos&donts in technical writing

    40/121

    /ae it Big K*extL

    *his is Arial >

    *his is Arial >

    *his is Arial F

    *his is Arial

    *his is Arial D

    *his is Arial FF

  • 7/23/2019 dos&donts in technical writing

    41/121

    /ae it Big K*extL

    *his is Arial >

    *his is Arial >

    *his is Arial F

    *his is Arial

    *his is Arial D

    *his is Arial FF

    Too Sall

    / $ Bi KH

  • 7/23/2019 dos&donts in technical writing

    42/121

    /ae $t Big KHow toEstimateL

    .oo at it !rom N !eet away

    $ ft

  • 7/23/2019 dos&donts in technical writing

    43/121

    9onts9onts

    =ont "tyle "hould #e 6eada#le

    6ecommended !onts8Arial, *ahoma,

    Veranda"tandardi0e the =ont *hroughout

    *his presentation is in Ta*oaTa*oa

    Do %

  • 7/23/2019 dos&donts in technical writing

    44/121

    9onts9onts

    Dont Sacri=ce )eada+ility forStyle

    Dont Sacri=ce )eada+ility forStyle

    Dont Sacri=ce )eada+ility

    for Style Dont Sacri=ce )eada+ility for

    Style

    Dont %

  • 7/23/2019 dos&donts in technical writing

    45/121

    >eep "t Siple

    9O#TS9O#TS

  • 7/23/2019 dos&donts in technical writing

    46/121

    >eep "t Siple ?Tet@

    *oo manycolors

    *oo*ooMany=ontsand Styles

    *he D x N ruleGo more than D lines per slide

    Go more than N words per line

    Whil h d k d d id i l

  • 7/23/2019 dos&donts in technical writing

    47/121

    While hard work and good ideas are essential to success, your

    ability to express those ideas and get others to join you is just

    as important. Much of this verbal expression will be one on

    one or in small groups, but periodically you will be involvedin more formal and public speaking in front of larger numbers.

    If this thought makes you nervous, you are not alone. Many

    speakers lack the skills and confidence to make effetcive

    presentations. We have all been victims of speakers who put

    us to sleep. Despite knowing how ineffective many speakers

    are, many of us have found that, despite the best intentions,

    we havent fared much better. We knew the topic and the

    ideaswere written down, but the presentation still didnt go

    well. Was it the way you delivered the presentation! Was itbecause the audience didnt seem interested!

  • 7/23/2019 dos&donts in technical writing

    48/121

    $ha% &as &r'n(&i%h %ha%)

  • 7/23/2019 dos&donts in technical writing

    49/121

    Ieep $t "imple K*extL

    $nstructional *echnology8A complex integrated processinvolving people, procedures, ideas,

    devices, and organi0ation, !oranaly0ing pro#lems and devising,implementing, evaluating, andmanaging solutions to those pro#lems

    in situations in which learning ispurposive and controlledKH/6" 'th ed)L

    %oo detailed !

  • 7/23/2019 dos&donts in technical writing

    50/121

    Ieep $t "imple K*extL

    A process

    involving people, procedures O tools

    !or solutions

    to pro#lems in learningKH/6" 'th ed)L

    *ns%ruc%i'nal +echn'l'(y,

    &uch Sim'ler

  • 7/23/2019 dos&donts in technical writing

    51/121

    Aaps and "talicsAaps and "talics

    DO #OT !SE 455 A4P"T45 5ETTE)S /aes text hard to read

    Conceals acronyms

  • 7/23/2019 dos&donts in technical writing

    52/121

    Use a TemplateUse a Template

    3se a set !ont and colorscheme)

    Diferentstylesaredisconcertingto theaudience.

    !ou "ant the audience to focuson "hat #ou present$ not the"a# #ou present.

  • 7/23/2019 dos&donts in technical writing

    53/121

    Ieep $t "imple KPictureL

    Art wor may distract your audience

    Ar%is%ry d'es n'% subs%i%u%e -'r c'n%en%

  • 7/23/2019 dos&donts in technical writing

    54/121

    Ieep $t "imple K"oundL

    "ound efects may distract too

    se s'und 'nly &hen necessary

  • 7/23/2019 dos&donts in technical writing

    55/121

    Ieep $t "imple K*ransitionL

    *his transition is annoying, notenhancing

    /Appear/ and /isappear/ are be%%er

  • 7/23/2019 dos&donts in technical writing

    56/121

    5iit 4niation5iit 4niation

    3se the same animationthroughout the entire presentation

    3sing more than one can #e verydistracting

    *he audience will only see the

    animation and not the messageyou;re trying to get across

    %%

    8a%Dont

    i i i i5i it 4 i ti%

  • 7/23/2019 dos&donts in technical writing

    57/121

    5iit 4niation5iit 4niation

    3se the same animationthroughout the entire presentation

    3sing more than one can #e verydistracting

    *he audience will only see the

    animation and not the messageyou;re trying to get across

    %%

    Do

    %

  • 7/23/2019 dos&donts in technical writing

    58/121

    Ieep $t "imple KAnimationL

    $ ft

    %oo distracting !

  • 7/23/2019 dos&donts in technical writing

    59/121

    Ieep $t "imple KAnimationL

    $ ft

    Sim'le ( to the 'oint

  • 7/23/2019 dos&donts in technical writing

    60/121

    /ae $t Clear

    /ae $t Clear

  • 7/23/2019 dos&donts in technical writing

    61/121

    /ae $t ClearKCapitalisationL

    A.. CAP$*A. .E**E6" A6E

  • 7/23/2019 dos&donts in technical writing

    62/121

    /ae $t Clear K=ontsL

    "anseri! B"eri! Z

    )usyclear

  • 7/23/2019 dos&donts in technical writing

    63/121

    3se the "ame 8ackground8ackgroundon Each "lide

    Do %%

  • 7/23/2019 dos&donts in technical writing

    64/121

    Dont%

  • 7/23/2019 dos&donts in technical writing

    65/121

    CCoolloorrss

    6edsand orangesare high9energy #ut can #e di@cult tostay !ocused on)

    5reens,#lues,and #rownsaremellower, #ut not as attentiongra##ing)

    6edsand5reenscan #e di@cultto see !or those who are color#lind)

  • 7/23/2019 dos&donts in technical writing

    66/121

    4void T*ese Ao+inations

    Examples85reen on Blue

  • 7/23/2019 dos&donts in technical writing

    67/121

    CCoolloorrss

    :hite on dar #acground should not#e used i! audience is more than !taway)

    *his set o! slides is a good example)ou can read the slides up close)

    *he !urther away you get, the harder itis to read)

    *his is a good color com#ination i!viewed on a computer)

    A dar #acground on a computer

    screen reduces glare)

    CCoolloorrss

  • 7/23/2019 dos&donts in technical writing

    68/121

    CCoolloorrss

    .arge Hall Events

    Avoid C*iteC*iteBacgrounds

    *he white screen can #e+linding in a dar room

    Dark SlidesDark Slideswith 5ig*t5ig*tAolored TetAolored Tet:or Best

    Dont

  • 7/23/2019 dos&donts in technical writing

    69/121

    TheThe CCoolloorrWheelWheel

    Colors separated #yanother color arecontrasting colorsKcomplementaryL

    Ad4acent colors harmoni0ewith one another K5reenand ellowL

    Colors directly opposite oneanother are said to C.A"H

    Clashing colors providereada+ility

    OrangeOrangeon8lue8lueDo %

  • 7/23/2019 dos&donts in technical writing

    70/121

    /ae $t Clear KComplementL

    3se contrasting colors

    1i(h% 'n dar s dar 'n li(h%

    se c'pleen%ary c'l'rs

    +hese c'l'urs c'pleen%

  • 7/23/2019 dos&donts in technical writing

    71/121

    /ae $t Clear KComplementL

    3se contrasting colors

    1i(h% 'n dar s dar 'n li(h%

    se c'pleen%ary c'l'rs

    +hese c'l'urs d' n'% c'pleen%

    BackgroundBackgroundAAoolloorrss

  • 7/23/2019 dos&donts in technical writing

    72/121

    *his is a good mix o!colors) 6eada#leQ

    gg%emember& %eadabilit#' %eadabilit#' %eadabilit#'

    *his is a #ad mix o!colors) .ow contrast)3nreada#leQ

    *his is a good mix o!

    colors) 6eada#leQ

    *his is a #ad mix o!colors) 4void +rig*t

    colors on w*ite.3nreada#leQ

  • 7/23/2019 dos&donts in technical writing

    73/121

    /ae $t Clear KColorsL

    3se contrasting colors

    .ight on dar vs dar on light

    3se complementary colors

  • 7/23/2019 dos&donts in technical writing

    74/121

    /ae $t Clear KContrastL

    3se contrasting colors

    .ight on dar vs dar on light

    3se complementary colors

    l'& c'n%ras%

    hi(h c'n%ras%

  • 7/23/2019 dos&donts in technical writing

    75/121

    /ae $t Clear KContrastL

    3se contrasting colors

    .ight on dar vs dar on light

    3se complementary colors

    +his is li(h% 'n dar

  • 7/23/2019 dos&donts in technical writing

    76/121

    /ae $t Clear KContrastL

    3se contrasting colors .ight on dar vs dar on light

    3se complementary colors

    +his is dar 'n li(h%

  • 7/23/2019 dos&donts in technical writing

    77/121

    /ae $t Clear K"i0eL

    "i0e implies importance

    l K i L

  • 7/23/2019 dos&donts in technical writing

    78/121

    /ae $t Clear K"i0eL

    "i0e impliesimportance

    Cl K l i L

  • 7/23/2019 dos&donts in technical writing

    79/121

    /ae $t Clear K=ocal PointsL

    =ocal points direct attention

    / $ Cl K= l P i L

  • 7/23/2019 dos&donts in technical writing

    80/121

    /ae $t Clear K=ocal PointsL

    =ocal points direct attention

  • 7/23/2019 dos&donts in technical writing

    81/121

    /ae sure the audiencecan read themQ

    $rap*s and A*arts$rap*s and A*arts

    $rap*ics and A*arts$rap*ics and A*arts

  • 7/23/2019 dos&donts in technical writing

    82/121

    Avoid using graphics that are di@cult to read) $n this example, the#right colors on a white #acground and the small !ont mae the graphhard to read) $t would #e very di@cult to see, especially in the #ac o!a room)

    (

    Dont %

    *his graph contains too much in!ormation in an

  • 7/23/2019 dos&donts in technical writing

    83/121

    *his graph contains too much in!ormation in anunreada#le !ormat)

    0

    Dont %

    *his is a good, reada#le ta#le) *a#les, especially large

  • 7/23/2019 dos&donts in technical writing

    84/121

    g p y gones, should #e placed on a separate slide)

    *+- ri #- I/&0S restarted, e1loo' controlcontinues

    *+"" &on " /hange to mounting cu' control

    *+"2 %ue 2* 3eturn to e control, ilter wheel test)egins

    *+"* 4ed 55 Increase control tem'erature to allowfor 6" 7 8ariations

    *+"5 %hur 95 Begin dar:s e8ery 2rdor)it

    *+"9 ri $* ;< test 8isit = /ontrol tem' 6#.5 7

    Do %

    = lli . 7# d

  • 7/23/2019 dos&donts in technical writing

    85/121

    =alling .eaves 7#served

    /hristchurch ;unedin 4ellingtonJanuary ,52","2* *,"2,95* 2,#2*,59*

    e)ruary ,#$>,*59 ",2*5,59$ 9,">,"2*

    &arch $,"2*,$$> 9,59$,"2 9,#2*,$>9

    ?'ril 9,#->,>-$ #,>$#,-5* $,-*#,#-9

    &ay >,#29,>-$ #,2*5,2-* *,>59,*59

    June 9,>*,2*5 9$>,#-5 *,"2,959

    July >,>-#,2*5 5,2*$,-2* >,>>5,$>9

    ?ugust >,9$*,"2* >,#$,# $,"2#,#-5

    Se'tem)er *,#2",#*5 >,-"2,"2- -,-5#,*->

    0cto)er ",9#>,#-9 -,-*5,>-# 5,5-9,#-9

    o8em)er 5,>9*,#2* *$>,#"2 9,9$>,"5

    ;ecem)er ","2*,"2 -,52", 2,#*5,95*

    %oo detailed !

    = lli . i /illi

  • 7/23/2019 dos&donts in technical writing

    86/121

    =alling .eaves in /illions

    In #9

    /hristchurch ;unedin 4ellingtonJanuary * 2

    e)ruary " 9

    &arch $ 9 9

    ?'ril 9 # $

    &ay > # *

    June 9 # *

    July > 5 >

    ?ugust > > $

    Se'tem)er * > -

    0cto)er " - 5

    o8em)er 5 # 9

    ;ecem)er " - 2

    &uch Sim'ler

    = lli .

  • 7/23/2019 dos&donts in technical writing

    87/121

    =alling .eaves

    %oo detailed !

    = lli .

  • 7/23/2019 dos&donts in technical writing

    88/121

    =alling .eaves

    &uch Sim'ler

  • 7/23/2019 dos&donts in technical writing

    89/121

    *hese are exampleso!

    good graphs, withniceline widths and goodcolors)

    Good GraphGood Graph

    Do %

    A*arts and $rap*sA*arts and $rap*s

  • 7/23/2019 dos&donts in technical writing

    90/121

    A*arts and $rap*sA*arts and $rap*s

    Dont

    A*arts and $rap*sA*arts and $rap*s

  • 7/23/2019 dos&donts in technical writing

    91/121

    A*arts and $rap*sA*arts and $rap*s

    1&

    (

    ,

    -

    /

    6

    #ort*#ort*

    4erica4erica

    Europe 4ustralia

    Mode A

    ode 8

    ode A

    Do %

    IllustrationsIllustrations

  • 7/23/2019 dos&donts in technical writing

    92/121

    IllustrationsIllustrations

    3se only when needed, otherwise they#ecome distracters instead o!communicators

    *hey should relate to the message andhelp mae a point

    As yoursel! i! it maes the message

    clearer "imple diagrams are great communicators

    Do %

  • 7/23/2019 dos&donts in technical writing

    93/121

    Dont %

  • 7/23/2019 dos&donts in technical writing

    94/121

    Be Progressive

    *ypes o! $nstructional *ools

  • 7/23/2019 dos&donts in technical writing

    95/121

    /om'le@ity of Interactions

    &odeo

    f

    Instru

    ction

    Indi8idual Pair Arou'

    ;irectInstruction

    AuidedInuiry

    ;isco8eryCearning

    "ndividual"nstructive

    Tools

    "ndividualAonstructive

    Tools

    SocialAonstructive

    Tools

    SocialAounicative

    Tools

    "nforational Tools

    *ypes o! $nstructional *ools

    %oo many in one go!

    *ypes o! $nstructional *ools

  • 7/23/2019 dos&donts in technical writing

    96/121

    /om'le@ity of Interactions

    &odeo

    f

    Instru

    ction

    Indi8idual Pair Arou'

    ;irectInstruction

    AuidedInuiry

    ;isco8eryCearning

    "ndividual"nstructive

    Tools

    "ndividualAonstructive

    Tools

    SocialAonstructive

    Tools

    SocialAounicative

    Tools

    "nforational Tools

    *ypes o! $nstructional *ools

    Progressi8e (

    thus focused

    3nderstanding *echnology

  • 7/23/2019 dos&donts in technical writing

    97/121

    3nderstanding *echnology

    =loppy dis

    3ser inter!ace

    CP3

    $J7 Error

    Bacup syste

    "o!tware

    /ouse

  • 7/23/2019 dos&donts in technical writing

    98/121

    3nderstanding *echnology

    =loppy dis

    3ser inter!ace

    CP3

    $J7 Error

    Bacup syste

    "o!tware

    /ouse

  • 7/23/2019 dos&donts in technical writing

    99/121

    3se Bullet Points to Cover3se Bullet Points to CoverComponents o! Each $deaComponents o! Each $dea

    5iit Eac* Slide to One5iit Eac* Slide to One

    "dea"dea

    /ae $t Clear K=ontsL

  • 7/23/2019 dos&donts in technical writing

    100/121

    /ae $t Clear K=ontsL

    Serif fonts are difficult to read on screen "anseri! !onts are clearer

    Italics are difficult to read on screen

    Gormal or +old!onts are clearer

    3nderlines may signi!y hyperlins

    $nstead, use colorsto emphasise

    /ae $t Clear KGum#ersL

  • 7/23/2019 dos&donts in technical writing

    101/121

    /ae $t Clear KGum#ersL

    3se num#ers !or lists withse1uence=or example8

    How to put an elephant into a !ridge?

    >) 7pen the door o! the !ridge

    ) Put the elephant in) Close the door

    /ae $t Clear KGum#ersL

  • 7/23/2019 dos&donts in technical writing

    102/121

    /ae $t Clear KGum#ersL

    How to put a girafe into a !ridge?

    >) 7pen the door o! the !ridge

    ) *ae out the elephant

    ) Put the girafe in

    F) Close the door

    BulletsBullets

  • 7/23/2019 dos&donts in technical writing

    103/121

    BulletsBullets

    Ieep each #ullet to > line, at the most

    .imit the num#er o! #ullets in a screen to D,F i! there is a large title, logo, picture, etc)

    *his is nown as +cueing

    ou want to +cue the audience on whatyou;re going to say

    Cues are a a #rie! +preview 5ives the audience a +fraework to #uild upon

    BulletsBullets (con )(con )

  • 7/23/2019 dos&donts in technical writing

    104/121

    BulletsBullets (con.)(con.)

    $! you crowd too much text, theaudience won;t read it

    *oo much text loos #usy and is hard toread

    :hy read it, when you;re going to tell themwhat it says?

    7ur reading speed does not match ourlistening speedR hence, they confuseinstead o! reinforce

    /ae $t Clear KBulletsL

  • 7/23/2019 dos&donts in technical writing

    105/121

    /ae $t Clear KBulletsL

    3se #ullets to show a list without Priority

    "e1uence

    Hierarchy, -))

    Points to )ee+erPoints to )ee+er

  • 7/23/2019 dos&donts in technical writing

    106/121

    Points to )ee+erPoints to )ee+er

    .imit each slide to > idea

    .imit each #ullet point to only a !ew words

    to avoid long sentences that go on and onQ .imit animation *oo much animation can

    #e distracting) Be consistent with animationand have all text and photos appear on the

    screen the same way each time) *here aremany animation modes to choose !rom, #utit is #est to use 4ust one throughout)

    Do not do t*is%5iit 8ullet Points

    To a few words

    Points to )ee+erPoints to )ee+er

  • 7/23/2019 dos&donts in technical writing

    107/121

    Points to )ee+erPoints to )ee+er

    Ieep #ullet points #rie!

    3se the same #acground !oreach slide

    3se dar slides with light

    colored text in large halleventsDo %

    Avoid the +All :ord "lideAvoid the +All :ord "lide

    Dont

  • 7/23/2019 dos&donts in technical writing

    108/121

    Avoid the All :ord "lideAvoid the All :ord "lide

    Another thing to avoid is the use o! alarge #loc paragraph to introduceyour in!ormation) Attendees do notliketo have what is on the screen,read to t*ever#atim) "o, pleaseuse short, #ulleted statements and

    avoid typing out your wholepresentation on to the slides) Also, itis di@cult !or some to listen and read

    a large amount o! text at the same

  • 7/23/2019 dos&donts in technical writing

    109/121

    *o mae a slide stand out,*o mae a slide stand out,

    change the !ont, #acground,change the !ont, #acground,

    or add animation)or add animation)

    YOUYOU

  • 7/23/2019 dos&donts in technical writing

    110/121

    YOUYOU

  • 7/23/2019 dos&donts in technical writing

    111/121

    Be Consistent

    Be Consistent

  • 7/23/2019 dos&donts in technical writing

    112/121

    Be Consistent

  • 7/23/2019 dos&donts in technical writing

    113/121

    Be Consistent

  • 7/23/2019 dos&donts in technical writing

    114/121

    Be Consistent

  • 7/23/2019 dos&donts in technical writing

    115/121

    Be Consistent

  • 7/23/2019 dos&donts in technical writing

    116/121

    Be Consistent

  • 7/23/2019 dos&donts in technical writing

    117/121

    Be Consistent

  • 7/23/2019 dos&donts in technical writing

    118/121

    Be Consistent

  • 7/23/2019 dos&donts in technical writing

    119/121

    $n "ummary

    Big "imple

    Clear

    Progressive

    Consistent

    *ips !or Presenting

  • 7/23/2019 dos&donts in technical writing

    120/121

    *ips !or Presenting

    .imit the num#er o! slides

    slides per minute is the maximum

    Practice moving #etween slides) Be prepared !or technical

    di@culties

    Avoid the use o! Sashy transitions)*his is *77 SashyQ

    "ome =inal :ords

  • 7/23/2019 dos&donts in technical writing

    121/121

    "ome =inal :ords

    Communication is the ey *ext to support the communication

    Pictures to simpli!y complex concepts

    Animations !or complex relationships

    Tisuals to support, not to distract

    "ounds only when a#solutelynecessary