Situational Note-taking: Capture Significant Insights Outside the Room

A case study

From June 15 to June 21, I engaged in a thematic conversation with a friend via email discussions, exploring various topics around the theme of Note-taking and Knowledge Engagement. See the screenshot below.

The above diagram is one of the by-products of the thematic conversation. This post will share more background on the process of making the diagram. Moreover, I’d like to use this story to explain the framework behind the diagram.

A Thematic Conversation About Note-taking

My friend’s primary theme is “Consciousness and Thoughts” from a practical perspective. He doesn’t want to develop a scientific theory of Consciousness or a philosophical theory of Consciousness. He aims to develop a simple framework to explain how Consciousness works to high students.

Our conversation touched on several related themes such as the Note-taking System, Zettelkasten, Niklas Luhmann’s Creative Life, Semiotic System Diagram, Experience Sampling Method (ESM), The Network of Project, Mental Moves, Spontaneous Concept System, Early Discovery, Knowledge Brand, etc.

The conversation ended on June 21 because I was busy preparing for our family road trip from June 24 to July 3.

There are several outcomes triggered by the thematic conversation. The major outcome is the possible book titled Thematic Exploration: The Early Discovery of Knowledge Engagement (book, v1) which was edited on June 23.

On June 19, I replied to the #4 thread of the thematic conversation and briefly introduced the Strategic Thematic Exploration framework. On June 23, I expanded the email into a long post and made a TOC (Table of Contents) for a possible book in one day.

I also mentioned my unit of analysis on Mind: Context (Mind) in the #4 thread. It also triggered me to publish a post about it on TALE.

The above “Note-taking” and “Draft-making” diagram was born on June 15. It was related to the #1 thread of the thematic conversation.

The Story

The draft of the diagram was made at the Pearland Recreation Center & Natatorium. I sent my son to attend an event of a summer swim camp at the Natatorium.

Inspired by our thought-provoking thematic conversation, I decided to bring Sonke Ahrens’ 2017 book How to Take Smart Notes with me to the Natatorium.

Although I had read this book before, that night I wanted to explore it again. Immediately, I found myself pausing at Page 2.

I noticed that there are two terms: note-taking and draft-making.

Writing is not what follows research, learning or studying, it is the medium of all this work. And maybe that is the reason why we rarely think about this writing, the everyday writing, the note-taking and draft-making. Like breathing, it is vital to what we do, but because we do it constantly, it escapes our attention.

Upon reflection, I recognized a contrast between Sonke Ahrens’ perspective and my own. While his primary theme revolves around academic production, my primary theme is about tacit knowledge and creative cognition in general.

In order to highlight this difference, I started making a visual note by using the “Dot and Circle” meta-diagram in my notebook. See the photo below.

After returning home, I continually worked on the idea immediately.

What did I do?

I did three things within less than one hour.

First, I quickly made the final version of the diagram on Miro, utilizing the “Dot and Circle” template.

Second, I wrote a short post titled Knowledge Engagement: The “Dot and Circle” meta-diagram on Curativity Center’s blog hosted on Medium. The “Note-taking” and “Draft-making” meta-diagram was based on a meta-diagram called “Dot and Circle”. I had been planning to write a post about the meta-diagram for a while.

I just added a short note about the “Note-taking” and “Draft-making” diagram in the blog post.

This week I started a thematic conversation about “note-taking” with a friend. Our conversation inspired me to think about “note-taking”, “concept system” and “project engagement”.

Tonight I made the diagram below. The primary focus of the diagram is “Note-taking” and “Draft-making”.

Moreover, this diagram inspired me to discover the following three types of “Frame for Work”.

Frame A: a Framework for Developing a “Spontaneous Concept System”

Frame B: a Framework for Running a “Developmental Project”

Frame C: a Framework for Curating Notes and Continuous Curation

Since these diagrams share a set of terms, you can see them as a diagram network.

You can pay attention to two details:

