This case study should be based on your individual experience and draw from your personal, professional, or academic lives. They should be succinct (1,000 words or less) and convey a case that is directly related to the topic of discussion in class. Case studies should loosely follow the following format.
- Catchy Title: Puns and plays on words encouraged
- Background (6-8 sentences): This should include your subjective experience and dialogue about the situation (contextual) and objective information that helps define the environment or the case.
- Problem (2-3 sentences): What problem or conflict are you discussing? Why is the problem or conflict relevant?
- Solution/Intervention (3-6 sentences): What was done to remedy the problem? How was the intervention designed and administered?
- Outcome (3-6 sentences): What was the outcome after the problem or encounter? Was there change? Did the change last? What was learned about the solution? Would you change the solution or intervention?
- Reflection (2-4 sentences): How is it directly related to the reading and/or content topic for the week?
- February 6th
The groups will propose an official scope of work (SOW) to the organization they are assisting. An SOW is a simple formal agreement between two parties, meant to outline the process and deliverables of a given project. Regardless of the type of project your interdisciplinary group is conducting, your SOW document should contain similar information including; introduction/objectives, scope of the project, period performance, schedule of deliverables, expenses and acceptance. See attachment A for a template.
- February 27th
Each member of the group will write a brief (500 words or less) plan for the project experience. At the end of the semester you will be asked to reflect on that plan and the interdisciplinary experience. Each group members IIP should be attached to the SOW when submitted as an assignment. The IIP should minimally include the following:
- What will you, personally, contribute to the project? What tasks will you complete, what role(s) will you fulfill for the group?
- What do you hope to gain from the experience? This might include skills you hope to develop, expertise you hope to gain about a particular problem domain or industry, valuable connections or relationships you hope to make, and/or new perspectives or insights you hope to gain.
- What challenges do you anticipate?
- What strategies will you use to overcome challenges?
- How do you define interdisciplinary success for your group?
- February 27th
The group will develop a Power Point presentation for the 3rd All-hands meeting. The presentation should include: (1) description of the site (demographics, location, type etc); (2) Description of health and safety considerations specific to site (may be pulled from site conversation and/or OSHA 300 logs) (3) details of your agreed upon SOW (4) description of how your project is interdisciplinary; and (5) a single specific question for class discussion. The presentation will be no more than 10 minutes in duration with 5 minutes for discussions.
There should be no more than 2-3 presenters per group. The individuals who deliver the first presentation will not present in the final class so that all team members get an opportunity. The presentation will be graded as a group project by faculty mentors based on presenter ability to address the above sections and timeliness (attachment B). The individual oral presentations will be graded on clarity of communication (attachment C).
- February 27th
The group will prepare a final Powerpoint presentation for the class. The presentation should include: (1) a review of your site and project SOW (2) methodology used to gather information and findings (3) final recommendations to your site; (4) learning points: (what worked, what didn’t, what to do differently). This presentation should be no more than 15 slides and last no more than 15 minutes. The presentation will be graded as a group (attachment B). There should be no more than 2-3 presenters per group. The individual who presents in the first presentation will not present in the final class (attachment C).
- May 8th
The group will prepare a final report with references. The final report should be professionally structured to follow an outline similar to a white paper and adequately address the SOW. A typical white paper includes: an abstract or executive summary (no more than 300 words), introduction, problem definition, methods, data/information discovered, high-level recommendations, detailed recommendations, and summary/call to action. See attachment D for more details.
- May 8th
Each member of the group will write a brief (2-3 page) personal reflection on the project experience. Although teams are encouraged to debrief about the project as a group, this is an individual assignment and each person’s work should be unique. Your reflection should answer the following questions, in at least a paragraph each:
- What did you, personally, contribute to the project? What tasks did you complete, what role(s) did you fulfill?
- What were your group’s successes? What aspects of the project went well?
- What were your group’s challenges? If you had the project to do over, what would you do differently?
- What did you gain from the experience? This might include skills you developed, expertise you gained about a particular problem domain or industry, valuable connections or relationships you made, and/or new perspectives or insights you gained.
- What development needs did you identify for yourself as a result of this experience? As you look ahead to your future role as an occupational and environmental health professional, what 1-2 skills or knowledge domains do you most need to focus on in the near future?
- What advice would you give to next year’s Interdisciplinary Seminar students about how to approach this course?
- What would you change to make the course a better learning experience?
- May 15th