Thursday, July 04, 2002



Get up to speed on K-Logging.. brent ashley:

The thinking-out-loud style of writing a K-log journal of project activities allows every part of the process to remain available during and after the project. This allows detailed review and enables latecomers to the project to get up to speed. The dead-end attempts that provide the best opportunity for learning are documented and kept for others to learn from.

more great language for your team briefing...

[a klog apart]
10:56:21 PM •  • comment  


Klogging 101: What, Why, and How.. Explaining klogging to the gang at the office? To your user group?

Here's a little slide show you can use.

Klogging 101: What, Why, and How.

Talking points for 15-20 minutes.

Not included, but may be useful: a demo session.

  • Bring your favorite blogging tools (some of the slides mention UserLand products).
  • Write to the web
    • Open an edit page.
    • Write a post.
    • Publish it.
    • See the results on the web.
  • Comment on incoming news and data
    • Look at the news aggregator.
    • Comment on one.
    • Publish your comment and see the results.

Suggestions? Click here to send an email to the editor of this weblog. <A title="Add Phil Wolff to your AIM Buddy List" href="aim:addbuddy?screenname=evanwolff">AIM Y! @Ryze

[a klog apart]
10:55:50 PM •  • comment  


Unstructured content. Martin Butler has written a brief and to-the-point article highlighting that 80% of the content in an organisation is "unstructured", [Column Two]
10:49:31 PM •  • comment