swaldron58
commented
3 years ago Initial ideas:
- Publishable statement(s) of benefits of 3.1. Not just statements of updates where the reader needs to decipher what that means to them or their organization, but also where we can, outline commercial and/or productivity advantage. Arguably particular attention paid to tool vendors. Expecting this task to take one person about 8 to 10 hours spread over a week.
- Publishable examples of targeted use cases such as support of Python or tool updates. The intent here is to demonstrate the efforts are reasonable in scope and cost. This will allow us to generate data for overall cost/benefit statements.
- Publishable statement(s) of where 3.1 is already in use and the benefits gained. This would need to be updated on a regular basis. This may include notices of projected 3.1 implementations.
In the marketing call on Oct 22nd, a request for the tech teams to create material to better communicate the benefits of 3.1. Marketing has to take the lead on messaging, but needs more consumable content targeted for various audiences.