Date   

RealKM Magazine Award #awards

Arthur Shelley
 

Happy New Year KMers,

 

I hope that your festive season was full of shared experiences and rekindled relationships (proving that KM is a real science that has practical application even in our personal lives).

 

You may be aware that in December (in that year we do not wish to mention), a GOOD thing happened…

Real KM Magazine received a well deserved Knowledge Award from the Australian Society for Knowledge Management.

I wanted to share a few reflections on this service here (which I also did on KM4Dev, so apologies for cross-posting).

 

I would appreciate your considering this post to ensure Real KM magazine can be sustainable in the excellent service it provides and is recognised for…

Thanks… (neither Stephen nor Bruce asked me to write this or knew it was coming before I posted it):

 

RealKM Magazine is a shining example of genuine knowledge sharing that adds value to all readers.

Everyone in this forum will benefit from being a regular reader (and potentially a contributor).

 

Stephen Bounds (Founder) & Bruce Boyes (Lead writer and editor – both contributors here in this forum as well) deserve all the accolades they have received for the very hard work they invest, and continue to invest. They publish a credible (evidence based) and insightful (full of useful ideas and examples of good KM Practice) publication that is superior to some high cost commercial/academic publications.

 

The reason we benefit from this quality publication is Stephen & Bruce invest many more hours than they get paid for and this is not a sustainable (or fair) model. 

If each reader became a subscriber, even if only donating $1 per week (a fraction of the cost of a cup of coffee), the magazine could generate an even more comprehensive sharing and the people creating the value for you, could be more appropriately compensated for their effort. I personally financially patronise the initiative because I believe in what the magazine achieves for many. I encourage all KMers to think about reciprocity, respect and mutual value relationships

 

Mostly, we get what we deserve in life ... but with the advent of internet an unreasonable expectation “free extraction” mentality is becoming more common in society.

Societies like SIKM Leaders are a terrific source of Knowledge, because of a few people like Stan and his contributing friends investing time to assist others. This is great thing. However, not everyone can do this, which should not limit the range of ways we can acquire knowledge.

 

Of course we can get "Free information" – but it is a gamble on what you receive in an internet search. 

However ...

invest significant time to critically analyse the search output content to make informed judgement to separate outright lies from promotional propaganda from (potential) "truths" (they are all out there).

Then ...

verify the evidence behind the potential "truths" to determine how credible they are what the knowledge gaps & limitations are...

 

At this stage, you are far better served to subscribe to RealKM Magazine as this is the investment they do for you...

Surely this is worth making a contribution to...?

 

I reflect on the thinking that expects high quality services to be available free! 

Ask your local shops if you can pop in and grab anything you want - for nothing ...

Unlike your shops, RealKM Magazine just want to cover their costs of being a KM Sharing Role Model, not make a profit.

Please think about this, as unsustainable models eventually expire. 

Can you spare the cost of a coffee each month?

How much value can you create when you apply the received knowledge?

Would you share all you insights with everyone for no return? 

How much can you expect others to simply give you fir nothing?

 

If we want a fair sharing world/community (effectively a foundation principle of KM), we need to balance our contributions and receiving actions!

We are the culmination of the decisions we make – individually and collectively.

 

 

 

 

Regards

Arthur Shelley

Producer: Creative Melbourne

Author: KNOWledge SUCCESSion  Sustained performance and capability growth through knowledge projects

Earlier Books: The Organizational Zoo (2007) & Being a Successful Knowledge Leader (2009)

Principal: www.IntelligentAnswers.com.au 

Founder: Organizational Zoo Ambassadors Network

Mb. +61 413 047 408  Skype: Arthur.Shelley  Twitter: @Metaphorage

LinkedIn: https://www.linkedin.com/in/arthurshelley/

Free behavioural profiles: www.organizationalzoo.com

Blog: www.organizationalzoo.com/blog

Creative-Melbourne-Banner_2018_Final_Smaller

 

 


Re: Knowledge Management: Each man is my superior in that I may learn from him." #learning

