<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>Writing Helpful Recommendations by Kathy Tally</title>
      <link>https://padlet.com/ktally97/QualityMatters</link>
      <description></description>
      <language>en-us</language>
      <pubDate>2016-12-29 18:50:38 UTC</pubDate>
      <lastBuildDate>2017-01-05 21:48:05 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url></url>
      </image>
      <item>
         <title>EXAMPLE</title>
         <author>ktally97</author>
         <link>https://padlet.com/ktally97/QualityMatters/wish/144882737</link>
         <description><![CDATA[<div>When I looked at the assignments in your course, while everything was very well organized<strong> (BALANCED)</strong>, I was not able to find clear explanations on the requirements for learner interactions. SRS 5.4 states that "the requirements for learner interaction are clearly stated" (<strong>SRS 5.4 is cited</strong>). In order to meet expectations for SRS 5.4, the Annotations suggest that you provide specific expectations for learner interaction to make it easier for the learner to meet your expectations <strong>(SPECIFIC)</strong> For example, you might include a statement in your syllabus that instructs students to log into the course 3-5 times per week and to be sure to make their first discussion post by Thursday at 5 p.m. and their replies by Sunday no later than 11:59 p.m. <strong>(CONSTRUCTIVE, MEASURABLE</strong> and <strong>SENSITIVE)</strong>. It would also be helpful to include any specific expectations with each assignment regarding your expectations for learner interaction to ensure their success on each assignment. For more details on how to meet SRS 5.4, reading the Annotations in the Rubric would be especially helpful.</div>]]></description>
         <enclosure url="" />
         <pubDate>2016-12-29 18:59:48 UTC</pubDate>
         <guid>https://padlet.com/ktally97/QualityMatters/wish/144882737</guid>
      </item>
      <item>
         <title>#3</title>
         <author></author>
         <link>https://padlet.com/ktally97/QualityMatters/wish/145607525</link>
         <description><![CDATA[<div>While the content of the text was of high quality, the font and background color made it a bit difficult to read. Standard 8.4 states that "the course design facilitates readability." The suggestions in the Annotations include the use of simple fonts that can be clearly distinguished from the background. For example, changing to a white background could improve contrast with the text, making it easier to read. Also, the headings and text are clearly discernible, however limiting the number of fonts on the page would further improve this.</div>]]></description>
         <enclosure url="" />
         <pubDate>2017-01-05 21:37:21 UTC</pubDate>
         <guid>https://padlet.com/ktally97/QualityMatters/wish/145607525</guid>
      </item>
      <item>
         <title>The information provided was very helpful, however, the text was difficult to read. The text and background tended to blend together which made for unreadable portions. According to SRS 8.4 Accessibility and Usability, the text should be clearly distinguishable from the background. By just changing the background or font size you could eliminate this issue.</title>
         <author></author>
         <link>https://padlet.com/ktally97/QualityMatters/wish/145607616</link>
         <description><![CDATA[]]></description>
         <enclosure url="" />
         <pubDate>2017-01-05 21:38:26 UTC</pubDate>
         <guid>https://padlet.com/ktally97/QualityMatters/wish/145607616</guid>
      </item>
      <item>
         <title>#3 :  There were many engaging illustrations, comments and content. However, the different sized fonts and type styles could distract from the content (SRS 8.4). Try keeping the font style and size the same throughout each document to &quot;increase readability&quot; and &quot;minimize distractions&quot; (SRS 8.4) from your wonderful content.</title>
         <author></author>
         <link>https://padlet.com/ktally97/QualityMatters/wish/145607629</link>
         <description><![CDATA[]]></description>
         <enclosure url="" />
         <pubDate>2017-01-05 21:38:38 UTC</pubDate>
         <guid>https://padlet.com/ktally97/QualityMatters/wish/145607629</guid>
      </item>
      <item>
         <title></title>
         <author></author>
         <link>https://padlet.com/ktally97/QualityMatters/wish/145607666</link>
         <description><![CDATA[<div>When I reviewed your course on Scuba Diving, I found the activities worthwhile and, for the most part, matched with the stated objectives. However,&nbsp; Outcome 2.2 emphasizes the importance of outcomes that can be easily measured. You might want to consider making objective your 2.6 a Goal for the course, rather than an objective (because it is a worthy goal. but not measurable in a course). Alternatively, you could reword it slightly, "I feel my ability to communicate with or understand&nbsp;&nbsp;dolphins is likely better as a result of this course." This way, a simple question could in theory query confidence in students'&nbsp;empathy and understanding of sea animals. <br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-01-05 21:38:56 UTC</pubDate>
         <guid>https://padlet.com/ktally97/QualityMatters/wish/145607666</guid>
      </item>
      <item>
         <title>It was very useful to read specific unit objectives in the intro of each unit.  I struggled, however, to understand how these objectives are measurable, for example, &quot;you will think differently as to the definition of democracy&quot;.  SRS 2.2 provides helpful guidance as to writing measurable objectives. You could break this objective into more measurable components, such as &quot;Upon completion of this unit, you will be able to definite the term democracy.&quot; You current objectives do lend themselves to more detailed measurements</title>
         <author></author>
         <link>https://padlet.com/ktally97/QualityMatters/wish/145607688</link>
         <description><![CDATA[]]></description>
         <enclosure url="" />
         <pubDate>2017-01-05 21:39:13 UTC</pubDate>
         <guid>https://padlet.com/ktally97/QualityMatters/wish/145607688</guid>
      </item>
      <item>
         <title>Recommendation 3</title>
         <author></author>
         <link>https://padlet.com/ktally97/QualityMatters/wish/145607704</link>
         <description><![CDATA[<div>The page content was thorough and well organized.  However, the use of pink Comic Sans font on a yellow background made it difficult to read.  SRS 8.4 states that "the course design facilitates readability."  In order to meet expectations of SRS 8.4 you should choose a more traditional font and choose a more readable color scheme.  For example, you might </div>]]></description>
         <enclosure url="" />
         <pubDate>2017-01-05 21:39:27 UTC</pubDate>
         <guid>https://padlet.com/ktally97/QualityMatters/wish/145607704</guid>
      </item>
      <item>
         <title>Loved the focus of your learning objectives.  But while the general focus was great, the language wasn&#39;t always measurable. (2.1, 2.2)  Of course, we all want our students to &quot;understand&quot;.  The difficulty there is that understanding is internal, we get at understanding by other methods.  Focus on language which demonstrates that understanding.  For example, instead of stating &quot;the student will understand these three points....&quot;  try &quot;the student will be able to explain these three points...&quot;  The ability to explain the ideas is usually how we measure understanding.  </title>
         <author></author>
         <link>https://padlet.com/ktally97/QualityMatters/wish/145607739</link>
         <description><![CDATA[]]></description>
         <enclosure url="" />
         <pubDate>2017-01-05 21:39:50 UTC</pubDate>
         <guid>https://padlet.com/ktally97/QualityMatters/wish/145607739</guid>
      </item>
      <item>
         <title>Great learning objectives , but it would be more helpful, think if you avoided the technical terms used</title>
         <author></author>
         <link>https://padlet.com/ktally97/QualityMatters/wish/145607834</link>
         <description><![CDATA[<div><br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-01-05 21:41:13 UTC</pubDate>
         <guid>https://padlet.com/ktally97/QualityMatters/wish/145607834</guid>
      </item>
   </channel>
</rss>
