Principle
Do not standardize an AI ritual before testing it
Structure can add friction without adding judgment.
When it fits
- A team wants to mandate a structured AI-use protocol because it sounds disciplined or collaborative.
When to avoid it
- The 2026 field experiment had important design limitations; use it as a warning against untested scaffolding, not proof that structured collaboration is bad.
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.
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.
Connected ideas
Useful withTest 'AI as thought partner' on the work that needs judgment
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.