Arthur Shelley
 

Thanks for the article share Bill.

The world improves when we see the learning as the key outcome rather than the physical outputs generated.

Whilst a project output (tangible deliverable) does have value, it is rarely more important than the learning, relationships and trust built (or destroyed if not well- led) by those involved.

 

Regards

Arthur Shelley

Producer: Creative Melbourne

Author: KNOWledge SUCCESSion  Sustained performance and capability growth through knowledge projects

Earlier Books: The Organizational Zoo (2007) & Being a Successful Knowledge Leader (2009)

Principal: www.IntelligentAnswers.com.au 

Founder: Organizational Zoo Ambassadors Network

Mb. +61 413 047 408  Skype: Arthur.Shelley  Twitter: @Metaphorage

LinkedIn: https://www.linkedin.com/in/arthurshelley/

Free behavioural profiles: www.organizationalzoo.com

Blog: www.organizationalzoo.com/blog

Creative-Melbourne-Banner_2018_Final_Smaller

 

 

From: main@SIKM.groups.io <main@SIKM.groups.io> On Behalf Of bill@...
Sent: Monday, 11 January 2021 7:08 AM
To: SIKM@groups.io
Subject: [SIKM] Knowledge Management: Each man is my superior in that I may learn from him.” https://linkedin.com/pulse/knowledge-management-each-man-my-superior-i-may-l

 

2021 provides an oppty to leverage what we can learn from others-better. Grateful if you would check out my latest article: Knowledge Management: Each man is my superior in that I may learn from him.” https://linkedin.com/pulse/knowledge-management-each-man-my-superior-i-may-learn-bill-kaplan

 

Watching CBS Sunday Morning today and it got me thinking about this through a KM lense.

 

Best

 

Bill

 

  

 

Learn more about the solutions and value we provide at www.workingknowledge-csp.com

 


Re: Lessons Learned Storage & Access #lessons-learned

Tom Barfield
 

David - based on the many responses this sounds like a topic that would benefit from a live discussion.  Would you be interested in having the community host a live peer assist discussion to focus on your question?  If so, I will work with others in the community to set this up.

Tom


Job Opening: Knowledge Manager in Mumbai #jobs

Stan Garfield
 

From Susan Inman, Global Director of Knowledge Management at L.E.K. Consulting: "We are looking for a Knowledge Manager in Mumbai to lead our Knowledge Management team for the Asia Pac region. If you have the necessary qualifications coupled with the drive to be part of a fast paced organization, apply here."


Knowledge Management: Each man is my superior in that I may learn from him." #learning

 

2021 provides an oppty to leverage what we can learn from others-better. Grateful if you would check out my latest article: Knowledge Management: Each man is my superior in that I may learn from him.” https://linkedin.com/pulse/knowledge-management-each-man-my-superior-i-may-learn-bill-kaplan

 

Watching CBS Sunday Morning today and it got me thinking about this through a KM lense.

 

Best

 

Bill

 

  

 

Learn more about the solutions and value we provide at www.workingknowledge-csp.com

 


Job Opening - Senior Knowledge Management Officer #jobs

Stan Garfield
 

Senior Knowledge Management Officer
AlignMNH
Baltimore, MD or Washington, DC
https://jobs-jhpiego.icims.com/jobs/4072/job


Re: Lessons Learned Storage & Access #lessons-learned

Nirmala Palaniappan
 

Hi David,

