2023-08-02 Communications WG Meeting notes
Date
Aug 2, 2023
Attendees
Name | Organization | Role | Present? |
---|---|---|---|
Andrea Pitkus | University of Wisconsin-Madison | Steering Committee member | No |
Eric Crugnale |
| Steering Committee member | Yes |
Nanguneri Nirmala |
| Steering Committee member | Yes |
Mehdi Nassiri | Indiana University | Steering Committee member | No |
Agenda
Workgroup Leadership
All chosen Workgroup leaders are to be Co-Chairs (as per Shield Community Charter). At least one selected leader must be a Steering Committee member.
·Review/Develop Workgroup Charge
Workgroup charges shall include the Workgroup's purpose, leadership, objectives, scope, deliverables, timeline, and proposed Member participation
Draft purpose: The Branding and Communication Workgroup is responsible for communicating information, recommendations, accomplishments and other work product of the SHIELD Community. The Workgroup will strive to deliver these communications in a consistent, effective and professional manner through various communication channels including, web, email, industry publications, industry conferences, webinars, white papers and other means as required.
Discuss Recruiting additional Workgroup members
Review/Modify list of potential initiatives
First initiative: IVD Vendor Outreach as per Steering Committee
Prioritize initiatives
Set initial goals/deliverables
Meeting cadence and schedule
Discussion topics
Only 2 members were in attendance.
Discussed need to attract additional membership to this workgroup in order for it to be effective
Discussed creating a one-page SHIELD overview document
Discussed meeting cadence and settled on bi-weekly meetings at this point
Discussed idea of creating Calendar/Event page within Confluence where members can find all SHIELD-related meeting invites.
Next meeting - 8/16/23 - 12pm ET
Time | Item | Presenter | Notes |
---|---|---|---|
|
|
| |
Action items
Quick decisions not requiring context or tracking
For quick, smaller decisions that do not require extra context or formal tracking, use the “Add a decision…” function here.
Decisions requiring context or tracking
For decisions that require more context (e.g., documentation of discussion, options considered) and/or tracking, use the decision template to capture more information.