The Architecture of Personal Knowledge Management

Introduction

Harold Jarche posted a useful deconstruction of the processes involved in web-based personal knowledge management (PKM). Building on this, and in order to make a lot of implicit stuff in my head explicit, I've started developing the model into a full mapping of processes to tools.

Harold's model looks like this:

As I began to unpick Harold's seven processes I realised that although they are primarily focused on "self", one key aspect to understand them is to identify the different roles that "self" (and "others") play. This aspect of the model so far is shown in the Introductory View.

Alongside the work of developing models for each of the processes, I began to develop a view of the key information artefacts manipulated by the PKM processes - PKMInformationView

Processes

The next seven maps each focus on one process, and identify key sub-processes, top-level application services, and the information handled by each process.

Modelling Approach

Modelling Language

I've decided to use Archimate as the modelling language, as an opportunity to learn it.

Next Steps

expand the application layer
model a couple of specific tools to test the vertical integrity of the model