You’ve already received some excellent answers and pointers. Here are some insights and suggestions I am happy to share. Hope you find these to be useful and relevant to your business environment 

  1. As far as possible, it is a good idea to extend and enhance existing systems to capture lessons learned on the go as opposed to setting up a separate technology platform. For example, if you have a product management system or a CRM platform, it may be more effective to upgrade/customise them to include lessons learned 
  2. If you have no option to customise existing systems and are setting up a separate system, do integrate it with existing systems and bring it under a common search umbrella 
  3. Conduct brainstorming sessions with subject matter experts and key users to decide on the metadata for lessons learned. Map it to the processes, type of knowledge, expected benefits, whether it is conceptual or practical, time frame and so on
  4. To add to Nick’s excellent input regarding embedding lessons learned into procedures, processes, checklists etc, you could include a status box in the lessons learned platform and archive those that have been institutionalised and converted into a “habit”
  5. If your organisation enjoys video-based learning, do remember that it is not always necessary to document lessons learned in a conventional manner. Some lessons learned can be curated into an impactful video 
  6. If you can afford it, have content writers work on polishing and making the lessons learned consumable and enjoyable 
  7. Create and provide a lot of sample templates to bring in at least some amount of standardisation of content 
  8. Doing #7 might help you leverage on Machine Learning/NLP algorithms to discover patterns, analyse them and use them as inputs for decision-making/Management 
  9. If feasible, identify and employ champions and give them the responsibility of “managing” lessons learned in business critical and/or evolving areas. Engage them in curating and assisting in the application of lessons learned in the said areas 
  10. Get creative in the way you brand the initiative/programme and make it enjoyable and rewarding (though, it seems like your colleagues don’t particularly need encouragement in submitting lessons learned)

If you would like to discuss this or have further queries, please do not hesitate.

Regards
Nirmala 

On Fri, 8 Jan 2021 at 5:43 PM, Chris Collison <chris.collison@...> wrote:

Fully agree with you regarding the ‘clearing house’ concept Nick, and great chapter by the way.

  

The perfect lessons learned database is an empty one – and conversely, a library of lessons which are starting to gather dust is an indicator of a failure of organisational learning. 

 

I wonder if we need a metaphor with in which lessons have a shorter shelf-life and are a means to an end rather than an end in themselves…    A lessons learned larder perhaps?

 

Chris Collison

Knowledgeable Ltd

Author of the KM Cookbook

@chris_collison

 

 

 

From: <main@SIKM.groups.io> on behalf of Nick Milton <nick.milton@...>
Reply to: "main@SIKM.groups.io" <main@SIKM.groups.io>
Date: Friday, 8 January 2021 at 08:59
To: "main@SIKM.groups.io" <main@SIKM.groups.io>
Subject: Re: [SIKM] Lessons Learned Storage & Access #lessonslearned

 

David, the best way to deal with massive numbers of lessons, is to embed them into guidance and best practice. You may have hundreds of lessons now, in a few years you will have thousands, and asking people to sift through these, resolving contradictions, sorting through repeat and duplicate lessons, becomes completely impractical.

 

If you look at organisations which are successful in lesson learning, such as NASA, the Oil Sector, the Military etc, you see that the lessons database (or lessons management system) is not the final repository of the lessons, but is a clearing house, directing the lessons to the subject matter experts who will embed them into procedure, process, guidance and doctrine. The lessons management system only holds those lessons which are still in process of being learned, and once that lesson is embedded into working practice it can be considered “learned” and removed from the system.

 

Project managers therefore only really need to follow the updated guidance, into which the lessons are embedded, rather than sifting through hundreds or thousands of entries.

 

You can find more details of this approach on my blog (here for example), and in my book “The Lesson Learned handbook”. The attached article may also be useful.

 

Nick Milton
Knoco Ltd
www.knoco.com

blog  www.nickmilton.com

twitter @nickknoco

Author of the recent book - "The Knowledge Manager’s Handbook"

 

"Ambition without knowledge is like a boat on dry land." 
--Mark Lee

 

 

From: main@SIKM.groups.io <main@SIKM.groups.io> On Behalf Of David Graffagna
Sent: 07 January 2021 16:53
To: main@SIKM.groups.io
Subject: [SIKM] Lessons Learned Storage & Access #lessonslearned

 

Hello all,

 

As I have mentioned in previous messages, my KM Team has a number of work-in-progress efforts aimed at enhancing our overall knowledge sharing environment. One of our targets for this year is a focus on a more standard approach to soliciting, gathering, capturing and providing access to key lessons learned from variety of projects and initiatives.

 

