Dear OSU colleagues,

Please help!  We are working to develop a new information service through OSU to provide people in Oregon and beyond with practical information about pest management and pesticide risk reduction.

Innovative challenge video

insert video here

Show your support for this project by completing this quick web form. 

Your name, position title and organization will be listed as a “Project supporter.

Summary

This “shovel ready” initiative is at the core of OSU’s educational mission and will help to establish OSU as the go-to information service and community organizer for high-quality information (in English and Spanish) to help people solve pest problems and reduce the risk of pesticides to people and the environment.

See the Fundraising Case Statement and Postcard for more information about the plan to implement this exciting advancement of OSU’s outreach mission.

Where we need help!

Project plan and budget

With financial support from a consortium of agencies from the Portland area and in-kind contributions from OSU units (College of Agricultural Sciences, Integrated Plant Protection Center, and Pollinator Health Program) we are planning to implement the project in phases.

  1. July 2017 – December 2017.  Conduct inclusive engagement process to help finalize the content and evaluation plans for this online information service.
  2. Years 1 and 2. Develop base technology and content in English and Spanish including pesticide risk reduction displays, content types, and database construction.
    • Watershed

Diversity, Equity, and Inclusion

As a design-informed process, we seek feedback from a range of diverse stakeholders to ensure this educational resource will be easy-to-use helping clients to find and understand content that is written in simple language with abundant pictures, line drawings, and other visual information.  Content will be displayed in both English and Spanish.

Funding status

Work plan and timeline

WorkCostFunding neededPledged funds
Inclusive engagement feedback from stakeholders for year 1$175,000FundedContracts from Metro and EMSWCD + In-kind from
Project management0.5 FTE for 4 yearsOSU College of Agricultural Sciences
Technology $200,000$50,000$30,000 from Pollinator Health; $75,000 from EMSWCD; $45,000 from Metro
Pesticide risk reduction$650,000
Pollinator health$30,000$30,000 from Pollinator Health10 content pages
Animal pests$30,000Funded10 content pages
Household pests35 content pages
How to horticulture guides40 content pages
Weed management140 content pages
Plant problems390 content pages
Maintenance per year

Questions for the innovative community

Specific details on inclusive engagement process to collect feedback from diverse participants.  How to recruit contracted community groups?  How to select groups to represent diverse communities?  Can someone at OSU help facilitate the inclusive engagement

Community supported fundraising:  Am I dreaming?

More here….


Supporting documents

Learn more about this important project:

Note: All text and images are for example only.

June 2016 Project Report

  • Stakeholder Requirements Report
    • Pesticide risk reduction communications plan
    • Site development plan
    • Content development plan
    • Technology development plan
    • Review process
    • Site maintenance plan
    • Marketing plan
    • Evaluation plan
    • Appendix 8: Sample content pages
    • Appendix 9: Content outline
  • Discovery Process (Appendix 1 – Appendix 7)
    • Appendix 1: Discovery process participation
    • Appendix 2: Focus group notes
    • Appendix 3: Initial online survey (Anonymous survey results)
    • Appendix 4: Initial online survey (Non-anonymous survey results)
    • Appendix 5: Follow-up online survey of stakeholder requirements
    • Appendix 6: Focus group for pesticide risk reduction communications
    • Appendix 7: Background demographic research
Print Friendly, PDF & Email

Leave a reply

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> 

required