570 likes | 822 Views
Tips for the presentation of data Presentation by: Astrid Marschatz UNDOCO, DevInfo Project Manager DevInfo v6.0 training workshop Geneva, 7-11 December 2009. Why do we want to present data?. Why do we want to present data?. To portray and describe facts To communicate information
E N D
Tips for the presentation of data Presentation by: Astrid Marschatz UNDOCO, DevInfo Project Manager DevInfo v6.0 training workshop Geneva, 7-11 December 2009
Why do we want to present data? • To portray and describe facts • To communicate information • To advocate for issues and persuade audiences • To engage readers/viewers • It is essential for presentations of data to be • clear • informative • self-explanatory • pleasant in appearance
The optimal presentation of data depends partially on …. • The type of data (e.g. text or numeric, categorical or binary) • The amount of data and the space available • The type of media (printed, PowerPoint, etc.) • The audience • The message to be conveyed
Benefits of tables • Display information in a clear and orderly manner • Good for large amounts of information and detailed data Source: TransMONEE 2005
Benefits graphs • Graphs can display information in a clear, effective and visually appealing manner • Graphs help to show • relative distributions • disparities between groups • relations between indicators (correlation) • trends over time
Graphs help to show relative distributions Source: InfoUNICEF Argentina. Source: Tajik GenderInfo
Graphs help to show disparities between groups Source: CEE CIS Regional MDG. Source: CEE CIS Regional MDG.
Graphs help to show relations between indicators Source: MDG Info 2009. Source: MDGInfo 2009.
Graphs help to show trends over time Source: MDGInfo 2009. Source: MDGInfo 2009.
Benefits maps ARGENTINA Population size, 2001 • Maps can display information in a clear, effective and visually appealing manner • Maps help demonstrate how data vary geographically Source: InfoUNICEF Argentina.
Tips for preparing clean, comprehensible data tables • Table titles should be concise and descriptive, presenting the reader/viewer with a clear idea of • the table’s content • the population included • the reference period • E.g. “Share of adultsaged 15 years and older living with HIV, who are women, 1990, 2002, 2006 (Percentage)” • Columns and rows should have a heading/stub identifying the data presented
Tips for preparing clean, comprehensible data tables • The unit of measure should be mentioned either in the title of the table or in the column/row headings/stubs • For clarity, row/column arrangement should follow a standard (natural or logical) order, e.g. alphabetical, geographical, by magnitude • The use of decimal points within tables must be consistent • Numeric values should be right-justified • The source of data must always be specified
Table hard to read. Units? Location? Source?
Colored cells for easy interpretation of data Source: DevInfo Armenia PRSP-MDG. Source: DevInfo Armenia PRSP-MDG.
No special row arrangement Rows arranged alphabetically Rows arranged by data value Source: CEE CIS Regional MDG Source: CEE CIS Regional MDG Source: CEE CIS Regional MDG
Tips for preparing clean, comprehensible graphs • Graphs should be visually appealing and easy for readers/viewers to comprehend • Graphs take up space so they should illustrate only important points • Do not use graphs if you have too few or too many values, or values show little variation • Choose a clear graphical display • The most appropriate type depends partly on the number of categories to be represented and their relative size • Graphs should be understandable by themselves, i.e. the title and subtitle should refer to • the content • the population • the reference period
Tips for preparing clean, comprehensible graphs (cont.) • For clarity, arrangement should follow a natural or logical order, e.g. alphabetical, geographical, by magnitude • Redundant features such as excessive gridlines and labels or unnecessary 3-D effects should be avoided, since they crowd the plot area and risk distracting the reader/viewer • All axes should be properly labeled. The unit of measurement for each axis must be clear, and tick marks and gridlines included where necessary • Axis scales should start with the minimum value. If scale breaks are used, these should be marked with a symbol • The source of data must always be specified
Wrong type of graph for data Source: CEE CIS Regional MDG
Wrong type of graph for data Source: MDGInfo 2009.
Axis break should be very visible!! == Source: MDGInfo 2009
Wrong type of graph for data Source: MDGInfo 2009.
Different units on same axis Source: MDGInfo 2009.
No special column arrangement Source: InfoUNICEF Argentina. Columns arranged alphabetically Source: InfoUNICEF Argentina. Columns arranged by data value Source: InfoUNICEF Argentina.
Unnecessary gridlines or data labels Source: MDGInfo 2009.
Excessive gridlines Source: MDGInfo 2009.
Tips for preparing clean, comprehensible data maps • They should be visually appealing and easy for readers to comprehend • Maps take up space so they should illustrate only important points • Maps should be understandable by themselves, i.e. titles should refer to the content, the population, and the reference period • Maps should be accompanied by a legend, and by labels when necessary • The source of data must always be specified
SERBIA – VOJVODINA Population density (persons per sq km), General practitioners (per 1000 population) and Hospital beds (per 1000 population Too many themes Population density General practitioners Hospital beds Source: DevInfo 5.0 Srbija Serbia
SELECT COUNTRIES OF ASIA AND EUROPE Telephone lines, 2002-2004 Per 100 population Too many data categories Source: UNICEF, SOWC 2007.
SELECT COUNTRIES OF ASIA AND EUROPE Telephone lines, 2002-2004 Per 100 population Source: UNICEF, SOWC 2007.