Friday, May 01, 2015

Parsing KMworld 2014 -- Day 1

KMworld has graciously posted all of the presentations from its 2014 conference. Let's take a look at the presentations from the first day, November 5 2014:

Pugh presents Knowledge is Business. She is apparently pushing her book: Smarter Innovation -- using interactive processes to drive better business results.
  • There's some stuff about the transition from a knowledge-enabled strategy to a knowledge-driven strategy.
  • Knowledge products include frameworks, research and development, integrated services, education, consulting. Knowledge can be instilled (in the product), distilled (knowledge for sale), embodied (people, community).
  • She cites some stuff from Ark Group
  • Uses of knowledge include: bridging, social and operational integration, capabilities validation, market and industry exploration, commercialization
  • Organizational-level capacities: shared language/metadata, consensus innovation process, sense-making/benchmarking, swaps, sabbaticals, mindfulness
  • Individual-level: mastery, self-awareness, boundary tracking, attracted to foreign, comfort with ambiguity, convening skills
  • Team/community level: integrity/courtesy/inclusion/translation, "desire-to-know" vs. "need-to-know"
  • Overall -- interesting but maybe a bit high level.

  • So we've got silos… no surprise
  • Difference between complicated and complex problems
  • So we need systems thinking. Okay, very Senge.
  • "Improving a part can destroy a system" i.e., you can't put a jet engine in a car
  • KM includes interactions and interdependency
  • Good stories…
  • Theory of Constraints.
  • KDSD = knowledge discovery sharing and distribution
  • Model-based repositories and visualization
  • Either very wise or very dated

McCabe (Unisys) provides "Knowledge transfer across generations":
  • She has a business method patent or two, one apparently with a guy named Goodall so it can't be all bad!
  • Some decent stats about aging in the work force
  • Some more good stats about "employee turnover as % of salary":
    • Clerical 50-80%
    • Skilled hourly 75-100%
    • Professional: 75-125%
    • Technical: 100-150%
    • Engineers: 200-300%
    • Supervisors: 100-150%
    • Mid managers: 125-200%
  • Employee k lifecycle: recruit, onboard, develop expertise, transfer k, exit
  • Great case study for workforce renewal training

  • I like Richard's stuff so let's see what we get.
  • Identified learning objectives. Nice.
  • Emailing is big… but poorly done.
  • Decent stats on usage of information services
  • Interesting. I don't think that most people are here yet but it provides some decent guidance.

Nelson of Mayo clinic on "Pushing the envelope : from CMS to KCMS":
  • This could be cool, particularly given my recent interest in the KCS stuff. And the guy has "Ontologist" in his title!
  • It looks to be a big case study
  • We have a "content value chain" that goes from "unstructured -- human consumption" up to "smart content -- human consumed, machine organized and interpreted"
  • Used semantics for targeted ads and dynamics links
  • It all seems to be driven by Sitecore and TopBraid (from TopQuadrant)

Most of the presentations are available as PPTs:

Peterson and Phair of MITRE provide "Using tangible interfaces for predictive knowledge delivery":
  • So… capture whiteboards to SharePoint
  • Add a keypad to the whiteboard so that authors can introduce their credentials (i.e., metadata for discoverability)
  • Write commands or specific instructions in a specific part of the whiteboard
  • Future: sensing presence (i.e., an employee enters a building a needs an office space), sensing conversation.

Minicucci of IBM with "Enterprise search for Knowledge Management":
  • Combine structured and unstructured
  • Clustering with text analytics, entity extraction, sentiment analysis,
  • Next: "Cognitive exploration"
  • Hmmm… there's a difference between search and expert analysis.  The expert has to understand question, produce answers and evidence, analyze, assess confidence, and deliver

