Category: knowledge sharing

Good Suggestions for “Fixing the Q&A” Session

whatsyourstoryerealitiesThere is a useful post on the HBR blog by  that is a good follow-on to yesterday’s post about webinars. Thomas talks about the mismatch between the intention for interaction with the audience, and the poor design of most Q&A sessions that happen after keynotes or talks. Here is a snippet, then I have some amplifications below.

Some solutions to the Q&A dysfunction already exist. Some hire a professional moderator or use software tools to crowdsource the questions. Others experiment with radically new ways to run events, such as the unconference movement. However, those solutions are often expensive or time-consuming to deploy, making them infeasible for many types of events. Here are four techniques that I’ve used with great results, and that can be deployed without any kind of preparation:

  1. Do an inverse Q&A. An inverse Q&A is when I the speaker pose a question to the audience, asking them to discuss it with the person sitting next to them. A good question is, “For you, what was a key take-away from this session? What might you do differently going forward?” People love the opportunity to voice their thoughts to someone and unlike the traditional Q&A, this approach allows everybody to have their say. It also helps them network with each other in a natural manner, which is something many conferences don’t really cater to.
  2. Ask for reactions, not just questions. When you debrief on the small-group discussion, insisting on the question format makes it awkward for the people who just want to share something. As you open the floor, specifically say “What are your reactions to all this? Questions are great, but you are also welcome to just share an observation, it doesn’t have to be in the form of a question.”
  3. Have people vet the questions in groups. An alternative to the inverse Q&A is to ask people to find good questions in groups. Simply say, “Please spend a minute or two in small groups, and try to find a good question or a reflection you think is relevant for everybody.” Then walk around the room and listen as people talk. If you hear an interesting reflection, ask them to bring it up during the joint discussion, or bring it up yourself.
  4. Share a final story after the Q&A. Given that even the best-run Q&A session is unpredictable, it is best to have the Q&A as the second-to-last element. I always stop the Q&A part a few minutes before the end, so I have time to share one final example before getting off the stage. That way, even if the Q&A part falls flat, you can still end your session with a bang instead of a fizzle.The above methods can help you turn any keynote into a better experience. What other techniques — ideally simple ones — have you seen or used?

via 4 Ways to Fix the Q&A Session – Thomas Wedell-Wedellsborg – Harvard Business Review.

The first thing I really want to amplify is the focus on questions – thinking about them and forming them more intentionally, both from the presenter and from the people formerly known as the audience.  Crap questions generate crap responses. People seeking to be heard often respond in kind with crap responses because they were so busy getting ready to speak, they weren’t listening. So we also see a relationship between crap questions and poor listening. As a speaker, it is your/mine/our job to bring value by offering good questions and to both role model good listening when we hand off the mic, and to make it easier for people to listen well.

How do we make it easier for people to listen well?

  • Present well. This is covered well other places, but if we are rambly (spell check suggested “brambly” which also fits!), unclear or just off point, we will have lost the audience well before the Q&A. Why not aim for having people SO EXCITED by the time you finish speaking…
  • ...so that the only solution is to let them have a conversation. Start with table or pair conversations so this energy can be unleashed, rather than squelched by passing a single mic and constricting/controlling that energy?
  • Harvest. The presenter’s job is then to harvest what was generated out of all that energy, and Thomas’ suggestions are spot on. You can also do post it note harvests, capture visually, among many options. The point here is you steward, you become of service.

Beyond the Webinar

The earthLet me confess right up front: I really don’t like webinars. Too often they feel “done unto me.” I am powerless, at the mercy of the organizers. I may have access to a chat room (Thank Goodness!) But more often than not, these are content delivery mechanisms with token participant interaction in the form of crowded Q&A segments or polls with varying degrees of relevance. What is worse is that I have been a perpetrator of these practices so I continue to try and change my evil ways.

Changing ingrained habits requires some reflection – of self and of the state of the practice of these so-called “webinars.”  Recently I had the chance to offer feedback on a webinar I experienced as a recording.  I’ve edited/generalized my thoughts to share. In a follow up post I’ll reflect on my own practice — this is where I need to cut to the bone!
1. Us/Them: It is logical for an organizer or organizing agency to want to  appear well prepared for sharing their work. We all like folks to know we “did our homework.” We get our slides spiffed up and appropriately formatted for the webinar tool we are given. We time our remarks. We practice speaking clearly and at an appropriate pace.

