Talk:Knowledge mapping

From Cynefin.io
Jump to navigation Jump to search

General discussion

Knowledge mapping is one of the three key pillars in the assessment for the adoption of the Field guide to managing complexity (and chaos) in times of crisis. What are the other two pillars - human sensor networks, and the entanglement of informal and formal networks? - Ebester (talk) 09:49, 13 September 2021 (UTC)

I have used the template for Methods, but as it is an Assembly, it needs some adjustments. I have added the headline "Methods and concepts". Could someone bring the changes needed please? @Dave --Corinalupu (talk) 09:30, 4 March 2021 (UTC)

Added picture to illustrate the overall K mapping assembly(age?). Format is PDF as the Wiki currently prevents the upload of SVG files. Available to provide the original vectorial file to anyone who wants to improve the picture or correct inaccuracies or major mistakes. -----Luca OrlassinoT-A-L-K 09:46, 10 April 2021 (UTC)  Done

Vector picture uploaded. Improvements still needed. -----Luca OrlassinoT-A-L-K 18:57, 26 April 2021 (UTC)

Assemblage typical flow

Attempt at capturing sequencing and links between Methods in the Assemblage, in the flow that Dave describes: Dglanvill (talk) 11:56, 19 April 2021 (UTC)

  • Inputs to "capture decisions" can = SenseMaker data, decisions diaries / lessons learned journals, workshops, etc. (sub-methods)
  • These decision items are clustered, mapped and analysed in Decision Mapping
    • (Optional detour into DI-map vs Process map comparison for executive reflection, and knowledge projects resulting from this)
  • Then apply ASHEN to unpack each decision cluster (from outputs of Decision Mapping) in more detail.
    • Cluster the results of ASHEN into Knowledge Objects (defn: some meaningful/coherent cluster of knowledge that can be managed) and rank based on their vulnerability to loss (probably the key priority measure for knowledge)
  • Knowledge objects + key Decisions ("keeping decision-makers up at night" from Decision Mapping?) -> inputs into the Dependency Matrix (rows and columns)
    • Dependency matrix is processed to identify opportunities and therefore a portfolio of strategic knowledge projects.


Another suggestion for the last one:

  • Knowledge objects + key "things that matter", for instance "essential functions" or "core processes" ("what keeps decision-makers up at night" from A preliminary stage?) -> inputs into the Dependency Matrix (rows and columns)
    • Dependency matrix is processed to identify opportunities and therefore a portfolio of strategic knowledge projects. --Corinalupu (talk) 10:38, 20 April 2021 (UTC)

Priority items on Knowledge mapping page and related methods

