Today again I delecter of an activity I both hate and adorn. The noble name I give is Knowledge Combing, the hatefull own is sorting my stuff. Benefit: Beyond keeping my stuff neat and actual the fact to review tons of things in a short time and do the effort of bringing it back into my mind and check that it rings bells is a very efficient way to reinforce long term memory and refresh short term one. At one end there is whatever I collect from my daliy work, thoughts, exchange or rreadiings. This will first be collct in a large ToSort folder. First step almost daily will be to sort this into first and second level hiearchy. First level is to which silo of my life it corresponds personal or professional. very ovious for some stuff, less when it is insights about personal relates to professional. I am a focused man so professional means Kneaver only but other people mayhave several silos. Second level in the Kneaver Silo will be split along execution or functional split: Software development, Knowledge Management, Marketing, Management. Up to here it easy and best done asap. Below that it would be very time consuming to tag (because we can say move to folders or tag it is the same). To group common stuff at once under a name, any name is a good practice. Say whatever I wrote down durin a ragansocial chat I will keep under #ragansocial date. That wil be easier to sort herefater. Big chunks like this are quikcly finding their place down the taxonomy of Kneaver Filer. Now we face two situations - The taxonomy is changing andgetting more and more refined as the contents is larger and we gain more understanding of the field. - Some pieces are left over and stay in higher level of hierarchy because not time is dedicated to sort them, or they were sort in the wrong place and must be sorted again. Knwoledge Combing is about reviewing such pieces lagging in the ToSort areas. I can come acrosss stuff 9 years old. Well I am the first user of Kneaver there is a good reason to it. sensemaking at posteriori. This isthe place where a strong procedure must tak place and lead to as much pruning as possible. - Items are old but it happens that recent events brings a new light on it and the tension between the importance you placed on it at that ttime and what you know it between makes it relevant to keep somewhere. example : Delicious ToU when I accepted them versus the sunset of it. Example of Don’t. Stil be very selective here because everything can be seen as potentialy enlighteeing at any time. - The items are old, your don’t remember why you kept them, the context is lost, it relates to company or people who went out of your radar in between -> drop Names of dolders below can be different for you but keep this hierarchy: TechWatch: Things I keep because it could help, be a reference one day. Methodology: ThingsI found, not yet contextualized by judged as applicable and relevant/ XX project; things wihc are conextualized and/or applied each int is project