Marketing & Sales Roundtable Beta Program Best Practices November 2004.

Slides:



Advertisements
Similar presentations
A BPM Framework for KPI-Driven Performance Management
Advertisements

[Product Name] Marketing Plan
Marketing & Sales Roundtable Total Product Planning: Delivering What Customer Requires March 2003.
Roadmap for Sourcing Decision Review Board (DRB)
HR – Are we marketing the brand ? Neil Scurlock Head of Learning & Development The Chartered Institute of Marketing.
State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D.
Chapter 2 – Software Processes
Intuitive Design Inc. New Product Development Progress March 25, 2006 Prepared for: Company Management Team Dave Leis.
Existing Documentation
ACT Integrated Managed Support 2013 ITSMF USA Project of the Year Assurant’s Unconventional Approach, Uncommon Results AIMS.
Creating Customer Self Sufficiency Neeti Seth Sr. Manager, Customer Support, Mercury.
LR NYU Fall 2007 Business Operations New Product Development Process.
T /5115 Software Development Project I/II Project Planning Jari Vanhanen Ohjelmistoliiketoiminnan ja –tuotannon laboratorio Software Business and.
Use Case Development Social Journey Template. A “Use Case” is simply a defined way of using Yammer to accomplish a goal or complete a task. Define the.
IS 214 Needs Assessment and Evaluation of Information Systems Managing Usability © Copyright 2001 Kevin McBride.
Online Postgraduate Admissions Project Kate Ward – Project Manager.
Basic Elements Environmental Analysis –Customer Analysis –Competitor Analysis –Channel Analysis –Company Internal Analysis –Public Policy Analysis.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
Marketing & Sales Roundtable Lead Generation: Feeding the Sales Funnel September 2003.
Student Assessment Inventory for School Districts Inventory Planning Training.
MARCH 2010Developed by Agency Human Resource Services, DHRM1 Organizational Design What Is It? Organizational Design is the creation of roles, processes,
Marketing & Sales Roundtable Marketing ’ s Role in Driving the Customer Focus into the Planning Process November 2002.
1 Requirements Elicitation Slinger Jansen. 2  1. Motivation  2. Requirements  3. Continuous RE  4. The RE Framework  7. Fundamentals of Goal Orientation.
Kickoff Meeting Jam 11/18/2011 © Copyright All rights reserved.
The BIM Project Execution Planning Procedure
Interview Team Selection Randall Birkwood. What it is: - A simple, clean process - Convenient resources for interview team - Ensures interview team is.
What is Business Analysis Planning & Monitoring?
Examining Marketing and Business Advanced Marketing.
 Contoso is working on Wireless 1xEvDo application to handle high speed 3G application data transfer (voice, video data) in mobile phones while working.
