Wilson Mar bio photo

Wilson Mar

Hello. Hire me!

Email me Calendar Skype call 310 320-7878

LinkedIn Twitter Gitter Google+ Youtube

Github Stackoverflow Pinterest

Evangelism dependencies

Sequence of deliverables


Overview

This diagram is an example of the deliverables necessary for evangelism:

Different colors in the diagram delineate possible levels of secrecy or ownership by different teams.

The sequence of what comes first, second, and so forth can also be different for each organization.

Let’s look now at the wisdom, the PROTIPs, behind each item in sequence.

  1. We start with the pain points, where people need to take action and are likely to be looking for solutions, which is the definition of a sales prospect.

  2. Prospects are likely to encounter an organization’s competitors, so a strategy is needed to best answer concerns, both verbally and in real products and services.

  3. Ideally, differentiation and positioning is summarized by keywords “sound bytes” and Twitter hashtags used in emails and titles of presentations.

  4. But rather than just empty slogans, statistics about customers (their concerns, where they live, both indistry-wide and your particular sub-groups) should drive messaging.

  5. Real people and their organizations
  6. and their stories (“proof points”)
  7. in presentation graphics so
  8. social media reflects reality and sincerity.

  9. Validated “proof points” in testimonials and surveys are needed to prove Return on Investment on time spent to
  10. view demos, take calls, and read communications.

  11. scripted videos are essentially short recordings of conversations and conceptual explanations given during
  12. live demos, meetups, and conference presentations.

  13. On the technical side, sample applications are used in
  14. benchmark statistics which provide a factual and repeatable basis to prove competitiveness.
  15. Such are what external industry analysts (such as Gartner) can use to make their case for you.

  16. Yes, books are still helpful for publicity and credibility.

  17. But video courses with student interaction and quizzes to ensure learning is what delivers capable users who can
  18. achieve useful results during Hackathons and actual deployments of your offering.



These items don’t cover all of the artifacts relevant to technical evangelism, so contact me for more.

NOTE: The diagram was (created with animations in MS PowerPoint 2011)

More on technical evangelism

This is one of several topics:

  1. Job Descriptions
  2. Resumes (mine)

  3. Evangelism dependencies
  4. Deliverables and Events Budgeting spreadsheet
  5. Evangelism Cost-Benefit analysis (Bang-for-the-buck comparion)

  6. Events and Conferences
  7. Calendar of Announcements
  8. Milestone events

  9. Social media
  10. Social media strategy
  11. Tweets
  12. Sentiment analysis (of favorable words or not)
  13. Responses to social media
  14. Tech Press mentions

  15. Competitive Comparisons (by analysts and others)
  16. Competitive Strategy
  17. Competitive Comparison Kit (for people to run for themselves)
  18. Objections, and how to handle them

  19. Target Customers
  20. Customer References
  21. Proof Points
  22. Email databases (User Acquisition)
  23. Remarketing of current or lapsed users

  24. Product websites
  25. Product wikis
  26. User Forums (Google, LinkedIn, Reddit, etc.)
  27. Surveys

  28. Product Roadmaps
  29. Release Schedule
  30. Tasks
  31. Issues

  32. Enviornments for development, testing, demos, training, etc.
  33. Demo presentation scripts
  34. Beta activities
  35. Release Notes

  36. Tutorials
  37. Live event sign-up administration
  38. Webinars
  39. Video production capability
  40. Live Video Streaming

  41. Spiffs
  42. Hackathons
  43. Participating in Conferences
  44. Running Conferences
  45. Dynamic projections of tweets, etc.

  46. Recruitment follow-up