HA Mtg Scope Clarification

Goal for our first HA meeting is really to level-set and confirm where we are and what has been done so far. This meeting should really be used as an introduction. 

HAs have shared a lot about their current challenges and pain points already. So we shouldn't make it look like we're starting from scratch. Their effort will need to be acknowledged.

We will need to give them a sense of ownership and make sure that they sign off on each item that we will address with them. 

High level structure of Wednesday's meeting:

• Introduction

  • People

    • Team presentation and round table

  • Project summary from a General perspective

    • CHEFS

      • Problem statement:

        • duplicated effort

        • lack of standardization

        • time consuming submission

      • Vision:

        • standardization 

        • better user experience

        • reduce duplication

• Acknowledging current status of gap analysis

  • Get issue log from Jay*******

  • Focus on Logistics issues

• What's next

  • Working sessions to schedule

    • Will address each components/envelops separately

• Takeaways should be:

  • For CGI:

    • Confirmation of main pain points

    • Names of people who should be involved

  • For HAs:

    • Knowledge that the project is starting and discovery of the team

    • might need to identify people who should be involved

Mentions of the need to distinguish between reporting and submission. The business has a tendency to talk about "reporting" when they're really talking about the data submission.