--- title: "Schema on Read vs Write™ — Training Framework for Knowledge Transfer" description: "A training framework that builds on what skilled trades already know. Teaching the framework, not the facts — letting expertise fill in the details. Originated by River Caudle." canonical: "https://rivercaudle.com/schema-on-read/" author: "River Caudle" keywords: - Schema on Read - training framework - knowledge transfer - skilled trades - industrial training - analogical learning - OT training - electrician network training - plumber network training - River Caudle - Riverman robots: index, follow license: Riverman Fair License v2.0 --- # Schema on Read vs Write™ **Training framework for knowledge transfer.** > *"Teaching the framework, not the facts — letting expertise fill in the details."* Originated by [River Caudle](https://rivercaudle.com/). Used under the [Riverman Fair License v2.0](https://rivercaudle.com/license/). --- ## The data-management metaphor ### Schema on Write (traditional training) In data management, Schema on Write means defining rigid data structures before storing information. Every piece of data must fit predetermined categories and relationships. **Applied to training:** Pre-defined rigid procedures and knowledge structures. Learners must memorize and follow exact protocols. Standardized curriculum, fixed learning paths. One-size-fits-all regardless of prior experience. > *"Here's exactly how you do X, Y, and Z — memorize these steps."* ### Schema on Read (adaptive training) In data management, Schema on Read means storing data flexibly and applying structure when you need to use it. The framework adapts to the data, not vice versa. **Applied to training:** Flexible conceptual frameworks. Learners construct understanding dynamically. Leverage existing mental models to interpret new information. Personalized learning paths based on prior expertise. > *"Here's the universal pattern — apply it using what you already know."* --- ## Why skilled trades are natural Schema-on-Read learners **Tradespeople already have the schema.** They just need to read new data through existing frameworks. ### Existing mental models - **Flow systems** — water through pipes = electricity through circuits = data through networks - **Feedback loops** — thermostats = governors = control systems - **Hierarchical organization** — electrical panels = network switches = system architecture - **Troubleshooting logic** — systematic problem-solving approaches ### Research evidence Skilled trades professionals: - **Learn 75% better through hands-on training** when new concepts are linked to existing knowledge - **Process patterns through specialized neural pathways** (caudate nucleus) that bypass conscious analysis - **Develop "systemic intuition"** — recognize universal patterns across different systems - **Diagnose problems faster than they can explain reasoning** — because they're using existing schemas --- ## The adaptive schema design ### Core principle — provide framework, not facts **Universal patterns as teaching tools** 1. **Flow dynamics** — conservation principles, bottlenecks, control mechanisms 2. **Feedback systems** — sensing, processing, response cycles 3. **Hierarchical architecture** — modularity, interfaces, emergent properties 4. **System boundaries** — inputs, outputs, internal processes ### Worked example — teaching network segmentation to electricians #### Schema on Write approach (traditional) > "VLANs are virtual local area networks that segment traffic by assigning switch ports to different broadcast domains using 802.1Q tagging protocols…" #### Schema on Read approach (adaptive) > "Think of your electrical panel — you don't put your 220V dryer circuit on the same breaker as your 110V lights. Network segmentation works the same way: different 'circuits' for different types of traffic, with controlled connections between them." ### Progressive complexity **Level 1 — Direct Analogy.** Map familiar trade concepts directly to new technical domains. Obvious structural similarities, clear one-to-one correspondence. **Level 2 — Pattern Recognition.** Identify universal principles that apply across multiple domains. Abstract from specific examples to general frameworks. **Level 3 — Creative Application.** Apply frameworks to novel situations requiring adaptation. Combine multiple patterns for complex problem-solving. --- ## Implementation strategies ### 1. Blended representation techniques **Start concrete, move abstract:** - Begin with physical demonstrations using familiar tools - Gradually introduce abstract representations - Maintain connections between concrete and abstract throughout **Example — teaching packet routing:** 1. **Concrete** — water-valve demonstration showing flow control 2. **Bridging** — network diagrams using plumbing symbols 3. **Abstract** — standard network topology diagrams 4. **Integration** — troubleshooting using both mental models ### 2. Analogical scaffolding - **Surface similarities** — start with obvious visual/functional matches - **Structural relationships** — map deeper cause-and-effect patterns - **Systemic principles** — identify universal laws governing both domains **Example — plumber learning network engineering:** - **Surface** — pipes look like network cables - **Structural** — water pressure = network bandwidth, valves = switches - **Systemic** — flow conservation laws apply to both water and data ### 3. Communities of practice Peer learning where experienced tradespeople learn technical skills together. Share experiences and collectively construct new understanding. Maintain respect for existing expertise while building new capabilities. Psychological safety for experts to become novices again. ### 4. Performance-based assessment Real-world application. Portfolio development showcasing cross-domain problem-solving. Reflective documentation of mental model evolution. Pay-for-performance tied to actual job success. --- ## Schema on Read success stories ### Microsoft Software & Systems Academy **Challenge:** Transition military veterans to tech careers. **Approach:** Leveraged military leadership and systems thinking. Mapped project management to software development. Used existing troubleshooting frameworks for debugging. **Result:** 87% job placement rate in tech roles. ### BreakLine Education **Challenge:** Transition top-tier veterans to business careers. **Approach:** Translated military operational experience to business operations. Mapped strategic planning to corporate strategy. Used existing leadership frameworks for team management. **Result:** 95% placement rate in Fortune 500 companies. ### Industrial Networking Training **Challenge:** Teach network engineering to skilled trades. **Approach:** Plumbing analogies for flow concepts. Electrical troubleshooting mapped to network diagnostics. Existing safety frameworks applied to cybersecurity. **Result:** 75% faster learning compared to traditional IT training. --- ## Cognitive science foundation **Cognitive Load Theory** — reduces cognitive load by building on existing knowledge structures. Frees mental capacity for learning new domain-specific details. Prevents overwhelm from too much new information at once. **Constructivist Learning** — learners actively construct knowledge rather than passively receive it. New information integrated with existing mental models. Personal meaning-making improves retention and transfer. **Transfer of Learning** — similar underlying structures enable knowledge transfer between domains. Abstract patterns more likely to transfer than specific procedures. Analogical reasoning strengthens with deliberate practice. --- ## Common implementation mistakes ### What doesn't work - **Forced analogies** — stretched beyond their useful limits - **Oversimplification** — assuming all domain knowledge transfers perfectly - **One-size-fits-all** — same analogies for different trade backgrounds - **Ignoring where analogies break** — creating new misconceptions ### What does work - **Flexible frameworks** — multiple analogies for the same concept - **Explicit bridging** — deliberate discussion of how analogies work - **Graduated complexity** — start simple, introduce ambiguity - **Reflection on the transfer process** — practice spotting when analogies apply and when they don't --- ## Assessment questions ### For instructors 1. What existing frameworks do learners bring to this topic? 2. Which analogies will be helpful vs. misleading? 3. Where will the analogy break down and need explicit correction? 4. How can I help learners build bridges between domains? ### For learners 1. How is this similar to something I already know? 2. Where does the similarity break down? 3. What new mental model am I building? 4. How will I apply this framework in novel situations? --- ## Closing > *"The best training doesn't replace what people know — it builds on what they know to create what they need to know."* --- ## See also - **SHIP Framework™** — what's being taught: - **RIVER Method™** — the troubleshooting workflow taught alongside: - **Frameworks index**: - **Riverman Fair License v2.0**: --- *Document — Schema on Read vs Write™ · Originator — R. Caudle · Rev. 01 · Issued Houston, Texas, 2026.05.11*