Sonicare’s connectivity also allows for the collection of data concerning products in the field, such as usage information, hardware status, triggering the purchase of brush heads and more. Combined with user profiles, this can give powerful insights to drive customer journey mapping across the lifetime of a product. Similarly, that same data can be used to improve product development and create better-targeted marketing campaigns.
And just imagine what will be possible with products elsewhere in the home? One commonly cited example is of lighting and heating being controlled through an app; however, the possibilities are seemingly endless. An air purifier could give advice around environmental conditions, and the connectivity of any number of personal medical and health devices actually enable the entire home monitoring market.
Once you’ve figured out the value that can be generated from products and data, how do you ensure that the right propositions are created? First, you need to create very clear user stories using Agile development (including a lot of prototyping) and validate these with consumers – your most important stakeholder here.
Second, make sure your selected use cases work! This is especially true with connected products, where service, reliability, speed and responsiveness are important. Now, I’m not saying it’s necessary to have all use cases covered from the start, but you should have a clear vision on where you want to go based on a representative sample.
When defining a connected product, not only should you look to the user stories directly related to the product, but also to the ecosystems they connect to and the value that can be generated from them. With Philips’ Health Suite Digital Platform (HSDP), we are creating new user stories on a versatile platform. This means that key stakeholders from across businesses must work together more closely, creating products that can link up internally and enable additional user stories.
Let's assume that you’ve done your homework well. You’ve created the right user stories, and the data models of your connected product have been correctly defined. Soon enough you will start receiving data from those products in use. For this you’ll need to be prepared. First, by keeping the data secure and regulating access, and second, ensuring that it’s ready to analyze and drive additional value and insights. It’s this ‘secondary’ aspect of the connected proposition that must be developed in parallel (or even before) you bring connected products to market.
Do not underestimate the work that this phase takes; data is fiddly, highly detailed and requires significant resources to fix and clean when data models are broken.
The Impact of Connected Products on Value Chains
Connected products are in the process of completely transforming value chains. In Service, for example, remote connectivity gives technical support teams access to products from afar. This in turn allows them to gather data, check status and in more and more cases, allows for remote service and repair. The reduced need to ship products to and from service centers brings clear benefits. Taking it one step further, imagine the kind of customer services that could be delivered when you don’t even have to wait for a problem – where the need for service can be anticipated and pro-active steps taken to solve it? To close the loop, all of the information generated by this flow of data can feed back into R&D processes, where these valuable insights can inform future product propositions.
