{"id":2504,"date":"2013-10-04T11:00:09","date_gmt":"2013-10-04T10:00:09","guid":{"rendered":"http:\/\/www.idenk.com\/blog\/?p=2504"},"modified":"2013-10-03T19:14:22","modified_gmt":"2013-10-03T18:14:22","slug":"getting-it-facilitating-understandingin-timely-chunks","status":"publish","type":"post","link":"http:\/\/www.idenk.com\/blog\/getting-it-facilitating-understandingin-timely-chunks\/","title":{"rendered":"Getting it: facilitating understanding,in timely chunks"},"content":{"rendered":"<p>A friend was saying this week how she now \u2018gets\u2019 her iPhone. A shop assistant was describing a feature, and she just understood it. That wasn\u2019t always the case for her.<\/p>\n<p>In the late 1990s \u2018Knowledge Management\u2019 was at the peak of its fad cycle. \u00a0And at that time I heard US leadership expert Peter Senge explain a model of learning he finds helpful. He described two sorts of knowledge transfer:<\/p>\n<p>A) First The Syntactical. This is where colleagues share many common assumptions \u2013 so there is a basic level of understanding that allows easy communication of meaning. Like two chess grandmasters, one person can merely outline a new idea (e.g. on a move), and the other person gets it. They tend to be equally motivated \u2013 and connected with sufficient trust and respect to value the other point of view too. This peer to peer approach is seen in \u2018communities of practice\u2019 where there is curiosity and enough common ground to allow the use of shorthand \u2013 so things move fast. In Syntactical knowledge transfer \u2018straight\u00a0transmission is easy and often swift \u2013 however, even dry talks and dense articles engage becasuse the content is so meaningful and shared.<br \/>\nB) Or The Transformative. Here a shared understanding needs to be built \u2013 and this requires relationships to be developed, different points of view understood and the meaning of words to be explained. The quality of the experience (whether a talk or a workshop session) really matters. It takes time.<\/p>\n<p>As moderators and facilitators, we are concerned with both. However, it is easy for us (or bosses or clients) to make assumptions about how fast things need to move, assumptions\u00a0that might not quite reflect the needs of the group.\u00a0 Our desire for pace\u00a0may be due to the ambition we have of completing certain things by the end of the day and our learning style\/needs, not the groups.<\/p>\n<p>When designing an event we need to think of the time\u00a0required to ensure each session achieves its learning goals. Thinking and asking \u201cis this a time for syntactical or transformative learning\u201d really helps.<\/p>\n<p>So when considering the design of an agenda, here are a few pointers:<\/p>\n<p>1) A facilitated day tends to be made up of four 75-90 minute chunks \u2013 interspersed with breaks (i.e. arrival, chunk 1, coffee, chunk 2, lunch etc). Think of each of these chunks as the length of a film, many sports matches or a sleep cycle. After an hour and a half or so the human body needs some movement and transition. There is a natural cycle and rhythm at work \u2013 and we do well to remember that.<\/p>\n<p>2) Remember a little known Russian psychologist for the <a href=\"http:\/\/en.wikipedia.org\/wiki\/Suspense#Zeigarnik_effect \" rel=\"nofollow\">Zeigarnik effect <\/a>\u2013 the legacy from Bluma Zeigarnik is that the human mind finds it helpful to be reminded what is about to happen, regularly and especially at the end of one chunk (before the break and heading into the next chunk!). This creates a helpful suspense between the parts \u2013 when we state what is coming up, others start to anticipate it and move to wanting it \u2013 a bit like a trailer in a cinema.<br \/>\n3) Think about how long each part within a chunk is likely to need \u2013 what will it take for the group to understand a presenters point or work through an issue? This is where knowledge transmission A or B comes in: syntactical learning means participants are ready to apply ideas much more quickly. Think of this as about how long you would allow for a scene in a film if you were a director or scriptwirter. Or, as a home viewer, are you going for fast forward or slow-mo!<br \/>\n4) Even when you allow longer\u00a0because you know\u00a0transformative learning is needed, long talks are not required.\u00a0 We see in the popularity of TED talks (at less than 20 minutes each) that any input is probably best being kept short before a group can reflect, speak and apply. Do you\u00a0practise the key sandwich principles for adult learning? Do make sure: first, you start with where the group is at; before taking any input\/talk;, then ensuring\u00a0lots of time to consider and trial and review the application of what has been learnt.<br \/>\n5) And a <a href=\"http:\/\/sethgodin.typepad.com\/seths_blog\/2013\/10\/on-going-over-your-time.html\" rel=\"nofollow\">recent blog<\/a>, argues that even if a presenter has a short slot, keep it shorter than scheduled anyhow! Do you rehearse your speakers? Do you know how to timekeep a contributor in an relaxed manner, stopping a session in a way that seems calm and respectful (and in tune with interest of the group)?<\/p>\n<p>I hope that made sense \u2013 I sort of assumed an type A audience\u2026did I get that right for you?<\/p>\n<p>All the best in applying the ideas\u2026these relate to the Ps of participants, principles, potential risks and process in our <a href=\"http:\/\/www.idenk.com\/blog\/the-13-ps-for-perfect-meetings\/\" rel=\"nofollow\">13Ps<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A friend was saying this week how she now \u2018gets\u2019 her iPhone. A shop assistant was describing a feature, and she just understood it. That wasn\u2019t always the case for her. In the late 1990s \u2018Knowledge Management\u2019 was at the peak of its fad cycle. \u00a0And at that time I heard US leadership expert Peter [&hellip;]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[135,26],"tags":[47,76],"_links":{"self":[{"href":"http:\/\/www.idenk.com\/blog\/wp-json\/wp\/v2\/posts\/2504"}],"collection":[{"href":"http:\/\/www.idenk.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.idenk.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.idenk.com\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"http:\/\/www.idenk.com\/blog\/wp-json\/wp\/v2\/comments?post=2504"}],"version-history":[{"count":4,"href":"http:\/\/www.idenk.com\/blog\/wp-json\/wp\/v2\/posts\/2504\/revisions"}],"predecessor-version":[{"id":2512,"href":"http:\/\/www.idenk.com\/blog\/wp-json\/wp\/v2\/posts\/2504\/revisions\/2512"}],"wp:attachment":[{"href":"http:\/\/www.idenk.com\/blog\/wp-json\/wp\/v2\/media?parent=2504"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.idenk.com\/blog\/wp-json\/wp\/v2\/categories?post=2504"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.idenk.com\/blog\/wp-json\/wp\/v2\/tags?post=2504"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}