The points listed below, in decreasing order of priority, are referred to both the Knowledge mapping page and to the pages of the method which form the assemblage:

  1. Getting method names right
    1. Executive problem identification
    2. Problem-knowledge matrix = Dependency matrix (was QQE) Done
    3. Decision map-process map comparison
    4. Project mapping on Cynefin (or refer this to one of the existing Cynefin methods as one special case)
  2. Gathering useful sources (incl. blogs, videos, and method practitioners' experiences)
  3. Restructuring Knowledge mapping as a prototypical assemblage template Done
  4. Creating the template page for Assemblages (also referenced in Assemblages) based on Knowledge mapping Done
  5. Updating the Knowledge mapping assemblage picture accordingly

(Above list initiated by -----Luca OrlassinoT-A-L-K 10:35, 14 April 2021 (UTC))

User talk:LucaOrlassino Shouldn't we consider first the amount of content before turning something into a page?
    1. Executive problem identification > is a step in knowledge mapping that can then be used in QQE matrix
    2. Problem-knowledge matrix > that already has a name which might be changed but for now is QQE matrix
    3. Decision map-process map comparison > is also a step in decision mapping
    4. Project mapping on Cynefin (or refer this to one of the existing Cynefin methods as one special case)> is also a step in at the end of knowledge mapping
@LucaOrlassino: Confirmed with Dave:
    1. Executive problem identification > yes - this is a necessary step/input, and we can unpack various ways to get them to do this... the simplest version is asking "what keeps decision-makers up at night?" but more elaborate may include decision journalling etc...
    2. Problem-knowledge matrix > is called Dependency matrix (was QQE) - this is a sub-method page
    3. Decision map-process map comparison > is a step in the Decision mapping sub-method
    4. Project mapping on Cynefin = contextualization, refer to the existing Cynefin methods (such as 3-points) - this is an Output link from KM into the next steps... Dglanvill (talk) 12:33, 16 April 2021 (UTC)
I would offer as first priority to get all the content into a single place and then split it, and figure out if specific pages are needed, because a part starts to be substantial. --Corinalupu (talk) 12:04, 14 April 2021 (UTC)
@Corinalupu:, I might be wrong here, but from KM/DM initial sessions, I remember that Dave's request was to have separate methods (not just steps) for each of the points above, and a separate Wiki page for each of them, so that methods could easily be recombined in a modular manner. Putting (almost) everything in one place can be a temporary option, but it limits recombination and would imply relevant later rework. More below. -----Luca OrlassinoT-A-L-K 14:56, 14 April 2021 (UTC)
About Executive problem identification: I'm quite sure Dave suggested to have it as a separate method in one of the two preliminary sessions. It has a validity of its own even as a standalone module, and, besides a list of problems which in turn become the matrix input, it includes highlighting outliers as a specific output with a value of its own. -----Luca OrlassinoT-A-L-K 14:56, 14 April 2021 (UTC)
About Problem-knowledge matrix, I understand that "QQE matrix" is an obsolete name Clusters in the tail (2014), and that the new name is "Dependency matrix" (see referenced blog posts). Btw, a QQE Matrix page already exists: if this is the case, it should be deleted / redirected-----Luca OrlassinoT-A-L-K 14:56, 14 April 2021 (UTC)
Confirmed with Dave: this is the Dependency matrix, previously called QQE matrix. Suggest that we delete QQE page but is it possible to name new page as "Dependency matrix (QQE)" to enable connections with older content? On page, we can define QQE (qualitative-quantitative-emergent) which will help spell out the what and why of the method. Dglanvill (talk) 12:33, 16 April 2021 (UTC)
About Decision map-Process map comparison, it could be a step in Decision mapping, but I suspect it could also work well with the output of Anecdote circles (and maybe less so Future backwards?). Its output, in turn, is an input for the Project output in Cynefin--~~
About Project output in Cynefin (which from a workflow point of view I would imagine similar or nearly identical to Butterfly stamping?), it can take inputs from both the matrix and the decision-process comparison. I would suggest that the method graph would be much readable if we had it as a separate node. -----Luca OrlassinoT-A-L-K 14:56, 14 April 2021 (UTC)
I believe this is taking the project outputs into a Cynefin Contextualisation exercise ie 4-Points or similar. So perhaps we should represent it in the assemblage, with clarity as to how and why you would link this in, but link out to the method page for the process details? Dglanvill (talk) 12:33, 16 April 2021 (UTC)
User talk:LucaOrlassino Thanks for taking me through your thought process and intentions, it helps me understand where your suggestions come from. I'm pretty sure Dave was talking about the pages that already exists. I have watched both videos 2 or 3 times. That being said, it doesn't matter. There could still be value to have them as pages, I agree. But on the other hand, there is nothing worse than trying to understand a method and needing to open 5 other pages for a couple of steps that could be summed up in 10 lines each, because there is nothing more to say. That's why I think it would be better to first see what's the content, before deciding to fit it in a new page or not and then pick the appropriate name, if we see that it can go even further than originally said. --Corinalupu (talk) 16:57, 14 April 2021 (UTC)
@Corinalupu:, no objection on seeing content first. -----Luca OrlassinoT-A-L-K 18:52, 14 April 2021 (UTC)

References =

The Tacit Dimension, Michael Polanyi. 1966. This is the book that contains the quote "we can know more than we can tell" but it only mentioned in the forward of the book written by Amartya Sen --GregBro (talk) 18:53, 23 February 2021 (UTC)

Find a reference for the 3 rules of knowledge mgmt - blog? --GregBro (talk) 18:53, 23 February 2021 (UTC)

Retrieved from ‘https://cynefin.io/index.php?title=Talk:Knowledge_mapping&oldid=5209’