Date   

Re: ESNs... more than "like" capabilities #ESN

dennis.pearce@...
 

We use Jive here.  It has many "structured outcomes" as they call them.  
  • You can mark a comment in a discussion as "helpful."  Links to helpful comments are aggregated at the top of the discussion so that readers can jump to them.
  • If someone asks a question, a single response can be marked as "correct."  This places a copy of the response directly under the question, with a link to "see this in context" which jumps the reader down to the point in the discussion where the answer was posted.
  • A discussion can be marked as "final."  This collapses the discussion so that only the original post and the correct answer are visible, although there is a link that will allow readers to open it back up to view the full discussion if they want.
  • A document can be marked "official" or "obsolete."  These can be used as filters across the document repository and affect the weight of the search results positively or negatively, respectively.  The "obsolete" designation throws up a flag when someone clicks on a link to the doc, and allows the user to provide a link to content that should be used instead.
These various designations are all configurable as to who can mark what under what circumstances.


ESNs... more than "like" capabilities #ESN

Jamie Martino
 

Hello everyone, 


Is anyone using an ESN (even SP addon) that has more than just a "like" and "share" button, but goes further into "this helped me" or "solved my problem" for content, posts and replies? If so, which one(s) is it?


Many thanks in advance. 
Best, 

Jamie


Re: SNA: utterly worthless and possibly damaging? #SNA-ONA-VNA

Patti Anklam
 

Hi, all,

Certainly I have to respond to such a provactive subject line!  Thanks, @katepugh for the mention. Nils argues that the SNA is only a snapshot in time. That is what I always say when I teach SNA. But the snapshot can lead to useful questions and insights...

More, however: Once I saw where the article and "complexitools" was going with value creation structure I kept looking in the original and the comments for a nod to Verna Allee, who really broke this ground a long time ago; I have long been a believer (I almost always use a value network analysis when I work with organizations). So it is nice to see it rise again, but it would also be good to see some attribution or reference.

/patti



Re: SNA: utterly worthless and possibly damaging? #SNA-ONA-VNA

Katepugh <katepugh@...>
 

Resending with Tom's original post (and the link) below Fred's 

On Feb 16, 2017, at 7:25 AM, Katepugh katepugh@... [sikmleaders] <sikmleaders@...> wrote:

 

Tom, Nils et al

Nice article! I think Nils has taken what we all do with SNA (map structures as they show flow of information, disease, influence, etc.) and just singled out the "reputation" structure into its own science.

At Columbia Information and Knowledge Strategy Master's we have been teaching about SNA for six years. It is just basically graph theory (and mathematics) where the "nodes" are people and the "edges" can be anything. We have students include reputation or influence as one edge, and describe potential interventions. 

I agree we all should do SNA for a reason, and understandings of value creation and reputation are great reasons. Giving a specific SNA that maps reputation a privileged spot in our thinking is a good idea. It i s not a new science. But it is a valuable focus, and so are others like managing addiction, obesity, and reproductive health. 

@Patti Anklam, who has influenced my thinking, has always said that SNA -- or rather, the mapping part -- is just the first step. It provokes questions. Putting a lens on the org or other set of connected items, even machines, and representing it visually in a novel way is a worthy art. 

Kate


Katrina Pugh
Academic Director 
Columbia University Information and Knowledge Strategy Master's Program

On Feb 16, 2017, at 6:24 AM, fred@... [sikmleaders] <sikmleaders@...> wrote:

 

Thanks for the link, Tom.  Very interesting read.


Fred Nickols

From Tom Short 


Re: January 2017 SIKM Call: Arno Boersma - Design Thinking for KM #monthly-call #design-thinking

joanna_pierce@...
 

Greetings All:

I'm sorry to have missed this call last month, but just got around to reviewing it the other day. I must say thank you to Arno--this was a very enjoyable presentation, and I wish I could have been there for the discussion. So, hoping to continue it here.

I love the idea of a "Fail Fair," to show how you've failed to others in the organization, but staying optimistic and possibly sharing how you're going to pick up and start again. Doing a "lessons learned" analysis isn't something that my organization does a lot with projects, and we have a lot of silos. I think this would be a great opportunity to bridge the gaps across the company and show what we've done, getting feedback and similar insights from other departments. 

From a KM perspective, there's a definite fear about failing in this space as there have been many iterations of this effort in my department. The rest of the organization is just starting to get a toe in the water in the KM space. I believe our current KM solution will stick (we're about 2-years in and growing every month). Some other areas are starting to reach out to us, having their own failed attempts and looking for something that's showing ROI, strong user adoption, etc. But, we still have much to learn.

Has anyone else had success with getting something like a "Fail Fair" off the ground? How can we get leadership buy-in to start something like this? What are scaling options?