The challenge this presents is that the end product puts the speaker and/or the organization at the center. We create an us/them dynamic before the event even starts. Think about set ups where the only ones who can use the voice tool to communicate are the organizers. Those who bear the presentation file are in control of the message. The tool administrator(s) control the process (i.e determining that they speak for 60 minutes, then there is Q&A.)

The use of a one way style of presentation reinforces the power dynamics of the speaker/expert/organization as central, and everyone else as “audience.” All too often, the audience is never heard. Is that a good use of precious synchronous time? Why not send out a video or narrated PowerPoint? An online gathering is time better spent as a multi-directional mode of “being together” — even online. This does NOT diminish the importance and value of content we “deliver” to others. Here are some options to consider.

Options:

  • Move away from meetings that are primarily broadcast which holds control with the presenter. Sharing information is essential, but synchronous time should always have significant multi directional interaction. For my colleagues in international development, I think everyone has values of inclusiveness and shared participation. We have to “walk this talk” in webinars as well.
  • Small things can create or break down us/them.  For example don’t just show where you are on a map at the start of a webinar, add dots for all the participants and their locations. Better yet, use a tool that allows them to add their own dots. Help the group see not only you,  but “we” – all the people working together about something we all care deeply about.
  • Because we lack body  language online, it is useful to really scrutinize our language.From the wording in the slides and by the speaker, consider changes in language so that it is more inclusive of the participants.

 

2. Strive for  good practices for learning/engaging online. Webinars in general run the risk of being even less engaging than a dark room face to face with a long PowerPoint. There is a saying in the online facilitation world “A bad meeting F2F is a terrible meeting online.” So we need to be even more attentive to how we structure online engagements to reflect a) how adults learn b) the high risk of losing attention (especially due to multi tasking) and c) the cultural and power diversity inherent in your group. Quality content is important, but it alone is not a reason to use an interactive platform — you can deliver content in many ways. Choosing a synchronous mode, to me,  implies interaction.

Options:

  • Consider keeping online meetings to 60 minutes. If not, do a stretch break every at 30 and 60 minutes. Say “let’s take a 60 second break.” Stand up, stretch, look away from the screen and give your body a moment of respite. We’ll call you back in 60 (90-120) seconds (sometimes a bio break is useful!)
  • A useful rule of thumb is to break up information presentation with some means of audience engagement/participation every 7-15 minutes. Use polls, chat, “red/green/yellow” feedback mechanisms, hand raising, checking for understanding, etc. This may mean you have someone facilitating these other channels if it is too distracting for the host and speakers. (Over time it does get easier, but practice is critical!)
  • Take questions approximately every 15 minutes vs holding at end. People stop listening carefully and are thus less prepared to ask questions after longer periods of time. (They are also more prone to multitasking, etc.)
  • Don’t just deliver information – use narrative. Stories hold our attention better than a series of bullet points. In fact, ditch those boring slides unless you are using the printed information to make it easier for people coming from a different first language.
  • Deliver the useful content in a different manner and use the webmeeting entirely for questions and interactions. Send a recording introducing the team. Send a narrated PowerPoint about the topic. Keep these content packages smaller. For example, if you were trying to give an overview of a portfolio of projects, you could break it up into some sub packages. 1) about the team 2) strategy, 3) project descriptions, 4) monitoring and evaluation strategy, etc.
  • Secondary tip: Do not think of these information products as polished products — don’t waste energy overproducing. That sucks the human element out of it. Imperfection is a door to engagement… seriously. Moments of uncertainty, tough questions — these engage the participants.
  • Stay relaxed as a narrator and speak at useful pace for understanding, particularly for those who have English as a second (or third, fourth) language. Keep that human touch. Add little bits of personal information and affect. Be human.
  • Let participants ask question verbally, not just in chat if possible. While there are many technical complications and sometimes the burden of accents on unclear audio channels, voice brings again brings in that human element. (Video does too, but there are bandwidth considerations. When you can, consider using it.)
  • Encourage collective note taking in the chat room or with complementary tool. When people share this task, they listen more carefully and the begin to learn about each others strengths and insights as people add additional information or annotations.
  • When someone asks a question, note who asked the question. This helps everyone see that people are heard, even if the audio option is not practical (for various reasons, no mic, etc. )  At the end of the call, specifically thank by name those who asked questions to encourage the behavior for future interactions.
  • In Q&A sections, consider a visual to help people pay attention. Use the whiteboard for noting the questions, answers, links that refer to what has been spoken about, etc.

There are a few ideas. What are yours?

