Weekly thinking on workflow transformation, AI collaboration, learning systems,
the future of work, and systems design. Signal is interview ammunition, authority
building, and systems-thinking made visible.
Post Index
WorkflowPublished
Handoffs Are the Hidden Cost Nobody Budgets For
Teams measure the cost of the work. They rarely measure the cost of passing the work between people — and that is where transformation programs quietly bleed time.
4 min
Map any content pipeline — Idea → Authoring → Editing → Review → QA → Accessibility → Localization → Publishing → Delivery → Measurement — and the temptation is to optimize each box. Faster authoring. Faster QA. But the boxes are rarely the problem. The arrows are.
Every arrow is a handoff, and every handoff carries a tax: context has to be re-explained, quality degrades at the boundary, ownership goes ambiguous, and work sits in a queue waiting for the next person. The cost is invisible because no single person owns the gap between two functions.
This is why SeaSound case studies lead with handoff reduction rather than tool adoption. You can buy a faster authoring tool and still ship slower, because you never touched the seven handoffs around it. Diagnose the arrows first. See the Workflow case studies for the full treatment.
AI CollaborationPublished
AI-Native vs. AI-User: The Difference That Decides Outcomes
Most organizations adopt AI as a faster typewriter. The teams pulling ahead are doing something structurally different — and the gap is widening.
5 min
An AI user bolts a model onto the existing workflow: the same steps, the same handoffs, now with a drafting assistant in the middle. Output speeds up locally, but the system still moves at the speed of its slowest handoff.
An AI-native team asks a different question: if this model can classify, draft, route, and validate, what should the workflow look like? They redesign around the capability instead of decorating the old process with it. Review gates move earlier. Intake gets structured so the model has something to work with. Humans move to judgment, not mechanical processing.
This is the whole reason DIVE puts Enable last. You earn the right to apply AI by first diagnosing the workflow, integrating the knowledge, and validating the model. AI applied to an un-diagnosed workflow just automates the dysfunction. See the DIVE framework.
Systems DesignPublished
Your Operating Model Is Your Real Operating System
People + Process + Technology + Governance. When a transformation stalls, it is almost always one of these four layers — and almost never the one everyone is blaming.
4 min
When delivery slows, the reflex is to blame technology: the wrong tool, the missing integration, the legacy platform. Sometimes that is true. More often the technology is fine and the failure lives in one of the other three layers — unclear ownership (People), undefined handoffs (Process), or absent decision rights (Governance).
Treating the operating model as a system — four interacting layers rather than an org chart — lets you locate the actual fault. The Ops surface uses this lens for every swimlane and RACI map. Fix the layer that is broken, not the layer that is loudest.
Learning SystemsDrafting
Why Governed AI Adoption Beats Fast AI Adoption
Speed without governance creates confident, scalable error. A short case for putting the gate before the gas pedal in learning content pipelines.
In progress— min
Learning SystemsDrafting
Assessment Data Is a Content Signal You're Ignoring
Most learning orgs treat assessment results as a scorecard. Treated as a feedback loop, the same data tells you exactly which content to revise next.
In progress— min
AI CollaborationDrafting
Keep the Human Load-Bearing
Human-in-the-loop is not a courtesy checkbox. It is a structural decision about where judgment and accountability must remain.