Key Takeaways

  • Matt Pocock's course creation starts with an "explore and exploit" phase, generating a high volume of raw ideas in an Obsidian vault, akin to a zettelkasten.
  • He moves from loose ideas to a concrete plan using a custom planning application, letting disparate notes naturally coalesce into a coherent course structure.
  • Lessons are rigorously prioritized (P1, P2, P3), with P1s—the most essential content—recorded first to form the course's foundation.
  • His core content principles demand that each lesson teaches only one concept, knowledge dependencies are explicit, and learners are challenged without being overwhelmed.
  • These principles are formalized in his "Matt Pocock's Technical Course Creation Process" to build highly structured and effective learning experiences.

The Matt Pocock's Technical Course Creation Process

  • 1. Explore & Exploit Phase: Start by identifying compelling topics and unique angles for the course. Generate a large volume of ideas, storing them as loose notes in an Obsidian vault or similar knowledge base, akin to a zettelkasten system.
  • 2. Planning & Coagulation: Utilize a custom application or a structured planning tool to organize the myriad notes. This process allows disparate ideas to coalesce into a coherent course outline, revealing natural sections and groupings of information.
  • 3. Prioritization: Assign a priority level (e.g., P1 for essential, P2 for important, P3 for supplemental) to each individual lesson based on its criticality and contribution to the overall learning objectives of the course.
  • 4. Core Content Recording & Iteration: Begin recording the high-priority (P1) lessons first, forming the foundational content of the course. Be prepared to discard or defer less critical content that doesn't fit or is unnecessary for the core learning path.
  • 5. Adhere to Lesson Principles: Ensure each lesson focuses on teaching only one distinct concept. Clearly define and communicate the dependencies between different lessons and knowledge points. Design challenges and exercises that push learners without overwhelming them, fostering engagement and retention.

When This Works (and When It Doesn't)

Matt Pocock's method shines for highly structured, in-depth technical courses, like his recent offering: 4.5 hours of tightly edited video across roughly 100 units, packed with extensive exercises. This systematic approach excels when the goal is to impart complex technical skills in a clear, sequential manner, guaranteeing learners build foundational knowledge before moving to advanced concepts. The explicit focus on single-concept lessons and dependency mapping makes it perfect for programming languages, frameworks, or specific engineering disciplines where mastery requires a logical progression.

However, this methodical rigor might be overkill for quick, informal tutorials or courses aimed at broad conceptual understanding rather than deep technical proficiency. If your goal is a quick demo, a high-level overview, or a course where the learning path is highly flexible and non-linear, Pocock's P1-first, single-concept structure could slow you down. It's a method built for precision and depth, not speed or broad strokes.

What to Do With This

This week, consider building a short, impactful internal course to onboard new engineering hires to your team's specific codebase or a custom internal tool. Instead of ad-hoc explanations, apply Pocock's process. First, spend a few hours in your favorite note-taking app (Obsidian, Notion, even a simple text editor) dumping every single concept a new hire must know – this is your Explore & Exploit Phase. Don't filter, just generate. Next, try to group these loose ideas into logical modules. Use a simple spreadsheet for Planning & Coagulation to outline a potential 3-5 lesson series. Then, prioritize each concept: what's a P1 (absolutely essential to get started), a P2 (nice to know soon), or a P3 (can wait)? Focus on recording only the P1s first, following Pocock's lead. Finally, as you build each lesson, ask: "Does this teach only one thing? Are the prerequisites clear? Is it challenging enough to make them think, but not so much they quit?" This focused approach ensures your onboarding isn't just comprehensive, but genuinely effective.