1 min read

Building AI Products — Series Index

Model capability becomes product value only when applied to worthwhile problems and designed for uncertainty, correction, and trust. The sequence connects problem choice, UX, evals, model strategy, data, metrics, economics, support burden, and audit.
1 min read

BizOps — Series Index

Companies need a bridge between strategy, decisions, and execution when coordination begins to fail. The sequence clarifies when that bridge is needed, how it differs from adjacent roles, and how operators become durable operating architecture.
1 min read

AI-Native GTM — Series Index

AI changes go-to-market work most when it strengthens revenue learning rather than merely automating activity. The sequence builds from signals, source-of-truth discipline, account attention, relevance, and pipeline inspection toward bounded agentic workflows and an operating model.
1 min read

AI Quality Systems — Series Index

Reliable AI requires a managed quality system, not isolated checks. The sequence connects evals, gold sets, regression tests, judgment calibration, confidence thresholds, review loops, drift analysis, ownership, and release gates into an auditable operating discipline.
Series Index 1 min read

AI Adoption That Actually Changes the Company — Series Index

AI changes a company only when people change consequential work and daily habits. The sequence moves from use-case readiness and stakeholder behavior through enablement, manager rituals, honest metrics, pilots, and operating models to a practical adoption audit.
1 min read

Agent-Native Tools — Series Index

Software designed for people creates drag for agents that need efficient action surfaces, durable state, and explicit trust boundaries. The sequence connects compound commands, resumable work, safe affordances, permissions, and tool contracts to a different software company.
2 min read

Workflow Ontology Series #2: The Basic Objects of Work

Workflow redesign fails when tools and automation arrive before the work itself has clean definitions. Distinguishing requests, tasks, projects, owners, states, blockers, dependencies, exceptions, approvals, and handoffs preserves signal and makes intervention possible.
2 min read

Workflow Ontology Series #1: Work Needs an Ontology Too

Accidental definitions of tasks, ownership, blockers, approvals, and completion create work state drift between recorded status and operational reality. A shared ontology makes workflow fields trustworthy claims, improving throughput, capacity planning, risk management, and accountability.

Choose your reading rhythm.

Start with a weekly briefing, add daily notes, or hear only when a durable essay or research update is ready.
You've successfully subscribed to Antoine Buteau
You've successfully subscribed to Antoine Buteau
Welcome back! You've successfully signed in.
Press ESC to close.