November 29, 2018
Sandra Blair, Vice President Product Strategy
Across industries, one-quarter of revenues and profits come from launching new products and services, according to McKinsey & Company. However, failures rates of launches remain high – around 40 percent – regardless of product complexity or the amount of money spent on introducing a new product.
Employ best practices, including conducting “day-in-the-life” simulations engaging all company departments prior to launch and monitoring user reaction closely post launch to improve your chance of success.
In many cases, companies focus nearly all of their resources on product development and usability testing at the expense of operations. Questions about how to market the product, sell it, price it, deploy it on a repeatable basis, train employees and customers on how to use it, and support it through technology and customer service often go unanswered until the launch is impending.
Representatives from all aspects of the business – marketing, sales, training, implementation, customer service and operations, for example – should be included at the kickoff meeting and kept in the loop as product development and testing progresses.
Often known as the “pilot” environment, Operational Acceptance Testing (OAT) ensures that end-to-end processing is validated – that is, everything required to support the product is in place.
Some innovative products perform well in many use cases but fall short in others – for example, a promising innovation can fail in its attempt to scale. Stress testing allows for monitoring an application crash and its recovery. Volume testing inflates databases to their maximum capacity and performance levels to monitor throughput and response times.
Day-in-the-life simulations prior to product launches engage employees in role-playing as consumers and replicate entire end-to-end processes as much as possible. Companies should evaluate all aspects of using the product and its support services. Product performance and customer service, including call centers, “hot lines” and chat should be reviewed under different scenarios. Response times should be recorded and connectivity tested.
IT and operations play a large role in “day-in-the-life” simulations – IT monitoring activity and throughput, and operations monitoring calls. If evaluating a new payment product, operations would monitor transactions and output, ensuring that new transactions appear on statements, are reconciled and can be reversed accurately.
End-of-month or end-of-year simulations also should be tested for products affected by any different activities occurring during these periods.
No one should expect perfection right out of the gate. It’s important to make quick adjustments based on early response to products. Take the case of Pingit, launched by Barclays in 2012. Pingit met with initial disappointment since teens under 18 weren’t allowed to use it. Parents, wanting to send money to their children, complained on social media. Barclays acted quickly and dropped its age requirement to 16.
Post-launch measurements should include:
Vice President Product Strategy
Sandra Blair has over 25 years of operational and consulting experience in Financial Services. She specializes in leading teams that provide technology solutions to the largest companies in the Fortune 500. Her experience spans the financial technology industry -- primarily electronic payment processing and banking -- with extensive experience in developing systems, call centers, and back-office operations for a number of industries.