# Output Formats ## Table of Contents 1. [Presentation Script](#presentation-script) 2. [Course Outline](#course-outline) 3. [Knowledge Card](#knowledge-card) 4. [Article / Document](#article--document) All formats must contain the four core elements: **Challenge**, **Model**, **Evidence**, **Anchor**. The difference is in structure, depth, and tone. --- ## Presentation Script **Use for:** Talks, speeches, conference presentations, team shares (typically 5-20 minutes). **Tone:** Conversational, vivid, paced for spoken delivery. Short sentences. Rhetorical questions. ### Template ```markdown # [Title -- framed as the audience's challenge, not the speaker's topic] ## Opening: The Challenge (40% of total length) [Vivid scenario that puts the audience inside the universal challenge] [Show the familiar/obvious approach] [Reveal why it fails -- create the cognitive gap] [Transition: "So if [obvious approach] doesn't work, what does?"] ## The Model (30% of total length) [Introduce the model with its memorable label] [Explain the structure briefly -- keep it to one core idea] [Show how the speaker's experience demonstrates the model in action] [Emphasize the role/mindset shift, NOT tool details] ## The Anchor (20% of total length) [Build to the one sentence] [Deliver the anchor -- the specific, portable judgment] [Brief implication: what this means for the audience's own work] ## Close (10% of total length) [Return to the opening challenge with new eyes] [End on the anchor or a memorable restatement of it] ``` ### Guidelines - Write for the ear, not the eye. Read aloud to test. - One idea per paragraph. No dense blocks. - The audience should be able to retell the talk using only: the challenge, the model label, and the anchor. --- ## Course Outline **Use for:** Training modules, workshops, educational sessions (30 min to multi-hour). **Tone:** Structured, pedagogical. Clear learning objectives. ### Template ```markdown # [Module Title -- framed as a capability the learner gains] ## Learning Objective By the end of this module, learners will be able to: [Apply the model] to [their own context] in order to [achieve outcome]. ## Section 1: Enter the Challenge (25% of time) ### Activity: Recognition Exercise [Present 2-3 real scenarios. Ask learners to identify what they would do.] ### Reveal: Why the Obvious Approach Falls Short [Show where typical responses break down] [Create the cognitive gap using the 3-beat structure] ### Bridge [Frame the question the model answers] ## Section 2: The Model (35% of time) ### Model Introduction [Name]: [One-sentence definition] ### Model Deep Dive [Explain each component of the model with examples] ### Case Study: The Original Experience [Use the speaker's experience as the primary case study] [Map each element of the case to the model components] ### Discussion / Application [Pose: "Where in your work do you see this pattern?"] ## Section 3: Practice (25% of time) ### Exercise [Learners apply the model to their own scenario] [Structure: Identify challenge -> Apply model -> Share insight] ### Debrief [Surface common patterns from the exercise] [Reinforce the model through learner-generated examples] ## Section 4: The Anchor (15% of time) ### Key Takeaway [Deliver the anchor sentence] ### Transfer Planning [Each learner identifies one specific action for their own work] ### Close [Return to the opening scenarios -- reinterpret through the model] ``` --- ## Knowledge Card **Use for:** Quick-reference summaries, one-pagers, memos, Slack/email shares, internal knowledge bases. **Tone:** Dense, precise, scannable. Every word earns its place. ### Template ```markdown # [Title -- the model name or a provocative reframe] ## The Challenge [2-3 sentences describing the universal problem] ## The Model: [Memorable Label] [One paragraph explaining the core structure] [Optional: Simple diagram or formula, e.g., "100 -> 10 -> 1"] ## How It Works [Brief evidence from the original experience -- 3-5 sentences] [Focus on the shift (role, mindset, structure), not procedures] ## The Anchor > "[The one sentence to carry away]" ## Apply It [1-2 sentences: How to spot this pattern in your own work] [Optional: One diagnostic question the reader can ask themselves] ``` ### Guidelines - Target length: 200-400 words. - Must be readable in under 2 minutes. - The anchor should be visually prominent (use blockquote). --- ## Article / Document **Use for:** Blog posts, internal articles, published essays, long-form documentation. **Tone:** Narrative, exploratory, richly argued. Allows for nuance and multiple examples. ### Template ```markdown # [Title -- a tension, question, or provocative claim] ## Opening Hook [A specific, vivid moment that dramatizes the challenge] [Draw the reader in with story, not thesis] ## The Problem Everyone Recognizes [Expand the opening into a universal pattern] [Cite multiple examples across domains to validate universality] [Acknowledge the common/obvious approach -- show it's reasonable but insufficient] ## The Turn [The cognitive gap -- clearly articulate why the obvious approach fails] [Use the 3-beat structure: familiar -> failure -> opening] [This is the "hinge" of the article -- the most important paragraph] ## A Different Lens: [The Model] [Introduce the model with its label] [Explain the structure] [Walk through the original experience as the primary case study] [Show the key shift -- not tools, but thinking/role/structure change] ## Beyond the Original Case [Apply the model to 1-2 additional domains or scenarios] [This proves the model transfers -- it's not just one person's story] ## What This Means [The anchor -- delivered with full context and nuance] [Implications for the reader's own practice] [Optional: What this model does NOT cover / its limits] ## Closing [Return to the opening image/story with new meaning] [Final restatement of the anchor -- landing with accumulated weight] ``` ### Guidelines - Target length: 800-2000 words. - Use section headers to maintain scanability. - The article should pass the "so what?" test at every paragraph -- the reader should never wonder why they're still reading. - At least one additional example beyond the original case to prove transferability.