A weed resistance management game: a teaching tool

Research output: Contribution to journalArticlepeer-review

1 Scopus citations

Abstract

BACKGROUND: This article provides instructions and materials to moderate an interactive resistance management game. The game is designed to generate discussion about the challenges and possibilities of coordinating resistance management activities among groups of farmers. The game has been successfully applied in classroom settings, extension workshops, and at professional weed science meetings. Research has found farmers often perceive the success of their own resistance management may be thwarted if their neighbors are not adequately managing resistance as well. This can lead to negative ‘tragedy of the commons’ outcomes. RESULTS: In past applications of the game exercise, participants have often responded in ways consistent with similar studies in experimental and behavioral economics. This includes dividing benefits evenly (even though this is not a requirement of the game) or treating one-time transactions as potentially repeated exchanges. Player behavior may also be greatly influenced by their attitudes toward monetary risks. CONCLUSION: The game allows participants to explore ways to overcome the tragedy of the commons and illustrates the roles of information sharing and economic incentives in finding solutions. It also allows participants to experiment with bottom-up voluntary approaches toward resistance management as an alternative to top-down regulatory approaches.

Original languageEnglish (US)
Pages (from-to)2376-2382
Number of pages7
JournalPest management science
Volume74
Issue number10
DOIs
StatePublished - Oct 2018

Keywords

  • common pool resources
  • game
  • herbicide resistance
  • regulation
  • resistance management
  • role-playing

ASJC Scopus subject areas

  • Agronomy and Crop Science
  • Insect Science

Fingerprint

Dive into the research topics of 'A weed resistance management game: a teaching tool'. Together they form a unique fingerprint.

Cite this