Pilot
Test in real conditions, not controlled demos.
The Pilot phase moves AI from whiteboard to workflow. Most organizations run pilots that are too controlled -- isolated from real data, real users, and real operational pressure. A well-structured pilot surfaces integration friction early, validates assumptions against actual performance, and produces the evidence base needed to justify Full Operating Capability.
Flight Crew structures pilots around three constraints: a defined scope (one use case, one team, one workflow), a fixed time horizon (typically 30-60 days), and pre-agreed success criteria. We instrument the pilot for measurement from day one and build a debrief protocol that informs the IOC transition.
You have a clear priority use case from Discovery but no structured test
Previous pilots ran too long or lacked measurable outcomes
Teams are unclear on what success looks like for AI adoption
Vendor demos impressed but real-world results were disappointing
Pilot results measured against pre-agreed criteria
Integration friction documented and resolved or scoped
Team capability assessed -- training needs identified
Decision made: proceed to IOC, redesign pilot, or deprioritize
See how FC-OS operationalizes this every night.