33 Matching Annotations
  1. Nov 2022
    1. https://www.evernote.com/shard/s204/client/snv?noteGuid=5b7828b7-c4f9-4242-b62f-788eeb44c76e&noteKey=34f69bfeebbb6bca&sn=https%3A%2F%2Fwww.evernote.com%2Fshard%2Fs204%2Fsh%2F5b7828b7-c4f9-4242-b62f-788eeb44c76e%2F34f69bfeebbb6bca&title=Powerful%252C%2Bnon-judgmental%2Bquestions

      Powerful, non-judgmental questions

      • If you had to guess, what would have to be true for you to...?
      • If you did know...
      • (on tangent) ...and how does that relate to you?
      • What's not allowing you to...?
      • What prevents you from asking…?
      • Do you want to go into this?
      • What's your criteria for saying yes?
      • What would have you say yes?
      • What are the things we're lacking?
      • What's the scary question that you're not asking?
      • What are the qualities you want for [being, action, process, etc.]?
      • How would you behave if you were the best in the world at what you do?

      I'm starting a list of powerful, non-judgmental questions for coaching or just relationships in general. Here's the starting batch https://t.co/ktsYVxkQna pic.twitter.com/Dq1zQnWqAS

      — Tiago Forte (@fortelabs) January 15, 2019
      <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

      These questions and similar ones (work this out) could be interesting prompts to be included on a syllabus or as starts for an annotated syllabus. (eg: What do you want to get out of this class? What do you already know about these areas? How can we expand on what you know? What would you like to explore?, etc.)

    1. Tiago’s methodology is app-agnostic. He’s a systems and principles kind of thinker, so even though I use physical notecards, his work has influenced the evolution of my processes.

      Billy Oppenheimer indicates that Tiago Forte's systems and methods have influenced the evolution of his own note taking process.

  2. Oct 2022
    1. Does anyone else work in project-based systems instead? .t3_y2pzuu._2FCtq-QzlfuN-SwVMUZMM3 { --postTitle-VisitedLinkColor: #9b9b9b; --postTitleLink-VisitedLinkColor: #9b9b9b; --postBodyLink-VisitedLinkColor: #989898; }

      reply to u/m_t_rv_s__n https://www.reddit.com/r/Zettelkasten/comments/y2pzuu/does_anyone_else_work_in_projectbased_systems/

      Historically, many had zettelkasten which were commonplace books kept on note cards, usually categorized by subject (read: "folders" or "tags"), so you're not far from that original tradition.

      Similar to your work pattern, you may find the idea of a "Pile of Index Cards" (PoIC) interesting. See https://lifehacker.com/the-pile-of-index-cards-system-efficiently-organizes-ta-1599093089 and https://www.flickr.com/photos/hawkexpress/albums/72157594200490122 (read the descriptions of the photos for more details; there was also a related, but now defunct wiki, which you can find copies of on Archive.org with more detail). This pattern was often seen implemented in the TiddlyWiki space, but can now be implemented in many note taking apps that have to do functionality along with search and tags. Similarly you may find those under Tiago Forte's banner "Building a Second Brain" to be closer to your project-based/productivity framing if you need additional examples or like-minded community. You may find that some of Nick Milo's Linking Your Thinking (LYT) is in this productivity spectrum as well. (Caveat emptor: these last two are selling products/services, but there's a lot of their material freely available online.)

      Luhmann changed the internal structure of his particular zettelkasten that created a new variation on the older traditions. It is this Luhmann-based tradition that many in r/Zettelkasten follow. Since many who used the prior (commonplace-based) tradition were also highly productive, attributing output to a particular practice is wrongly placed. Each user approaches these traditions idiosyncratically to get them to work for themselves, so ignore naysayers and those with purist tendencies, particularly when they're new to these practices or aren't aware of their richer history. As the sub-reddit rules indicate: "There is no [universal or orthodox] 'right' way", but you'll find a way that is right for you.

  3. Aug 2022
    1. The technique is simple: you highlight the main points of a note,and then highlight the main points of those highlights, and so on,distilling the essence of a note in several “layers.”
    1. The real issue with "learning in public" is them emphasis placed on "being an expert," which is *everywhere*. It's a capitalist mindset, convincing people that even as beginners they should consider themselves "experts" bc this is how you get exposure aka how u scale.

      The public online commons, by means of context collapse, allows people to present themselves as experts within an area without actually being experts.

      Some of these "experts" or "gurus" primarily have expertise in communication or promoting themselves or a small piece of a topic about which they know a little more than the average public.

  4. Jun 2022
    1. Compass Points, a routine for examining propositions.

      via https://pz.harvard.edu/sites/default/files/Compass%20Points_0.pdf

      • E- excited
      • W- worrisome
      • N - need to know
      • S - stance or suggestion for moving forward

      These could be used as a simple set of rules for thumb for evaluating and expanding on ideas in note taking or social annotation settings.

      Compare these with the suggestions of Tiago Forte in his book Building a Second Brain. Which is better? More comprehensive? Are there any ideas missing in a broader conceptualization? Is there a better acronymization or analogy for such a technique?

    1. Just be sure to take notes along the way.

      Not a half bad sentence to end the whole enterprise with.

    2. If we overlay the four steps of CODE onto the model ofdivergence and convergence, we arrive at a powerful template forthe creative process in our time.

      The way that Tiago Forte overlaps the idea of C.O.D.E. (capture/collect, organize, distill, express) with the divergence/convergence model points out some primary differences of his system and that of some of the more refined methods of maintaining a zettelkasten.

      A flattened diamond shape which grows from a point on the left so as to indicate divergence from a point to the diamond's wide middle which then decreases to the right to indicate convergence  to the opposite point. Overlapping this on the right of the diamond are the words "capture" and "organize" while the converging right side is overlaid with "distill" and "express". <small>Overlapping ideas of C.O.D.E. and divergence/convergence from Tiago Forte's book Building a Second Brain (Atria Books, 2022) </small>

      Forte's focus on organizing is dedicated solely on to putting things into folders, which is a light touch way of indexing them. However it only indexes them on one axis—that of the folder into which they're being placed. This precludes them from being indexed on a variety of other axes from the start to other places where they might also be used in the future. His method requires more additional work and effort to revisit and re-arrange (move them into other folders) or index them later.

      Most historical commonplacing and zettelkasten techniques place a heavier emphasis on indexing pieces as they're collected.

      Commonplacing creates more work on the user between organizing and distilling because they're more dependent on their memory of the user or depending on the regular re-reading and revisiting of pieces one may have a memory of existence. Most commonplacing methods (particularly the older historic forms of collecting and excerpting sententiae) also doesn't focus or rely on one writing out their own ideas in larger form as one goes along, so generally here there is a larger amount of work at the expression stage.

      Zettelkasten techniques as imagined by Luhmann and Ahrens smooth the process between organization and distillation by creating tacit links between ideas. This additional piece of the process makes distillation far easier because the linking work has been done along the way, so one only need edit out ideas that don't add to the overall argument or piece. All that remains is light editing.

      Ahrens' instantiation of the method also focuses on writing out and summarizing other's ideas in one's own words for later convenient reuse. This idea is also seen in Bruce Ballenger's The Curious Researcher as a means of both sensemaking and reuse, though none of the organizational indexing or idea linking seem to be found there.

      This also fits into the diamond shape that Forte provides as the height along the vertical can stand in as a proxy for the equivalent amount of work that is required during the overall process.

      This shape could be reframed for a refined zettelkasten method as an indication of work

      Forte's diamond shape provided gives a visual representation of the overall process of the divergence and convergence.

      But what if we change that shape to indicate the amount of work that is required along the steps of the process?!

      Here, we might expect the diamond to relatively accurately reflect the amounts of work along the path.

      If this is the case, then what might the relative workload look like for a refined zettelkasten? First we'll need to move the express portion between capture and organize where it more naturally sits, at least in Ahren's instantiation of the method. While this does take a discrete small amount of work and time for the note taker, it pays off in the long run as one intends from the start to reuse this work. It also pays further dividends as it dramatically increases one's understanding of the material that is being collected, particularly when conjoined to the organization portion which actively links this knowledge into one's broader world view based on their notes. For the moment, we'll neglect the benefits of comparison of conjoined ideas which may reveal flaws in our thinking and reasoning or the benefits of new questions and ideas which may arise from this juxtaposition.

      Graphs of commonplace book method (collect, organize, distill, express) versus zettelkasten method (collect, express, organize (index/link), and distill (edit)) with work on the vertical axis and time/methods on the horizontal axis. While there is similar work in collection the graph for the zettelkasten is overall lower and flatter and eventually tails off, the commonplace slowly increases over time.

      This sketch could be refined a bit, but overall it shows that frontloading the work has the effect of dramatically increasing the efficiency and productivity for a particular piece of work.

      Note that when compounded over a lifetime's work, this diagram also neglects the productivity increase over being able to revisit old work and re-using it for multiple different types of work or projects where there is potential overlap, not to mention the combinatorial possibilities.


      It could be useful to better and more carefully plot out the amounts of time, work/effort for these methods (based on practical experience) and then regraph the resulting power inputs against each other to come up with a better picture of the efficiency gains.

      Is some of the reason that people are against zettelkasten methods that they don't see the immediate gains in return for the upfront work, and thus abandon the process? Is this a form of misinterpreted-effort hypothesis at work? It can also be compounded at not being able to see the compounding effects of the upfront work.

      What does research indicate about how people are able to predict compounding effects over time in areas like money/finance? What might this indicate here? Humans definitely have issues seeing and reacting to probabilities in this same manner, so one might expect the same intellectual blindness based on system 1 vs. system 2.

      Given that indexing things, especially digitally, requires so little work and effort upfront, it should be done at the time of collection.

      I'll admit that it only took a moment to read this highlighted sentence and look at the related diagram, but the amount of material I was able to draw out of it by reframing it, thinking about it, having my own thoughts and ideas against it, and then innovating based upon it was incredibly fruitful in terms of better differentiating amongst a variety of note taking and sense making frameworks.

      For me, this is a great example of what reading with a pen in hand, rephrasing, extending, and linking to other ideas can accomplish.

    3. Wayne LacsonForte: On My Way To Me
    4. Tagging for personal knowledge management is a subject unto itself. Whilenot necessary to get started, I’ve written a free bonus chapter on tags you candownload at Buildingasecondbrain.com/bonuschapter.

      Forte's book is a pathway that acts as just another part of his sophisticated sales funnel.

    5. organizing system PARA,* which stands for the four main categoriesof information in our lives: Projects, Areas, Resources, and Archives.These four categories are universal, encompassing any kind ofinformation, from any source, in any format, for any purpose.*

      a project based (pseudo-folder) approach

    6. On average I capture just twonotes per day

      Tiago Forte self-reports that he captures two notes a day.

      Link to other's notes per day including Barthes, Luhmann, et al.

    1. As Lane put it, it's a Personal Information Storage System (PISS).

      What a zinger! 😜

    2. Tiago's book follows the general method of the commonplace book, but relies more heavily on a folder-based method and places far less emphasis and value on having a solid index. There isn't any real focus on linking ideas other than putting some things together in the same folder. His experience with the history of the space in feels like it only goes back to some early Ryan Holiday blog posts. He erroneously credits Luhmann with inventing the zettelkasten and Anne-Laure Le Cunff created digital gardens. He's already retracted these in sketch errata here: https://www.buildingasecondbrain.com/endnotes.

      I'll give him at least some credit that there is some reasonable evidence that he actually used his system to write his own book, but the number and depth of his references and experience is exceptionally shallow given the number of years he's been in the space, particularly professionally. He also has some interesting anecdotes and examples of various people including and array of artists and writers which aren't frequently mentioned in the note taking space, so I'll give him points for some diversity of players as well. I'm mostly left with the feeling that he wrote the book because of the general adage that "thought leaders in their space should have a published book in their area to have credibility". Whether or not one can call him a thought leader for "re-inventing" something that Rudolphus Agricola and Desiderius Erasmus firmly ensconced into Western culture about 500 years ago is debatable.

      Stylistically, I'd call his prose a bit florid and too often self-help-y. The four letter acronyms become a bit much after a while. It wavers dangerously close to those who are prone to the sirens' call of the #ProductivityPorn space.

      If you've read a handful of the big articles in the note taking, tools for thought, digital gardens, zettelkasten space, Ahren's book, or regularly keep up with r/antinet or r/Zettelkasten, chances are that you'll be sorely disappointed and not find much insight. If you have friends that don't need the horsepower of Ahrens or zettelkasten, then it might be a reasonable substitute, but then it could have been half the length for the reader.

  5. May 2022
    1. The lengthand format don’t matter—if a piece of content has been interpretedthrough your lens, curated according to your taste, translated intoyour own words, or drawn from your life experience, and stored in asecure place, then it qualifies as a note.

      Forte's definition of a note.

    2. Forte, Tiago. Building a Second Brain: A Proven Method to Organize Your Digital Life and Unlock Your Creative Potential. Atria Books, 2022. https://www.simonandschuster.com/books/Building-a-Second-Brain/Tiago-Forte/9781982167387.

    1. Apps and courses that help you make these pretty pictures are not helping you to advance your knowledge or to write increasingly insightful works.

      Based on my preliminary reading of Tiago Forte's forthcoming book, this seems broadly true.

    1. for personal wiki and how to build knowledge (and even creation) out of streams you might want to check into @fortelabs's stuff. possibly a good link between streams and gardens and back.

      Evidence that Tiago should be aware that Le Cunff didn't coin "digital garden" in 2020.

  6. Feb 2022
  7. Nov 2021
    1. When we look at the Zettelkasten, it looks quite inconspicuous and small and doesn't give away the secret. The outer appearance is trivial, so what is it then that made Luhmann refer to it as his second brain.

      the translation for "second brain" is direct? Does he provide a source for where this was recorded? It's the first time I've heard the phrase outside of Tiago Forte's use.

  8. Jul 2021
  9. Nov 2020
    1. Finally, you gain the ability to reuse previously built packets for new projects. Maybe some research you did for an online marketing campaign becomes useful for a new campaign. Or some sketches that didn’t quite make it into an old design give you inspiration for a new one. Or some book notes you wrote down casually turn out to be very useful for an unforeseen challenge a year later.

      The Intermediate Packet approach allows you to reuse previously built packets for new projects

      By incorporating existing packets in new projects, you gain the ability to deliver new projects much faster.

    2. Fourth, big projects become less intimidating. Big, ambitious projects feel risky, because all the time you spend on it will feel like a waste if you don’t succeed. But if your only goal is to create an intermediate packet and show it to someone — good notes on a book, a Pinterest board of design inspirations, just one module of code — then you can trick yourself into getting started. And even if that particular Big Project doesn’t pan out, you’ll still have the value of the packets at your disposal!

      The Intermediate Packet approach make big projects less intimidating.

      Big projects feel risky because the time you spend on it feels like a waste if you don't succeed. Intermediate Packets allow you to finish smaller chunks. You can use this to trick yourself to get started on bigger things.

    3. By always having a range of packets ready to work on, each one pre-prepared to work on at any time, you can be productive under any circumstances – waiting in the airport before a flight, the doctor’s waiting room, 15 minutes in between meetings.

      If you have a range of packet sizes available to work on, you can use any time block size to deliver value.

    4. Third, you can create value in any span of time. If we see our work as creating these intermediate packets, we can find ways to create value in any span of time, no matter how short. Productivity becomes a game of matching each available block of time (or state of mind, or mood, or energy level) with a corresponding packet that is perfectly suited to it.

      The Intermediate Packet approach ensures you are delivering value after every iteration, regardless of size

      You no longer need to rely on large blocks on uninterrupted time if you focus on delivering something of value at the end of each block of time.

    5. Second, you have more frequent opportunities to get feedback. Instead of spending weeks hammering away in isolation, only to discover that you made some mistaken assumptions, you can get feedback at each intermediate stage. You become more adaptable and more accountable, because you are performing your work in public.

      Intermediate Packets give you more opportunities to get feedback

    6. The first benefit of working this way is that you become interruption-proof. Because you rarely even attempt to load the entire project into your mind all at once, there’s not much to “unload” if someone interrupts you. It’s much easier to pick up where you left off, because you’re not trying to juggle all the work-in-process in your head.

      The intermittent packet approach makes you more resilient towards interruptions

      Because you're not loading an entire project in your mind at once, you're not losing as much context when you get interrupted.

    1. Bringing this back to filtering, not only am I saving time and preserving focus by batch processing both the collection and the consumption of new content, I’m time-shifting the curation process to a time better suited for reading, and (most critically) removed from the temptations, stresses, and biopsychosocial hooks that first lured me in.I am always amazed by what happens: no matter how stringent I was in the original collecting, no matter how certain I was that this thing was worthwhile, I regularly eliminate 1/3 of my list before reading. The post that looked SO INTERESTING when compared to that one task I’d been procrastinating on, in retrospect isn’t even something I care about.What I’m essentially doing is creating a buffer. Instead of pushing a new piece of info through from intake to processing to consumption without any scrutiny, I’m creating a pool of options drawn from a longer time period, which allows me to make decisions from a higher perspective, where those decisions are much better aligned with what truly matters to me.

      Using read-it later apps helps you separate collection from filtering.

      By time-shifting the filtering process to a time better suited for reading, and removed from temptations, you will want to drop 2/3 of the content you save.

      This allows you to "make decisions from a higher perspective"

    1. There are different schools of thought in the realm of productivity.

      The energy school focuses on optimizing your energy levels. The focus school is all about getting into and staying in flow. The efficiency school is obsessed with the logistics of work.

      Tiago positions his philosophy as the value school: Making sure you deliver value after every block of work by delivering, what Tiago calls, Intermediate Packets.

      He draws parallels to Just In Time production from Toyota and Continuous Integration in software development.

      Intermediate Packets is continuous integration for knowledge work.