[2026 kcdc] designing agentic workflows that teams actually use

Speaker: Alexandria Hamilton

See live blog table of contents for more posts


Context

  • One person company
  • 32 agents
  • Bottlenecks with human in the loop. Repeated a number of times that human is the bottleneck. Balance control and speed
  • If fail, because of human
  • “we” – agents part of team

Agents

  • Each agent has own purpose
  • Help with code, calendar, marketing, come up with lyrics, governance, cataloging, checking news
  • Agents doing well so getting promoted to cloud and not human in the loop
  • Org chart of agents; have leads
  • Each agent has a specific thing to do/purpose
  • Skills – ex: firecall, opensco, buffer

When don’t need agents

  • Agents are expensive
  • guardrail: 30 day waiting period before add another agent

Names

  • Some people give them human names and treat as human teammates
  • But want to be able to destroy when don’t need so don’t get too attached

Log

  • Keep log of all workflow
  • Log schedule, handoff, interactions, failures
  • Stored in Obsidian
  • “If it isn’t written down, the AI is improvising it”
  • Helpful for finding old conversations/backup of human memory

Judge

  • The LLM is never the judge
  • Background agents help as judge

Claude

  • Filter ideas with Claude
  • Refine ideas
  • Package and give to agents
  • Using Max subscription. Want to space out token use

Consistency

  • “Consistency is a byproduct of structure, not of intent, memory, or discipline”
  • Slow and steady wins the race
  • Ok if things break. Don’t want agents out in the wild doing whatever
  • Ok with human being the bottleneck
  • Some days failures because human not available
  • Pimon looks for anomalies

Operating Loop

  • Each agent runs certain days/times on a schedule (try to take Sunday off)
  • Want to keep token usage low. Spreading out which days each runs helps
  • Some talk to each other
  • Give each specific things to do

Agent HQ

  • Includes file describing each agent – persona, what does, example invocations
  • Calendar showing when runs
  • Output of Claude code

Health care

  • Marketers need to show accurate
  • Still need to go over data

Relationship with AI

  • Not replacing us, argue with it every day.
  • Partner, not intern
  • Ask Claude how to make improvements: ex to agent schedule

Takeways

  • Agents are good
  • Human is the bottleneck. This is fine. See firsthand everything that went wrong

My take

The session I attended in this room also started 8 minutes late due to video issues. Not the speaker’s fault, but would be nice if someone announced that working on it. Her speaking style is great; high energy and clear which I really needed this morning! I feel inspired. Showing Agent HQ at the end was great!

Leave a Reply

Your email address will not be published. Required fields are marked *