Brenkovich of Accenture "Enterprise search for KM: improving content access for consultants across Accenture."
  • Ooo! A case study!
  • Only 37% of consultants could find what they needd
  • Phases:
    1. Content accessibility. Focus on best content, noise reduction, awareness raising. Content mgmt scorecard quarterly. 30% increase in content access (37% to 48%)
    2. Establish content ready state and commit to communities. Integrated social learning; established CM accountabilities; more content quality; calendar with monthly content tasks; focus on communities with an "Enablement Toolkit" or cookbook for community; 58% increase in content access (48% to 76%)
    3. Maintain content steady state and community uplift. Content management CoE; professional communities; community engagement; community governance; leadership accountability; showcase curated content; improve mobile collaboration.
  • Content scorecard:
    • Provide the best content. Improved harvesting; simplified contribution; content rating campaigns; reminders to rate downloaded material
    • Reduce the noise. Quarterly review of content older than 3 years; improved archival processes; clean up of duplicates
    • Improve access. Monthly contribution review for tagging; search best practices (best bets, type aheads, relevancy tuning); CM enablement for content creators; clean up of incomplete or incorrect tagging
    • Raise awareness. "Find content" communications in global newsletter; inclusion of content and collaboration in onboarding and other training
  • Results:
    • Provide best content: 50% of content rated (up from 13%); engagement profile completions up 80%; proposal completions up 180%; deliverable completions up 320%
    • Reduce noise: 73% reduction in content older than 3 years; eliminated >1000 duplicate titles
    • Improve access: fixed tagging on 7000 contributions; 58% reduction in bad searches
    • Raise awareness: 42% increase in use of our collaboration tools
  • They build content dashboards to track progress
  • CoE. Knowledge Specialist responsibilities. Content harvesting, content audit, contribution review, content archiving, content requests; repackaging content; search optimization; support for practice enablement; managing community sites; developing offering essentials and key documents; driving CoP communication; training content support
  • They talk about the 3 types of communities (a la the ARMY): professional communities, communities of practice, communities of interest.
  • Measuring community success: dashboard, survey, program scorecard

Cheryl McKinnon "Go beyond traditional ECM : new approaches to managing enterprise content"
  • It's always nice to see something from Cheryl, formerly of Open Text and Nuxeo. She even came to visit me once when she was with Nuxeo. Let's see what she has to say.
  • Four disruptors -- transform the customer experience; embrace the mobile mind shift; turn big data into business insights; become a digital disruptor
  • Drivers for ECM: search, content sharing, compliance, archive consolidation, cost-effective automation, paper reduction
  • Analytics seem to be a trend. Data on usage monitoring/system auditing, user interviews, bugs/requests, PoC, log files, etc.

Varney "Evolving a premier digital workplace at KCTCS"
  • Kentucky community colleges?
  • PSFT, Sitecore, Blackboard, OnBase, Inteliworks, AdPro
  • Yeah, yeah… And they use ADKAR from Prosci (which Brian F. mentioned just last week) for change management
  • Awareness; Desire; Knowledge; Ability; Reinforcement

Schneier "When knowledge walks out connecting, sharing and capturing alumni knowledge for development"
  • I had seen this one before
  • World Bank Group
  • Alumni want to help, primarily around providing informal expert help, expert interviews, etc.
  • Introduced a skill finder

Horn "Talent development: a knowledge sharing lens"
  • MWH
  • Real process for new hires:
    • Onboarding. Brand, core values, purpose, people, professional culture
    • Induction. Clarify roles and expectations; compliance training. Two weeks.
    • Orientation. Basic training. 90 days.
  • Integrate knowledge transfer into the plan
  • Use events: annual conference, community calls, pair and share
  • Recognition and incentives. It's on the PA; awards.
  • Hero spotlight
  • Community success factors:
    • Community measurement
    • Motivation, recognition, rewards
    • Supporting technology
    • Standard collaboration processes
    • Development of trusted relationships
    • Leadership, governance, and sponsorship
    • Clear business case and objectives
    • Adequate resources and support
    • Member engagement and defined roles
    • Clear deliverables and activities
  • Knowledge transfer: mentor relationships; knowledge forums; work assignments; k-transfer plan
  • Identify risk of knowledge loss: single points of failure; retirement
  • Identify key knowledge.

Wolf "Knowledge capture and transfer at Kraft Foods"

  • They used a knowledge modeling process called MASK
  • MASK: Method for Analyzing Structured Knowledge
  • Developed by Louis Ermine at the French Commission de l'energie atomique in 1993
  • It needs a KM Lead; a sponsor; an expert; a recipient who owns the knowledge books; and a facilitator
  • The MASK process
    • Needs assessment. Lead and sponsor. Criteria: rarity, strategic fit, difficult in acquiring, difficulty in applying
    • Scoping. Led by MASK facilitator. Input from expert and recipient. Validated by sponsor. Provides a base for elicitation.
    • Eliciting and modeling. Led by MASK facilitator. 1 expert per 4 hour interview. Output captured on paper and audio records. Models generated by facilitator.
    • Validation. Completed by Expert with facilitator and lead support. Detailed editing of tech content.
    • Sharing. Recipient introduces the book to relevant groups. Expert attends and supports.
  • Body of Knowledge = basic phenomena + concepts + processes + history + know how + evolution
  • Activity model+phenomenon model+sample concept model+task model + history model + lineage model 


Post a Comment

Subscribe to Post Comments [Atom]

<< Home