My question to this group regards your knowledge and insight around the storage of those lessons learned and providing access to lessons learned/insights for a broad audience to tap into and consume. Let me set the context so you have a sense of where our challenges lie.

 

Our primary source for lessons learned typically comes from significant, cross-function, multi-year projects … so numerous people involved, a wide variety of functional areas participating, and broad range of potential knowledge areas for learning. Over the past months we have worked with a handful of project managers in soliciting lessons from their project team members as part of the project wrap-up/closeout; helping us get a sense of the breadth and depth of what those teams learned during their initiative.

 

Frankly, the volume and value of what we have received back is beyond our initial expectations. The team members, individually or in small functional groups, have been great in answering the standard set of questions we have crafted and capturing replies in the format we have provided (Excel for now). One team, for example, consisting of 15 individuals provided us with more than 70 individual “line items” of lessons learned on anything from budget/finance, communications, design & development, marketing/commercialization, production planning, risk mitigation … and on and on across a long list of knowledge areas and activities. Currently, from six projects we’ve ‘tested’ we have over 500 lessons learned, but grouped (and captured) specific to each particular project.

 

Here's one of my biggest challenges … if we have hundreds of lessons learned what’s the best way of capturing and sharing (e.g., making them accessible) those without overwhelming our audiences … while making it easy for them to find the right lesson in the right context?

 

So, bottom line … would love to know good, effective approaches you’ve seen around capturing and sharing those lessons. What have you seen around lessons learned from broad-ranging projects?

 

Looking forward to hearing your thoughts and insights!

 

Best regards,

 

David Graffagna

--
"The faithful see the invisible, believe the incredible and then receive the impossible" - Anonymous


Re: Lessons Learned Storage & Access #lessons-learned

Chris Collison
 

Fully agree with you regarding the ‘clearing house’ concept Nick, and great chapter by the way.

  

The perfect lessons learned database is an empty one – and conversely, a library of lessons which are starting to gather dust is an indicator of a failure of organisational learning. 

 

I wonder if we need a metaphor with in which lessons have a shorter shelf-life and are a means to an end rather than an end in themselves…    A lessons learned larder perhaps?

 

Chris Collison

Knowledgeable Ltd

Author of the KM Cookbook

@chris_collison

 

 

 

From: <main@SIKM.groups.io> on behalf of Nick Milton <nick.milton@...>
Reply to: "main@SIKM.groups.io" <main@SIKM.groups.io>
Date: Friday, 8 January 2021 at 08:59
To: "main@SIKM.groups.io" <main@SIKM.groups.io>
Subject: Re: [SIKM] Lessons Learned Storage & Access #lessonslearned

 

David, the best way to deal with massive numbers of lessons, is to embed them into guidance and best practice. You may have hundreds of lessons now, in a few years you will have thousands, and asking people to sift through these, resolving contradictions, sorting through repeat and duplicate lessons, becomes completely impractical.

 

If you look at organisations which are successful in lesson learning, such as NASA, the Oil Sector, the Military etc, you see that the lessons database (or lessons management system) is not the final repository of the lessons, but is a clearing house, directing the lessons to the subject matter experts who will embed them into procedure, process, guidance and doctrine. The lessons management system only holds those lessons which are still in process of being learned, and once that lesson is embedded into working practice it can be considered “learned” and removed from the system.

 

Project managers therefore only really need to follow the updated guidance, into which the lessons are embedded, rather than sifting through hundreds or thousands of entries.

 

You can find more details of this approach on my blog (here for example), and in my book “The Lesson Learned handbook”. The attached article may also be useful.

 

Nick Milton
Knoco Ltd
www.knoco.com

blog  www.nickmilton.com

twitter @nickknoco

Author of the recent book - "The Knowledge Manager’s Handbook"

 

"Ambition without knowledge is like a boat on dry land." 
--Mark Lee

 

 

From: main@SIKM.groups.io <main@SIKM.groups.io> On Behalf Of David Graffagna
Sent: 07 January 2021 16:53
To: main@SIKM.groups.io
Subject: [SIKM] Lessons Learned Storage & Access #lessonslearned

 

