I’ve been giving talks and having lots of meetings with executives across a number of different industries who are interested in the internet of things and aren’t quite sure what to do. Based on the past ten years of my work around this topic, here are some high-level recommendations.
Assumptions: chances are you have a research department or the product arm of your business is changing because your industry is changing. Latching on to the internet of things, AR/VR, cloud and digital is likely to help you solve some problems but not all. Chances are you need a change of culture and a change of senior management. This article is specifically for your business if you’ve decided to commit to #iot as a topic area and are ready to commit to it for a minimum of 3 years.
- Think about legacy
Staff turn-around in technical teams can be high (especially if they’re young) and chances are you’ll be recruiting web developers, creative technologists, industrial designers and electronics engineer as part of a good team that can prototype new connected product ideas for your business. These teams, when they work well are self-sufficient and therefore a culture of quick iterative prototypes is developed. This culture clashes with the need for comprehensive documentation of each idea. Successful high resolution prototypes are one thing but the interesting little prototypes that lead you there are just as important. Making sure code, circuitboard diagrams, BoMs and demo videos are available is important to make sure someone in Marketing or the next technical lead can understand a development process.
- Know your history and your landscape
You are joining a rich ecology of startups, government programs, tools and standards groups. You’re not doing this on your own so you better get used to collaborating with others that may have competing interests but are much smaller than you and have developed better tools. It takes a particular type of humility but what you’ll get out of it will stand out from what’s being done by your industry. The point of the internet of things is the breakdown of industry silos. The trick here is to grow a circle of ‘care’ so work with people in a way that opens up your abilities and your contacts so they can do the same. That’s why it’s the internet of things and not the intranet of things. People expect APIs for your services and the open mind to go with it.
- Help users get literate
In light of the recent splat of press about the internet of things and security we have to work as an industry to give people the tools to know what they should do. We struggle to do this online already and when things are added to the mix of course it complexifies things a lot, but the opportunity here is for a decent amount of time spent with end-users, not just ‘personas’ who are so loved by some design thinkers. There’s nothing like giving people something to live with for a while (be it either at home or at work) to get great feedback and highlight opportunities. It’s not with post-its, it’s not with ideas, it’s with functional high resolution prototypes that you’ll have to invest in fabrication. This means spending months (a long-term trial of the average social robot is 3 months) with customers finding out how your product fits. Only then will you have something that can change people’s lives (at work or at home!) and only then can you help them understand the risks best.
- Be patient
Don’t assume you’ll be able to create value for your organisation quickly, getting teams to work together and have good ideas they can prototype and iterate (takes ages to order parts) and then getting something that’s unique enough to showcase once a year at CES means that to get noticed and the right partners on board long term you’ll have to do this for some years. You’ll learn a lot and try to trust your team to work slowly but steadily. It’s difficult when you’re probably tied to whatever you can do within a financial quarter but if you want to change your business, that’s the price to pay. Try not to change innovation managers too often that’s really disruptive to the process and technical teams and jeopardises progress. Also give them a good budget, they have to buy machinery and parts! :)