Also, here are some previous posts about similar issues:

Mirror Mirror, On the Wall: Learning in a Crowded Life

mirrorbyPhotoComiXonFlickrCC14 years ago I did my first overseas gig in Central Asia. I stayed with the project over three years including a number of trips to Armenia to work with the team on the ground. (See White-2005-Little) Ostensibly I was there to help facilitate learning around using online tools for community development, particularly in rural towns being connected via a school connectivity project. But in the end, what I realized was that my role was as a mirror for the team to see itself.

As we had our final closing circle for an After Action Review before the project began its transition away from the organization to the Ministry of Education, we started with the first question “What did we intend to do?” That was pretty easy. The project had a clear mandate, goals, and measurable intermediate outputs. We transitioned quickly into “What did we actually do.” There were the things we had dealt with, change, reformations of assumptions and operating conditions, etc. No big surprises.

When we got to the third question, “What did we learn?” we sat for a moment in silence, pondering. You could feel something change in the room. The concern that the Ministry would muck it all up, unspoken, but present. The acknowledgement of grief of having to let the program grow was palpable. Maybe even a sense of failure, fearing the transition was untenable.

Then one of the amazing women of the program opened her mouth and helped us begin. She said something to the effect of “Nancy Jan, you have helped me realize how much we have grown in our ability to really support change in our communities.” Then it began to flow, and the group unearthed first changes in themselves, the lessons they learned. From there insights about structural and environmental factors emerged in ways that were constructive for subsequent work – for the Ministry’s and their own. Something broke open. It was no longer a laundry list of things done.

The ability to learn lessons about projects, to surface them and analyze them with sufficient clarity starts with the ability to learn about ourselves. To reflect on our ways of working, of perceiving the work we do, of our assumptions and blind spots. This team had started with little appreciation of their own skills, their ability to influence their partners and stakeholders, and their deep creativity sprung from their even deeper commitment to their work. If anything, they hid their own light.

I’m currently working on two projects that are, in essence, about how we learn from our work. One is the development of a self-paced eLearning module on Experience Capitalization, which is a process for describing project work, extracting lessons and recommendations, creating communications products and channels for those lessons so they can be seen, adapted and used by others with similar interests and goals. How do we build our individual and organizational capacity to do that? My mirror role is to try and understand and interpret the content created by subject matter experts, and see it through novice eyes.

The second project is as a very peripheral participant helping a knowledge management initiative pick up clues to what is being learned about the learning in the project. How do we notice useful bits, pick them up, reflect on them and share them? The team leader has expressed a very open willingness to start with himself, which is rare and wonderful. So mirrors up!

I keep going back to that moment in Armenia, and the same element emerges. We often don’t (or can’t) see what is right in front of us, mostly because we are too busy, working too fast, and can’t seem to find the “mirror” to stop and look ourselves in the eye and reflect. We may lack some basic structure or affordances TO reflect. What if we took time to reinsert reflection and these affordances into our work? Would something change?

Is it that simple?

I don’t think it is that simple, or that learning from doing IS simple. But this pattern of finding a moment to “be heard” – even if by our own selves, is critical to both identifying and internalizing/applying learning. It is that moment of taking a breath before we do something new, something technical or challenging. Focus. Attention.

So back to the mirror. When you ask someone, heck, when you pay someone else to help you learn, you take the time to learn. One of those odd incentives that seem silly because of course we want to learn. But we don’t. That’s when the mirror role comes in very handy.

As much as I LOVE being the mirror (it is a fantastic role), it is not a sustainable strategy when learning becomes a matter of importance as it is in my work in international development. Think of the learning that is, or SHOULD be going on now with the Ebola epidemic.

I am going to write about this a few more times in the coming weeks and months to try and whittle down one or two things that are actionable, doable and can be motivated from within to leverage more learning from our work, and helping it connect with others who may be able to use our learning.

Image by PhotoComIX on Flickr, Creative Commons

Where is the Cooperation in International Development and Cooperation

Warning: The following was written in haste, has repetition and can very much stand a good edit. But if I don’t hit post, this won’t go out. Life is busy.

Earlier today my friend and respected KM/KS practitioner Ian Thorpe Tweeted a link to a consultancy announcement.

kmtoolkittweet

I blithely responded:

Now, I was pretty tough on Ian and did not offer any context. Later this morning he posted a really thoughtful blog post on the thinking behind his organization’s desire to have their own internal Knowledge Exchange Toolbox. I started to post a comment, but the comment grew so large I decided a post here was called for.

