| 1 | { |
| 2 | "academic-research": { |
| 3 | "summary": "Research-reporting method that builds a defensible claim from question, method, and result while keeping limitations visible.", |
| 4 | "keywords": [ |
| 5 | "academic", |
| 6 | "research", |
| 7 | "thesis-defense", |
| 8 | "methodology", |
| 9 | "peer-review" |
| 10 | ] |
| 11 | }, |
| 12 | "consulting-decision": { |
| 13 | "summary": "Answer-first, evidence-led decision-document method with restrained analytical design defaults.", |
| 14 | "keywords": [ |
| 15 | "consulting", |
| 16 | "decision-support", |
| 17 | "answer-first", |
| 18 | "evidence", |
| 19 | "analytical" |
| 20 | ] |
| 21 | }, |
| 22 | "creative-pitch": { |
| 23 | "summary": "Creative-work presentation method that grounds one idea in a real insight and shows it living across every place it will appear.", |
| 24 | "keywords": [ |
| 25 | "creative", |
| 26 | "advertising", |
| 27 | "branding", |
| 28 | "campaign", |
| 29 | "concept" |
| 30 | ] |
| 31 | }, |
| 32 | "incident-postmortem": { |
| 33 | "summary": "Blameless incident review method that reconstructs a timeline, separates contributing factors from blame, and commits to verifiable actions.", |
| 34 | "keywords": [ |
| 35 | "postmortem", |
| 36 | "incident", |
| 37 | "reliability", |
| 38 | "root-cause", |
| 39 | "blameless" |
| 40 | ] |
| 41 | }, |
| 42 | "investor-pitch": { |
| 43 | "summary": "Fundraising narrative method that carries an investor from why now to why this team, on evidence rather than adjectives.", |
| 44 | "keywords": [ |
| 45 | "fundraising", |
| 46 | "pitch", |
| 47 | "startup", |
| 48 | "traction", |
| 49 | "investor" |
| 50 | ] |
| 51 | }, |
| 52 | "narrative-keynote": { |
| 53 | "summary": "Story-driven keynote method that earns one idea through tension, turn, and concrete human detail.", |
| 54 | "keywords": [ |
| 55 | "keynote", |
| 56 | "storytelling", |
| 57 | "narrative", |
| 58 | "persuasion", |
| 59 | "talk" |
| 60 | ] |
| 61 | }, |
| 62 | "operating-review": { |
| 63 | "summary": "Recurring business-review method that separates result, variance, cause, and owned commitment without softening bad numbers.", |
| 64 | "keywords": [ |
| 65 | "business-review", |
| 66 | "metrics", |
| 67 | "variance", |
| 68 | "operations", |
| 69 | "accountability" |
| 70 | ] |
| 71 | }, |
| 72 | "product-launch": { |
| 73 | "summary": "Value-first launch method where every capability claim is earned by a demonstrable moment before it is named.", |
| 74 | "keywords": [ |
| 75 | "product", |
| 76 | "launch", |
| 77 | "positioning", |
| 78 | "demo", |
| 79 | "capability" |
| 80 | ] |
| 81 | }, |
| 82 | "science-explainer": { |
| 83 | "summary": "Public-explanation method that builds understanding from familiar ground through visual analogy, without trading accuracy for accessibility.", |
| 84 | "keywords": [ |
| 85 | "explainer", |
| 86 | "science-communication", |
| 87 | "popular", |
| 88 | "analogy", |
| 89 | "public" |
| 90 | ] |
| 91 | }, |
| 92 | "solution-proposal": { |
| 93 | "summary": "Client-facing proposal method that proves understanding first, then earns the work through a specific, costed plan.", |
| 94 | "keywords": [ |
| 95 | "proposal", |
| 96 | "presales", |
| 97 | "bid", |
| 98 | "client", |
| 99 | "engagement" |
| 100 | ] |
| 101 | }, |
| 102 | "technical-deepdive": { |
| 103 | "summary": "Mechanism-first technical explanation method that grounds every claim in constraints, trade-offs, and observable behavior.", |
| 104 | "keywords": [ |
| 105 | "technical", |
| 106 | "architecture", |
| 107 | "engineering", |
| 108 | "mechanism", |
| 109 | "trade-off" |
| 110 | ] |
| 111 | }, |
| 112 | "workshop-teaching": { |
| 113 | "summary": "Learn-by-doing training method that sequences objective, worked demonstration, practice, and honest checks for understanding.", |
| 114 | "keywords": [ |
| 115 | "training", |
| 116 | "workshop", |
| 117 | "teaching", |
| 118 | "practice", |
| 119 | "onboarding" |
| 120 | ] |
| 121 | } |
| 122 | } |
| 123 |