Your submission must represent your original work and understanding of the course material. Most performance assessment submissions are automatically scanned through the WGU similarity checker. Students are strongly encouraged to wait for the similarity report to generate after uploading their work and then review it to ensure Academic Authenticity guidelines are met before submitting the file for evaluation. See Understanding Similarity Reports for more information.
Grammarly Note:
Professional Communication will be automatically assessed through Grammarly for Education in most performance assessments before a student submits work for evaluation. Students are strongly encouraged to review the Grammarly for Education feedback prior to submitting work for evaluation, as the overall submission will not pass without this aspect passing. See Use Grammarly for Education Effectively for more information.
Microsoft Files Note:
Write your paper in Microsoft Word (.doc or .docx) unless another Microsoft product, or pdf, is specified in the task directions. Tasks may not be submitted as cloud links, such as links to Google Docs, Google Slides, OneDrive, etc. All supporting documentation, such as screenshots and proof of experience, should be collected in a pdf file and submitted separately from the main file. For more information, please see Computer System and Technology Requirements.
You must use the rubric to direct the creation of your submission because it provides detailed criteria that will be used to evaluate your work. Each requirement below may be evaluated by more than one rubric aspect. The rubric aspect titles may contain hyperlinks to relevant portions of the course.
A. Choose one of the case studies from the “Case Studies” file in the Supporting Documents for Task 2 at the bottom of this page, and then analyze your chosen case study by doing the following:
1. Analyze your chosen case study using one of the eight systems archetypes this course covers in Section 2, Lesson 2.
2. Submit an accurately completed systems archetype diagram (sometimes referred to as a causal loop diagram) that matches the details of your chosen archetype and chosen case study.
Note: You can create your diagram using one of the templates from the “Task 2 Diagram Templates” file in the Supporting Documents below.
3. Summarize the problem(s) in your chosen case study by explaining how the parts of your case study relate to one another through your chosen archetype and the changes that occur within the overall system.
B. Acknowledge sources, using in-text citations and references, for content that is quoted, paraphrased, or summarized.
Note: Sources are NOT required for this task, but if sources are used, they must be acknowledged and cited appropriately. Fake, non-existent, or AI-generated sources are not acceptable.
C. Demonstrate professional communication in the content and presentation of your submission.
File Restrictions
File name may contain only letters, numbers, spaces, and these symbols: ! - _ . * ' ( ) File size limit: 200 MB
File types allowed: doc, docx, rtf, xls, xlsx, ppt, pptx, odt, pdf, csv, txt, qt, mov, mpg, avi, mp3, wav, mp4, wma, flv, asf, mpeg, wmv, m4v, svg, tif, tiff, jpeg, jpg, gif, png, zip, rar, tar, 7z