← All curriculum
Module 2 · Proof: build useful evidenceMon, Sept 2160 min
Choose the operating shape
Compare model, tool, vendor, and partner choices against the workflow, data, risk, cost, and operating capability of the organization.
Faculty: Eike von Seggern · Joshua Simon
Learning objectives
- ▸Evaluate build vs buy vs partner for a use case
- ▸Score vendors against their data reality
- ▸Set technical governance boundaries
Key concepts
LLM APIs, RAG, fine-tuningBuild vs buy vs partnerVendor evaluation scorecardTechnical governance
Memorize this
🧠 Build vs buy vs partner🧠 RAG🧠 Vendor scorecard
Your study flow
- 1. Read
Read the session guide above. Note the ideas that change how you see your organization's current AI question.
- 2. Test
Take the module quiz in Learn & Memorize to check understanding.
- 3. Drill
Run the spaced-repetition flashcards to lock in the terms from this module.
📝 Test this session
Question 1 of 7Choose the operating shape
What does RAG do?
Flashcards for this module
- Supervised vs unsupervised learningSupervised = model learns from labeled examples (X→Y). Unsupervised = model finds patterns in unlabeled data (clustering, segmentation).
- LLMLarge Language Model: a deep network trained on vast text to predict next tokens; the engine behind generative AI. Limits: hallucination, context window, no true reasoning.
- Agentic AISystems that use a model plus tools, memory, and loops to pursue a goal with limited supervision: vs a single model call. Example: Anthropic's agent patterns.
- Data silosData trapped in separate systems/teams. The #1 blocker to AI: if data isn't accessible and quality, no model can save the use case.
- RAGRetrieval-Augmented Generation: feeding an LLM relevant retrieved context at query time to ground answers in your own data and reduce hallucination.
- Build vs buy vs partnerBuild = custom IP/control; Buy = vendor SaaS (faster, but vendor lock-in & data risk); Partner = co-build with consultants. Decision depends on data reality and core competency.
Build for Module 2: Use Case Map + Technical Brief + Prototype Demo