• Curating Notes: I didn’t add a hyperlink there. It means I didn't write something about the topic.
• Diagram Network: The “Note-taking” and “Draft-making” diagram is part of a large diagram network.

Third, I shared the short post on Linkedin.

I didn’t have enough time to write a long article such as this one that night. Instead, I decided to write a short blog post about the “Dot and Circle” meta-diagram.

Why?

Because these three tasks didn’t require deep thinking. I only needed to use the “Dot and Circle” template, and curated some pieces about four examples by copying and pasting texts and pictures from my old posts.

The next day, I shared the Linkedin post by adding the following piece:

The attached diagram was inspired by Sonke Ahrens’ book How to Take Smart Notes (2017).

Last night, I read the book and found the following text:

“Writing is not what follows research, learning or studying, it is the medium of all this work. And maybe that is the reason why we rarely think about this writing, the everyday writing, the note-taking and draft-making. Like breathing, it is vital to what we do, but because we do it constantly, it escapes our attention” (p.2)

The author connects “note-taking” and “draft-making” together for his book. He introduces Niklas Luhmann’s method of note-taking to academic students and professors who have to write papers and books for their journey of knowledge engagement.

Most people think about the same way, note-taking is a process of productivity. Yes, it is part of Knowledge Production.

However, there is an aspect called Knowledge Discovery. Note-taking is also about Developing your “Spontaneous Concept System”.

If you are not an academic student or professor, you don’t have to rely on publishing papers and books as your primary activities. However, you have to work on improving your ideas systematically.

Why?

Your Spontaneous Concept System is the model of your projects. One month ago, I worked on a Strategic Design Research project about a web3.0 platform, I discovered a Concept System after testing the platform. It was clear that the founder and designer of the platform have built a model of the platform.

And, we can use a Concept System as the representation of the model.

Moreover, if you are a product designer, you can watch the development of your Concept System and improve it because it is the model of your product.

If your product is a web3.0 platform, what’s your Draft?

What’s a “Draft of Product”? You can find your terms!

(6/16/2023)

References

TALE: A Possible Theme called “Spontaneous Concept System”
https://lnkd.in/gXUxYSBJ

TALE: A Possible Theme called “Early Discovery”
https://lnkd.in/g5fE9ajM

The Territory of Concepts
https://lnkd.in/g_RGh9N3

I highlighted “Concepts” and “Project” on the [“Note-taking” and “Draft-making”] diagram. In the above piece, I redefined the term “Draft”.

For Sonke Ahrens, the “Draft” means drafts of academic papers or books. For me, the “Draft” can be referred to as “Drafts of Products” too.

A Concept System refers to a cognitive framework for a project such as writing an academic book or developing a product.

In this way, my model is a more general framework for connecting Ideas, Notes, and Projects.

Why didn’t I place Projects in the center of the circle? See the diagram below.

This is the power of a diagram network. We can use the same meta-diagram to represent different parts of a large system. You can find the whole system in Knowledge Engagement: The “Dot and Circle” meta-diagram.

The Model

Now we can move to the model behind the diagram.

How to read the above diagram? You can pay attention to two things:

• Process: Ideas > Notes > Draft
• System: Draft + Notes + Project + Concepts

The “Process” part is called “Dot” while the “System” part is called “Circle”.

The “Process” part can be broken down into two steps.

In this way, we can separate the above diagram into three sub-diagrams.

The first sub-diagram is about the “Ideas > Notes” step. We should note that this is not a simple linear process.

• Ideas refer to any mental element (or knowledge spark) inspired by immediate experiences
• Notes refer to any record of emerging ideas in any form of media such as text, visual, voice, etc
• Capture means recording an idea in a material medium such as an index card, a digital photo, a diagram, etc.
• Inspire means new ideas emerge while reading or reflecting on notes

Last year, I used the term “Knowledge Spark” for the Knowledge Discovery project. I also developed a typology of Sparks in order to design a canvas.

