TOOL #65. HOW TO USE VISUAL AIDS AND PRESENT QUANTITATIVE DATA 1. INTRODUCTION Many interventions deal with a complex range of issues and highly technical subject matter. Illustrations and visual aids can provide both expert and non-expert readers with a clear overview of the problems and their drivers, policy objectives and solutions, as well as the different steps in the analytical process. This tool presents three visual aids which are particularly relevant for policy interventions: problem trees, objective trees and intervention logic diagrams. These tools can help illustrate complex ideas and facilitate common understanding and better communication both inside the Commission and with external stakeholders. The text below also presents tips on how to present quantitative data clearly. 2. PROBLEM TREES What are problem trees? A problem tree is a highly effective communication tool that helps to demonstrate the need for intervention. It is used to visualise the identified problems, the interactions between these problems, their underlying drivers and likely consequences. The output is a graphical presentation of problems arranged according to ‘causes’ and ‘effects,’ joined by a core, or focal, problem. The problem tree should provide a simplified but robust representation of the reality. It also encourages a logical, comprehensive and coherent narrative and structure to the analytical process and report. How to create problem trees The graphs can be created in MS Word, Excel, equivalent open-source tools or specialised software such as DoView, MS Visio, Smart Draw or Lucidchart. Box 1 shows an example on disclosure of non-financial and diversity information by certain large companies and groups (amending Council Directives 78/660/EEC and 83/349/EEC) 766 . The links between the problems, their drivers and the consequences can be clearly seen. For example, poor quality financial information is a problem that is caused, inter-alia, by a lack of incentive for companies to disclose such information. Problem trees can also usefully illustrate what is outside the scope of the EU intervention; for instance because not all of the problem(s) can or should be addressed by EU level action. The example in Box 2 on the initiative on e-invoicing in public procurement 767 illustrates this: 766 http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:52013SC0127&from=EN 767 http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:52013SC0222&from=EN
12
Embed
TOOL #65. HOW TO USE VISUAL AIDS AND PRESENT QUANTITATIVE DATA · TOOL #65. HOW TO USE VISUAL AIDS AND PRESENT QUANTITATIVE DATA 1. INTRODUCTION Many interventions deal with a complex
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
TOOL #65. HOW TO USE VISUAL AIDS AND PRESENT QUANTITATIVE DATA
1. INTRODUCTION
Many interventions deal with a complex range of issues and highly technical subject
matter. Illustrations and visual aids can provide both expert and non-expert readers with a
clear overview of the problems and their drivers, policy objectives and solutions, as well
as the different steps in the analytical process.
This tool presents three visual aids which are particularly relevant for policy
interventions: problem trees, objective trees and intervention logic diagrams. These tools
can help illustrate complex ideas and facilitate common understanding and better
communication both inside the Commission and with external stakeholders. The text
below also presents tips on how to present quantitative data clearly.
2. PROBLEM TREES
What are problem trees?
A problem tree is a highly effective communication tool that helps to demonstrate the
need for intervention. It is used to visualise the identified problems, the interactions
between these problems, their underlying drivers and likely consequences. The output is
a graphical presentation of problems arranged according to ‘causes’ and ‘effects,’ joined
by a core, or focal, problem. The problem tree should provide a simplified but robust
representation of the reality. It also encourages a logical, comprehensive and coherent
narrative and structure to the analytical process and report.
How to create problem trees
The graphs can be created in MS Word, Excel, equivalent open-source tools or
specialised software such as DoView, MS Visio, Smart Draw or Lucidchart.
Box 1 shows an example on disclosure of non-financial and diversity information by
certain large companies and groups (amending Council Directives 78/660/EEC and
83/349/EEC)766. The links between the problems, their drivers and the consequences can
be clearly seen. For example, poor quality financial information is a problem that is
caused, inter-alia, by a lack of incentive for companies to disclose such information.
Problem trees can also usefully illustrate what is outside the scope of the EU
intervention; for instance because not all of the problem(s) can or should be addressed by
EU level action. The example in Box 2 on the initiative on e-invoicing in public
Intervention logic for health and nutrition claims
DRIVERS PROBLEMS General
OBJECTIVES Operational OBJECTIVES
INPUTS: Actions by
public authorities, food business operators, EFSA
OUTPUTS
RESULTS
Lack of truthful, clear, reliable and useful information for consumer on the nutritional status of foods
Foods contain false health claims and thus mislead the consumer
Problems with the free circulation of foods bearing nutrition and health claims in the Internal Market
No level playing field for food business operators for making health and nutrition claims on foods
High level of consumer protection from untruthful and misleading claims and facilitating consumers' healthier food choices
Improve the free movement of foods bearing nutrition and health claims within the Internal Market
Guarantee legal certainty for food business operators on the use of nutrition and health claims
Ensure the same level of scientific evidence for the substantiation of nutrition and health claims
Ensure that only authorised nutrition and health claims may be used on the EU market
Ensure that nutrition and health claims are coherent with nutritional advice
Regulatory framework requiring scientific substantiation of nutrition and health claims
Absence of scientific criteria for making nutrition and health claims on foods
Different rules governing the use of nutrition and health claims made on foods in different Member States
A harmonised list of permitted nutrition claims
Conditions for the use of nutrition and health claims
Restriction of claims on alcoholic beverages
Nutrient profiles the establishment of nutrient profiles
A harmonised list of authorised health claims
Ensure fair competition in the area of foods bearing nutrition and health claims
Procedure for the establishment of the list of authorised health claims by the collection of national lists by Member States, scientific evaluation by EFSA, adoption of the list of authorised health claims by Commission
Procedure for authorisation of new health claims via application by Food Business Operators, scientific evaluation by EFSA, authorisation by Commission
- Harmonised use of nutrition and health claims
- Better alignment of nutrition and health claims with nutritional advice by public health authorities
- Increased trust of consumer in nutrition and health claims
- Reduction of misleading nutrition and health claims on foods marketed in the EU
- Smoother functioning of the internal market
- Legal certainty for food business operators when using health and nutrition claims
- Fair competition in the area of foods bearing nutrition and health claims by creating a level playing field for food business operators
5. PRESENTING QUANTITATIVE DATA
How to present quantitative data?
Data can be presented in the text, in a table, or pictorially as a chart, diagram or graph.
Any of these may be appropriate for demonstration. Detailed tables should be put in an
annex, with a summary in the main text for demonstration purposes. In general the
following is a guide to presenting numerical data:
Text alone should not be used to convey more than three or four numbers.
Sets of numerical results should usually be presented as tables or graphs: (a) well-
presented tables and graphs can concisely summarise information which would be
difficult to describe in words alone; (b) on the other hand, poorly presented tables and
graphs can be confusing or irrelevant.
The text should always include mention of the key points in a table or graph. If it does
not warrant discussion it should not be there. You should ensure the message in the text
is consistent with that in the table.
There are two main types of graph:
• Line graphs can show more detail than bar charts. They should be used when the
horizontal axis represents a continuous quantity (such as time).
• When the horizontal axis is a qualitative factor - such as countries, products, etc. -
bar charts are natural.
Tables used for demonstration purpose are intended to be assimilated quickly by the
reader. They should be clear and well-presented and reduce numbers to relatively few
significant digits.
It is preferable not to use overly large tables: (a) if the information is all necessary, split it
into manageable components; (b) omit any column which can be readily calculated from
data in other columns. Less relevant categories can be combined.
344
Box 7. Tables versus graphs
In general, tables are better than graphs for giving structured numeric information. For
instance:
In general, graphs are better than tables for indicating trends, making comparisons, or
showing relationships.
Good practice
Tables and graphs should be self-explanatory: the reader should be able to understand
them without detailed reference to the text; users may well pick things up from tables or
graphs without reading the whole text.
The titles of the tables/graphs should be informative
Rows and columns of tables or axes of graphs should be clearly labelled: what is