Skip to content

Instantly share code, notes, and snippets.

@ianakelly
Last active July 12, 2016 19:56
Show Gist options
  • Save ianakelly/097b3b0dd26054f0ba1a277e892ddcd7 to your computer and use it in GitHub Desktop.
Save ianakelly/097b3b0dd26054f0ba1a277e892ddcd7 to your computer and use it in GitHub Desktop.

##Product Focus:## Too tight of connection to a product will corrupt the ability to go broader - if we tie to product we MUST assume that we will be targeting mainly existing customers and a small set of future customers. This mean the targets CANNOT be external pipeline or contact metrics but must be tied to Customer Satisfaction (NPS), Customer Retention, and Improvements to Product.

##Targeted Comms and Collateral:## We need to come up with a solid message of how we add value in MAS even if we have limited conversion to MAG. This means we need to understand the underlying SKU upgrade price to MAG and understand how to influence upgrade decisions and sales support. Without solid sales support we will struggle as an upgrade is too small to work on for most sales folks looking to retire quota - may need accelerated quota retirement for a time.

We should agree on a solid Problem/Solution Fit message for MAS. There needs to be a better set of understood and expressible use cases (With Code Samples) to discuss this journey.

We need to better codify the sales rhythms to move from solution fit to committed purchase - this needs shoring up with Sales.

Co-Creation - The concept is the highest and best use of any relationships we pursue - Partners, Patronage Development (https://www.patreon.com/), or Customers. We need to lead with this mentality, in the world of "Vendor Control Points" this WILL be differentiating.

Personal Note - We may need to consider a MAS without MAG or competitor offering if we want to see ubiquity of MAS usage. If we forever tie MAS success to MAG we will NEVER gain ubiquity.

Target Customer/Developer to be engaged = Security Oppressed "Desire to Punt on Security" (Sees Security requirements as a burden to be avoided), Enterprise Aligned (Tied to traditional Enterprise silo inefficiency model - May not be as successful in Product Teams who own their space), Vendor Locked (to Layer7) Additional notes: Could have strong advocacy in the EA/Governance ranks to "Prop up MAG purchase decisions" This may take both Developer Evangelist and Services engagements.

Target Market = Industrial, Transportation, FinTech (Real Estate, Document Heavy areas like Taxation, Property Management, Legal)

Before anyone starts saying "Lets have a Free Plan" Sage Advice: picture alt https://twitter.com/johnsheehan/status/750391633078652929

MAS Site - I am very impressed with the work on the MAS site, there are for sure some minor enhancements that can be done but if we pull the accountability from the current team I have major doubt to our ability to ever arrive at as good a place as we are now. We need to open up the Social and Code elements of the plan and add members to the team to seek out our verticals to address the needs. See Outcome Oriented Teams vs Activity Oriented Teams - http://martinfowler.com/bliki/OutcomeOriented.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment