The Inverse relation between risks and benefits : the role of affect and expertise
<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd">
<record>
<leader>00000cab a2200000 4500</leader>
<controlfield tag="001">MAP20150030016</controlfield>
<controlfield tag="003">MAP</controlfield>
<controlfield tag="005">20150930122935.0</controlfield>
<controlfield tag="008">150916e20150701esp|||p |0|||b|spa d</controlfield>
<datafield tag="040" ind1=" " ind2=" ">
<subfield code="a">MAP</subfield>
<subfield code="b">spa</subfield>
<subfield code="d">MAP</subfield>
</datafield>
<datafield tag="084" ind1=" " ind2=" ">
<subfield code="a">7</subfield>
</datafield>
<datafield tag="100" ind1="1" ind2=" ">
<subfield code="0">MAPA20150015020</subfield>
<subfield code="a">Sokolowska, Joanna</subfield>
</datafield>
<datafield tag="245" ind1="1" ind2="4">
<subfield code="a">The Inverse relation between risks and benefits</subfield>
<subfield code="b">: the role of affect and expertise</subfield>
<subfield code="c">Joanna Sokolowska, Patrycja Sleboda</subfield>
</datafield>
<datafield tag="520" ind1=" " ind2=" ">
<subfield code="a">Although risk and benefits of risky activities are positively correlated in the real world, empirical results indicate that people perceive them as negatively correlated. The common explanation is that confounding benefits and losses stems from affect. In this article, we address the issue that has not been clearly established in studies on the affect heuristic: to what extent boundary conditions, such as judgments¿ generality and expertise, influence the presence of the inverse relation in judgments of hazards. These conditions were examined in four studies in which respondents evaluated general or specific benefits and risks of affect-rich and affect-poor hazards (ranging from investments to applications of stem cell research). In line with previous research, affect is defined as good or bad feelings integral to a stimulus. In contrast to previous research, affect is considered as related both to personal feelings and to social controversies associated with a hazard. Expertise is related to personal knowledge (laypersons vs. experts) as well as to objective knowledge (targets well vs. poorly known to science). The direct comparison of the input from personal and objective ignorance into the inverse relation has not been investigated previously. It was found that affect invoked by a hazard guides general but not specific judgments of its benefits and risks. Technical expertise helps to avoid simplified evaluations of consequences as long as they are well known to science. For new, poorly understood hazards (e.g., stem cell research), expertise does not protect from the perception of the inverse relation between benefits and risks. </subfield>
</datafield>
<datafield tag="650" ind1=" " ind2="4">
<subfield code="0">MAPA20080545260</subfield>
<subfield code="a">Riesgos</subfield>
</datafield>
<datafield tag="650" ind1=" " ind2="4">
<subfield code="0">MAPA20080553357</subfield>
<subfield code="a">Beneficios</subfield>
</datafield>
<datafield tag="650" ind1=" " ind2="4">
<subfield code="0">MAPA20080591182</subfield>
<subfield code="a">Gerencia de riesgos</subfield>
</datafield>
<datafield tag="650" ind1=" " ind2="4">
<subfield code="0">MAPA20080615130</subfield>
<subfield code="a">Relación costo-beneficio</subfield>
</datafield>
<datafield tag="700" ind1="1" ind2=" ">
<subfield code="0">MAPA20150015778</subfield>
<subfield code="a">Sleboda, Patrycja</subfield>
</datafield>
<datafield tag="773" ind1="0" ind2=" ">
<subfield code="w">MAP20077000345</subfield>
<subfield code="t">Risk analysis : an international journal</subfield>
<subfield code="d">McLean, Virginia : Society for Risk Analysis, 1987-2015</subfield>
<subfield code="x">0272-4332</subfield>
<subfield code="g">01/07/2015 Volumen 35 Número 7 - julio 2015 , p. 1252-1267</subfield>
</datafield>
</record>
</collection>