Collaboration cycle
Collaboration cycle
Breadcrumbs

Gov Leads Sync

Last Updated: September 9, 2026

Formerly known as “PO Sync”

Waiver available: No

Recommended timing: Schedule once you have an idea for how to solve your problem statement and have drafted a Product Outline. This is the first touchpoint you schedule after Collab Cycle kickoff.

How this touchpoint helps you, VA, and Veterans

Gov Leads Sync opens the lines of communication between your team and VA government leadership. It's part of the Collaboration Cycle's Kickoff process, required for every team.

Use this meeting to align on goals early, so your product team and our shared service teams can work faster and more confidently together for the rest of the Collaboration Cycle.

No GitHub ticket yet? Start with a Collab Cycle kickoff first.

What you need to bring

Required:

Optional:

  • Any other artifact you think would help the discussion

You don't need to prepare a presentation — this is a discussion, not a pitch.

You’re ready for this touchpoint when

  • You've developed an idea for how to solve your problem statement

  • You've drafted a Product Outline

How to schedule your review

  1. Kickoff the Collab Cycle
    First, start the process by opening a Collab Cycle ticket. Gov Leads Sync is the first touchpoint you schedule afterward.

  2. Create a ticket
    Click "Schedule a Gov Leads Sync" in your Main Collab Cycle ticket to generate a Gov Leads Sync GitHub ticket

  3. Add your artifacts
    Add links to your artifacts in your Gov Leads Sync GitHub ticket before scheduling your meeting

  4. Book a time
    Click the Calendly Gov Leads Sync calendar link in your GitHub ticket when you’re ready to schedule

How to prepare for your review

Deadline: Share your Product Outline before the meeting so we can review it in advance.

How to deliver: Link to your Product Outline in your Gov Leads Sync GitHub ticket.

What happens during the meeting

Format: 30-minute discussion — no presentation needed.

Who should attend: One or two government employees from your team, ideally the staff closest to this project's work.

Who else will be there: About 5–6 government staff who lead teams that work with VA.gov product development teams.

Typical agenda — we'll ask about:

  1. How we can best partner together

  2. The problem you're solving and your expected outcomes

  3. How far along your team is

  4. Your team's experience with VA.gov

  5. Whether you have questions about the Collaboration Cycle or design touchpoints that can help you prepare for Staging Review

  6. Whether you have an embedded accessibility specialist

  7. Whether you're planning research with Veterans

We'll also discuss how these resources can help you build faster:

  • VA Design System — tested, ready-to-use components for your product designs

  • VA Content Style Guide and the centralized Content and Information Architecture team — help Veterans find and understand your product

  • Accessibility Design Experience team — build to (and beyond) Section 508 compliance and avoid rework later

  • Veteran Research resources — a recruiting contract for usability testing and a library of past research

  • Historical context — other teams working on similar initiatives

Expected outcomes: Feedback happens live, in conversation — there's no written report to wait for.

What happens after the meeting

  • We add highlights from the meeting to your Gov Leads Sync GitHub ticket.

  • You're free to schedule your next touchpoint (but don’t need to wait for the meeting)

Waiver process

A waiver is not available for Gov Leads Sync, which is required for every team as part of the Collaboration Cycle's Kickoff process.


Help and feedback