David Kramer's high-entropy blog

Knowledge Management Tips

I ended up talking about knowledge management quite a bit at Agile Games 2018 and Mob Programming 2018.  I don’t have a lot of formal training in this area, but it’s something that I’ve focused on a lot, and I’ve learned a lot from people who have studied it a great deal.  Rather than respond directly, I decided to add a blog post about it, to benefit more people.  This is an unordered list of these tips.  I would love to hear your additions or feedback on it.

Push vs Pull Communication Channels

There are two different general ways of communicating information: Push and Pull.  Push is when you send information out to recipients and they get notified (email, Twitter, Slack, etc) and Pull is when the recipient seeks out that information that was published earlier (Website, wiki, CMS, documentation).  Using the wrong type can prevent the recipients from having the most recent information in a timely manner.  The main deciding factor is, is it more important that people know about this information as soon as possible (changes to policy, status/availability updates, issues), or that people have the information when they need it (requirements, specifications, resources, environment details).  Many tools can do both, like wikis, which allow people to get notified of updates).  Email doesn’t work nearly as well as you would think at either push or pull, because most people in technical fields get so many emails that they find it hard to both notice and respond to timely emails and categorize those emails so they can find them later.

Lower The Barrier To Information Sharing

Creating and updating documentation is rarely the most favorite part of anyone’s job.  It’s rarely prioritized when the work is planned out, if it’s budgeted at all.  Starting to write documentation seems to be much harder than adding to it, so making it easy to get started is a big deal.  A little bit of good documentation can be a whole lot better than no documentation. There are several ways to make it easier:

  • Create a culture that values knowledge management at all levels: If the culture from the top does not value knowledge management, and time spend “not coding” is seen as wasted or overhead, then knowledge management will never get the time, resources, and attention required to do it right.  If team members know that time spent on sharing knowledge won’t be appreciated, they are less likely to focus on it.  It’s also important to convince the technical community of the benefits to them personally, like not getting stuck being “the database guy” or “the owner of the Therblug component”.
  • Create templates: You can either create generic templates for the kinds of documentation or information sharing you expect, or identify an existing one as an exemplar. “This is what a component documentation home page should look like”.   “Here is an example release communication”.  “Stories should have a format like this”.
  • Use a tool that makes it easy to iterate and easy to find information: If your way of creating documentation is to write a word document or PDF and upload it to a shared drive, it’s not very likely you’ll see a 1.1 version, let alone a 2.0 version.  In part that’s because a word document is not a very good collaboration tool, and shared drives don’t make it easy to find things.  I am a huge fan of wikis.
    • Wikis let you truly collaborate (some in real time)
    • Wikis allow endless hyperlinking, instead of forcing one path to each document like a shared drive, and dynamic links in the text to other pages and people.
    • Wikis make formatting very easy so the writer can focus more on the content
    • Wikis usually have subscriptions to topics to notify interested parties of changes and additions
    • Many wikis allow enough security that some sensitive information can be published to a limited audience
    • Many wikis are versioned, allowing everyone to see changes over time, and revert undesirable changes
    • Wikis often let you export pages as HTML, PDF, or DOC if you need to distribute the information externally
    • Creating a new page in a wiki is usually as easy as referencing the name on an existing page
    • Wikis have built in search engines
  • Maintain distribution lists: Recording the information is only half the battle. It needs to be delivered to the right people.  Relying on people to keep track of everyone in each group, and even which groups are interested in which topics, is error-prone, especially in a growing organization.  Mailing lists can be helpful, but the best tool for maintain distribution lists is something that can be used by several channels, like Active Directory/LDAP.
  • Divide up the work: Sometimes there’s only one subject matter expert in an area, but it’s often the case that different people know all, or different parts. Instead of putting the burden on just one person, you can have different people work on different parts, or have reviewers contribute to the initial effort.

Read on…


I Know What I Want To Come Back As

I’ve actually felt this way for a very long time.  If I died and got to come back as something else besides a human, my (presumably non-traditional) choice would be to come back as an octopus.

  • They are very well adapted to their environment, and do pretty well in some other environments
  • They have ample appendages to manipulate their environment
  • They have the ability to live in many places and eat a variety of foods, which makes them resilient to hard times.
  • They have turbo boost!  And [some have] camoflage!

This article I found on Wired’s website talks about new examples of some species of octopus which have shown real tool use!  Not just real tool use, but carrying around tools for later use.  And that’s the part that distinguishes intelligent tool use from instinctive behavior.  I’ve seen documentaries on them solving various physical puzzles, but this is even cooler.  They even have a Beatles song about them.


So Much For DNA Evidence

From Slashdot: Scientists Learn To Fabricate DNA Evidence.  This article covers two techniques that can now be used to falsify a crime scene with planted DNA.

On the one hand, this was probably inevitable.  There’s very little man can understand but not control.  On the other hand, this is truly a shame, as DNA evidence has been used frequently in the past few years to free wrongly-accued long-term inmates who were convicted before DNA tests were common.


New Research On Itching

This is a subject very important to me right now.  I recently spend some time in a rainy part of Maine, and came back with at least two dozen mosquito bites.  They’re finally starting to ease up a little, but I’ve lost a lot of sleep from waking up scratching myself.

I found this article on Slashdot: Neuron Path Discovery May Change Our Conception of Itching.  It turns out that itching isn’t really just another form of mild pain.  There are separate circuits of nerve cells to convey itchiness and pain, and their studies suggest that itch and pain signals are transmitted along different pathways in the spinal cord.


Sticky Tape Found To Emit Terahertz Radiation

From Slashdot: Sticky Tape Found To Emit Terahertz Radiation.  Reading through the comments, this is more of an interesting curiosity than a practical discovery, but I find the explanation fascinating.  Terahertz-range radiation can be used for imaging, like C-rays.  Denser objects absorb more of the energy, so looking at the “shadow” from the other side of the object can show hidden weapons, etc.  Unlike C-rays, though, terahertz-range radiation does not harm the body.

Read on…


100 Essential Skills for Geeks

From Wired: 100 Essential Skills for Geeks.

I found this list fun, but a lot of the skills on their list are either too esoteric for even a mid-level geek (lock picking, bypassing passwords), or to specific to be be general geek knowledge (steganographics, robotics).  But it is fun.

I’ll update this post tonight with my score.  I welcome comments with yours.

Next Page »

Site info