This is key imo. The link between personal knowledge and communal K. In context of TGL it also means fleshing out the purpose, identity and intent of our work. A step to and in support of [[Networked Agency 20160818213155]] , here the functioning as a company Can I express this to the team?

This is a benefit that Doto does not express (because he stays within the context of ZK, and this one becomes apparent if you look at the ZK in the context of the group of collab. Any non-random and pre-existing group will find theur benefit in that context, rather than in the instrument's built-in affordances. tech+issue=value.

In TGL this would the diff domain teams and project teams, putting stuff to their own purpose.

Vgl landscapes, IEC writing projects, deskresearch/essays in general.

For me the purpose of a collab zk would need to be aligned to what drives the collaborators. E.g. how I tie pkm to individual professional activism and autonomy, and extended/aggregated to teamkm it drives the core value of constructive activism of my company, and how we use [[Systems convening denken Wenger Trayner 20230914131102]] to translate that into interventions and desirable client projects. Vgl [[PKM systems convening activisme relatie 20241123085857]] expressing that connection.

This describes a wiki too. What difference? Wiki tends to follow the Wikipedia model perhaps, aiming for completeness / definitive state? Wikipedia is not atomic in the ZK sense. Also public wiki's (the ones one is by def aware of) are an output themselves. My internal wiki 2004-2012 was much more atomic and not an output but an instrument. So if wiki then more of the instrument style, iow ZK by another name. A collective network of meaning and sense making