🌲The Konik Method for Making Useful Notes
[[3. Resources/Readwise/Full Document Contents/Articles/🌲The Konik Method for Making Useful Notes|Full Document Contents]]
## Document Notes
• The Konik Method for Making Useful Notes:
- Involves active note making
- Used when you have a specific goal and allotted time
• The role of technology in education:
- Technology can help to bridge the gap between students and teachers by allowing for better communication and collaboration.
- Technology can also help to create a more engaging learning environment, allowing for a variety of different activities and experiences for students.
• Benefits of technology in education:
- Technology can help to improve student learning outcomes by providing access to a wider range of resources.
- Technology can also help to improve assessment, providing students with more individualized feedback and assessment.
- Technology can also help to reduce costs, as it can be used to create more efficient and effective learning experiences.
Outline of The Konik Method for Making Useful Notes:
I. Introduction
A. Definition of The Konik Method
B. Benefits of The Konik Method
II. The Konik Method
A. Step 1: Create an Outline
B. Step 2: Focus on Key Elements
C. Step 3: Make Connections
D. Step 4: Synthesize
III. Wrapping Up
A. Benefits of Active Note Making
B. Tips for Improving Note Making Skills
The Konik Method for Making Useful Notes proposes a middle-of-the-road approach to note-taking which involves highlighting and annotating topics of interest, jotting down notes during meetings, and saving insightful tweets. The method involves recording information in two primary flavors: logs and indexes, and claims/evidence/explanations. It also involves using external tools such as Readwise and creating notes directly. Notes are intended for reference and not for self-improvement. The final step is to use the notes, such as when writing an article.
Take some highlights and try this prompt again.
> [!note]+ Document Notes
> ```markdown
>
> ---
> tags: [note-taking, PKM, Obsidian]
> author: [Eleanor Konik]
> source: [eleanorkonik.com]
> reference: [https://www.eleanorkonik.com/p/the-konik-method-for-making-notes]
> date created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
>
> ---
>
> # 🏷️ Title: 🌲The Konik Method for Making Useful Notes
>
<!-- deep-read:sections start -->
## 🧰 Action Inbox
- #articleseed — [H2] Publish “claim/evidence/explanation” primer — source link below.
- #xref — [H5] Compare Readwise vs Zotero workflows — Readwise, Zotero docs.
- #share — [H7] Share Dataview triage query example — Dataview link.
- #articleseed — [H3] “Reactive reading produces usable notes” case study — post draft.
- #addendum — [H6] Extend folder-vs-links stance with risks — prior post.
- #share — [H1] Demo “claims-as-titles” for mentors — workshop outline.
- #bmf — [H8] Fiction worldbuilding from operational notes — examples list.
- #xref — [H4] Note ethics of attribution with examples — policy page.
- #articleseed — [H9] Zettelizer setup guide for QuickAdd — repo link.
- #share — [H10] Video: “direct vs automated” note capture — talk proposal.
## 🧭 Table of Contents
- [📝 Summary](#-summary)
- [📖 Main Content](#-main-content)
- [🗒️ Notes](#️-notes)
- [📚 References](#-references)
- [🗣️ Paraphrase](#️-paraphrase)
- [📰 Newsletter](#-newsletter)
- [✅ Action Items](#-action-items)
- [🧪 Hypotheses](#-hypotheses)
- [📊 Methodology](#-methodology)
- [❓ Questions](#-questions)
- [🔮 Future Research](#-future-research)
- [💡 Implications](#-implications)
- [🧠 Learning Styles Assessment](#-learning-styles-assessment)
- [📊 Accessibility Assessment](#-accessibility-assessment)
- [🌍 DEIB Assessment](#-deib-assessment)
- [✅ Logical Validity](#-logical-validity)
- [🛡️ DARVO Analysis](#-darvo-analysis)
- [🎯 Conclusion](#-conclusion)
## 📝 Summary
- The piece explains a practical, tool-agnostic notes workflow.
- It favors messy, reference-ready notes over self-help artifacts.
- Stakeholders include researchers, writers, and PKM users.
- Tradeoffs balance retention, speed, and future-proofing.
- Bottom line: Title claims, cite sources, and keep notes usable.
## 📖 Main Content
- The method starts with motivations: pleasure, problems, and reactive intake.
- It captures information directly or via automations like Readwise.
- Core structure uses claim, evidence, and explanation naming.
- Evidence remains verbatim with links for attribution ethics.
- Triage uses Dataview tables and lightweight cleanup.
- Zettelizing creates atomic notes with embeddings and IDs.
- The system optimizes for later reuse, not perfection.
### 🗒️ Notes
### [H1] Titles use claims to improve retrieval
- "I give them all file names that are claims." — article.
### [H2] Claim/evidence/explanation scaffolds synthesis
- The article maps TEA/PEE/CER to note structure.
### [H3] Reactive reading produces usable notes
- Reactive intake occurs during downtime and errands.
### [H4] Verbatim evidence supports attribution ethics
- "Attribution is important... provide access to the primary source." — article.
### [H5] Direct capture improves retention and speed
- Direct notes are faster and improve retention through interaction.
### [H6] Automations save effort yet add fragility
- Automation aids scale, but tools can be brittle.
### [H7] Dataview triage surfaces high-signal items
- Triage by links, tags, and size prioritizes attention.
### [H8] Useful notes remain intentionally messy
- "Useful notes are messy, and time is valuable." — article.
### [H9] Use unique IDs to stabilize references
- Highlight IDs enable precise embeds and searches.
### [H10] Zettelizer streamlines atomic note creation
- QuickAdd script automates file creation and embeds.
### [H11] Example evidence quote for claim extraction
- "Zandee did not know the nomads’ language, so his friend Gulzar translated as Zandee asked how much they made from selling the cheese. “Nothing,” Gulzar said. “They just do it so that the milk will not go stale. At most, they will barter it with a shopkeeper who may give them a pound of sugar or a dozen matchsticks.”" — cited in article.
## 📚 References
- Author’s article: The Konik Method for Making Useful Notes (https://www.eleanorkonik.com/p/the-konik-method-for-making-notes)
- Readwise Reader overview (https://readwise.io/read)
- Obsidian: QuickAdd plugin by Christian B. (https://github.com/chhoumann/quickadd)
- Obsidian: Dataview plugin (https://github.com/blacksmithgu/obsidian-dataview)
- Zotero reference manager (https://www.zotero.org/)
- Atlas Obscura: The Kashmiri Cheese Brand Operating at 7,000 Feet by Safina Nabi (https://www.atlasobscura.com/articles/kashmiri-milk-cheese)
- TfTHacker: Obsidian Readwise Inbox guide (https://tfthacker.com/2022/02/obsidian-readwise-inbox)
- Kepano Obsidian theme info (https://obsidian.md/)
## 🗣️ Paraphrase
- The method emphasizes usable notes over polished aesthetics.
- Title claims, embed sources, and triage efficiently with simple tools.
## 📰 Newsletter
- Notes should serve you, not impress you.
- Title claims, keep quotes linked, and triage with Dataview.
- Want a demo on Reader-to-Obsidian? Reply and I’ll schedule it.
- Related tools: Readwise Reader, Zotero, QuickAdd, Dataview.
## ✅ Action Items
- DevRel
- Publish a live demo of claim-titled notes.
- Ship a Dataview triage snippet with examples.
- Developer advocacy
- Run a Reader-to-Obsidian workshop.
- Track adoption with event UTMs.
- Education
- Create a CER notes lab for mentors.
- Add PKM office hours for contributors.
- Developer experience
- Provide QuickAdd Zettelizer template.
- Offer Dataview query cookbook.
- Developer marketing
- Blog “messy notes, strong outcomes.”
- Share clips on LinkedIn and Make.
- Community management
- Encourage attribution norms in docs.
- Add note-ethics to CoC resources.
- Internal/external/cross-project
- Align OSPO-PKM guidelines with Legal.
- Set feedback loop on tooling issues.
- OSPO
- Policy & Governance
- Define note attribution and source access.
- License Compliance
- Teach citation hygiene in training.
- Security Management
- Document vuln intake note patterns.
- Software Inventory
- Template SBOM notes with claims.
- Developer Support
- Hold PKM consultation hours.
- Community Engagement
- Fund maintainers’ documentation sprints.
- Strategic Alignment
- Add PKM KPIs to OKRs.
- Community
- Maintainers
- Host roadmap clinic with note templates.
- Contributors
- Pair on first-issue note checklists.
- Sponsors
- Publish transparent documentation budgets.
- Ecosystem
- Drill coordinated disclosure note playbooks.
- WordPress
- Core
- CER format for feature proposals.
- Core Performance
- Claims for perf findings with evidence.
- Core AI
- Guardrails for AI citation accuracy.
- Core Program
- Ritualize weekly note triage.
- Playground
- Labs using claim-driven tutorials.
- Community
- Meetup kits on PKM with Obsidian.
- Training
- Lessons on claim titles and backlinks.
- Marketing
- Campaign “Notes that ship.”
- Support
- KB templates with source links.
- Design
- UX audits use CER structure.
- Documentation
- Examples-first with atomic notes.
- Polyglots
- Glossary note cross-links.
- Accessibility
- WCAG audits as claim files.
- Meta
- .org contributor note patterns.
- CLI
- Command docs with claim headers.
- Hosting
- Reliability checklists as claims.
- Tide
- Evidence-linked scoring notes.
- Openverse
- Provenance notes with sources.
- Themes
- Review notes, lints, and links.
- Plugins
- Provenance and security claims.
- The WPCC
- Programs
- Microgrants for documentation claims.
- Projects
- Governance clinics note templates.
- Funding experiments
- Publish transparent ledgers with claims.
- FAIR
- Technical independence
- Note provenance and signature checks.
- Policies and covenants
- Funding transparency claim files.
- Productized governance artifacts
- Ship charters and scorecards as notes.
## 🧪 Hypotheses
- Claim-titled files improve retrieval speed versus source-titled files.
- Verbatim evidence improves trust and reuse in community docs.
- Dataview triage increases processing throughput of saved items.
- Automation plus IDs reduces broken-reference incidents.
- Messy, incomplete notes still increase publication velocity.
### 📊 Methodology
- Run A/B searches on claim vs source titles.
- Survey trust with and without embedded quotes.
- Measure processed items per week with triage enabled.
- Track link rot incidents before and after IDs.
- Compare time-to-publish across cohorts.
### ❓ Questions
- Where do claim titles fail for non-text media?
- How much quoting is sufficient for trust?
- Which triage signals best predict usefulness?
### 🔮 Future Research
- Evaluate Reader vs Zotero for PDFs at scale.
- Map governance artifacts to CER schemas.
- Test LLM assistance for claim header drafts.
### 💡 Implications
- Practice: Favor claim naming and embedded citations.
- Policy: Codify attribution in contributor guides.
- Security: Preserve sources for audit trails.
- Education: Teach CER notes in onboarding.
- Funding: Budget time for documentation sprints.
### 🧠 Learning Styles Assessment
- Reading level estimate: Flesch-Kincaid Grade ≈ 9–10.
- Visual learners
- Present: Structural metaphors and flow.
- Improve: Diagrams of pipelines and triage.
- Aural learners
- Present: Linked talks exist externally.
- Improve: 3-minute audio summaries.
- Verbal learners
- Present: Clear terms and definitions.
- Improve: Glossaries and comparisons.
- Kinesthetic learners
- Present: Step-by-step Zettelizer setup.
- Improve: Checklists and small labs.
- Logical learners
- Present: CER logic and triage rules.
- Improve: Decision trees and KPIs.
- Social learners
- Present: Workshops and clinics potential.
- Improve: Cohort reviews and Q&A.
- Solitary learners
- Present: Self-paced note patterns.
- Improve: Reflection prompts.
- Naturalistic learners
- Present: Garden and travel examples.
- Improve: Lifecycle maps of note aging.
### 📊 Accessibility Assessment
- Screen reader semantics
- Present: Headings and clear sections.
- Improve: Alt text for images in examples.
- Keyboard navigation
- Present: Logical text order.
- Improve: Focus states in shared templates.
- Contrast and readability
- Present: Text-first guidance.
- Improve: Line-height guidance.
- Text resizing and reflow
- Present: Markdown reflows well.
- Improve: Prefers-reduced-motion notes.
- Media and captions
- Present: External talks may vary.
- Improve: Provide transcripts or captions.
- Forms and interactions
- Present: None in article.
- Improve: Add accessible checklists.
- Standards reference
- Map to WCAG 2.2 AA for docs.
### 🌍 DEIB Assessment
- Cultural breadth
- Present: Examples span domains.
- Improve: Global case studies.
- Inclusive language
- Present: Clear, neutral phrasing.
- Improve: Expand glossary for newcomers.
- Neurodiversity support
- Present: Chunked, flexible workflows.
- Improve: More consistent headings.
- Representation
- Present: Cites diverse sources.
- Improve: Intentional inclusion notes.
- Psychological safety
- Present: Encourages imperfect notes.
- Improve: Community guidelines linkage.
### ✅ Logical Validity
- Strong reasoning
- Inductive: Messy notes still yield outcomes ([H8]). Evidence from experience.
- Causal: Claim titles improve retrieval ([H1]). Plausible mechanism.
- Pragmatic: Automation tradeoffs acknowledged ([H6]). Balanced view.
- Fallacies
- No major fallacies noted. Claims stay scoped to practice.
- Tone of voice
- Pragmatic, candid, and tool-agnostic.
### 🛡️ DARVO Analysis
- Deny
- No denial patterns observed.
- Attack
- No attacks on others observed.
- Reverse victim/offender
- Not applicable.
## 🎯 Conclusion
- Use claims for titles, keep evidence verbatim, and cite sources.
- Triage, then zettelize only what matters.
- Next: Pilot this workflow in contributor onboarding.
### 🔗 References
- The method, tools, and examples: see References section above.
🔖 Zettel Candidates
- Titles reuse Claim Headers above; each links to sources.
- [H1] Titles use claims to improve retrieval — Improves search and scanning; apply to docs — article.
- [H2] Claim/evidence/explanation scaffolds synthesis — Standardize notes across teams — article.
- [H3] Reactive reading produces usable notes — Capture value in downtime — article.
- [H4] Verbatim evidence supports attribution ethics — Increases trust and auditability — article.
- [H5] Direct capture improves retention and speed — Favor direct for critical items — article.
- [H6] Automations save effort yet add fragility — Use cautiously with backups — article.
- [H7] Dataview triage surfaces high-signal items — Prioritize processing — Dataview.
- [H8] Useful notes remain intentionally messy — Optimize for outcomes — article.
- [H9] Use unique IDs to stabilize references — Reduce link rot — article.
- [H10] Zettelizer streamlines atomic note creation — Speed atomic conversion — QuickAdd.
Tag Coverage: #articleseed: 4 • #xref: 3 • #share: 3 • #bmf: 1 • #addendum: 1
```
<!-- deep-read:sections end -->
## Highlights
- Everybody uses different vocabulary, but this is what I like to call *active note making* because it's the sort of thing I do when I have a specific goal I am working toward. I do this when I have specifically allotted time for it. ([View Highlight](https://read.readwise.io/read/01gts292m74685gfjtm0dnb1b4))
- Tags: notes