I have introduced four types of knowledge sparks in Thematic Space: Sparks In, Statue Out.

• Imagery: Sparks inspired by literary works (or other sources) that evokes a mental image or other kinds of sense impressions.
• Semantics: Sparks inspired by the meaning of a word, phrase, sentence, or text.
• Narrative: Sparks inspired by storytelling, performance, and conversation, in a situational activity.
• Affordance: Sparks inspired by real interactions between humans, objects, and the environment.

Here I use “Imagery”, “Semantics”, “Narrative” and “Affordance” as labels for four types of Sparks. We should just see these terms as placeholders. So far, I can’t find other terms for the names of these four types of Sparks. Anyway, the point is the differences and similarities between these four types.

• Imagery/Semantics is located in the “Fiction” zone because they directly link to imagination and language.
• Narrative/Affordance refers to real situational embodied experience which is located in the “Fact” zone.
• Imagery v.s. Semantics: Imagery refers to visual mental images while Semantics refers to understanding and appropriate use of meaning in single words, phrases, sentences, and even longer units.
• Narrative v.s. Affordance: Narrative is about human-to-human communicative activities. Affordance is about human-to-environment embodied activities.

This is not an ideal typology of Sparks, I think these four types of Sparks are important types.

You can find an example of the “Ideas > Notes” step in Thematic Space: How to Record a Spark?

In the past several months, I worked on the Mental Moves knowledge project and adopted the term “mental elements” from Dean Keith Simonton’s Chance-configuration theory (Scientific Genius,1988).

What are mental elements?

According to Simonton, “In scientific creativity, the predominant mental elements are cognitions of some kind, such as facts, principles, relations, rules, laws, formulae, and images. Yet immediate sensations may also play a role in laboratory experimentation and field exploration, and feelings may figure in scientific thought and discourse as well (Mahoney 1976). Sometimes these mental elements can be evoked voluntarily (e.g., the deliberate retrieval of a stored fact from memory); at other times these elements enter mental processing involuntarily (e.g., via a conditioned emotional association). Moreover, these mental elements do not have to be fully conscious, but rather, many enter information processing at the periphery of consciousness. ” (1988, p.6)

I highlight some keywords from Simonton’s description of mental elements. It looks like this is a rough definition. And, it is very hard to give an accurate definition for such things.

For discussing note-taking, we can use Ideas, Knowledge Sparks, and Mental Elements interchangeably.

The “Notes > Draft” process means turning many notes into one draft.

• Elaborate: work on a particular note
• Curate: find more related notes in order to fill an emerging framework

As mentioned above, for Sonke Ahrens, the “Draft” means drafts of academic papers or books. For me, the “Draft” can be referred to as “Drafts of Products” too.

Since academic papers or books are Products too, we can directly use “Drafts of Products” to understand the term “Draft” in this model.

While the “Elaboration” part of the process is about Developing Individual Pieces, the “Curation” part of the process is about Turning Pieces into A Meaningful Whole.

How can we know the meaningful whole? We need to move to the Circle of Draft. See the third sub-diagram below.

The above diagram shows the Circle of Draft. There are many elements that are related to Drafts of Products, I only highlight three ideas for this model.

• Draft: the Primary Object we are working on
• Notes: the Objectificated Ideas
• Concepts: the Mental Elements that form a Mental Model for guiding our work on Draft
• Project: the Context of working on a Draft

Let’s use Draft of Books and Draft of Apps as two concrete examples for the present discussion.

If we work on a Draft of a book, Notes and Concepts directly contribute to the final document. We can copy and paste the original text of notes to our file and continue editing them. We also turn a network of concepts into a mental model in order to organize the draft.

If we work on a Draft of an app, Notes and Concepts don’t directly contribute to the final product unless the app is a content-centered app. My point is that Notes and Concepts are essential to developing a Defined Concept System in the field of Product Development.

For example, the picture below is a screenshot of a Web 3.0 app.

