Showing posts with label Storytelling. Show all posts
Showing posts with label Storytelling. Show all posts

Thursday, July 06, 2017

The Springboard: How Storytelling Ignites Action in Knowledge-Era Organizations (Book 6 of 30)

Title:  The Springboard: How Storytelling Ignites Action in Knowledge-Era Organizations
Author: Stephen Denning

The Springboard is an early book about storytelling as a tool within the KM discipline.  I'm sure there were lots of books about storytelling before that but it's THE book that raised the idea that knowledge management could be significantly boosted by leveraging the power of narratives.

There have been a few other books on the subject since then and the latest on my shelves is Putting Stories to Work, by Shawn Callahan.  This newer book has a broader focus on business storytelling and doesn't focus on the knowledge management applications but all the principles are the same.  In fact, I find that a broader business perspective is often necessary to effectively address challenges that are initially perceived as "KM challenges". The KM challenges don't become challenges in a vacuum.  They are challenges within a business environment, and organizational culture that is likely to affect all aspects of the organization.

Question:  Is it lunacy to tackle KM challenges without recognizing and addressing broader organizational issues?
Corollary question:  As a solo consultant, how much can I realistically tackle?

Personal Experience:  I've tried my hand at storytelling.  I've taken a couple of classes on the topic, I did a full series of storytelling talks through Toastmasters, and I'm still working on it.  In a few weeks, I'll be doing a presentation that has a storytelling feel to it.  I'll see if I can strengthen that element to make it more interesting.

I have written elsewhere about the use of didactic fiction and I've experimented a lot with that, to the point of writing an entire novel that was meant to be didactic.   Interestingly, Steve Denning followed this storytelling book with a piece of didactic fiction titled Squirrel Inc.: A Fable of Leadership Through Storytelling.  Case studies (fictional or not) are probably an easier way to convey key insights.

TO DO:
  • Add storytelling elements to the July 28th KMA presentation.  I already  know where the cliffhanger is.... 
  • Keep a record of "KM stories" based on my own experiences.  Create a special section (and tag) in my internal consulting wiki.
  • Explore how I treats stories when I consume them.  When reading new books, make a note of how stories are used to illustrate a point.  Do I typically read the stories or skip them to get to the point?  Is it like overly detailed descriptions in novels that I skip to get to the action?  Or do they really add value?

Saturday, February 05, 2011

KM Twitter Chats - Slow Motion Brainstorming on Storytelling

In the past couple of months, I've participated in a few Twitter chats run through the KMers group.  I haven't developed a strong pro or against attitude.  I like the idea of communicating with like-minded individuals who have similar professional interests but with whom I would otherwise have no contact through regular work-related tasks.  I still find them a little awkward.

Imagine a dozen people sitting around a table for a brainstorming session around a pre-determined topic. A facilitator welcomes everyone and starts up the conversation with a question. Imagine that instead of having to take turns to speak up, people are able to talk over each other, but everything is slowed down so that the participants are able to hear and comprehend what everybody else is saying.  There's a little more time to think about what to contribute to the conversation and you can respond to something that was said a minute ago rather than the last thing that was said without getting everyone totally confused.

I'll use the most recent KMers' chat on Corporate Storytelling and Knowledge Management as an example.

The 140-character limit forces has both advantages and disadvantages:
  • (+) You're not able to ramble on about an idea without making a point. If your 140 character message isn't clear on its own, people will just ignore it and move on quickly.

  • (-) Don't expect it to be more than a brainstorming session.  People will express ideas and share resources they're aware of, they may express agreement or ask for details, but there isn't time or space to go deep into anything.
  • (+/-) You're more inclined to turn your message into the equivalent of a movie tagline or a book logline. If your message is intriguing enough, you get a request for details.

  • (+/-) There is a "built-in" written record (transcript) of the conversation (keep that in mind when you're furiously typing a tweet).

  • (+) The conversation doesn't always end with the chat session.  Some participants in the chat may follow up with some additional thoughts or a summary of the chat in their blog (See Jeff Hester's blog post on Successful KM Storytelling).

  • (+) The chat's hashtag (#KMers) can be used at any time (beyond the specific hour of scheduled chat) to reach out to this particular KM community even if all the members of the community aren't among your followers.
Storytelling Resources: