<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>Group Problem Solving  by Truman Solverud</title>
      <link>https://padlet.com/tsolverud/ynp2jzi7785r</link>
      <description>An assignment for SPED 854</description>
      <language>en-us</language>
      <pubDate>2018-11-10 21:59:20 UTC</pubDate>
      <lastBuildDate>2023-03-16 02:46:42 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url>https://padlet-assets.s3.amazonaws.com/icons/Templeball.png</url>
      </image>
      <item>
         <title>Brainwriting</title>
         <author>tsolverud</author>
         <link>https://padlet.com/tsolverud/ynp2jzi7785r/wish/302917548</link>
         <description><![CDATA[<div>- a strategy for group problem solving that is an alternative to open discussion.  I chose this illustration to represent this concept, because it symbolizes the generation of solutions that represent the expertise, experiences and opinions of the team rather than the loudest voice.  This approach involves each member of the group writing down several potential solutions to a problem.  The ideas are exchanged and then used as a catalyst for other ideas, until no new ideas emerge (Cook &amp; Friend, 2017).  In addition to ensuring that everyone's voice in the group is heard, this strategy encourages new perspectives and may be effective for emotional or sensitive issues.  I pulled this concept from this weeks readings as it is a practical practice that I can use in my work right away.<br><br><br><br><br></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/290093341/c0777aeab12739598f25cdb2a089f88a/group.jpg" />
         <pubDate>2018-11-10 22:31:39 UTC</pubDate>
         <guid>https://padlet.com/tsolverud/ynp2jzi7785r/wish/302917548</guid>
      </item>
      <item>
         <title>Implementing the Solution</title>
         <author>tsolverud</author>
         <link>https://padlet.com/tsolverud/ynp2jzi7785r/wish/302923316</link>
         <description><![CDATA[<div>- the step that always seems to get overlooked.  Once a plan has been decided upon, finalizing it, by summarizing the details, the criteria for success, and a method for evaluating the results, may end up being glossed over, due to the extensive conversation that often goes into discussing options.  In reality, this is the most important part of the conversation. Formalizing this step of the problem solving process through the use of a tool such as the problem solving responsibility chart will ensure that the team leaves the meeting with a clear common vision of the way foreward and what their role is in the implementation and evaluation of the solution (Cook and Friend, p. 124, 2017).  I chose this graphic which represents the steps of implementation and the fact that the process of putting a plan in place is as much of a team undertaking as the development of a solution.<br><br></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/290093341/e1510dac211e3b9806d9a25d5ce3c5a6/Screen_Shot_2018_11_10_at_5_07_55_PM.png" />
         <pubDate>2018-11-11 00:08:32 UTC</pubDate>
         <guid>https://padlet.com/tsolverud/ynp2jzi7785r/wish/302923316</guid>
      </item>
      <item>
         <title>Deciding Whether to Problem Solve </title>
         <author>tsolverud</author>
         <link>https://padlet.com/tsolverud/ynp2jzi7785r/wish/302924718</link>
         <description><![CDATA[<div>- is a provocative question! Being reflective and asnwering the questions, "Is this a problem that needs to be solved" or "Is this a problem I should be involved with solving". Whether or not a collaborative approach is appropriate, resources are available and the problem is worthy of the effort that will be required to solve it are also important considerations (Cook &amp; Friend, 2017). Considering these questions early and as you move through the problem solving process will ensure the integrity of the effort and maintain the commitment of the members of the team.  The visual of a teammember reflectively contemplating whether  group problem solving is an appropriate approach is the inspiration for the picture I used. <br><br></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/290093341/7aba9289b4e40de95d6a56818f33f868/question.jpg" />
         <pubDate>2018-11-11 00:34:14 UTC</pubDate>
         <guid>https://padlet.com/tsolverud/ynp2jzi7785r/wish/302924718</guid>
      </item>
      <item>
         <title>A Step By Step Approach</title>
         <author>tsolverud</author>
         <link>https://padlet.com/tsolverud/ynp2jzi7785r/wish/302926694</link>
         <description><![CDATA[<div>- when using group problem solving, will insure efficiency and effectiveness.  Methodically and intentionally working through the following steps will support the team in developing and implementing a solution:<br>1.  Identify the Problem<br>2. Generate Solutions<br>3. Evaluate Potential Solutions<br>4.  Select a Solution<br>5.  Implement<br>6.  Evaluate Outcomes and Adjust if Necessary (Cook &amp; Friend, 2017).<br>This collaborative process requires strong leadership and a foundation of respect and strong communication within the group. The picture below represents the step-by-step process that must be negotiated by the team in order to achieve their goal of the implementation of a solution.  If one step is missed the integrity of the process will be in jeopardy.<br><br><br><br><br></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/290093341/22f2e51bf816a259ce8faa9ec18379e2/aip_passo_a_passo.jpg" />
         <pubDate>2018-11-11 01:09:50 UTC</pubDate>
         <guid>https://padlet.com/tsolverud/ynp2jzi7785r/wish/302926694</guid>
      </item>
      <item>
         <title>Evaluating the Outcome</title>
         <author>tsolverud</author>
         <link>https://padlet.com/tsolverud/ynp2jzi7785r/wish/302928403</link>
         <description><![CDATA[<div>- the most important step, and perhaps a whole new problem solving process. Meeting to examine the outcome of the group's implemented solution, and determining if it was successful, partially successful or unsuccessful is the final step.  If ot fully successful, the group must then reflect on whether the solution was implemented with fidelity, if a different solution that the group examined might be more appropriate, or if they should go back to the drawing board and reexamine if the problem was identified correctly and start the process over.  I chose the graphic below because the magnifying glass represents the effort that must be put into evaluating results, and the book represents the data that outcome represents.  Intensive monitoring and data collection is key to the evaluation of any plan that is developed by group problem solving.</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/290093341/34f30492016cb7019e087eecf9072ee9/Screen_Shot_2018_11_10_at_6_33_59_PM.png" />
         <pubDate>2018-11-11 01:34:24 UTC</pubDate>
         <guid>https://padlet.com/tsolverud/ynp2jzi7785r/wish/302928403</guid>
      </item>
   </channel>
</rss>