You see a Defined Concept System with the following concepts:

• DID Wallet
• DID
• Profile
• Passport
• Disconnect / Open / Switch

From the perspective of Project-oriented Activity Theory, a project is a process of objectification of a concept. Developing a complicated Web 3.0 app is a project of objectification of a Defined Concept System.

Moreover, a Defined Concept System is developed from a Spontaneous Concept System. In the stage of early stage, developers have a Spontaneous Concept System, then they develop it into a Defined Concept System while working on making Drafts of Products.

In this way, the “Note-taking” process and the “Draft-making” process are related to developing a Defined Concept System that is behind a product.

You can find more details about Spontaneous Concept System and Defined Concept System in TALE: A Possible Theme called “Spontaneous Concept System”

The Discussion (with ChatGPT)

This is the last section of the article. Instead of self-reflection, I am going to try a new method: Talk with ChatGPT.

Oliver: What’s the difference between field note-taking and literature note-taking?

ChatGPT:

Field note-taking and literature note-taking are two distinct approaches used for different purposes in academia and research. Let’s explore the differences between the two:

1.Purpose:

• Field Note-Taking: Field note-taking is the process of recording observations, data, and insights during fieldwork or research conducted in real-world settings. Researchers often engage in field note-taking during ethnographic studies, social research, anthropological research, or any research that involves direct observation in natural settings. The primary goal is to document what is happening in the field as accurately and objectively as possible.
• Literature Note-Taking: Literature note-taking, on the other hand, involves summarizing and synthesizing information from various academic sources, such as books, journal articles, research papers, and other published materials. The main purpose is to understand, analyze, and synthesize the existing knowledge and arguments in the literature to support one’s research or to gain a comprehensive understanding of a particular topic.

2. Context:

• Field Note-Taking: It is commonly used in qualitative research to gather data directly from the field, such as participant observations, interviews, and detailed descriptions of events or phenomena as they naturally occur.
• Literature Note-Taking: This method is used when conducting a literature review to gain insights into the existing research and to inform the development of a research question, hypothesis, or theoretical framework.

3. Data Source:

• Field Note-Taking: Data is collected through direct observation, interviews, focus groups, or interactions with participants in the field.
• Literature Note-Taking: Data is sourced from academic publications, books, and other written materials.

4. Nature of Content:

• Field Note-Taking: Field notes typically contain raw, unfiltered data and observations, including descriptions of events, behaviors, and context. The notes may be more informal, capturing the researcher’s thoughts and reflections in real-time.
• Literature Note-Taking: Literature notes are more structured and focused on summarizing key points, methodologies, findings, and conclusions from the sources. They are organized and help build a coherent understanding of the existing literature.

5. Analysis:

• Field Note-Taking: The analysis of field notes often involves identifying patterns, themes, and insights to develop a deeper understanding of the phenomena being studied.
• Literature Note-Taking: The analysis of literature notes involves synthesizing the information from different sources to identify gaps, contradictions, or areas of consensus in the existing literature.

In summary, field note-taking is used to collect data during fieldwork, while literature note-taking is used to summarize and synthesize existing information from academic sources. Both approaches are valuable in research, but they serve different purposes and require distinct methodologies.

Oliver: What’s the difference between Niklas Luhmann’s Zettelkasten and Literature note-taking?

ChatGPT:

Niklas Luhmann’s Zettelkasten (slip-box or card index system) and literature note-taking are two distinct knowledge management and note-taking methods used by researchers, academics, and writers. While both methods involve organizing and processing information, they have different approaches and purposes. Let’s explore the key differences:

1. Purpose:

• Zettelkasten: Niklas Luhmann’s Zettelkasten is a unique system for knowledge management and idea generation. The primary purpose of the Zettelkasten is to facilitate the development and organization of ideas and concepts. It is a tool for the generation of new insights and the formation of connections between various ideas.
• Literature Note-Taking: The purpose of literature note-taking is to summarize and synthesize information from external sources, such as books, articles, or research papers. It is focused on understanding and analyzing existing knowledge rather than generating new ideas.

