Workflow Redesign

• Enterprise processes are frequently cluttered with legacy handoffs, like digital versions of interoffice envelopes, which serve as administrative artifacts rather than value-add steps.8:28
• Leaders should identify five to eight core value streams—such as collecting payment or delivering a service—and ruthlessly eliminate any administrative step that lacks a direct, essential connection to the final outcome.10:25
• Faster departmental sub-processes do not constitute improvement if the underlying, unnecessary handoffs remain in place.

Model Routing and Design

• Deterministic or routine business work should be routed to cheaper models paired with specific software tools, reserving frontier models exclusively for investigative, edge-case reasoning.21:05
• Harness design must match model capability: routine tasks require thick harnesses, such as rigid, tool-backed structures, while frontier models perform best with thinner harnesses that allow freedom for complex exception handling.22:21
• Failing to route requests based on task difficulty risks impossible long-term cost control, as sending every interaction through a frontier model creates unsustainable token burn.7:04

Trust and Adoption

• Evals function as the essential control mechanism for scaled agent use, requiring concrete verification of correctness, record updates, and approval compliance rather than relying on qualitative impressions.24:58
• Embedding agents directly into existing interfaces like Slack reduces the friction of adoption by placing capabilities where employees already work, though this necessitates careful monitoring to prevent unchecked token growth.2:28