Principle
Do not standardize an AI ritual before testing it
Structure can add friction without adding judgment.
Before you use it
- Use when
- A team wants to mandate a structured AI-use protocol because it sounds disciplined or collaborative.
Keep this limit in mind
- The 2026 field experiment had important design limitations; use it as a warning against untested scaffolding, not proof that structured collaboration is bad.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Pilot the protocol against ordinary AI use on real work before making it policy. Measure output quality, throughput, coordination cost and where the structure actually helps. Keep only the steps that solve an observed failure mode. A formal workflow deserves the same evidence as the AI tool it is supposed to improve.
An example
Before requiring every document to be co-written by paired employees with AI, compare that process with ordinary individual AI-assisted work on representative documents.
Check your result
The protocol survives because it improves an observed outcome, not because it looks rigorous on a process diagram.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingDo not standardize an AI ritual before testing it
Evidence and sources
A 2026 field experiment found that one structured pair-based AI-use protocol was associated with lower document quality and substantially lower production than unstructured use.
The authors report important design limitations; the finding warns against assuming protocol structure is beneficial, not against all collaborative protocols.
Edition and review
Version 0.1.0
No review details are supplied for this edition.