2. Organization:

• Zettelkasten: The Zettelkasten is organized in a networked manner, where individual notes (Zettel) are interconnected through links or tags. The system encourages the creation of new notes that link to existing ones, forming a web of interconnected concepts.
• Literature Note-Taking: Literature note-taking involves summarizing information from different sources in a structured manner. It may include categorizing notes based on themes, topics, or the source of information. However, it does not emphasize interlinking of ideas as in the Zettelkasten.

3. Originality and Creativity:

• Zettelkasten: Luhmann’s Zettelkasten method is particularly aimed at fostering creativity and original thought. By encouraging the creation of new notes that link to existing ones, it stimulates the emergence of novel connections and ideas.
• Literature Note-Taking: While literature note-taking can provide a comprehensive overview of existing knowledge, its primary focus is on understanding and synthesizing the ideas presented in the literature rather than generating new ideas.

4. Source of Information:

• Zettelkasten: The content in a Zettelkasten primarily consists of the user’s own ideas, reflections, and insights. It is a repository of the individual’s thought process and intellectual development.
• Literature Note-Taking: Literature note-taking is based on information extracted from external sources, such as books, articles, or research papers. It serves as a summary and analysis of the work of other authors.

5. Research Process:

• Zettelkasten: The Zettelkasten method is an integral part of Niklas Luhmann’s research process. He used it extensively to develop his sociological theories and concepts.
• Literature Note-Taking: Literature note-taking is a standard practice during the literature review phase of academic research. It helps researchers gather information, understand existing knowledge, and identify relevant sources for their work.

In summary, the key difference between Niklas Luhmann’s Zettelkasten and literature note-taking lies in their primary purpose and approach. The Zettelkasten is focused on idea generation, creativity, and the development of interconnected knowledge, while literature note-taking is primarily about summarizing and synthesizing information from external sources during the literature review process.

Oliver: Can we apply Niklas Luhmann’s Zettelkasten to develop concept systems for developing a Web 3.0 product?

ChatGPT:

Yes, you can apply Niklas Luhmann’s Zettelkasten method to develop concept systems for developing a web 3.0 product. The Zettelkasten system can be a valuable tool for generating and organizing ideas, fostering creativity, and building a coherent knowledge base for the development of a web 3.0 product or any other complex project.

Here’s how you can use the Zettelkasten method in the context of web 3.0 product development:

1. Idea Generation: Use the Zettelkasten to jot down initial ideas, concepts, and potential features for your web 3.0 product. Each idea or concept should be captured as an individual note (Zettel).
2. Interlinking Concepts: As you create new notes, make sure to link them to existing ones that are related. In the context of web 3.0 product development, this could involve connecting notes that represent different aspects of the product, such as user experience, blockchain integration, decentralized features, data privacy, etc.
3. Categorization and Tagging: Group related notes together by using tags or categories. This can help you easily find and navigate through concepts that fall under specific themes relevant to your web 3.0 product.
4. Iterative Development: Continuously add new ideas, insights, and updates to your Zettelkasten as your understanding of web 3.0 and your product evolves. The Zettelkasten allows for iterative development, where you can revisit and refine existing notes and connections.
5. Supporting Research: When conducting research on web 3.0 technologies, applications, or related projects, take notes and link them to your Zettelkasten. This will help you draw upon external knowledge and insights during the development of your web 3.0 product.
6. Prototype and Testing Ideas: Use the Zettelkasten to prototype and test different ideas for your web 3.0 product. Link notes that describe potential functionalities or design elements to assess their feasibility and effectiveness.
7. Collaborative Knowledge Building: If you are working with a team on the web 3.0 product development, the Zettelkasten can serve as a collaborative knowledge base. Team members can add their notes, interlink concepts, and collectively build a shared understanding.
8. Conceptual Clarity: By organizing ideas in a networked structure, the Zettelkasten can help you gain conceptual clarity, identify knowledge gaps, and ensure consistency in the development of your web 3.0 product.

