Mary Fung
essayJune 26, 2026

Operating rhythm for AI-enabled teams

AI enablement needs a cadence that turns experiments into decisions, patterns, and stopped work.

AI enablement needs a rhythm.

Not a ceremony. Not a standing meeting where people perform enthusiasm. A real working rhythm that turns experiments into decisions, patterns, and stopped work.

A simple rhythm is enough to start.

Once a week, review one workflow. Pick something repeated, slow, error-prone, annoying, or dependent on one expert. Name the current path. Name where the work breaks. Run one small AI-assisted experiment against that break. Decide whether to adopt, adapt, or kill the experiment. Publish the useful pattern back to the team.

The team should keep an experiment log. Not a beautiful database. A plain record of what was tried, by whom, for what workflow, with what result, and what happened next.

Demo days can be useful, but only if they lead to decisions. A demo should end with one of three outcomes: keep testing, adopt into a workflow, or kill it. If every demo survives, the team is not learning. It is collecting.

Workflow audits matter more than tool audits. The question is not "what AI tools do we have?" The question is "where is work still being done in a way that no longer makes sense?"

Kill criteria should be named upfront. What would make the team stop this experiment? Low quality, low adoption, unclear ownership, high review burden, data risk, no time saved, no workflow changed. Killing bad experiments is part of the discipline.

Adoption metrics should be close to the work. Are people using the new path after the demo is over? Did the old path get retired? Did handoffs shrink? Did quality improve? Did the expert bottleneck loosen?

Internal playbooks should stay short. A useful playbook helps someone repeat a pattern without reading a novel. Use when. Inputs needed. Steps. Review checks. Known risks. Owner.

Shared prompt libraries are only useful if they include context and judgment. A prompt without when-to-use-it guidance is usually just another artifact to ignore.

The operating rhythm should make the team more honest.

What did we try? What worked? What failed? What did we change? What stopped?

That is the rhythm that turns AI from activity into capability.

← back to the field