Best,
Joanna


Re: SNA: utterly worthless and possibly damaging? #SNA-ONA-VNA

Katepugh <katepugh@...>
 

Tom, Nils et al

Nice article! I think Nils has taken what we all do with SNA (map structures as they show flow of information, disease, influence, etc.) and just singled out the "reputation" structure into its own science.

At Columbia Information and Knowledge Strategy Master's we have been teaching about SNA for six years. It is just basically graph theory (and mathematics) where the "nodes" are people and the "edges" can be anything. We have students include reputation or influence as one edge, and describe potential interventions. 

I agree we all should do SNA for a reason, and understandings of value creation and reputation are great reasons. Giving a specific SNA that maps reputation a privileged spot in our thinking is a good idea. It is not a new science. But it is a valuable focus, and so are others like managing addiction, obesity, and reproductive health. 

@Patti Anklam, who has influenced my thinking, has always said that SNA -- or rather, the mapping part -- is just the first step. It provokes questions. Putting a lens on the org or other set of connected items, even machines, and representing it visually in a novel way is a worthy art. 

Kate


Katrina Pugh
Academic Director 
Columbia University Information and Knowledge Strategy Master's Program

On Feb 16, 2017, at 6:24 AM, fred@... [sikmleaders] <sikmleaders@...> wrote:

 

Thanks for the link, Tom.  Very interesting read.


Fred Nickols


Re: SNA: utterly worthless and possibly damaging? #SNA-ONA-VNA

Fred Nickols
 

Thanks for the link, Tom.  Very interesting read.

Fred Nickols


SNA: utterly worthless and possibly damaging? #SNA-ONA-VNA

tman9999@...
 

I have never thought about it that way, but in a conversation on LinkedIn that is exactly how Niels Pflaeging put it in response to my comment about this excellent LinkedIn article, "Org Physics: How a triad of structures allows companies to absorb complexity".


My comment may be found below the article - as of today it is the newest comment there. Niels replied to it, defending his position. 


I thought some of the siKM folks might be interested in joining the discussion, and perhaps providing some alternative perspectives on this front. 


-Tom Short


 


Re: CoP - Archiving and Retention Policy #CoP #knowledge-retention #archiving

Jeffrey Dlott
 

The community is scattered throughout the US so we do not meet F2F


Re: Any Experience Here with Virtual Agents/Chat Bots? #AI #call-center

Curtis A. Conley
 

I'm just now kicking off a chatbot project as a POC to support our Collaboration Service (primarily supporting Office 365 tools like SharePoint, OneDrive, Yammer, Teams, Planner, and Box, etc.). We also have a number of training, end user engagement and adoption services that we support. 

For this POC, we're exploring if a chatbot can provide adequate support to many of the basic questions our end users end up asking either to our Yammer groups, service desk, via email, or IM etc. To a point the was brought up earlier - we have good training and documentation, FAQs, etc. and search can find it - but if I had a solution to the "how do you get users to search first" question, I'd be an independent consultant living on a private island... :)   

So we'd like to see if we can train the bot and have it be able to respond to conversations in Yammer, Skype, embedded on a SharePoint site, ServiceNow, etc. So we'll start with low hanging fruit (existing KBs, FAQs) and soon will begin to pull in actual Q&A from within Yammer, email, etc. If all works well, we'll be exploring how to "upgrade" the bot to perform personal assistant actions (e.g., creating tickets, provisioning workspaces). 



Job opening: Operations Knowledge Manager at Amgen (Road Island) #jobs

Curtis A. Conley
 

Amgen's Operations KM team is growing. Please let me know if you have any questions. 


http://careers.amgen.com/job-en/7146971/business-center-of-excellence-manager-west-greenwich-ri/ 


Business Center of Excellence Manager

The Operations Knowledge Manager (Business Center Of Excellence Manager) will be a key member of the Operations Knowledge Management (KM) team helping to advance KM across the global Operations business function, reporting to the Director of Knowledge Management.


Responsibilities Include:

  • Serve as the business owner of the central knowledge repository, the Operations Knowledge Marketplace, with responsibility for; content approval, curation, knowledge asset workflow, usage analytics and reporting, and SharePoint site collection administration
  • Will lead and facilitate the Operations Alert Process
  • Contribute to strategy-driven KM projects
  • Provide moderation and community management to KM forums and communities of practice (such as Yammer groups and in person working groups)
  • Oversee day-to-day business support for KM related issues



The Three Types of Knowledge #definition

Frank Guerino
 

Hi all,