I’m going to quote a sizable chunk of his post and then my response. But if this interests you, please go read the whole thing.

But, I think there are actually a few good reasons to reinvent or at least adapt.

People working in an organization tend to have more trust, and are thus more likely to use something that has been specifically created for them and has some form of official endorsement. This sounds like “not invented here syndrome” – but it’s not quite that.

The advantages of developing your own toolkit (or platform, strategy, bibliography, taxonomy etc.) include:

  • It can be written in the kind of language (and jargon and buzzwords) people in the organization understand
  • It can include tools selected to meet the specific needs of the organization, and the tools selected (even when sourced from elsewhere) can be adapted and tailored to the organizational context.
  • The tools can be tested on real organizational problems and the feedback obtained can be used to improve them and help communicate them better.
  • The tools can go through a quality review and sign off process that the organization understands and respects.
  • The fact that the toolbox is developed together with internal as well as external expertise means that staff know who they can follow-up with for advice and support on when and how to use them.

Overall these points mean that there is a sense of organizational ownership of the toolbox meaning not only is it officially sanctioned, but also officially supported and adapted to what the organization needs.

Thanks for adding really useful context, Ian. I find your reasoning totally logical. I have also heard it many times at other organizations.

First, can we connect usage to the factors you noted above in the context of ownership? Has anyone objectively looked at how usage of such a tool matters if it is internal or external?

I strongly suspect usage is driven by other, less visible, more informal things like seeing other peers use the tools, having colleagues they value endorse or role model, etc. I don’t have data. But in considering this,  I wonder about our assumptions about

  1. the use of these toolkits in general, and
  2. the importance of the points you make toward use (and improvements going forward).

Or are we just masking or missing the deeper, underlying issues? I really don’t know and I’d really LIKE to know.

I confess, I get totally frustrated when my own clients hire me to do things that are already done. The KS Toolkit came out of that frustration after three separate clients asked for the SAME thing and the differentiating factor was not whether the tool was on a private intranet or public, but branding. Yes, branding. Does that change the value of the toolkit? Should it?  Now, that said, over time the existing Toolkit product needs improvement. And your focus on adaptation is to me SUPER IMPORTANT. The issue of how to create and improve cooperatively sourced products alone deserves another blog post. (Note to self). But lets go back to rationale for internal vs. cooperative, shared resources.

I think a lot of the points you make are right on, but I also worry about some of the underlying causes that make these ideas of “needing internal validation,” “our language” and stuff so important in a field like international development and cooperation. From where I sit, I thought our field has shared goals.   So why do we have these counterproductive insider, invented here, not invented here, we are different from everyone else, etc attitudes? What do they represent? Control? Power? Fear? Territoriality? Reliance on the status quo?

Do we really understand if and why we need our unique products? Or is our vision too limited to see both the value and possibility for, and the mechanisms to cooperatively create, use, and improve resources?

Let me get more specific and look at each of Ian’s reasons for a customized product.

  • It can be written in the kind of language (and jargon and buzzwords) people in the organization understand. Having a sense of identity and ownership is important. But reinforcing organizational buzzwords and jargon does not help wider cooperation in the development field, no? Why might we want to reinforce this behavior? Think of the “beneficiaries” as well. Doesn’t our insider language and jargon distance us from them? 
  • It can include tools selected to meet the specific needs of the organization, and the tools selected (even when sourced from elsewhere) can be adapted and tailored to the organizational context. This is a compelling argument for internal platforms. Curation, adaptation and tailoring are really useful “value added” to a toolkit. But why not do that adaptation in a public, cooperative platform where others can learn from what you do, particularly those closest to your organizational domains. Why not do it WITH those others? Hm, as I write this, I wonder about shifting from “organizational” context to “practice” or “domain” context. So if tool X is more useful in working with Y population, lets make sure all of us working with Y population have access to that tool adaptation and can contribute towards its ongoing improvement?
  • The tools can be tested on real organizational problems and the feedback obtained can be used to improve them and help communicate them better. I can’t figure out the value of this being internal to an organization. Again, it relates to the practice, no? The global public good here is pretty darn high…
  • The tools can go through a quality review and sign off process that the organization understands and respects. Why can’t this happen in a cooperative platform? Heck, it might even contribute to better interorganization practices as a whole? And who is the arbiter of quality at the tool level when we rarely seem to care or pay attention at the application level where the IMPACT happens, right?
  • The fact that the toolbox is developed together with internal as well as external expertise means that staff know who they can follow-up with for advice and support on when and how to use them.  Again, I can imagine this same value on a public/cooperative platform.

