201109 Marketing Meetings

This is the agenda of the meetings of the Marketing Council in San Diego (September 2011).

Tuesday Q1 (hosted by Education)

• Joint meeting (hosted by Education) - education plan, and the education part of the marketing plan.

Tuesday Q2

1. Approval for marketing to be a co-sponsor of the "Maximizing the value of your HL7-involvement"-project of the International Marketing Committee.
2. Ambassador web page design (Grant, 10 minutes)
3. Issue list for the potential new marketing firm (Gora/Rene/Martin, 15 minutes)
   • Should follow directly from the Strategic Initiatives, plus any specific additional issues (identified by the board) outside of the scope of the SI
4. Strategic Marketing Plan
   • clarify the 'marketing view' of our products in the standards-category, and why this is a probably different one from the 'standard creator view' on our products - we need to document the context of our view, and the question we're trying to answer. In other words "to better define what a product "should be" in our environment". Also see Appendix A below.

Wednesday Lunch (12:30-13:45)

1. Meeting Cancelled

Thursday Q3

1. Quarter for overflow, if necessary.

Appendix A: TSC Minutes Sept.10th

1. From the TSC minutes: [1]
   • Product Strategy Project (Project Insight # 413) – web site development underway for presentation layer to product briefs according to architecture defined in the document circulated a month ago. Ed notes that the disconnect in our product strategy is an inability to select something specific out of V3 to be able to purchase it. He doesn’t have a solution for that but it’s a packaging issue on interdependencies in the technical packaging. CDA managed to break out, and ICSR was trying to, for separate packaging.
   • The organization is focused on developing things, not selling things. The domain perspective was necessary for scoping development in an area but packaging all the dependencies needed to implement just a domain or functional/business viewpoints is not available. Woody notes that Fresh Look is a consequence of those issues. Should the product list be reviewed with an eye for those areas that have broad applicability and where are they narrowly focused? Do we need a better product strategy, or do we need to better define what a product “should be” in our environment, versus trying to define the products we have. Ron notes that SAIF tried to define traceability from a set of requirements. This is in theory but not yet in play and is not available to define a product perspective. Woody notes the idea to set requirements for an EHR is too large to create an entire top down product strategy. Ron notes that the architecture is a frame from within you can define some bottom up packages.
   • TSC still needs to ask the board to consider a product strategy. Woody also notes we collectively need to look at the products already held out as products, and determine those that have a position where they can exist independent of other products, or as part of a formal product we have not yet recognized.