Persona Playbooks
The course creator's source library explained — a practical Capture→Connect→Create system for educators and course creators who want to curate sources once and reuse them across content, cohorts, and formats.
You've taught this topic forty times. You know the best article that explains the concept, the perfect case study that makes the abstract concrete, the research paper with the data that always lands with students. But you can't find any of them. Each time you teach, you rebuild — going back to Google, searching for the source you know exists, re-reading things you've read before.
Or the opposite problem: you have 2,000 saved sources, tagged with your subject area taxonomy, organized into folders that made sense when you built them. But students in your cohort ask "where can I learn more about X?" and you can't tell them — because your organization was for your research process, not for teaching them.
The course creator's source library is the knowledge system designed specifically for educators: curating sources once, in a way that makes them usable for teaching across formats, cohorts, and time.
Capture: Build a library of teaching-quality sources — not everything you've read, but the sources that are good enough to recommend, assign, or draw on in explanations.
Connect: Organize sources by concept and learning outcome, not by subject area or source type. A great analogy goes in "explanations of [concept]"; a key research finding goes in "evidence for [claim]."
Create: Produce the teaching outputs: course content, lesson plans, recommended reading lists, student resource guides, and the explanations and examples in the course material itself.
The course creator's version has a long time horizon: you're building a library you'll draw on across multiple cohorts, format changes, and years of teaching. Sources need to be preserved (not just bookmarked), organized for teaching use (not just personal reference), and maintained as the field evolves.
What course creators should capture:
Core explanations: The best available explanations of concepts you teach — articles, videos, book chapters, lecture notes that explain the concept more clearly than you could from scratch. These become recommended resources or inform your own explanations.
Research and evidence: The primary research that backs the claims you make in your teaching. "Research shows that spaced repetition produces 2x better retention" — the source for that claim should be in your library, preserved, with the specific page/finding noted.
Case studies and examples: Real-world examples and case studies that illustrate concepts. The story that makes the abstract concrete. The company that embodies the principle. The failure that illustrates what happens when you don't apply the concept.
Student-appropriate resources: Sources you'd assign or recommend to students — accessible, accurate, of appropriate depth for your audience.
Counter-examples and nuances: The examples that complicate the simple version of the concept. "This usually works, except when..." The intellectually honest teaching library includes the exceptions.
The teaching-quality filter: Unlike a personal research library (where you might save things for later consideration), the course creator's library should be filtered at capture: is this source good enough to recommend or draw on in teaching? If not — if it's simply interesting but not teaching-quality — it probably doesn't belong in the library.
Preserve against link rot: Course materials have long lifespans. An article you save for teaching a topic today may be referenced in course materials still in use in five years. For sources you'll rely on repeatedly, save full content — not just URLs. WebSnips saves the full content of web articles so the source is preserved even if the original URL disappears or is paywalled.
The course creator's organizational question: When you're developing a lesson on concept X, what do you need to find instantly?
Your organization should map directly to these retrieval questions.
The concept-first taxonomy: Organize by concept, not by source type. Not "Articles" and "Papers" and "Videos" — instead, organize by the concepts your courses cover. If you teach behavioral economics, your top-level organization is by concept: Loss Aversion, Status Quo Bias, Anchoring, Mental Accounting, etc. Each concept section contains explanations, evidence, cases, and resources — organized for teaching that concept.
Linking concepts: Concepts relate to each other. Loss Aversion relates to Risk Aversion and to Prospect Theory. When you save a source for one concept, tag it for related concepts that the source illuminates. A student's question about one concept may be better answered by a source tagged under a related concept.
Level tagging: Tag sources by student level:
introductory: appropriate for students encountering this concept for the first timeintermediate: assumes familiarity with the conceptadvanced: detailed, technical, requires backgroundpractitioner: applied; for professional development contextsA source tagged introductory + loss-aversion is instantly findable when you're developing the first module of an introductory course on behavioral economics.
Course content development: With a well-organized source library, course development becomes curation and synthesis rather than research from scratch. You know which sources you want students to engage with; the task is designing the learning arc that connects them.
For each lesson:
Recommended reading and resource guides: A well-tagged library makes creating reading lists straightforward: filter by concept + level + format. "Introductory reading on mental accounting for a business audience" is a query your library can answer in two minutes.
Updating courses across cohorts: The most underrated benefit of a source library: when the field advances, you update the library and the course update follows. New research displaces old research in the library; the course content referencing the old source gets updated. Without the library, every cohort's course update requires rebuilding research from scratch.
Live teaching: A well-organized source library makes you a better live teacher. A student asks an unexpected question; you know you have sources on that related concept; you can point them to the right resource without searching. This is the teacher's version of "having the answer at the tip of your tongue."
Dr. Sam is a professor who teaches organizational behavior and also runs a professional development workshop for managers. He has the same conceptual content across two very different audiences and formats.
Building the source library (ongoing):
When he encounters a great explanation of psychological safety — an article in Harvard Business Review — he saves it with WebSnips. Tags: psychological-safety, introductory, practitioner, hbr. One-line note: "Clear definition + Edmondson research cited + organizational example that lands with business audience."
When he finds the original Edmondson (1999) paper, he saves it separately. Tags: psychological-safety, advanced, primary-research. Note: "Source for the team performance research."
Developing a new module:
He's adding a module on psychological safety to his manager workshop. He searches his library: psychological-safety + practitioner. Finds: the HBR article (accessible for managers), a Harvard Business School case study, a Forbes piece with practitioner applications, and three examples he's tagged over the past year.
Building the academic version:
The same search at advanced returns the Edmondson paper and two meta-analyses. The module for his academic course draws on these.
Result: One source library, two audiences, minimal duplication of effort, and a library that gets richer every time he teaches.
| Stage | Tool | What it does |
|---|---|---|
| Web capture | WebSnips | Saves full content of articles, case studies, reports |
| Video resources | YouTube / Vimeo bookmarks | Keep separately; link from library |
| PDF management | Zotero or Google Drive | Academic papers, book chapters |
| Library organization | Notion or Airtable | Database: concept, level, format, one-line annotation |
| Course platform | Teachable, Thinkific, Kajabi | End-point; not for the source library |
The minimum viable course library:
Organizing by subject area rather than by concept. A "Marketing" folder serves your personal research. A "Customer Acquisition" folder with sub-tags for each acquisition concept serves your teaching. The teaching-oriented organization is harder to set up but orders of magnitude more useful.
Saving without annotations. A link to the HBR article is not a teaching resource. A link with the annotation "best practitioner explanation of psychological safety for non-academic audience; Edmondson's team performance research cited clearly" is instantly usable.
Not preserving sources. Course content has long lifespans. An article that disappears 18 months after you build a lesson around it is a problem. Save full content for your most relied-upon sources.
Not updating the library. The most dangerous stale knowledge in a course is outdated research cited as current. Build a library review practice: annually, flag sources more than 5 years old in high-velocity fields and check whether better or more recent sources have superseded them.
Separate libraries for different courses/formats. Maintaining one source library that serves all your courses (with level and audience tags differentiating use) is more efficient than separate libraries per course. The same concept appears in multiple courses; the library serves all of them.
The course creator's source library is the infrastructure that transforms teaching from repeated rebuilding into compounding improvement. Every source added to the library is available for every future cohort, every new format, and every adjacent course.
Curate once. Teach forever.
More WebSnips articles that pair well with this topic.
The academic researcher's knowledge workflow explained — a practical Capture→Connect→Create system for PhD candidates and researchers who are drowning in sources, citations, and link rot.
The analyst's evidence capture and due-diligence archive explained — a practical Capture→Connect→Create workflow for analysts, lawyers, and finance professionals who need citable, time-stamped evidence.
The consultant's knowledge workflow explained — a practical Capture→Connect→Create system for knowledge workers and consultants who need to manage high-volume information and retrieve it when it counts.