Adaptation is an important thing we ignore very often in KM. There is too much sense that replication and scaling are the solution. So I deeply respect this aspect of adaptation that I sense in Ian’s response.

My “yes, and” perspective  is that what you learn/do through adaptation is of value beyond your org. And insights come from beyond your org. And your org exists for public good, right? Why not build more nuanced structures that facilitate open, public, crowdsourced resources, ones that add that layers of adaptation – for example there are other orgs sharing UNICEF’s targets and goals who might also benefit from this need to improve tools.

I fully know that what I’m suggesting is not easy. We have learned through the KSToolkit.org that people DO have different needs, need the material organized or expressed differently. But those reasons don’t appear to be organizational. They appear to be driven by the users context and practice. And that these contexts and practices vary WITHIN organizations, and are often shared ACROSS organizations. And cooperatively creating and supporting a shared resource doesn’t fit into most organizational process or budgeting parameters, so when we see things like the KSToolkit.org we are seeing the work of committed individuals who make things happen, often in spite of their organizations. (And deep bow to all of you, including Ian who has been a toolkit supporter.)

I think there is a much larger, more valuable proposition of opening up some of this work across organizations and getting off the  focus on our organizations. Lets focus on our goals and the ultimate reason we are doing this. So every human being has the right to and access to food, clean water, housing, education and human dignity.

So what are the barriers? What is it we are really avoiding by sharing this “knowledge infrastructure?” Is it convenience? When we work for global public good, what is the cost of this “convenience?” What is keeping us from shifting towards more cooperative and networked structures which can tap a potentially broader and more diverse set of expertise, share the burden of refinement, adaptation, improvement and just simply reduce this recreation? We all need and benefit from the process of adapting and improving tools.  Many of the tools in a Knowledge Exchange toolkit will have relevance to wider audiences. At the same time, so much of what is in these toolkits is not rocket science. What IS rocket sciences is the organizational shifts and changes that actually enable people to USE this stuff. Toolkits are just a resource. And this opens another Pandora’s box for another blog post!

I’ll say it. Lets start breaking down more walls instead of using what is convenient and conventional to maintain the status quo. And a little starting point like KM and KS toolkits seems like an ideal laboratory to find new, cooperative, networked ways to maximize value and minimize waste. Let’s recreate and improve together. Otherwise we are supporting wheel reinvention.

And Ian, thanks for lighting me up to write about this today. You have helped me clarify my thinking. The next two things we need to consider is what it takes to cooperatively create global public goods (and a lot of good people have been doing some great work in other domains from which we can learn), and how to move the tools from toolboxes into practice!

via Why we sometimes need to reinvent the wheel | KM on a dollar a day.

Clay Shirky and “the collaborative penumbra”

Some words just catch us.

I was scanning this transcript of an interview with Clay Shirky (thank you Twitter network) and came across this quote:

So the collaborative penumbra around 3-D printing is a place where you don’t have to have someone who can do everything—from having the idea to making the mesh to printing it. You can start having division of labor. So you’ve got all of these small groups that are just working together like studios and still able to play on a world stage.

via The disruptive power of collaboration: An interview with Clay Shirky | McKinsey & Company.

I just loved the term, “collaborative penumbra.”

I continue to rabbit away at what has become my hobby research, how international development organizations plan for, pick, provision, monitor and evaluate their online collaboration platforms. What comes up again and again is that organizations have very limited ideas about the meaning and possibilities of collaboration. There is still this idea that it is composed of two things: document sharing and project management. And document sharing covers the territory of “knowledge sharing.” Sigh. I keep looking for useful anecdotes to demonstrate the rainbow of possibilities. But each example then points to the fact that this is a fundamental shift in the way work is done. That scares people. They like their “habitus” as Zaid Hassan talks about in his book, “The Social Labs Revolution.”

Here is another quote from the interview (emphasis mine):

“And all the way at the other end of the spectrum, you’ve got these collaborative environments where almost no one has to coordinate with anybody else. When I upload something to Thingiverse, or I make an edit on Wikipedia, it’s not like I need anybody else’s help or permission. So the collaborative range is expanding. The tight groups have more resources, and the loose groups can be much more loosely coordinated and operate at a much larger scale. And I think the people who think about collaboration want to know what’s happening to it, and the answer is everything.”

Go read the rest. There are more gems there… go to the source!