Hello all,

 

As I have mentioned in previous messages, my KM Team has a number of work-in-progress efforts aimed at enhancing our overall knowledge sharing environment. One of our targets for this year is a focus on a more standard approach to soliciting, gathering, capturing and providing access to key lessons learned from variety of projects and initiatives.

 

My question to this group regards your knowledge and insight around the storage of those lessons learned and providing access to lessons learned/insights for a broad audience to tap into and consume. Let me set the context so you have a sense of where our challenges lie.

 

Our primary source for lessons learned typically comes from significant, cross-function, multi-year projects … so numerous people involved, a wide variety of functional areas participating, and broad range of potential knowledge areas for learning. Over the past months we have worked with a handful of project managers in soliciting lessons from their project team members as part of the project wrap-up/closeout; helping us get a sense of the breadth and depth of what those teams learned during their initiative.

 

Frankly, the volume and value of what we have received back is beyond our initial expectations. The team members, individually or in small functional groups, have been great in answering the standard set of questions we have crafted and capturing replies in the format we have provided (Excel for now). One team, for example, consisting of 15 individuals provided us with more than 70 individual “line items” of lessons learned on anything from budget/finance, communications, design & development, marketing/commercialization, production planning, risk mitigation … and on and on across a long list of knowledge areas and activities. Currently, from six projects we’ve ‘tested’ we have over 500 lessons learned, but grouped (and captured) specific to each particular project.

 

Here's one of my biggest challenges … if we have hundreds of lessons learned what’s the best way of capturing and sharing (e.g., making them accessible) those without overwhelming our audiences … while making it easy for them to find the right lesson in the right context?

 

So, bottom line … would love to know good, effective approaches you’ve seen around capturing and sharing those lessons. What have you seen around lessons learned from broad-ranging projects?

 

Looking forward to hearing your thoughts and insights!

 

Best regards,

 

David Graffagna


Re: Lessons Learned Storage & Access #lessons-learned

Moria Levy
 

David

I have developed and implemented, over a dozen of times, a methodology for managing lessons, dealing also with the storgae and accessibility issues.
In a few sentences:
a. The lessons are extracted from the document, and a process takes places generalizing them, writing them accoarding to some rules and merging them with existing lessons.
b. They are written into a knowledgebase of lessons, including the lessons with their rational, meta-data, links to the debriefing documents and supplemental info.
c. The lessons knowledgebase is designed to be integrated in the organizational environment in cultural, processes, computting and physical matters.
The full methodology can bre found in  a book descrining it: https://www.amazon.com/Holistic-Approach-Lessons-Learned-Organizations/dp/1138564761#ace-g9859629705
I got positice feedbacks form colleagues woldwide as to this methodology.
If you have any specific questions- please adress me here or directly (moria@...) and I will be happy to explain/answer any issue concerning.
Moria


Re: Lessons Learned Storage & Access #lessons-learned

Nick Milton
 

David, the best way to deal with massive numbers of lessons, is to embed them into guidance and best practice. You may have hundreds of lessons now, in a few years you will have thousands, and asking people to sift through these, resolving contradictions, sorting through repeat and duplicate lessons, becomes completely impractical.

 

If you look at organisations which are successful in lesson learning, such as NASA, the Oil Sector, the Military etc, you see that the lessons database (or lessons management system) is not the final repository of the lessons, but is a clearing house, directing the lessons to the subject matter experts who will embed them into procedure, process, guidance and doctrine. The lessons management system only holds those lessons which are still in process of being learned, and once that lesson is embedded into working practice it can be considered “learned” and removed from the system.

 

Project managers therefore only really need to follow the updated guidance, into which the lessons are embedded, rather than sifting through hundreds or thousands of entries.

 

You can find more details of this approach on my blog (here for example), and in my book “The Lesson Learned handbook”. The attached article may also be useful.

 

Nick Milton
Knoco Ltd
www.knoco.com

