the 7 rules for a successful knowledge-transfer

Continuous-Knowledge-Exchange

Stefan Wendel we:namix GmbH

09.05.2011

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

About us

•  we:namix GmbH

•  Methodology „Continuous Knowledge Exchange“ for project-teams

•  „Social Knowledge-Management“ platform

wisdomclouds.com

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

The problem: knowledge-exchange today is far from perfect

Know those questions ? – “One day we should write this down” – “Where shall we put our lessons ?” – “To whom shall we send it ?” – “I still need to finish this documentation about our

lessons-learned”

Today‘s situation: Knowledge captured sporadically (if ever)

Explicit Knowledge („Libraries“)

Implicit Knowledge („Heads“)

Knowledge gets lost before it is captured

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

The 7 problems of today‘s Knowledge-Management

•  Time

•  Granularity

•  Silos

•  Up-to-date

•  Distribution

•  Knowledge-mining

•  Memorization

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

Continuous-Knowledge-Exchange 4 Basic principles

remind

capture structure

share

Continuous-Knowledge-Exchange Loop & Continuous learning

remind

capture structure

share

Continuous-Knowledge-Exchange is a closed loop: " Knowledge-objects (blue) are captured, structured and stored. Reminder and sharing in social networks brings knowledge to the people.

Continuous-Knowledge-Exchange Filling the gap

Document- Management (sporadically)

Tacit Knowledge

Continuous-Knowledge-"Exchange

(daily)

Continuous-Knowledge-Exchange is the basis for a daily knowledge-exchange

Continuous-Knowledge-Exchange Content

1  Product  

3  Roles  

7  Rules  

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

Continuous-Knowledge-Exchange Product: Knowledge-Backlog

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

Continuous-Knowledge-Exchange 3 Roles

1 Knowledge- Master

1-n Knowledge- Editors

1-n Submitter

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

Continuous-Knowledge-Exchange Rule1 & 2

1. Capture knowledge in less than 1 minute 2. Small atomic knowledge-units

✔ ✔

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

Continuous-Knowledge-Exchange Rule 3

3. Knowledge-Domains instead of Team-Silos

✔

Databases

Architecture

SOA

Team

1

Team

2

Team

3

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

4. Keep knowledge up-to-date

Continuous-Knowledge-Exchange Rule 4

✔

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

Continuous-Knowledge-Exchange Rule 5

5. Share within a social network of experts

Instead of

✔

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

Continuous-Knowledge-Exchange Rule 6

6. Notify members

✔

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

Continuous-Knowledge-Exchange Rule 7

7. Automate reminders

✔

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

Continuous-Knowledge-Exchange One methodology, 7 solutions

•  Time

•  Granularity

•  Silos

•  Up-to-date

•  Distribution

•  Knowledge-Mining

•  Memorization

✔

✔

✔

✔

✔

✔

✔

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

Continuous-Knowledge-Exchange Influences

Rise of Social Networks

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

Continuous-Knowledge-Exchange Influences

Agile / Lean

"Continuous

Simple Zero Waste

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

Continuous-Knowledge-Exchange Influences

Knowledge-Management

Community of Practice

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

Continuous-Knowledge-Exchange Influences

Principle 6, Agile Manifesto

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

Realization

First define and adapt the processed, then use the tools

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

Continuous-Knowledge-Exchange Recommended steps

Requirements   Prac5ces   Introduc5on  

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

Continuous-Knowledge-Exchange Step 1: Requirements

•  Goal ? •  Teams / hierarchies ? •  Types of knowledge ? •  Knowledge-domains ? •  Subject Matter Experts ? •  Knowledge creation ? •  Knowledge user ?

Requirements  -  Workshop -  Requirements document

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

Continuous-Knowledge-Exchange Step 2: Customize / define processes

•  Capturing •  Structuring •  Sharing •  Reminder •  Roles

Prac5ces  -  Customizing -  Description

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

Continuous-Knowledge-Exchange Step 3: Introduction

•  Tool •  Pilot •  Rollout •  Integration in daily business •  Iterations and feedback from user

Introduc5on  -  Tool -  Rollout

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

wisdomclouds.com

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

What is a wisdomcloud ?

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel

Wisdomcloud = {Members, Topics}

Continuous-Knowledge-Exchange for project-teams © 2011 we:namix GmbH, Stefan Wendel