Framework

Systems Over Goals for AI Adoption

Lava's internal playbook for spreading AI capability across the team without mandates, deadlines, or adoption goals. Instead of telling people to use AI more, the system creates a weekly loop: experiment freely, share wins and learnings, bake the best discoveries into shared defaults. The knowledge compounds organizationally rather than living in individual workflows.

How it works

  1. 1Goals for AI adoption create compliance theater — people log usage without changing how they actually work
  2. 2Systems create ambient learning: teammates experiment freely, with no pressure to adopt anything specific
  3. 3Weekly sharing loops surface what is actually working and move it from individual insight to team default
  4. 4Learnings get operationalized as default files, memory blocks, and shared context — not documentation to be ignored
  5. 5The organizational benefit compounds: each week's best practices become next week's baseline
  6. 6System design question: 'What structure makes the best AI practices the path of least resistance for everyone?'

Hear it on the podcast

Your API Keys Are Killing Your ProductivityListen to the episode

More from this episode

Get the next framework first

One email a week with the frameworks, tools, and founder stories from the podcast. Free.

More frameworks for AI & Automation

Every Decision Is a Prediction ProblemBen Turtle's foundational reframe: every business decision is a prediction. You choose A over B because you predict A leads to a better outcome. Science is prediction - a theory only holds if it forecasts the next observation. This reframe has tactical implications for founders: the company with the most accurate model of the future compounds the fastest. Building systematic prediction capability - not just execution speed - is the real AI-era strategic advantage.Chronological Grounding MethodLightningRod AI's core training innovation: use the natural time structure of real-world data as a supervisory signal, without human labels. Given data up to timestamp A, predict what happens at timestamp B. Repeat across all messy data. The model that gets good at this game learns genuine causal patterns - not surface correlations - and produces domain expertise that no frontier model has, because it came from data unique to your context.Two-Bucket Training Data FrameworkEvery organization building AI falls into one of two buckets, each with a mirror-image problem. Bucket 1 has too much data in the wrong format - dense, unstructured, chronological internal data that contains enormous value but resists standard training pipelines. Bucket 2 has no data at all and needs a domain-specific corpus created from public sources. LightningRod's chronological grounding method solves both with the same underlying engine.Vision-First AI DesignBuild AI interfaces around the primary human sense — vision — rather than defaulting to text chat. AI products that take screen share as their primary input can respond to what users actually see and do, not just what they describe, enabling a fundamentally more contextual and effective interaction model.Disneyland Quality StandardThe quality bar for AI voice products: everything must work perfectly because the moment the magic breaks — like Mickey Mouse taking his head off in the park — users don't lower their expectations. They leave. Trust in AI voice products, once broken, doesn't recover.Zero Hallucination ArchitectureDesigning AI systems for high-stakes environments by requiring every agent output to have traceability, auditability, and human-in-the-loop checkpoints wherever hallucination risk is non-zero.