blog  www.nickmilton.com

twitter @nickknoco

Author of the recent book - "The Knowledge Manager’s Handbook"

 

"Ambition without knowledge is like a boat on dry land." 
--Mark Lee

 

 

From: main@SIKM.groups.io <main@SIKM.groups.io> On Behalf Of David Graffagna
Sent: 07 January 2021 16:53
To: main@SIKM.groups.io
Subject: [SIKM] Lessons Learned Storage & Access #lessonslearned

 

Hello all,

 

As I have mentioned in previous messages, my KM Team has a number of work-in-progress efforts aimed at enhancing our overall knowledge sharing environment. One of our targets for this year is a focus on a more standard approach to soliciting, gathering, capturing and providing access to key lessons learned from variety of projects and initiatives.

 

My question to this group regards your knowledge and insight around the storage of those lessons learned and providing access to lessons learned/insights for a broad audience to tap into and consume. Let me set the context so you have a sense of where our challenges lie.

 

Our primary source for lessons learned typically comes from significant, cross-function, multi-year projects … so numerous people involved, a wide variety of functional areas participating, and broad range of potential knowledge areas for learning. Over the past months we have worked with a handful of project managers in soliciting lessons from their project team members as part of the project wrap-up/closeout; helping us get a sense of the breadth and depth of what those teams learned during their initiative.

 

Frankly, the volume and value of what we have received back is beyond our initial expectations. The team members, individually or in small functional groups, have been great in answering the standard set of questions we have crafted and capturing replies in the format we have provided (Excel for now). One team, for example, consisting of 15 individuals provided us with more than 70 individual “line items” of lessons learned on anything from budget/finance, communications, design & development, marketing/commercialization, production planning, risk mitigation … and on and on across a long list of knowledge areas and activities. Currently, from six projects we’ve ‘tested’ we have over 500 lessons learned, but grouped (and captured) specific to each particular project.

 

Here's one of my biggest challenges … if we have hundreds of lessons learned what’s the best way of capturing and sharing (e.g., making them accessible) those without overwhelming our audiences … while making it easy for them to find the right lesson in the right context?

 

So, bottom line … would love to know good, effective approaches you’ve seen around capturing and sharing those lessons. What have you seen around lessons learned from broad-ranging projects?

 

Looking forward to hearing your thoughts and insights!

 

Best regards,

 

David Graffagna


Re: Lessons Learned Storage & Access #lessons-learned

Joitske Hulsebosch
 

Hi David, I wonder if you know the 5 types of knowledge transfer of Nancy Dixon? she states that you need different things for different types of transfer. Here's summary on my blog: https://joitskehulsebosch.blogspot.com/2005/12/communities-of-practice-nancy-dixon-on.html

For instance when you want to transfer lesson om more complex project it is good to use an advisory approach where one team advises the other. 


Re: Lessons Learned Storage & Access #lessons-learned

Gabriela Fitz
 

Hi David:

I am wondering if you would be willing to share the standard set of questions you have been using to solicit the lessons learned? I would be super interested.

Best
Gabi

On Thu, Jan 7, 2021 at 1:56 PM Stan Garfield <stangarfield@...> wrote:
David, thanks for your post.  In addition to the excellent responses from Tom and Dennis, these resources may also be helpful:



--

Gabriela Fitz

Think Twice LLC

773.882.8250 | LinkedIn

www.thinktwicellc.com


Preferred Pronouns: she/her/hers





Re: Lessons Learned Storage & Access #lessons-learned

Stan Garfield
 

David, thanks for your post.  In addition to the excellent responses from Tom and Dennis, these resources may also be helpful:


Re: Lessons Learned Storage & Access #lessons-learned

Dennis Pearce
 

Hi David,

A while back I did a multi-part series of blog posts on Lessons Learned, based on some research I had done.  You might find some of them useful in what you're trying to do.  This is the initial post and then there are links to the successive ones within it.


Dennis Pearce


Re: Lessons Learned Storage & Access #lessons-learned

 
Edited

Hello David - it’s an interesting and fun KM challenge you have described. I’d start by figuring out some categories for the various lessons learned. One way to do this is affinity clustering - just grouping the LL’s like with like, without pre-defining any categories. 
Next, I’d look for a cluster of LL’s that have a focus on process or procedure, and start with those by reviewing how an existing process or procedure could be modified to incorporate the LL. (Last time I did this I used a Miro board - miro.com - and was able to upload a spreadsheet of ideas, which Miro turned into sticky notes - very cool. Free). 

Doing that is a way to get some “quick hits”, and may also lead to insights about other LL’s that were not initially considered to be related.

Next, I’d come up with category names for the other clusters (you could also do this before attacking P&P). I’d then look across clusters and prioritize LL’s that are critical (you’ll need to decide what constitutes “critical”!), and start working on what the best way is to incorporate those LL’s into the work they relate to. 

Doing this will likely give you insight into how to deal with many of the remaining LL’s, or if not that, then at least some idea about how to continue moving forward with your work. 

Good Luck! Let us know how you go with this - it’s an important KM area.
--
-Tom
--

Tom Short Consulting
TSC
+1 415 300 7457

All of my previous SIKM Posts


Lessons Learned Storage & Access #lessons-learned

David Graffagna
 

Hello all,

 

As I have mentioned in previous messages, my KM Team has a number of work-in-progress efforts aimed at enhancing our overall knowledge sharing environment. One of our targets for this year is a focus on a more standard approach to soliciting, gathering, capturing and providing access to key lessons learned from variety of projects and initiatives.

 

My question to this group regards your knowledge and insight around the storage of those lessons learned and providing access to lessons learned/insights for a broad audience to tap into and consume. Let me set the context so you have a sense of where our challenges lie.

 

Our primary source for lessons learned typically comes from significant, cross-function, multi-year projects … so numerous people involved, a wide variety of functional areas participating, and broad range of potential knowledge areas for learning. Over the past months we have worked with a handful of project managers in soliciting lessons from their project team members as part of the project wrap-up/closeout; helping us get a sense of the breadth and depth of what those teams learned during their initiative.

 

Frankly, the volume and value of what we have received back is beyond our initial expectations. The team members, individually or in small functional groups, have been great in answering the standard set of questions we have crafted and capturing replies in the format we have provided (Excel for now). One team, for example, consisting of 15 individuals provided us with more than 70 individual “line items” of lessons learned on anything from budget/finance, communications, design & development, marketing/commercialization, production planning, risk mitigation … and on and on across a long list of knowledge areas and activities. Currently, from six projects we’ve ‘tested’ we have over 500 lessons learned, but grouped (and captured) specific to each particular project.

 

Here's one of my biggest challenges … if we have hundreds of lessons learned what’s the best way of capturing and sharing (e.g., making them accessible) those without overwhelming our audiences … while making it easy for them to find the right lesson in the right context?

 

So, bottom line … would love to know good, effective approaches you’ve seen around capturing and sharing those lessons. What have you seen around lessons learned from broad-ranging projects?

 

Looking forward to hearing your thoughts and insights!

 

Best regards,

 

David Graffagna


Re: KnowledgeWebcast - Dr. Rachad Najjar #video #CoP #standards

Martin Dugage
 

Wow! Thank you Santosh. Really interesting webcasts. 
Happy new year to all of you. May the new year bring you one vaccination and a lot of happiness. 
And let me take this opportunity to thank all of you, and especially Stan for setting up this group, which is really outstanding. When I raised a question here about business cases in KM, I got MANY extremely relevant and immediate answers to my question. And I could not keep up answering all of you and I felt a little guilty about it. 
This group reminds me of the early days of the internet back in 2000 when groups could form to help each other without fearing trolls. 
Let's keep it that way. 
Warmest Regards to all of you.
Martin


Re: KnowledgeWebcast - Dr. Rachad Najjar #video #CoP #standards

Santhosh Shekar
 

Dear All,

