← All speakers

Bio, Work & Ideas

Dan Mason

Conference affiliation: Stride · 2025

Dan Mason is an AI product and technology leader who builds human-supervised AI systems for complex operational environments. At Stride, where he has held AI leadership roles, his work has ranged from modernizing legacy software to designing patient-support agents that keep clinical judgment in human hands.

Mason began in mobile software development before spending much of his career in product leadership. His background includes ESPN, NBCUniversal, Shutterstock and Viacom; at Shutterstock, he also worked on technology integration following an acquisition. Increasingly capable coding assistants eventually drew him back into hands-on development, a trajectory he describes in his professional teaching work.

His product philosophy emphasizes outcomes over output: AI should improve meaningful results, not merely generate more text, code or completed tasks. His writing on human-AI collaboration argues for helping workers experiment, recognize model limitations and redesign their responsibilities. In financial services, he has applied those principles to AI-assisted legacy modernization, including automated testing and multi-agent workflows; he also demonstrated Stride Conductor at FinovateFall 2024.

Building agents people can supervise

For a telemedicine system developed with Avila Science, Mason personally built the LangGraph-based agent layer supporting patients through multi-day treatment at home. The system combines text messaging, persistent patient state and escalation to human operators, while other engineers maintained the surrounding application, database and messaging infrastructure. His AI Engineer technical workshop reveals several distinctive design decisions:

  • Configurable treatment blueprints. Clinically approved guidance lives in documents that medical staff can maintain. Agents use those documents alongside treatment milestones, scheduled messages and patient-local time, allowing new workflows without rewriting the application or forcing patients through rigid, sequential questionnaires.
  • Legible agent orchestration. Mason uses LangGraph to make decision paths understandable to clients, connects approved documents and internal tools through Model Context Protocol, and limits sensitive information reaching the model. He favors portable architectures that preserve the option to change underlying models.
  • Complexity-triggered human escalation. A separate evaluator considers both response quality and operational complexity, including changed treatment state and multiple scheduled messages. Mason treats model-reported confidence cautiously and routes ambiguous situations to human supervisors.
  • Evaluation grounded in real workflows. His custom assessment harness combines LangSmith datasets with Promptfoo, accounting for shifting timestamps and acceptable variation in wording. He also uses AI coding tools for implementation while relying on architectural judgment and iterative review to keep generated software accountable.

Read the topics behind these talks

1 conference talk

Key ideas

Scroll to read ↓

Ava turns patient texts into proposed treatment-state updates, scheduled messages and human review, while keeping medical instructions in documents clinicians can maintain.

  • Keeping treatment on track at home
    3:06 ↗
  • Two systems with a defined contract
    6:27 ↗
  • From button pushing to supervised operations
    11:42 ↗
  • A proposal, an evaluator and a state boundary
    17:59 ↗
  • Onboarding, local time and movable treatment anchors
    24:20 ↗
  • Fresh runs and explicit document navigation
    32:15 ↗
  • The security boundary and model choice
    40:54 ↗
  • Following a check-in through LangSmith
    47:18 ↗
  • Investigating failures and challenging the evaluator
    55:40 ↗
  • Resuming a proposal for human feedback
    1:04:21 ↗
  • Keeping medical instructions maintainable
    1:09:38 ↗
  • Separating roles, knowledge and operating rules
    1:18:29 ↗
  • Tools define what the model can change
    1:28:12 ↗
  • Retry execution failures, evaluate state transitions
    1:32:26 ↗
  • A second treatment without a new application
    1:40:28 ↗
  • What the review score actually means
    1:44:04 ↗
  • Deploying and extending the workflow
    1:47:08 ↗
  • Handling new input and leaving an operable system
    1:51:18 ↗

References