William H. Bowers – Modeling Users: Personas and Goals Cooper 5.
Drive Customer Satisfaction. Cut Costs. Improve Efficiencies. Oracle i Support Chris Kirby Senior Sales Consultant Oracle.
© Group LLC. Not to be distributed without written permission of the 280 Group. 1 How to Run A Successful Beta Program Mike Freier Director, Business.
Marketing and Sales Roundtable Marketing ’ s Role in Driving the Customer Focus into the Planning Process November 2002.
EMI INFSO-RI SA2 - Quality Assurance Alberto Aimar (CERN) SA2 Leader EMI First EC Review 22 June 2011, Brussels.
SacProNet An Overview of Project Management Techniques.
Georgia Institute of Technology CS 4320 Fall 2003.
Microsoft Office Project 2003: Selling EPM in your Organization Matt Wilson Business Solutions Specialist LMR Solutions.
Info-Tech Research Group1 Requirements Gathering World Class Operations - Impact Workshop.
Leveraging Past Failures into Future Opportunities
Marketing & Sales Roundtable Positioning Strategy: The Foundation for Value Proposition and Messaging July 2001.
1 PROJECT RISKS IMPORTANCE OF COOPERATION BETWEEN PMs AND TEAM LEADs AUGUST 5, 2015.
Strategies for Knowledge Management Success SCP Best Practices Showcase March 18, 2004.
Chapter 2 – Software Processes Lecture 1 Chapter 2 Software Processes1.
2 Developing Marketing Strategies and Plans
July 19, 2005 Community Preparedness: Helping Community Leaders Prepare for Industrial Prospects.
1 Chapter 10 Instructor Shan A. Garib, Winter 2013.
Kathy Corbiere Service Delivery and Performance Commission
DEVELOPING THE WORK PLAN
eSciDoc Community Model Draft eSciDoc Community Model Overview 1.Introduction 2.Requirements on the Community Model 3.Organizational.
An Agile Requirements Approach 1. Step 1: Get Organized  Meet with your team and agree on the basic software processes you will employ.  Decide how.
PLANNING SUCCESSFUL PRODUCT LAUNCH
Impact Research 1 Enabling Decision Making Through Business Intelligence: Preview of Report.
IT Service Management: Sample Download 1.
Info-Tech Research Group1 Info-Tech Research Group, Inc. is a global leader in providing IT research and advice. Info-Tech’s products and services combine.
Information Sharing for Integrated Care A 5 Step Blueprint.
A Framework for Marketing Management International Edition 2 Developing Marketing Strategies and Plans 1.
Case: Taking an Existing Intelligence Operation to the Next Level Jens Thieme Head of Market and Competitive Intelligence.
What it is about? © SkillsRate is registered mark of SKILLSRATE SRL It is all about testing, testing skills,
How to use C OBI T implementation resources Brian Selby Director of C OBI T Initiatives ISACA.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
Planning Engagement Kickoff
Office 365 FastTrack Planning Engagement Kickoff
Process Improvement With Roles and Responsibilities explained
ITSM Governance is Imperative to Succeed
Guidance notes for Project Manager
Employee engagement Close out presentation
Bridging the ITSM Information Gap
Presentation transcript:

Marketing & Sales Roundtable Beta Program Best Practices November 2004

©2004 Rosemary Remacle 2 11:30–Introductions/Objectives 11:45 - Beta Program Best Practices: Presentation and Discussion 1:15–Summary and Wrap-up Agenda

©2004 Rosemary Remacle 3 What Do We Mean: “Beta Test”? Testing of a working product performed by real users in a production environment Last test before formal product launch, production shipments begin (GA) A test of all elements and process required for successful GA product The Beta program definition will be driven by product category and type of users – HW, SW, Services

©2004 Rosemary Remacle 4 Objectives for a Beta Program Product Gain deeper understanding of how product works in a ‘real world’ environment Stress products more completely and in different ways than in a lab setting Fine-tune product/service functionality (tweak vs. major overhaul) Test configuration planning, installation and support procedures and documentation (including technology and delivery partners where applicable) Test specifications and metrics to ensure quality levels of the specifications in a range of environments (e.g. usability, reliability, performance, etc.) Marketing Test corporate and product positioning platform, message architecture and plans for customer segment programs Develop a systematic way for capturing customer information and input Build key early customer relationships, generate references and referrals Understand weaknesses in company infrastructure required to support all customers’ requirements (total product)

©2004 Rosemary Remacle 5 Beta Program Development Collect and analyze user feedback Identify, prioritize issues to be resolved Develop integrated functional response plan Refine beta testing process Summary beta report doc Define beta testing process, participants and objectives Produce integrated functional plan - Engineering - Marketing - Sales - Professional Services - Support - Partners Develop criteria for beta test customers Identify and Recruit beta customers and set expectations Create beta program documentation Implement beta program - Product Distributed to Beta Users - Survey Vehicles in place - Reporting Process - Timelines, Milestones

©2004 Rosemary Remacle 6 Sample Criteria for Selecting Beta Customers Criteria(Hi – Med – Lo) Member of identified market entry customer segment(s) Does their application test stress the aspects of the product that need it? Match of company’s solution to perceived customer critical need Motivated to make fast decision within market window/Beta program manager in place Early adopter technology adoption cycle profile: high tolerance for Beta problems Referenceability: Big name, technology leader and/or key influencer in market entry segment, willing to be reference Existing business relationships with key members of Beta company team, users Internal Champion Geographic proximity for ease of support Technology or market leader

