‘How to Launch a Product’ Blog Series: Determining the Type of Release

Here at ReadyTalk, we use two methods in development – Agile and Lean, and depending on the type of development methodology used, we treat launches a little bit differently.

For Agile, we do a typical launch plan and work closely with Product Management and Marketing to execute on key deliverables. For Lean, our Product Strategists generally handle these launches as we are more likely to be in an Alpha or Beta phase, being sure to test products as we move along. With Lean, our cycle is to test and get feedback, which will tell us to either stay the course or pivot quickly– more quickly than Product Marketing and Marketing can support today. Once a product idea has been validated, it then moves into Product Management and gets into the regular product launch cycle.Update

The following series outlines launching products and services from our Agile development teams using the Pragmatic Marketing Framework, which provides definitions when it comes to roles and responsibilities.

The Type of Release

First, I work with Product Management to determine if it is a Major or Minor release. A Major release (usually indicated by a change from 16.2 to 17.0) is a major change in the software and may not be backwards compatible with previous versions.

A Minor release (usually indicated by a change from 16.2 to 16.3) indicates minor additions, enhancements and bug fixes and is backwards compatible.

Product Management will indicate if it is Alpha, Beta or Generally Available (GA). Alpha usually indicates that it is a first version of the software: it’s incomplete, buggy and will change significantly before it’s released in its final form. Goals for an Alpha are to get feedback from users and give partners early access. A Beta is much closer to what you expect to ship- it’s fairly complete and should have relatively few problems. It’s a confirmation by Beta customers that it really is ready for GA. It’s also a chance to get it out to partners as well. GA is a product that is ready to be released or sold to customers.

Product Marketing then works with Marketing on the timing of the launch. We look at what other items we are communicating/launchingto which audiences, and determine the best time for the launch.

I usually plan for about 8-12 weeks for Major releases and about 4 weeks for Minor releases. I set up a kickoff meeting with key stakeholders and determine what tactics we want to include. Westart with a template that highlights typical launch items for both Major and Minor releases, and walk through the plan to determine what will be needed to support the launch. Not all tactics are used every time. Working back from the launch date, we assign dates and resources to the tactics. Then I set up a weekly or bi-weekly meeting so we can be accountable for the deliverables outlined in the launch plan. A launch plan includes goals, objectives, sales enablement tools that sales will need, marketing activities (such as advertising, tradeshows, PR), communications, training, etc. I will go into further detail about each of these in future blogs. My next blog will focus on how to set launch objectives and goals and tell you what goes in a Messaging Strategy Document (MSD).

What? Crackle. Drop.

The Cost of Weak Online Conferencing for IT and Business

Conferencing is crucial to businesses, but they can also be detrimental without the right provider. The top 4 most common problems caused by weak conferencing are:

  1. Screen Shot 2016-02-03 at 3.21.24 PMPoor audio quality: Poor quality audio is one of those things that is hard to ignore, but can quickly ruin any online conference.
  2. Unreliable systems: Unreliable systems can cause panic and disruption. If you are using these systems for client meetings, it can damage your image and hurt your relationships.
  3. Difficult to join, difficult to use: Unintuitive and cumbersome conferencing solutions are a waste of time and resources.
  4. Lack of support: Your team should not have to troubleshoot your conferencing system when problems arise, but you may need assistance immediately. Lower quality conferencing services may not be available to assist you right away, or will send you to a user manual.

Do any of these sound familiar?

Not only are these problems frustrating, they could be quite costly to your business. Here are the 3 most serious ways your IT organization is directly affected:

  1. Security: With so much fraud, theft, and malicious software, your conferencing system security needs to be vigilant.
  2. Administration: Each conferencing system has its own infrastructure, and IT is normally stuck managing them. Choose the right one; otherwise, it may be a constant issue to maintain.
  3. Support: When conferencing systems are weak, IT takes the brunt of those issues. They are left troubleshooting problems, leaving less time for more important work.

Screen Shot 2016-02-03 at 3.22.49 PMWeak conferencing doesn’t just affect IT groups; these risks and costs affect the rest of the business as well. To find out more about the expansive costs a weak conferencing provider could have on your business, download our eBook, “What? Crackle. Drop.

Download Button