Belated wishes for Christmas and advance wishes for New year 2021 !! May the new year bring a great wave of healing and prosperity to the world !!
 
Please find the latest Knowledgewebcast  interview series with Dr. Rachad Najjar, Global Knowledge leader, GE Renewable, December Edition !! I have enjoyed talking to him on various KM topics, I want to thank him once again on behalf of the KM community for such amazing knowledge sharing !! 

 Please do watch and reach me out if you have any similar ISO KM Standard Case/story to share !!  

https://youtu.be/dFlF68CyQGk - part 1  - Journey of Rachad !!
https://youtu.be/xj5f6kUQhRM - part 2 - Practical case of ISO KM standard implementation !!! ( Must Watch - my recommendation)
https://youtu.be/BWnH4Uy_U44 - Part 3 - How to make Communities successful !!

Regards,
Santhosh Shekar


On Thu, Dec 3, 2020 at 8:13 AM Santhosh Shekar via groups.io <santhoshshekar=gmail.com@groups.io> wrote:
Sorry for cross Posting ! 
Dear All, 
Episode 1 - Nov 2020
The below link provides sources to the first episode with three parts. In this webcast, I interviewed Ian Fry, Chair, Australia Standards Committee; Director, Knoco Australia. He talks about his KM journey, KM at times of Pandemic, Bush Fire Lessons learned by Australian Government, lesson learned systems, KM Governance framework and standard, Australia's Nationwide KM, Guerrilla KM and shares many more pearls of wisdom.

https://youtu.be/9wJ1I1nVeG8 - YouTube Ian Interview part 1
https://youtu.be/wRAhV-EQEPA - YouTube Ian Interview part 2
https://youtu.be/RHS52ssGk_o - Youtube Ian Interview part 3

https://knowledgewebcast.podbean.com/
https://www.podbean.com/ew/pb-hjyf4-f33fce - Podcast Ian Interview part 1
https://www.podbean.com/ew/pb-rjvgq-f38c6c - Podcast Ian Interview part 2
https://www.podbean.com/ew/pb-kcxmy-f3c219 - Podcast Ian Interview Part 3

regards,
Santhosh Shekar 

On Wed, Nov 25, 2020 at 8:47 AM santhoshshekar <santhoshshekar@...> wrote:
Dear All,

I am delighted to share my first interview with Ian fry, who has 50 years of IT and KM experience combined. He speaks on various topics covering from Australian bush fire lessons, Lesson learned systems, KM standard 30401, his views and opinions on the same; KM challenges, Guariella KM etc in this part. 

Youtube Ian Fry Part-1  : https://youtu.be/9wJ1I1nVeG8

The single most purpose of creating this platform "knowledgewebcast" was to invite KM experts/executives and listen to them, on their KM journey, their views on KM standard (different school of thoughts), and also what they have to share as their learnings for the KM community !! 

Please do write to me with feedback and suggestions.

Regards,
Santhosh Shekar
twit @santhoshshekar 





Job Opening - Community Manager at Normal>Next #jobs

Stan Garfield
 

Scroll down past internship opening at https://normalnext.org/jobs/

Normal>Next is looking for a community manager for a client organization we are working with to create a remote-first approach to its health equity-focused leadership program. You will work alongside both the team at Normal>Next as well as the program’s participants and planning team. You will help set up the new community platform and train several part-time community managers who are alumni of the leadership program.

The ideal candidate will be an empathetic listener and graceful communicator, who can easily earn trust by being heartfelt, and who is comfortable both receiving and giving candid feedback.


Event: The Top 5 Lies We Tell Ourselves in Organizations - Wed, Jan 13 · 4:00 PM EST #webinar

Matt Moore
 

Hi,

This is an online facilitated session with John Hovell (a gentleman) and myself (a scoundrel). The time on the Meetup is EST (it’s Thursday morning in Eastern Australia).

More info here: https://www.meetup.com/Knowledge-Cafe/events/274768100/

Regards.

Matt Moore
+61 423 784 504

1541 - 1560 of 9977