Remember that the Zettelkasten is a flexible and adaptable method, so you can tailor it to suit the specific needs and challenges of developing a web 3.0 product. By leveraging this method, you can foster creativity, make informed decisions, and create a robust concept system to guide the development of your web 3.0 product.

Oliver: What’s your suggestion for developing concept systems for developing a Web 3.0 product?

ChatGPT:

Developing a concept system for a web 3.0 product involves creating a coherent and well-organized framework that outlines the core ideas, features, and functionalities of the product. Below are some suggestions to guide you through the process:

1. Understand Web 3.0 Concepts: Familiarize yourself with the key principles and technologies that define web 3.0, such as blockchain, decentralized applications (dApps), smart contracts, data sovereignty, interoperability, and more. Understanding these concepts will form the foundation for your concept system.
2. Define the Purpose and Target Audience: Clearly articulate the purpose of your web 3.0 product and identify the target audience. Understanding the problem your product aims to solve and who it serves is crucial for developing a focused and effective concept system.
3. Conduct Market Research: Research existing web 3.0 products and projects to identify gaps in the market and opportunities for innovation. Analyze user feedback, pain points, and preferences to inform your concept system.
4. Create User Personas: Develop detailed user personas that represent your target audience. Understand their needs, motivations, and pain points. This will help you tailor the concept system to address specific user requirements.
5. Identify Core Features and Functionalities: Based on your research and user personas, determine the core features and functionalities your web 3.0 product should offer. Prioritize the most essential elements and consider how they align with web 3.0 principles.
6. Concept Mapping: Use concept mapping techniques to visually organize and connect the core ideas and features. Concept maps can help you see relationships between different concepts and how they fit into the overall system.
7. Prototype and Iterate: Develop prototypes or mockups of your web 3.0 product to test and validate the concept system. Gather feedback from potential users or stakeholders and use this feedback to iterate and refine the system.
8. Consider Interoperability: In the context of web 3.0, interoperability is vital. Ensure that your concept system includes considerations for how your product will interact with other web 3.0 technologies and platforms.
9. Security and Privacy: Security and data privacy are critical aspects of web 3.0 products. Integrate measures to protect user data and ensure the overall security of the platform.
10. Involve the Development Team: Collaborate closely with your development team throughout the concept system development process. Their expertise and input will help ensure that the system is both technically feasible and scalable.
11. Document and Communicate: Clearly document the concept system, including the rationale behind design decisions and the interconnectedness of various concepts. Communicate the system to all stakeholders to ensure a shared understanding.
12. Test and Validate: As you progress with the actual development of the web 3.0 product, continuously test and validate the concept system against real-world scenarios and user feedback. Make adjustments as necessary to improve the product’s usability and effectiveness.

Remember that developing a concept system is an iterative process. Stay open to feedback, adapt to changes in the market and technology landscape, and keep refining your concept system to create a successful web 3.0 product.

Oliver: What’s your suggestion for developing concept systems for writing a book?

Developing a concept system for writing a book is a crucial step in organizing your ideas, structuring the content, and ensuring a coherent and engaging narrative. Here are some suggestions to guide you through the process:

1. Define Your Book’s Purpose: Start by clarifying the purpose of your book. Ask yourself what message or story you want to convey to your readers and what impact you hope to achieve. Understanding the main goal of your book will help you stay focused throughout the writing process.
2. Identify Your Target Audience: Determine who your intended readers are. Consider their interests, knowledge level, and what they might be looking for in a book like yours. Tailor your concept system to meet the needs and preferences of your target audience.
3. Create an Outline: Develop a detailed outline that outlines the main topics, chapters, and sections of your book. This serves as the backbone of your concept system and provides a clear roadmap for the writing process.
4. Use Mind Maps or Concept Maps: Consider using mind maps or concept maps to visualize the connections between different ideas, themes, and chapters in your book. These visual tools can help you see the overall structure and relationships between various elements of your content.
5. Break Down Your Book into Smaller Units: Divide your book into manageable units, such as chapters or sections. Each unit should have a specific focus and contribute to the overall narrative of the book.
6. Develop a Writing Schedule: Set a realistic writing schedule and allocate specific time for working on each section of your book. Consistent progress will help you stay motivated and on track.
7. Conduct Research (if applicable): If your book requires research, gather relevant information and organize it systematically in your concept system. Cite your sources to ensure proper attribution.
8. Gather Inspirations and Examples: Look for inspirations and examples from other books or authors that resonate with your writing style or subject matter. Analyze how they structure their content and draw insights from their approach.
9. Consider Visual Elements: If your book will include images, illustrations, charts, or graphs, consider how they will be integrated into the content. Plan for the placement of visual elements in your concept system.
10. Incorporate Feedback: As you develop your concept system, seek feedback from beta readers, writing groups, or editors. Their input can help you refine and strengthen your book’s concept.
11. Stay Open to Iterations: Be prepared for your concept system to evolve as you progress with your writing. Writing a book is an organic process, and new ideas may emerge that require adjustments to the initial concept.
12. Review and Revise: Periodically review your concept system to ensure that it aligns with your book’s vision. Revise and update it as needed to reflect any changes in your approach or content.

By developing a robust concept system for your book, you will have a solid foundation to guide your writing journey. It will help you maintain clarity, stay organized, and effectively communicate your message to your readers.

Oliver: Could you recommend some books about note-taking for product developers and product researchers?

ChatGPT

Certainly! Here are some books that cover note-taking and related topics, which can be beneficial for product developers and product researchers:

“How to Take Smart Notes: One Simple Technique to Boost Writing, Learning and Thinking — for Students, Academics, and Nonfiction Book Writers” by Sönke Ahrens

• This book introduces the concept of the Zettelkasten method and how it can enhance writing, learning, and creative thinking. While it is written with academics in mind, the principles can be applied to various fields, including product development and research.

“The Personal MBA: Master the Art of Business” by Josh Kaufman

• Though not explicitly about note-taking, this book provides an excellent overview of essential business concepts. Learning these concepts and taking concise, structured notes can be immensely valuable for product developers and researchers working in the business and tech industry.

“The Product Book: How to Become a Great Product Manager” by Product School

• This book is a comprehensive guide for aspiring and current product managers. While it may not focus solely on note-taking, it covers critical topics related to product development, and taking notes can help reinforce the learning process.

“Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days” by Jake Knapp, John Zeratsky, and Braden Kowitz

• While the book focuses on the sprint methodology for product design and development, it emphasizes the importance of documentation and capturing ideas during the sprint process, making it relevant to note-taking for product developers.

“Product Research Rules: Inspiring Principles for Discovery and Insights” by C. Todd Lombardo, Bruce McCarthy, and Evan Ryan

• This book delves into the fundamentals of product research, including various research techniques and methodologies. It may provide insights into how note-taking can be effectively used in the context of product research.

“Hooked: How to Build Habit-Forming Products” by Nir Eyal

• While not explicitly about note-taking, this book explores the psychology behind building habit-forming products. Taking notes on the key principles and insights can be valuable for product developers aiming to create engaging user experiences.

“Lean UX: Designing Great Products with Agile Teams” by Jeff Gothelf and Josh Seiden

• This book focuses on integrating user experience design and Agile development. Effective note-taking can be a vital tool in the Lean UX process to capture insights, user feedback, and experiment results.

Remember that while these books touch on note-taking and its relevance to product development and research, note-taking is a personal practice that can be adapted and refined to suit your specific needs and preferences.

Finally, I’d like to share several books about note-taking and concept development.

See the above picture.

Do you notice something strange?

what should you do now?