©2004 Rosemary Remacle 7 Beta Program Best Practices: The Short List Don’t abuse the generosity of beta customers with non customer-worthy product – develop a “phased beta approach” to address risks of putting beta product in big influential prospective customer Choose and recruit your beta customers, users to match market entry customer segment(s) Drive for confidentiality (NDAs, Beta agreements, etc.) Manage the program and beta users, communicate (bi-directional) regularly (program managers in both your company and customers) Provide a simple, easy method for beta users to give feedback, make them feel like part of the your team Encourage beta users to communicate with each other Respond quickly to all requests and problems Document, document, document

©2004 Rosemary Remacle 8 What Motivates Beta Testers ? Early adopter technology adopter cycle value profile Ability to contribute to product development process, be perceived as expert ‘Community’ participation Exclusive access to new product/Head start on resolution of their business problem ‘Free’ product/Incentives Career advancement Where do You Find Them? Sales Force/Executive Team relationships Partners (Channel, complementary products, etc.) Internet groups/Blogs/Bulletin Boards and Lists “Dead prospects” Customers’ competitors Other? User Groups/SIGs

©2004 Rosemary Remacle 9 Elements of Beta Program Research Plan [Realistic] sampling strategy - # of customers - # of participants - Functional representation Efficient user feedback (technical and marketing) collection tools (on-line, web page) Third party tools (e.g. web surveys - Survey Monkey, Zoomerang) for simple, measurable inputs - In-depth, qualitative (e.g. telephone/in-person interviews) for exploration of issues/requirements and positioning strategy validation - Forum discussions (open and hosted: web forum, conference calls, WebEx) Surveys: design for structured analysis! - Topics to be covered by function - Technical and marketing metrics - Qualitative ‘discussion’ topics

©2004 Rosemary Remacle 10 Beta Test Plan Definition - Project parameters, goals, activities and participants - Internal resources required, responsibilities identified -Foundation for beta report/summary Table of Contents - Product definition (in current state) -Target customer segment(s) – “user spec” (time, HW, etc.) - Parameters (# of participants, timeline, etc.) - Goals (UI, support requirements, testimonials, etc.) - Incentives (as appropriate to situation) - Beta team action items and responsibilities - Etc.

©2004 Rosemary Remacle 11 Post-Beta Test Make customer feedback accessible, institutional customer intelligence (Analyze customer feedback in structured way and document all issues) Prioritize issues (severity and repetition) and develop an integrated cross- functional action plan Incorporate beta user feedback into market-driven product roadmap Ensure all company infrastructure requirements identified have been fully addressed Review beta program process and execution performance and develop improvement plan Send out incentives (where appropriate) and thank individual Beta users personally (phone call, , etc.) in a timely fashion

©2004 Rosemary Remacle 12 Some Tips for Managing a Beta Program Establish well-integrated cross-functional team with representation from all stakeholders (executive, marketing, sales, engineering, support, partners, etc) Assign program owner (generally marketing) and define clear team member roles and responsibilities Agree cross-functionally on criteria for choosing a Beta site Promote importance and value of beta test to all functional organizations and share the beta information with all who need it

©2004 Rosemary Remacle 13 Key Beta Test Mistakes “Wrong” beta testers accepted Recruiting family or friends skews perspective Poorly managed beta testers and/or test data Prohibitive time commitment, resulting in drop-outs Viewing Beta program as revenue source Beta test period too short or too long Too few or too many beta users (difficult to manage) “Choosing the wrong beta testers is the best way I know to provide useless results”

©2004 Rosemary Remacle 14 Summary: A Successful Beta Program Product works as advertised Benefits are documented, validated and measured (overall, feature-specific) Product configuration, installation and customer support processes and documentation meet customer expectations Unanticipated or un-addressed total product requirements are identified and prioritized with level of criticality determined

©2004 Rosemary Remacle 15 Presenters Rosemary Remacle, Consultant Market Focus