The following article leverages Fred Nickols’ decision tree for The Three Types of Knowledge – Tacit, Implicit, and Explicit.  However, it goes further, by assuming that each form of knowledge is nothing more than data, which I know many of you have issues with but which aligns tightly with Enterprise Knowledge Management (EKM).  [The full address: https://www.if4it.com/knowledge-management-different-knowledge-types-tacit-implicit-and-explicit/]

Feel free to provide feedback.

My Best,

Frank
Frank Guerino, Managing Partner
The International Foundation for Information Technology (IF4IT)
http://www.if4it.com
1.908.294.5191 (M)


Re: CoP - Archiving and Retention Policy #CoP #knowledge-retention #archiving

 

How often does the CoP have an oppty to meet F2F?

 

From: sikmleaders@... [mailto:sikmleaders@...]
Sent: Tuesday, February 7, 2017 08:16
To: sikmleaders@...
Subject: Re: [sikmleaders] CoP - Archiving and Retention Policy

 

 

Thanks Neil for the feedback.

 

The CoP that I run has a little over 250 members from different functional units collaborating on 2 main business objectives. The main page is open to all members and includes a discussion board, wiki page, libraries, and useful links. We have another section called  'working group" which consists of smaller teams collaborating on more focused projects (restricted access).

 

My archiving and retention question is 2 fold:

 

1. What are some reasonable solutions for the main page?

2. What is reasonable for the individual working groups?

 

The main page content is added a la carte whereas the 'working group' content is more intentional and is more of a collection.

 

Hope this is clearer.

 

Thank you!

 

Jeff


Re: CoP - Archiving and Retention Policy #CoP #knowledge-retention #archiving

Stan Garfield
 

Jeff, this article may be of interest: Don't automatically archive content


Re: CoP - Archiving and Retention Policy #CoP #knowledge-retention #archiving

Jeffrey Dlott
 

Thanks Neil for the feedback.


The CoP that I run has a little over 250 members from different functional units collaborating on 2 main business objectives. The main page is open to all members and includes a discussion board, wiki page, libraries, and useful links. We have another section called  'working group" which consists of smaller teams collaborating on more focused projects (restricted access).


My archiving and retention question is 2 fold:


1. What are some reasonable solutions for the main page?

2. What is reasonable for the individual working groups?


The main page content is added a la carte whereas the 'working group' content is more intentional and is more of a collection.


Hope this is clearer.


Thank you!


Jeff


Re: CoP - Archiving and Retention Policy #CoP #knowledge-retention #archiving

Jeffrey Dlott
 

Thank you for replying to my post. Some very interesting pearls of wisdom in there!


Jeff


Re: CoP - Archiving and Retention Policy #CoP #knowledge-retention #archiving

Neil Olonoff
 

Jeff, 

It seems to me you may wish to add some detail to your description, which would provide valuable context in crafting a viable solution. 

Neil 

Neil Olonoff 
Mobile: 703.283.4157
Skype: nolonoff


On Mon, Feb 6, 2017 at 3:21 PM, jedlo@... [sikmleaders] <sikmleaders@...> wrote:
 


Would appreciate any feedback. We are considering migrating content to a searchable archive after 12 months then purging content at 6 years.


Is that reasonable? How are people doing this?


Thanks!


Jeff



Re: CoP - Archiving and Retention Policy #CoP #knowledge-retention #archiving

 

Very informative and still very useful in many dimensions

 

Bill

 

 

 

 

  

 

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

 

 

 

 

From: sikmleaders@... [mailto:sikmleaders@...]
Sent: Monday, February 6, 2017 15:36
To: sikmleaders@...
Subject: Re: [sikmleaders] CoP - Archiving and Retention Policy

 

 

This is kind of old but perhaps some of it's still relevant -

 

 

I wrote this back in 2009.

 

Regards

Lee

 

 

On Mon, Feb 6, 2017 at 3:21 PM, jedlo@... [sikmleaders] <sikmleaders@...> wrote:

 

 

Would appreciate any feedback. We are considering migrating content to a searchable archive after 12 months then purging content at 6 years.

 

Is that reasonable? How are people doing this?

 

Thanks!

 

Jeff

 

 


Re: CoP - Archiving and Retention Policy #CoP #knowledge-retention #archiving

Lee Romero
 

This is kind of old but perhaps some of it's still relevant -


I wrote this back in 2009.

Regards
Lee


On Mon, Feb 6, 2017 at 3:21 PM, jedlo@... [sikmleaders] <sikmleaders@...> wrote:



Would appreciate any feedback. We are considering migrating content to a searchable archive after 12 months then purging content at 6 years.


Is that reasonable? How are people doing this?


Thanks!


Jeff





CoP - Archiving and Retention Policy #CoP #knowledge-retention #archiving

Jeffrey Dlott
 


Would appreciate any feedback. We are considering migrating content to a searchable archive after 12 months then purging content at 6 years.


Is that reasonable? How are people doing this?


Thanks!


Jeff

4861 - 4880 of 9974