Skip to main content

Collaboration cycle

The Collaboration Cycle is where teams who are building products/features on get feedback and guidance on their product/feature to ensure it meets experience standards for design, content, information architecture, quality assurance, accessibility, and research. Teams engage with the Collaboration Cycle throughout their product’s/feature’s lifecycle.

How it works

The Collaboration Cycle is a series of touchpoints during which VFS team members get guidance on the following areas:

  • Design

  • Content

  • Information Architecture

  • Quality Assurance

  • Accessibility

  • Research

  • Analytics

  • Privacy & Security

  • Contact Center

The below illustration maps out when Collaboration Cycle touchpoints occur in a product’s/feature’s lifecycle. Teams should engage with the Collaboration Cycle when they begin building or iterating on their product/feature.

Platform Collaboration Cycle. A process flow begins with Prioritize, passes through four phases, and ends with Evolve. Phase 1 is Define, and includes the Collaboration Cycle Kick-off, Design Intent, and Sitewide Content and IA Intake Request. Phase 2 is Discover, and includes Midpoint Review, Research Review, and Analytics Request. Phase 3 is Build, and includes Contact Center Review, Staging Review, and Privacy, security, infrastructure readiness review. Phase 4 is Validate, and includes TBD.

Platform Collaboration Cycle flow image

The “Define” phase

The “Discover” phase

The “Build” phase

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.