<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Daniel Elizalde on Medium]]></title>
        <description><![CDATA[Stories by Daniel Elizalde on Medium]]></description>
        <link>https://medium.com/@delizalde?source=rss-adec3aa69dfd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*m8eYUA8hxoCIDIrU.jpeg</url>
            <title>Stories by Daniel Elizalde on Medium</title>
            <link>https://medium.com/@delizalde?source=rss-adec3aa69dfd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 12:37:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@delizalde/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Why There’s No Killer App for IoT]]></title>
            <link>https://medium.com/iotforall/why-theres-no-killer-app-for-iot-5646fda5a0fe?source=rss-adec3aa69dfd------2</link>
            <guid isPermaLink="false">https://medium.com/p/5646fda5a0fe</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[industry]]></category>
            <category><![CDATA[iot]]></category>
            <dc:creator><![CDATA[Daniel Elizalde]]></dc:creator>
            <pubDate>Thu, 16 Nov 2017 15:26:00 GMT</pubDate>
            <atom:updated>2017-11-16T15:26:00.994Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Any company can create the right killer app that solves the need of their specific customer.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/0*zppbTpJSKTBITy-M.jpg" /></figure><p>Every new technology trend brings speculation and talk about a “killer app” that will be the solution to all of our problems.</p><p>Tech publications and blogs produce countless articles searching for the “killer app” for the iPhone, the Cloud, Blockchain, Artificial Intelligence, and of course, IoT. We’ve also even seen the same hype for development processes. I can’t tell you how many times I’ve heard that Agile is that silver bullet. Or maybe it was Lean, or Kanban? Hard to keep track.</p><p>But as a Product Manager, we can’t keep chasing the next big thing all the time. It’s true we need to understand where technology is going, but we need to be more pragmatic and realize there is no single “killer app” for anything. Particularly for IoT.</p><h3>Is predictive maintenance the killer app for IoT?</h3><p>Predictive maintenance refers to the practice of <a href="https://www.iotforall.com/go-big-iot-value-preventive-maintenance/">adding sensors to collect and analyze real-time data from industrial equipment to predict when it is likely to fail</a>.</p><p>I often talk to companies who want to get into IoT by offering predictive maintenance solutions. They are interested not because they’ve spotted a customer need, but because they’ve heard that predictive maintenance is where the money’s at in IoT. In essence, somebody convinced them that predictive maintenance <em>is</em> the killer app for IoT.</p><p>It is true that predictive maintenance is getting a lot of traction with industrial companies, but that’s because it addresses a tough problem that those particular companies already had. Not because predictive maintenance in itself is the solution to all problems.</p><p>My advice is this: Instead of looking for the killer app for IoT, companies should focus on understanding their customer’s needs and evaluating how they can leverage the Internet of Things to solve those problems in a better, faster, or cheaper way.</p><p>In short, by understanding your customer’s needs, you can design the <em>right</em> killer app for that particular customer challenge.</p><p>If you stop considering IoT as a silver bullet and instead look at it as another tool in your portfolio, you can move past the hype and start working towards building real solutions.</p><h3>Other innovative applications leveraging the Internet of Things</h3><p>To drive this point home, I’d like to share a few real-world applications in use today. Notice that these products are not creating a new category of problems. Instead, they provide more efficient solutions to existing customer problems. These companies understood their customer’s challenge and then leveraged IoT by asking the question, “How can I provide a better solution by acquiring and processing real-world signals from my customer’s environments?”</p><p>If you think about it, acquiring and processing real-world signals is one of the key attributes of IoT, so with that in mind, what innovative solution could you create for your customers?</p><h3>1. Reducing traffic congestion via smart parking</h3><p>As cities grow, so does their traffic congestion. And in many cities, a big contributor to this congestion is lack of parking spaces. Think about cities like San Francisco or New York. Drivers spend a lot of time circling around buildings trying to find a parking space. This in turn increases the traffic of already congested areas.</p><p>Some cities are looking at IoT to address this issue. By placing sensors on the street and on lighting posts, cities are able to track which parking spots are available and offer this information to companies who can monetize this data via apps or other types of services.</p><p>The parking information is also aggregated in the Cloud and allows cities to study traffic patterns to plan for better solutions in the future.</p><h3>2. Optimizing waste collection</h3><p><a href="https://www.actility.com/customer-stories/suez-implements-connected-bins-netherlands/">A company in the Netherlands</a> is using the Internet of Things to track waste through its complete lifecycle. They place sensors in each of their bins to inform waste collectors when the bin is full and needs attention. This allows them to optimize collection routes and minimize the time and effort it takes to collect this waste.</p><p>Their collection trucks are also equipped with load sensors that determine, in real-time, the amount of waste that the main disposal center can expect as the trucks approach their destination.</p><h3>3. Increasing resiliency in the electric grid</h3><p>To increase resiliency in the electric grid, utilities around the world are leveraging IoT solutions to detect where power was interrupted so they can send a team to fix it right away. It used to take hours before utilities could determine the exact location of a fault. Today, they have this information in real-time, plus they can apply machine learning to anticipate the location where faults are likely to occur.</p><h3>4. Helping with conservation efforts</h3><p>The applications for the Internet of Things go across all industries and verticals. For example, <a href="http://www.savetheelephants.org/project/tracking-real-time-monitoring/">teams in Africa</a> are leveraging IoT to prevent elephant poaching. The teams tag each elephant with a smart collar and track the elephant’s location and motion patterns.</p><p>The information collected by the collar is analyzed in the Cloud by specialized algorithms. Some of these algorithms can detect when an elephant becomes immobile, which could be a sign of an attack by poachers. The system sends alerts to the wildlife management bodies who provide fast response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/0*9Yd3kJcAl8t5Lfwj.png" /></figure><h3>The Bottom Line</h3><p>As I mentioned at the beginning of this post, there is no one, single killer app for IoT. Instead, any company can create the right killer app that solves the need of their specific customer, in their specific industry, and vertical.</p><p>In this post, I shared a handful of examples, but we are seeing applications in all industries, from Healthcare, to Energy, to Smart Agriculture, Smart Buildings, Transportation, etc. Companies in all industries are looking to adopt IoT as the catalyst to improve their existing solutions.</p><p>So as a Product Manager, where do you start? Forget trying to chase the killer app. The first step is to have a clear understanding of your customer’s needs.</p><p>The second step is to understand how you could improve your solution by collecting and processing real-world signals and therefore, providing a better, faster, cheaper, or more innovative solution to your customer — one that provides a lot of value and they can’t wait to give you money for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/0*r5uKAucDkF53_Dy8.png" /></figure><h3>Want all the latest advances and tech news sent directly to your inbox?</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5e6c65%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F5e6c65%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href">https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href</a></iframe><figure><a href="http://eepurl.com/cPPD79"><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*F49VxnybKhjmi-bFQGj4kg.png" /></a></figure><figure><a href="https://iot-for-all.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvZqvtDLMZxtmq7cRtj4pA.png" /></a></figure><figure><a href="https://iot-for-all.com/rss-feeds/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugIM8aESdtjz13As4I2JkQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5646fda5a0fe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iotforall/why-theres-no-killer-app-for-iot-5646fda5a0fe">Why There’s No Killer App for IoT</a> was originally published in <a href="https://medium.com/iotforall">IoT For All</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IoT Business Models for Bringing in $$$]]></title>
            <link>https://medium.com/iotforall/iot-business-models-for-bringing-in-7ed21acb0314?source=rss-adec3aa69dfd------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ed21acb0314</guid>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Daniel Elizalde]]></dc:creator>
            <pubDate>Fri, 06 Oct 2017 15:56:02 GMT</pubDate>
            <atom:updated>2017-10-27T17:50:52.724Z</atom:updated>
            <content:encoded><![CDATA[<h4>Here are the 5 business models you can use to monetize your IoT product.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*SQEpNCwBhNX7SiplckUdsw.jpeg" /></figure><p>With their ability to gather data after a product has been deployed, IoT products provide a platform to generate new and innovative business models that haven’t been seen before. In this post, I describe some of the most interesting <a href="https://www.iotforall.com/iot-transforms-business-models/">IoT business models</a> in use today.</p><p>I recently attended a very popular IoT conference in Silicon Valley. During a presentation, the keynote speaker asked the audience, “Who here is building a connected product?” About two-thirds of the audience raised their hand. Then he asked, “Who is making money with IoT today?” No hands went up this time.</p><p>This little engagement trick reinforced the fact that many companies are jumping into the opportunity of building IoT products without a clear monetization strategy, or put more simply, a strategy for how to make money from your IoT product.</p><p>Based on the <a href="https://techproductmanagement.com/iot-decision-framework/">IoT Decision Framework</a>, you are here:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/892/0*_XvUKxqfnuw6SXR4.png" /></figure><h3>1. Subscription Model</h3><p>One of the greatest benefits of a connected device is that it enables recurring revenue. Now instead of having a one-time sale, you can offer a subscription model in which you charge your customer a fee for providing continuous value.</p><p>A subscription model enables you to implement many of the benefits available to software-only products within your IoT solution. Basically, you are introducing an “as a Service” model but for a system including both software and hardware. By using SaaS models as an example, you can find ways to monetize your product not only with a monthly subscription, but also by providing paid upgrades, or even implementing a “freemium” model if your strategy supports it.</p><p>Another benefit of this IoT business model is that it empowers you to foster an active relationship with your customer. In the past, hardware manufacturers used to “throw their products over a wall”, meaning that once they completed the sale, they rarely interacted with their customer anymore. IoT products break that barrier down. As your device gathers more data, you will be able to learn more about your customer and provide more valuable features tailored to their specific needs.</p><p>Some common IoT applications using the subscription model include “monitoring as a service” and “predictive maintenance as a service”. Here are some <a href="https://www.iotforall.com/iot-subscription-strategy/">important considerations if you’re thinking implementing a subscription model</a>.</p><h3>2. Outcome-Based Model</h3><p>The outcome-based model is an example of an innovative approach enabled by IoT products. The idea is for customers to pay for the outcome (or benefit) the product provides, as opposed to the product itself.</p><p>Remember the saying, “People don’t buy drills, they buy holes”? Well, the outcome-based model works in the same way. Customers pay for the “holes” they make as opposed to paying for the drill.</p><p>For example, think of a water pump manufacturer. In the past, their business revolved around selling pumps, and they measure success by meeting quota on a certain number of pumps per quarter. But let’s be real. Customers are not looking to buy a pump. They are looking to move water from point A to point B for some purpose. For example, they need water to cool another system, to water plants, or to power a generator. That’s their real need.</p><p>Now imagine a sophisticated pump manufacturer who creates a next-generation pump that monitors the amount of water it pumps. Now, the manufacturer can talk to the customer in the language they care about: amount of water pumped (similar to “holes drilled”). In this case, the customer is not buying a pump. Instead, they are paying a variable fee per month for the amount of water they source. They are paying for the outcome, which is, water sourced.</p><p>Companies can be creative with how to monetize IoT solutions as part of an outcome-base model. For example, the manufacturer can decide whether they’ll lease or sell their pumps. If the customer is interested in the outcome (water sourced), then they might not want to have a depreciating asset on their balance sheet (pump). Therefore, having them pay for the water sourced as opposed to paying for the pump itself can reduce the customer’s objection to buying expensive equipment.</p><h3>3. Asset-Sharing Model</h3><p>A big concern when buying expensive equipment is whether the customer will be able to utilize the equipment to its maximum capacity. This is where the idea of sharing assets comes into play. We are starting to see this model already with car-sharing or bike-sharing companies. Think about it like this: why do I need to pay for the full price of a car if it’s going to be parked outside my house 90% of the time. Could I just pay for the amount of car I use?</p><p>IoT has the potential to solve this problem, and we are already starting to see solutions with self-driving cars, virtual power plants, shared drones, and more.</p><p>This IoT business model revolves around selling your extra capacity back into the market. The goal is to maximize the utilization of your product across multiple customers. That way, each customer pays a reduced price and you are able to get faster market penetration, compared to when a single customer has to pay for your complete product.</p><p>I had the opportunity to work within this model deploying smart batteries for commercial buildings. The batteries provided energy to the building, and if they had any extra capacity, they were able to sell that energy back to the Grid. In this model, the batteries are a shared asset between the building and the Grid. This approach allowed our customers to get our systems at a reduced price since now they didn’t have to carry the burden of paying for the whole system, whether they use the extra capacity or not.</p><p>You might be thinking, “Why not just install a smaller battery?” And that’d be a fair question. Sometimes, they don’t make smaller batteries (or smaller pumps, or turbines, you name it). Most of these systems are very complex, so you can’t get custom sizes. So, you can just throw away that extra capacity or you can figure out a way to monetize it. That’s where the intelligence built into smart devices can help you.</p><h3>4. IoT Products as a Proxy to Sell Another Product</h3><p>Your IoT product can be a conduit for selling other products. In this model, you might sell the IoT product at cost or even at a loss since the goal is to get the product in the customer’s hands so you can start selling your other products. This approach reminds me of the early strategy from Ford, where the plan was not to make money on the cars themselves, but on the parts and service.</p><p>Amazon uses this model with their <a href="https://www.amazon.com/b/?ie=UTF8&amp;node=10667898011">Amazon Dash Buttons</a>. These “connected buttons” come pre-configured to order a specific product, say detergent or toilet paper. When you press the button, it re-orders that item from Amazon and it arrives at your door within a few days.</p><p>Amazon’s goal is to provide “contextual shopping”, meaning the ability to reorder a product right when you need it. By introducing this clever connected product, Amazon is reducing the barriers for you to re-order any product you need. In this case, the Amazon Dash Button is not a revenue maker in itself, it is just a vehicle to sell other products in Amazon’s catalog.</p><p>We are seeing more and more manufacturers adopting this approach for products that require refills. Printer manufacturers are creating “smart printers” that automatically order ink when they are low. We have a <a href="https://techproductmanagement.com/iot-solution/">connected pitcher that automatically orders new filters</a> and many other examples.</p><h3>5. IoT Products as a Vehicle to Monetize Data</h3><p>The value of IoT is in the <a href="https://www.iotforall.com/differentiate-iot-product-provide-insights/">insights you can derive from the data you collect</a>, data has become the <a href="https://www.iotforall.com/data-worlds-most-precious-resource/">world’s most precious resource</a>. The question is, who benefits from the data and insights? Think about companies like LinkedIn or Facebook. They collect a huge amount of data from all of us (often for free) and although they provide us (the user) with value for providing that data, the real value is provided to advertisers and other third party companies that use that data to promote their products and services.</p><p>In this case, LinkedIn or Facebook are tools to collect data to offer to advertisers.</p><p>The same model works in IoT. You can build your product to provide value to the end user, and also to collect valuable data you can then sell to a third party. In this approach, you can offer your IoT device at no cost to eliminate the friction with the end user. The goal is to deploy as many devices as possible to collect data. The more devices you have out there, the more attractive your data proposition will become to third parties.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*zqL5yFaUPkhc3Hd6abFjVA.png" /></figure><p>There are many examples of IoT products leveraging this model. Think of energy efficiency devices installed in buildings to monitor their energy consumption. The building manager benefits from this data, but utilities or other aggregators can pay a hefty sum to receive aggregated data from thousands of buildings.</p><p>The same is true with devices that monitor your driving habits. They provide you with some interesting insights, but insurance companies get the most value as they are able to understand driving patterns for thousands of people.</p><p>This IoT business model can be a line extension of your core business, meaning you can start by solving the needs of your end user and later, you can decide to branch out into monetizing their data. These two models don’t conflict with each other as long as you make your customers aware of how their data will be used and you make sure to safeguard their privacy.</p><p>Keep in mind that sharing aggregated data with other companies is not just an “add on” to your existing IoT solution. It’s a full product that requires understanding your third party users, assessing the impact to your infrastructure, etc. I recommend using the <a href="https://techproductmanagement.com/iot-decision-framework/">IoT Decision Framework</a> to see how this new functionality will impact your existing product.</p><h3>The Bottom Line</h3><p>As a Product Manager, it is important to understand how your product adds value to your customer and to your company. So it is very important to have a clear strategy for how to monetize your product. The good news is that IoT products provide many new and innovative business models for monetization of your product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*zqL5yFaUPkhc3Hd6abFjVA.png" /></figure><h3>Want all the latest advances and tech news sent directly to your inbox?</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5e6c65%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F5e6c65%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href">https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href</a></iframe><figure><a href="http://eepurl.com/cPPD79"><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*F49VxnybKhjmi-bFQGj4kg.png" /></a></figure><figure><a href="https://www.iotforall.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvZqvtDLMZxtmq7cRtj4pA.png" /></a></figure><figure><a href="https://www.iotforall.com/rss-feeds/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugIM8aESdtjz13As4I2JkQ.png" /></a></figure><p><em>Originally published at </em><a href="https://www.iotforall.com/iot-business-model-monetize-product/"><em>www.iotforall.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ed21acb0314" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iotforall/iot-business-models-for-bringing-in-7ed21acb0314">IoT Business Models for Bringing in $$$</a> was originally published in <a href="https://medium.com/iotforall">IoT For All</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Provide Insights, Not Data]]></title>
            <link>https://medium.com/iotforall/provide-insights-not-data-e6498f0d5b71?source=rss-adec3aa69dfd------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6498f0d5b71</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[Daniel Elizalde]]></dc:creator>
            <pubDate>Fri, 28 Jul 2017 14:08:55 GMT</pubDate>
            <atom:updated>2017-08-02T02:35:10.184Z</atom:updated>
            <content:encoded><![CDATA[<h4>How I discovered the importance of having a data strategy the hard way.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IvMtAPKl0va_SumL9xycmg.jpeg" /></figure><p>IoT products are known for producing large amounts of data. Some people even argue that the reason to deploy IoT products is to produce and collect all this data, that the data in itself is what provides the value. I don’t think so. IoT products need to provide insights.</p><p>In this post, I describe the importance of having a data strategy and share how I discovered this the hard way.</p><h3>What’s Your Data Strategy?</h3><p>At the end of the day, an IoT product is no different than any other product in the mind of the customer. It either delivers value or it doesn’t. It either solves the job it was hired to do or it doesn’t.</p><p>Why am I telling you this? Because one of the biggest challenges companies face when building IoT products is having a data strategy — a plan for how you’re going to derive value from your data.</p><p>A data strategy goes beyond the collection and management of the data. It starts with defining an ultimate goal you want to achieve with your product and then <a href="https://iot-for-all.com/iot-product-managers-guide-iot-technology-stack/">walking the IoT Technology Stack</a> to understand what data you need to collect, store, analyze, and transfer at each layer of the stack. This is one of the key objectives of going through the Data Decision Area in the <a href="https://techproductmanagement.com/iot-decision-framework/">IoT Decision Framework</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/0*MBpsWAqBfx-2CBc6.png" /></figure><h3>The More Data, the Better, Right?</h3><p>Wrong. Let me share a story about the importance of having a clear data strategy.</p><p>Early in my career, I developed a turn-key IoT solution for a semiconductor manufacturing company. My customer, let’s call him Kevin, hired the company I was working for to automate their process for characterizing new hardware chips. Characterization is just a fancy word for putting a computer chip through every possible input you can imagine, and then recording its output to ensure it performs as closely as possible to the mathematical models engineers used to design that chip.</p><p>Configuring every possible input combination by hand is an impossible task. But if you could have a computer do the inputs for you and store all the output data in the Cloud, then you could save a lot of time and improve the overall quality of your product. That’s where we came in.</p><p>Once we installed and provisioned the solution, Kevin and his team were very excited, since for the first time they were able to execute all sorts of input combinations they weren’t able to test before. The project was a big success.</p><p>A few months later, I received a call from Kevin asking for help. “We are drowning in data,” he said, “and we don’t know what to do with it.” The system we developed had a lot of high-speed sensors and actuators, producing many gigabytes of data per second. Yes, per second.</p><p>Running the system for just a few minutes would create so much data that they’d need weeks to make sense of all the new information. They had solved the problem of visibility, but in doing that, they had created another (maybe bigger) problem of having a lot of data they weren’t able to manage, analyze, or process in any meaningful way.</p><h3>Always Lead With a Data Strategy</h3><p>They say hindsight is 20–20. Today it’s clear to me that I should have done a better job at understanding the ultimate goal of the customer, as opposed to just delivering what they asked for in this custom solution.</p><p>Don’t get me wrong, from my company’s perspective the deployment was a success. We delivered on time and within budget, and the customer gladly signed off on their shiny new system. But in reality, we made the problem worse.</p><p>This story is not a one-off. In fact, I see this occurring over and over as I talk to Product people around the world. Companies too often focus on addressing the problem’s symptoms, rather than digging deeper to understand what the customer is really trying to accomplish. More often that not, we put a lot of emphasis on providing just data, not insights.</p><p>I was fortunate that Kevin trusted my company enough to bring us back to help them on a phase 2 of the project, to address the problem of too much data. This time we were careful to dive deeper into the needs of the whole company, not only of his team.</p><p>We quickly learned that they had no expertise manipulating data, they had no data analysts on staff, and they really didn’t have the necessary knowledge to take over the system we developed for them.</p><p>I spent the next few months working with them implementing a data strategy and a data management solution to address these concerns. We dialed down the amount of data they produced and were able to centralize all data (even the data coming from other departments) in a private cloud where we later added a layer of analytics and visualization. Things looked much better after that.</p><p>I’ll never forget that lesson.</p><p>Machines or “things” can produce an enormous amount of data. They never get tired, so they can produce data day and night. Non-stop. Without a clear data strategy and a clear path to providing value with that data, IoT solutions are useless. They are just adding to the noise.</p><h3>The Importance of Industry Knowledge</h3><p>There’s an old joke that goes something like this: A shepherd is looking after his herd when suddenly a young man in a sports car stops by. The young man asks the shepherd, “If I can guess how many sheep you have, can I keep one of them?” The shepherd agrees. The young man starts running calculations using the latest and greatest technology. “You have 280 sheep,” he says.</p><p>The shepherd sighs and tells the young man, “If I guess what your profession is, can I get my sheep back?” The young man agrees. “You are a consultant,” he says. Surprised, the young man asks, “How did you know!” “Well, you are charging me a steep price, you are telling me something I already know, and obviously you know nothing about my business because you are taking away my dog!”</p><p>This story applies to Product Managers as well. It’s not uncommon for PMs to develop products for industries we aren’t that familiar with, and so we end up solving a problem that didn’t need solving or just producing a lot of data and no value.</p><p>Looking back, lack of industry knowledge contributed to the issues we had when building Kevin’s system. It was a new industry for me (and my company). We knew how to build high-performance IoT solutions for other industries, and although the solution space translated very well, the problem space was very different.</p><p>We had spent a good amount of time learning about our customer and their pains, but we didn’t have a frame of reference for the challenges of that industry. The result: a product that was partially valuable, but didn’t solve the problem all the way.</p><p>So what is the moral of our shepherd-consultant story?</p><p>Know your customer’s industry. Product Managers need to understand as much as they can about their customer’s business. In other words, you need to have <a href="https://techproductmanagement.com/what-it-takes-to-be-a-great-product-leader-the-four-pillars/">deep domain knowledge</a>.</p><p>When you become an expert in the challenges that your customer and their industry peers face, you can ask better questions and make better decisions for your product, and in turn, provide more value for your customer.</p><h3>The Bottom Line: Provide Insights</h3><p>Many IoT products today focus on producing data instead of insights. This results in disappointed customers that are not able to capitalize on the value of the solution and are forced to do extra work to extract useful information out of the data.</p><p>As Product Managers, it’s our responsibility to understand our customer’s world, including having a good understanding of the most common challenges of our target industry. Only then will we be able to craft a solid data strategy that solves our customer’s needs.</p><p><em>Originally published at </em><a href="https://iotforall.com/differentiate-iot-product-provide-insights/"><em>iotforall.com</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*R6Vs7D7zKjxMqtm_ZF1pEg.png" /></figure><h3>Want all the latest advances and tech news sent directly to your inbox?</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5e6c65%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F5e6c65%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href">https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href</a></iframe><figure><a href="http://eepurl.com/cPPD79"><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*F49VxnybKhjmi-bFQGj4kg.png" /></a></figure><figure><a href="https://iot-for-all.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvZqvtDLMZxtmq7cRtj4pA.png" /></a></figure><figure><a href="https://iot-for-all.com/rss-feeds/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugIM8aESdtjz13As4I2JkQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6498f0d5b71" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iotforall/provide-insights-not-data-e6498f0d5b71">Provide Insights, Not Data</a> was originally published in <a href="https://medium.com/iotforall">IoT For All</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Should I Use an IoT Platform?]]></title>
            <link>https://medium.com/iotforall/should-i-use-an-iot-platform-791441867c8f?source=rss-adec3aa69dfd------2</link>
            <guid isPermaLink="false">https://medium.com/p/791441867c8f</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[platform]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Daniel Elizalde]]></dc:creator>
            <pubDate>Thu, 20 Jul 2017 18:30:49 GMT</pubDate>
            <atom:updated>2017-08-03T19:20:56.088Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Building your own IoT infrastructure means wasting time and money, and jeopardizes the quality of your product.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cNNVq58Vgnb1q_yAFAP3gQ.jpeg" /></figure><p><em>News flash: If you’re building your own IoT infrastructure, you’re wasting time and money, and jeopardizing the quality of your product.</em></p><p><em>In this post, I discuss how you can reduce cost and boost quality with an IoT platform, how to choose the right platform, and debunk myths about the benefits of building your infrastructure in-house.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/0*F5oZBndHzTVWRFbL.png" /></figure><p>You simply don’t need to build the complete IoT infrastructure yourself. There’s no point reinventing the wheel.</p><p>By using a platform, you’ll save costs because you’ll have more functionality with less engineering effort, sooner. And you can focus your development efforts on what really matters: your core value proposition.</p><p>Think about it. IoT platform vendors have large teams of developers improving features, fixing bugs, and making sure their offering is rock solid. By leveraging their work, the quality and stability of your product will ride the wave of their investment.</p><p>Although this post talks about software and hardware platforms, the build vs. buy decision is a business conversation. Therefore, based on my <a href="http://techproductmanagement.com/iot-decision-framework/">IoT Decision Framework</a>, we are here:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/908/0*IAu3AtODR5lN1ADr.png" /></figure><h3>What is an IoT Platform, Anyway?</h3><p>The goal of any platform is to reduce your development risk, accelerate your product’s time-to-market, and reduce cost. In fact, I recently talked to someone at AWS who said their internal vision is to <em>“take over all the sh*t companies don’t want to deal with.”</em></p><p>There you have it.</p><p>When people talk about IoT platforms, they usually launch into technical jargon like transport protocols, rules engines, data lakes, etc. While all that’s important and should be considered at some point, it doesn’t really make clear how a platform can help you.</p><p>So let’s break down the key tasks that an IoT product needs to perform, and therefore, highlight the functionality that should be covered by a platform. In general, an IoT product needs to:</p><ol><li>Acquire data from the real world (via sensors)</li><li>Process data locally (edge computing)</li><li>Connect to the cloud to send data / receive commands</li><li>Store data in the cloud</li><li>Analyze data in the cloud</li><li>Command the “things” to perform specific tasks based on insights</li><li>Present insights to users</li></ol><p>In addition, there are some “behind-the-scenes” operations you’ll need:</p><ul><li>All operations should be done securely throughout the IoT stack</li><li>You need the ability to identify and manage all of your devices (at scale)</li></ul><p>Based on this simplified description, a good IoT platform should provide the tools and infrastructure to cover as many of these tasks as possible. For example, if you select a platform that’s very strong on analytics, but doesn’t help you in getting data from the devices to the cloud, then you’ll have a big gap.</p><h3>How Do I Select the Right Platform?</h3><p>As of today, there are hundreds of IoT platforms available in the market, with more coming out every day. In fact, according to <a href="https://iot-analytics.com/product/list-of-360-iot-platform-companies/">IoT Analytics, there are over 450platforms out there today</a>, so you’ll need to do your research.</p><p>Choosing the right vendor can be daunting. To get you started, here are 5 key areas to look for:</p><ol><li><strong>Reputable company.</strong> IoT is risky enough as it is. Trusting the core of your product to an unknown company might backfire. Make sure you evaluate their reputation, stability, financials, and track record.</li><li><strong>Large ecosystem.</strong> IoT is so big that there’s no way a single company can dominate it all. Looking for a company with a strong app and partner ecosystem will be a good investment in optionality and expansion. Most of the top IoT platform providers don’t do hardware themselves, but they have a strong partner ecosystem to pull from. That is always a good sign.</li><li><strong>Open APIs.</strong> Extensibility will be key, so make sure you select a provider that gives you programmatic access to as much of their functionality as possible.</li><li><strong>Vertical focus. </strong>Aligning with a vendor that understands your industry is always a plus. Their solution will be designed to handle your type of data, analytics, and even help you comply with industry regulations.</li><li><strong>Strong onboarding</strong>. Adopting a new platform is not a trivial thing. Look for companies that have a strong solutions team (or professional services) that can train your team, help you with the architecture, and handhold you through the proof of concept stage.</li></ol><p>Here are some of the top IoT platforms in the market today (in no particular order). Their functionality is somewhat similar. Some of the main differences have to do with Industrial vs. Commercial focus. As you start your evaluation, you can’t go wrong with any of these:</p><ul><li><a href="https://aws.amazon.com/iot/">Amazon — AWS IoT</a></li><li><a href="https://www.ge.com/digital/predix">GE — Predix</a></li><li><a href="https://www.microsoft.com/en-us/cloud-platform/internet-of-things-azure-iot-suite">Microsoft — Azure IoT</a></li><li><a href="http://www.ibm.com/cloud-computing/bluemix/">IBM — Bluemix</a></li><li><a href="https://cloud.oracle.com/iot">Oracle Cloud IoT</a></li><li><a href="https://cloud.google.com/solutions/iot/">Google Cloud Platform</a></li><li><a href="https://www.artik.io/">Samsung — Artik modules &amp; cloud</a></li></ul><p>The beauty of these platforms is that they already did the infrastructure heavy lifting, which allows you to focus on your core application. These companies have spent hundreds of millions of dollars building their products so you don’t have to.</p><p>Ultimately, you are looking to build a partnership with one of these companies. It’s a complex decision, and you can’t make it alone. It’ll require you to work closely with various groups in your company including Engineering, UX, Data Science, Finance, and more.</p><h3>I Get It. But I’d Rather Build My Own Because…</h3><p>I’ve heard countless arguments about why companies need to build their own &lt;insert technology here&gt;. Too often, companies waste millions of dollars and years of effort reinventing the wheel, instead of pushing their product forward.</p><p>So let’s debunk some of the most common arguments against IoT platforms.</p><h4>1) My Product is Unique</h4><p>IoT platforms are meant to be generic, so most likely you’ll find some gaps vs. your ideal solution. The key here is to assess how big that gap is and figure out ways you could get around it. Is it a must have? Are there other platforms or software vendors that can cover the gap?</p><p>Also ask yourself if that functionality can wait. One of the big advantages of jumping onto a platform is that you piggy-back on their growth. Top companies have hundreds of developers working on enhancements and new functionality.</p><p>The gap you are experiencing might be covered in the next release, not to mention all the new functionality, partners, and tools they’ll continue to provide throughout the years.</p><h4>2) Platforms Are Expensive</h4><p>Yes, platforms cost money. But in the long run, these costs are small compared to what it’ll cost you to build your own.</p><p>Building a functional IoT backbone will take millions of dollars and many man-years of your engineering team. Not to mention QA, UX, Product Managers, etc. On top of all that development cost, you need to add support and maintenance costs. Forever. Instead of creating an asset, you’ve probably created a liability.</p><p>Even if you are able to pull off the enormous technical challenge, in the end, you’ll have something that’s not core, is not differentiated, and is probably 2–5 years behind where the industry is today. As a Product Manager, it’d be very hard to justify that investment.</p><p>Rich Mironov debunks the “do it yourself illusion” <a href="http://www.mironov.com/diy/">in this great post.</a></p><h4>3) Investors Will Give My Company a Lower Valuation</h4><p>Many folks are worried that investors will see less value in their product if they’re leveraging 3rd party components or platforms. Nothing is farther from the truth.</p><p>Investors care about unique value propositions and ROI. How would you explain to them that you spent their money reinventing the wheel? Not a conversation I look forward to.</p><p>Let me put it this way: saying that your product loses value if you build it on a platform is like saying Tesla cars have no value because they don’t make their own tires. Or saying Netflix has no value because they build it on top of AWS. I don’t think so.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/0*dkztLMVM8aeDlw5T.png" /></figure><h3>The Bottom Line</h3><p>Building an IoT product is very complex. By outsourcing non-core areas of your product to a platform, you’ll reduce risk, minimize cost, improve quality, and accelerate time to market.</p><p>Oh, and one last thought. If you aren’t thinking of using an IoT platform, I assure you your competitor is. Don’t be surprised if they beat you to market and are able to provide more value added features faster. Just sayin…</p><p><em>Originally published at </em><a href="https://iotforall.com/should-i-use-an-iot-platform/"><em>iotforall.com</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*R6Vs7D7zKjxMqtm_ZF1pEg.png" /></figure><h3>Want all the latest advances and tech news sent directly to your inbox?</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5e6c65%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F5e6c65%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href">https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href</a></iframe><figure><a href="http://eepurl.com/cPPD79"><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*F49VxnybKhjmi-bFQGj4kg.png" /></a></figure><figure><a href="https://iot-for-all.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvZqvtDLMZxtmq7cRtj4pA.png" /></a></figure><figure><a href="https://iot-for-all.com/rss-feeds/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugIM8aESdtjz13As4I2JkQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=791441867c8f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iotforall/should-i-use-an-iot-platform-791441867c8f">Should I Use an IoT Platform?</a> was originally published in <a href="https://medium.com/iotforall">IoT For All</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why is it so hard to create a good user experience in IoT?]]></title>
            <link>https://medium.com/iotforall/why-is-it-so-hard-to-create-a-good-user-experience-in-iot-293aa2480526?source=rss-adec3aa69dfd------2</link>
            <guid isPermaLink="false">https://medium.com/p/293aa2480526</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[humanity]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[Daniel Elizalde]]></dc:creator>
            <pubDate>Tue, 11 Jul 2017 20:05:37 GMT</pubDate>
            <atom:updated>2017-08-03T19:24:34.649Z</atom:updated>
            <content:encoded><![CDATA[<h4>Product and design teams face a new UX challenge: the IoT revolution.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n_ZX15EbUWckqD6M.jpg" /></figure><p>Creating a good user experience in IoT is hard. There are more layers of technology, more users to please, and more teams to coordinate than ever before. Are you prepared to lead the way as a Product Manager?</p><p>Throughout the years, UX practices have evolved and adapted to the latest technology trends, from the desktop application era, to the web revolution, to the mobile revolution.</p><p>But now, product and design teams face a new UX challenge, one that might be bigger than all the previous ones combined: the IoT revolution.</p><p>As this new era of technology continues to gain momentum and infiltrate all industries, one of the biggest challenges IoT product teams face is how to provide a consistent user experience across the entire IoT Technology Stack.</p><p>So why is creating an IoT experience more complicated than creating a traditional Cloud or mobile experience? The <a href="https://techproductmanagement.com/iot-decision-framework/">IoT Decision Framework</a> shows IoT products simply have more parts to consider.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/897/0*LXqE8cqVLjBG0E8t.png" /></figure><h3>Why Creating a Consistent User Experience in IoT is Hard</h3><p>Most Product Managers entering the IoT space usually have experience managing either hardware or software products. But IoT products include both software and hardware, bringing new challenges that most PMs are not familiar with.</p><p>From a product development perspective, hardware and software are likely to be developed and managed by different teams. But keep in mind that users don’t really care who’s building what. They expect a cohesive experience across every touchpoint of your product, regardless of whether it’s software or hardware.</p><p>Let’s look at a couple of real-world examples to show the complexities of delivering a cohesive IoT experience:</p><h3>Exhibit A: UX Challenges in Consumer IoT Products</h3><p>Think of a smart thermostat. Although this is a relatively simple product, it provides several user experience elements that pure software products don’t have.</p><p>First of all, there’s a physical device. And that device needs to be visually appealing, otherwise your customer won’t be willing to install it on the wall in the middle of their living room. This is a challenge that industrial designers are very familiar with, but if you’re a new IoT PM coming from a software background, this might be new terrain for you.</p><p>Next, the device itself provides a user interface to enable the user to set the temperature, display the time, etc. Right there, you have a second experience that you need to create. The user interface for your device needs to be intuitive and attractive, and it needs to fit in a small space.</p><p>As you work with your team to craft the user experience at the device level, you’ll need to decide whether to have a simple display, physical buttons, LCD screen with a touch interface, etc. Not only does it need to be easy to use and fully functional, but it also needs to be aesthetically pleasing and on brand.</p><p>In addition to the physical user interfaces, connected devices usually have web interfaces that address different use cases. For example, a smart thermostat is likely to have a web dashboard to provide detailed information about usage patterns or energy consumption. And it might have a mobile application to provide summary information and remote control on the go.</p><p>These form factors provide you with different levels of real estate to display information, so it’s important to understand the user’s mental model (what they are looking to accomplish) when interacting with each of these user interfaces.</p><p>All these different experiences need to be consistent with each other. Although the user is interacting with the thermostat through three different user interfaces (the thermostat, desktop, and mobile), your goal is to ensure that she feels like she is interacting with the exact same product, her thermostat, and not three different products.</p><h3>Exhibit B: UX Challenges in Industrial IoT Products</h3><p>Industrial products have even more challenges when it comes to user experience in IoT. Let’s use solar panels as an example. Imagine an array of solar panels installed on the roof of a commercial building. All the panels might be connected to a centralized hub or gateway to aggregate the signals coming from each panel.</p><p>This gateway might not need to be as good looking as the smart thermostat. After all, it will be installed on the roof of a building. But on the other hand, it needs to be rugged and waterproof since it’ll be installed outdoors.</p><p>Other design considerations include how technicians will interact with the gateway. Does it need an LCD display or should it only have a couple of LED lights to show it is working properly? Those are design decisions you’ll need to make.</p><p>Just like the smart thermostat, the product probably has a web dashboard for the facility manager to monitor performance, and it may have a tablet app for technicians to troubleshoot things in the field.</p><p>In addition to these interfaces, the gateway might need to connect to the building management system via a direct cable connection or via an API accessible directly from the gateway.</p><p>Though it might not be obvious, APIs and connectivity points are also user interfaces that you need to develop and craft a good experience for. These connections will be used by developers and system integrators who will form an impression of your product based on the interface you provide.</p><p>For them, it doesn’t matter if your end customer dashboard is very polished. If the interface they’re using isn’t equally polished, they’ll have a bad user experience and will rate your product poorly.</p><p>Let’s recap. In this commercial solar panel product not only do you have multiple software and hardware interfaces, you also have four users to please: the technician, the facility manager, the developer, and the systems integrator.</p><h3>So How Do You Ensure Consistency of Experience Across Your Product?</h3><p>What makes IoT products complicated is that now you have to address usability across the full <a href="https://iot-for-all.com/iot-product-managers-guide-iot-technology-stack/">IoT Technology Stack</a> and likely across multiple users.</p><p>Plus building an IoT product is a big undertaking, and it’s very common to have multiple teams involved throughout the development lifecycle. Most likely you’ll interact with other Product Managers, and there will be different Engineering teams responsible for developing different parts of the IoT Technology Stack. If that’s not enough, you’ll also have input from Sales, Marketing, Customer Success, etc.</p><p>So as a Product Manager, what can you do to address these challenges?</p><p>In a nutshell, you need to be the source of alignment between everybody involved. You need to have a deep understanding of all of your users and be a communication hub between every team within your company.</p><p>BTW, in my online course, <a href="http://courses.techproductmanagement.com/">The IoT Product Manager</a>, I teach a specific method for identifying and prioritizing users and their needs.</p><h3>The Bottom Line</h3><p>It’s our role as Product Managers to ensure all teams are aligned behind the product vision and to make sure everybody understands who your users are, how you are prioritizing features for each of them, and what user experience you want to provide to them. Only after you have this alignment can you start thinking about execution (<a href="https://iot-for-all.com/how-to-build-an-iot-product-roadmap/">IoT roadmaps</a>, backlogs, development, etc).</p><p><em>Originally published at </em><a href="https://iotforall.com/create-good-user-experience-in-iot/"><em>iotforall.com</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*R6Vs7D7zKjxMqtm_ZF1pEg.png" /></figure><h3>Want all the latest advances and tech news sent directly to your inbox?</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5e6c65%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F5e6c65%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href">https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href</a></iframe><figure><a href="http://eepurl.com/cPPD79"><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*F49VxnybKhjmi-bFQGj4kg.png" /></a></figure><figure><a href="https://iot-for-all.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvZqvtDLMZxtmq7cRtj4pA.png" /></a></figure><figure><a href="https://iot-for-all.com/rss-feeds/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugIM8aESdtjz13As4I2JkQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=293aa2480526" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iotforall/why-is-it-so-hard-to-create-a-good-user-experience-in-iot-293aa2480526">Why is it so hard to create a good user experience in IoT?</a> was originally published in <a href="https://medium.com/iotforall">IoT For All</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Make Sense of IoT Hardware]]></title>
            <link>https://medium.com/iotforall/how-to-make-sense-of-iot-hardware-d1921add69e0?source=rss-adec3aa69dfd------2</link>
            <guid isPermaLink="false">https://medium.com/p/d1921add69e0</guid>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[hardware]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Daniel Elizalde]]></dc:creator>
            <pubDate>Fri, 24 Feb 2017 18:27:21 GMT</pubDate>
            <atom:updated>2017-08-05T05:38:13.706Z</atom:updated>
            <content:encoded><![CDATA[<h4>Demystifying IoT hardware for Product Managers</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MqU7ZeoHb0odhANBwbQuNg.jpeg" /></figure><p>Hardware decisions impact your IoT product’s cost, user experience, application capabilities, and more. But only about 20% of IoT Product Managers have experience managing hardware. In this post, I demystify IoT hardware to help you understand how a smart device acquires, processes, and communicates data to the Cloud.</p><p>After surveying hundreds of Product Managers across industries and backgrounds, I’ve found that only about 20% of PMs working in IoT have hardware experience. By contrast, over 76% of them are familiar with managing software products.</p><p>But in IoT, <a href="http://techproductmanagement.com/iot-primer/">hardware and software work together across the IoT Technology Stack</a>. And managing hardware products requires very different skills than managing software. That is one of the reasons why building IoT products can be very daunting for new and even seasoned IoT Product Managers.</p><p>If you’re an IoT PM who comes from a software background, take a minute to arm yourself with the information in this post. You’ll be glad you did next time you talk with Hardware Engineering or are faced with a hardware-related challenge.</p><p>Based on my <a href="https://techproductmanagement.com/iot-decision-framework/">IoT Decision Framework</a>, hardware is part of the Technology Decision Area. Therefore, you are here:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/890/0*VTCVbNarp7lPdtNO.png" /></figure><p><strong>Recommended article:</strong> <a href="https://techproductmanagement.com/iot-decision-framework/">A Product Management Framework for the Internet of Things.</a></p><h3>Why Do I Need to Understand IoT Hardware? Doesn’t Engineering Make Those Decisions?</h3><p>Yes, engineers are responsible for researching, proposing, and executing on hardware choices for the product. But it’s important for the Product Manager to be involved and to guide engineering on the product needs so they can choose the best solution. After all, hardware decisions can impact your product’s cost, user experience, application capabilities, and more.</p><p>The more you understand about how hardware works, its nuances, and its nomenclature, the more empowered you’ll be to have smart conversations with your engineering team.</p><h3>The 4 Building Blocks of IoT Device Hardware</h3><p>With as many IoT applications as there are IoT entrepreneurs, it would be impossible to generalize a hardware architecture. But regardless of the application, all IoT devices share some commonalities or “building blocks”, as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/0*28OVAnmcc9TotI8G.jpg" /></figure><h3>Building Block 1: Thing</h3><p>I define “thing” as the asset that you want to control or monitor.</p><p>In many IoT products, the “thing” is fully integrated into the smart device. For example, think of products like a smart water pump or an autonomous vehicle. These products control and monitor themselves. In this case, your product includes all four building blocks in a single package as shown below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/710/0*050idSZtWn62-SGl.jpg" /></figure><p>But there are many other applications where the “thing” stands alone as a “dumb” device, and a separate product is connected to it to make it a smart device. In this case, your product only includes the three modules in blue below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/0*UecG4O7IrJTdFQyL.jpg" /></figure><p>This is very common in industrial applications where companies have existing assets, and they want to make them “smart” by connecting them to the Cloud. Some examples include wind turbines, jet engines, conveyer belts, etc.</p><p>The reason I point out this difference is to make you aware that there are different business models you could choose from. Your company can decide to build brand new devices that are smart from the very beginning, or you can decide that your value proposition is to provide a way to turn existing things into smart things, opening the door to what’s called “brownfield opportunities”.</p><p>Either one is fine, just keep in mind that this distinction will affect many other decisions you make for your product.</p><p>Most of the examples above are B2B products, but what about B2C products? In the consumer product world, many IoT products only include the three modules in blue above. That’s because the “thing” they are monitoring is often a human or the environment of the home. Think of a FitBit or a Nest thermostat.</p><h3>Building Block 2: Data Acquisition Module</h3><p>The data acquisition module focuses on acquiring physical signals from the “thing” and converting them into digital signals that can be manipulated by a computer.</p><p>This is the hardware component that includes all the sensors acquiring real-world signals such as temperature, motion, light, vibration, etc. The type and number of sensors you need depend on your application.</p><p>The data acquisition module includes more than sensors though. It also includes the necessary hardware to convert the sensor signal into digital information for the computer to use. This includes signal conditioning, analog-to-digital conversion, scaling, and interpretation.</p><p>For the data acquisition module, the important considerations to focus on are:</p><ul><li>What physical signals do I need to measure? (i.e. what type of sensors do I need)</li><li>How many sensors of each type do I need?</li><li>How fast should I measure the real-world signal? (i.e. sample rate)</li><li>How much accuracy do I need in my measurement? (i.e. sensor resolution)</li></ul><p>The answers to these questions will inform the requirements for your data acquisition module, as well as give you an idea of how much data your device will produce.</p><p>In an upcoming post, I’ll detail how sensors work in IoT. Make sure you <a href="http://techproductmanagement.com/newsletter/">subscribe to my newsletter</a> to receive the post in your inbox as soon as it goes live.</p><h3>Building Block 3: Data Processing Module</h3><p>The third building block of the device is the data processing module. This is the “computer” that processes the data, performs local analytics, stores data locally, and performs any other computing operations at the edge.</p><p>You don’t need to be an expert in computer architecture to have a solid conversation with your engineering team about this module. Your role should be to understand the overarching goal of the product and ask the right questions that will guide your team to the right decisions. The two most important considerations to focus on are:</p><ul><li>Processing power (i.e. how much processing will you do at the edge?)</li><li>Amount of local data storage (i.e. hard drive size — how much data will you need to store at the edge?)</li></ul><p>The decisions you and your team make will have a direct correlation with performance, functionality, cost, size of the device, useful life, etc. Let’s discuss each of those questions in more detail.</p><h4>How much processing power do you need?</h4><p>To determine how much processing power your device needs, you should start by understanding all the different tasks that the device needs to perform.</p><p>Items that will impact your decision include:</p><ul><li>How many sensors do you need to read? (More sensors will require more processing power.)</li><li>Do you need to perform real-time control? (This will definitely increase the processing power required.)</li><li>Does your application need to perform analytics at the edge? (This will also increase the processing power required.)</li><li>Do you have enough processing power to support future software upgrades/releases? (Your new and improved software upgrades will likely require more processing power.)</li><li>What are the size constraints of your device? (For example, a Fitbit only has so much space, limiting the computer size and processing power.)</li></ul><h4>How much local storage do you need?</h4><p>The amount of local storage you need depends on your data retention policy. Once you define how much data you need to acquire, how often, and how much you will send to the Cloud, then you can calculate how much local storage you’ll need as temporary storage for doing calculations or to serve as a buffer in case you lose the connection to the Cloud.</p><p>If your product is expected to work offline, you need to define for how long it will operate without a connection, and therefore, how much data you need to be able to store locally. Some applications require no interruptions in the data, either because the Cloud Analytics won’t be able to handle data gaps or because you have a legal agreement with the customer for data continuity.</p><h3>Building Block 4: Communications Module</h3><p>The last building block of your device’s hardware is the communications module. This is the circuitry that enables communications with your Cloud Platform, and with 3rd party systems either locally or in the Cloud.</p><p>This module may include communication ports such as USB, serial (232/485), CAN, or Modbus, to name a few. It may also include the radio technology for wireless communications such as Wi-Fi, LoRA, ZigBee, etc.</p><p>The communications module can be included in the same device as your other modules, or it could be a separate device that is specifically for communications. This approach is often referred to as a “gateway architecture”.</p><p>For example, if you have three sensors in a room that need to send data to the Cloud, you might have those sensors connected to a single gateway in that same room, and the gateway consolidates this data and sends it to the Cloud. That way, you only need one communications module, not three.</p><h3>The Bottom Line</h3><p>As an IoT Product Manager, you don’t need to be an expert in all areas of the IoT Technology Stack. But you do need a solid understanding of the major components and how an end-to-end IoT solution is put together.</p><p>My recommendation is to get as familiar as possible will all layers of the <a href="http://techproductmanagement.com/iot-primer/">IoT Technology Stack</a>. I’ll be covering all the other layers of the stack in future articles. Subscribe to my newsletter below to make sure you don’t miss out on those posts.</p><p>If you’d like to learn more about IoT Product Management, I invite you to <a href="https://techproductmanagement.com/newsletter/">subscribe to TechProductManagement’s newsletter</a>.</p><p><em>Originally published at </em><a href="https://iotforall.com/iot-hardware-introduction-explanation/"><em>iotforall.com</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*R6Vs7D7zKjxMqtm_ZF1pEg.png" /></figure><h3>Want all the latest advances and tech news sent directly to your inbox?</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5e6c65%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F5e6c65%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href">https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href</a></iframe><figure><a href="http://eepurl.com/cPPD79"><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*F49VxnybKhjmi-bFQGj4kg.png" /></a></figure><figure><a href="https://iot-for-all.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvZqvtDLMZxtmq7cRtj4pA.png" /></a></figure><figure><a href="https://iot-for-all.com/rss-feeds/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugIM8aESdtjz13As4I2JkQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d1921add69e0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iotforall/how-to-make-sense-of-iot-hardware-d1921add69e0">How to Make Sense of IoT Hardware</a> was originally published in <a href="https://medium.com/iotforall">IoT For All</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Build an IoT Product Roadmap]]></title>
            <link>https://medium.com/iotforall/how-to-build-an-iot-product-roadmap-9ad0529c0bea?source=rss-adec3aa69dfd------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ad0529c0bea</guid>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Daniel Elizalde]]></dc:creator>
            <pubDate>Wed, 11 Jan 2017 20:10:12 GMT</pubDate>
            <atom:updated>2017-08-06T06:06:48.372Z</atom:updated>
            <content:encoded><![CDATA[<h4>Let’s face it. Building an IoT product roadmap is hard — much harder than building roadmaps for “normal” technology products.</h4><p>That’s because IoT products are complex systems. To create a working solution, <a href="http://techproductmanagement.com/iot-primer/">all layers of the IoT Technology Stack</a> — device hardware, device software, communications, cloud platform, and cloud applications — need to work together. It’s like having to manage five products in one, and your roadmap needs to be the glue that keeps all your stakeholders aligned with your vision.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9OMtb_QmwqknjK4CacOzaQ.jpeg" /></figure><h3>The IoT Roadmap — Your Key to Aligning Stakeholders and Teams</h3><p>An IoT roadmap needs to show the product direction as well as the impact of new features in a way that makes sense for all stakeholders. Your stakeholders might be from Sales, Marketing, the Executive team, Engineering, and more. They all have different needs and different levels of understanding of how the product is put together.</p><p>In fact, IoT introduces additional complexity because even the technical implementation is probably split across multiple groups. Depending on your company’s structure, you might have dedicated teams for hardware vs. software, embedded vs. cloud development, etc. No single team will have a holistic understanding, which makes it even more important for you (and your roadmap) to communicate the full picture.</p><p>Because of this complexity, managing an IoT product is similar to managing a portfolio of products, with the distinction that ALL the products in your portfolio need to work together to form a cohesive solution. Not an easy task.</p><p>The key to creating a solid IoT product roadmap is to balance a high-level view of the end-to-end product with more detailed views at each layer of the IoT Technology Stack. That way, you’ll be able to provide the right level of information for your different stakeholders and ensure nobody loses sight of the big picture.</p><p><strong>Suggested reading:</strong> <a href="http://techproductmanagement.com/iot-primer/">Internet of Things: A Primer for Product Managers</a></p><h3>Building Your High-level IoT Product Roadmap</h3><p>Let’s use an example to illustrate all the moving parts of an IoT product roadmap. Let’s pretend your company builds industrial water pumps.</p><p>After talking to a lot of customers and sales folks, you discover that a major concern for your customers is to keep operations going at all times. They would like to know if a pump is about to fail so they can proactively order parts and schedule service. This would reduce downtime and save them a lot of money. Such “predictive maintenance” is very valuable to your customers, and they are willing to pay a lot for it.</p><p>Researching solutions with engineering, you learn that as a pump ages, it starts to vibrate. The more it vibrates, the closer it is to failing. Therefore, if you were able to monitor pump vibration and perform analytics on that data, you’d be able to predict failures. With this information and some business due diligence, you determine this is a great solution and you are ready to put it in the roadmap for internal buy-in.</p><p>Your high-level roadmap might look something like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0XiCStKVta7Yn275zvxIKg.png" /><figcaption><strong>Example of high-level roadmap</strong></figcaption></figure><p>As you can see, this is no different than the roadmap for a non-IoT product. The challenge here is that it is very difficult for your stakeholders — Executives, Sales, Marketing, and Engineering — to understand what it will take to build this functionality and what the final product looks like. It’s also difficult to understand why release #1 will take 6 months and release #2 and #3 will be shorter.</p><h3>Using Story Mapping to Enhance Your IoT Roadmap</h3><p>For your IoT roadmap to convey the full story, you need to provide another level of detail describing the features of the high-level roadmap across the IoT Technology Stack.</p><p>I’ve found that story mapping is a great way to dive into this next level of detail. I like to combine story mapping with the IoT Technology Stack to show how features align to the various layers of the end-to-end IoT product.</p><p>The result is a visualization that is still higher level than a “product backlog”, but gives enough information for all teams to understand the big picture. This view also empowers teams to understand how the planned functionality relates to the day-to-day work they’ll need to do.</p><p>Here’s how this approach would look for our “smart pump” example. From this view, it is easier to explain the work that needs to get done to support the predictive maintenance functionality. Notice how the names of the high-level features in the previous roadmap became the theme for each of the releases. This helps your team keep an eye on the big picture while still focusing on smaller details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tGk5xvPaZ_HJPQHqz9vANQ.png" /><figcaption><strong>Example of story mapping roadmap</strong></figcaption></figure><p>Notice that not all layers have to be impacted on every single release. In this example, there are no features in the “Communications” layer after release #1. This example assumes that the release #1 features in the “Communications” layer will be able to support the functionality of releases #2 and #3.</p><p>From this visualization, it is easy to see that release #1 is the only one that impacts your device’s hardware. Therefore, it’s easy to explain why release #1 will take longer than other releases.</p><p>You can also see that fewer layers are impacted in releases #2 and #3. The initial release will be the longest because you need to build a lot of infrastructure. Once you build that initial “plumbing”, then you’ll be able to add features on top of it at a much faster pace. You can use this tool to explain that evolution as well.</p><p><strong>Suggested reading:</strong> <a href="http://techproductmanagement.com/iot-decision-framework/">A Product Management Framework for the Internet of Things</a></p><h3>Using The Roadmap to Coordinate Engineering</h3><p>You can also use the story mapping roadmap to coordinate multiple engineering teams across various layers of the IoT Technology Stack. Every team needs to share a unified vision of where the product is going. But at the same time, they need to understand the work that lies ahead for their specific team. This roadmap can help you with both goals.</p><p>As shown below, you can take “vertical slices” to create specific roadmaps for each engineering team across multiple releases. As long as the data format and the interfaces between layers are well defined, this approach will enable each team to work independently and make progress faster.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4m1n1Knw4co6BXuDGF74eg.png" /><figcaption><strong>Example of team-specific roadmap</strong></figcaption></figure><h3>The Bottom Line</h3><p>As a Product Manager, you will always face challenges when communicating the product vision throughout your company. It’s a difficult task, and yet it is probably the most important function of our role. The approach outlined in this post provides you with a very powerful communication tool you can use to clearly express your product ideas and get everybody aligned. The result: increased transparency, which results in better communication, happy teams, and happy customers.</p><p>If you enjoyed this article, you can get more content on IoT Product Management by <a href="http://techproductmanagement.com/newsletter/">joining my newsletter.</a></p><p>PS: I originally wrote this article as a guest post for the <a href="https://www.productplan.com/blog/">ProductPlan Blog</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*R6Vs7D7zKjxMqtm_ZF1pEg.png" /></figure><h3>Want all the latest advances and tech news sent directly to your inbox?</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5e6c65%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F5e6c65%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href">https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href</a></iframe><figure><a href="http://eepurl.com/cPPD79"><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*F49VxnybKhjmi-bFQGj4kg.png" /></a></figure><figure><a href="https://iot-for-all.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvZqvtDLMZxtmq7cRtj4pA.png" /></a></figure><figure><a href="https://iot-for-all.com/rss-feeds/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugIM8aESdtjz13As4I2JkQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ad0529c0bea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iotforall/how-to-build-an-iot-product-roadmap-9ad0529c0bea">How to Build an IoT Product Roadmap</a> was originally published in <a href="https://medium.com/iotforall">IoT For All</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 Ways to Get a Product Management Job when You Lack Industry Experience]]></title>
            <link>https://medium.com/@delizalde/7-ways-to-get-a-product-management-job-when-you-lack-industry-experience-dec3ebf271f8?source=rss-adec3aa69dfd------2</link>
            <guid isPermaLink="false">https://medium.com/p/dec3ebf271f8</guid>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Daniel Elizalde]]></dc:creator>
            <pubDate>Wed, 14 Dec 2016 19:14:32 GMT</pubDate>
            <atom:updated>2018-12-19T02:23:21.361Z</atom:updated>
            <content:encoded><![CDATA[<p>This article was originally posted in <a href="http://danielelizalde.com/">DanielElizalde.com</a></p><p>Many Product Managers still think industry experience is unnecessary to get hired. However, as a hiring manager, I know firsthand that industry experience can make a difference when deciding between final job candidates. Learn why hiring managers DO value industry experience, and how to develop a game plan to gain industry knowledge and position yourself as a strong candidate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*IpoEd68sWrEuM_qs.jpg" /></figure><p>There are a lot of articles making the argument that Product Managers don’t need domain knowledge. By domain knowledge, I mean specific experience in an industry or vertical. For example, experience in eCommerce, Energy, Finance, Healthcare, etc.</p><p>These articles claim that as long as a PM knows how to understand users, prioritize features, create a roadmap, and work with engineering, then they are covered.</p><p>If it is true that Product Managers don’t need any industry experience, why does this topic keep coming up again and again in forums, blogs, podcasts, and meetups?</p><p>Well, it keeps coming up because lots of Product Managers continue to lose job opportunities for candidates with industry experience.</p><p>Now, it is possible to get a PM job without industry experience, but all things being equal, candidates with that experience will always have the upper hand.</p><h4>[tweetherder]All things being equal, PM candidates with industry experience will always have an advantage.[/tweetherder]</h4><p>Don’t believe me? Let’s look at it from the perspective of the hiring manager.</p><h3>Hiring Manager’s Perspective</h3><p>As a hiring manager myself, I do prioritize Product Management experience above industry experience. But as our profession evolves, having strong PM skills is becoming a basic requirement. To stand out, you (ideally) also need technical, business, and domain expertise.</p><p>During the recruiting process, the hiring manager needs to weigh the skills the candidate brings to the table with the effort it will take them to ramp up. And yes, this is where industry experience makes a difference.</p><p>Not having industry experience will make your ramp up a lot slower in many ways. Here are two examples that happen to be at the core of your role as a PM:</p><ul><li><strong>Building credibility with other teams: </strong>Not having industry experience has an impact on how fast you can build credibility with engineering and other subject matter experts across the company.</li><li><strong>Leading product strategy: </strong>Not understanding basic user needs, and not knowing who the main players in the industry are, will slow down your ability to create a competitive product strategy and roadmap.</li></ul><p>In these cases, the hiring manager needs to decide whether industry knowledge can be picked up fast enough. They’ll also decide if the PM organization or company as a whole has the ability (i.e. time, money, inclination) to invest in bringing new employees up to speed in their industry.</p><p>Some companies simply don’t have the time or resources to provide industry training to new employees. They need someone who can hit the ground running <em>today.</em></p><h3>7 Ways to Make Up for a Lack of Industry Experience</h3><p>Does this mean you won’t be able to get a job in a different industry? Not at all! In fact, most of us will switch industries several times throughout our careers.</p><p>The important part is to have a game plan for how to position yourself as a strong candidate. Here are 7 ways you can do it:</p><h3>1) Acknowledge that industry experience is important</h3><p>OK, this might be hard to swallow, but you have to start by acknowledging that industry experience is important and as long as you don’t have it, you’ll be at a disadvantage versus other candidates. That’s just a fact. Once you make peace with this, then you can move on and start working on a plan.</p><p>This is especially important when talking to the hiring manager and subject matter experts in the company you’re interviewing with. Telling these people that industry knowledge is not important is a slap in the face. These people have probably spent years building that knowledge, and they are proud of it. Negating their expertise is not going to go over well.</p><h3>2) Make sure your other skills are rock solid</h3><p>If you don’t have industry experience, the only way you will stand out is if your other skills are extremely solid and they can compensate for your weakness in this area.</p><p>I believe Product Managers should be strong in the <a href="https://danielelizalde.com/what-it-takes-to-be-a-great-product-leader-the-four-pillars/">4 Pillars of Product Leadership</a>. These pillars are:</p><ol><li>Soft skills</li><li>Business acumen</li><li>Technology &amp; UX skills</li><li>Domain knowledge</li></ol><p>The Technology &amp; UX pillar might be a good one to focus on. For example, you might be moving from managing an eCommerce product into a CRM product. Although these are different industries, they both share Cloud as the technology backbone. If you can demonstrate that you are effective at managing all the nuances of a Cloud product, then you’ll be ahead of the game.</p><p>This is also true for <a href="https://danielelizalde.com/iot-primer/">IoT Product Management</a>. If you have IoT business or technical experience, then you should play that up as a strong point in your resume even when changing industries.</p><h3>3) Understand the hiring manager’s pain</h3><p>It is imperative to understand the pain the hiring manager is looking to solve. Why is she hiring for this role right now? What is the first project she’ll need you to tackle? That can give you an idea of the core skill set she needs and is an opportunity to position yourself as the solution since the pain might not be industry specific.</p><h3>4) Understand the team you’ll be working in</h3><p>Heads of Product understand that they need to build a strong team. The team as a whole needs to be well versed in all the pillars of product leadership, but it is expected that each team member will be stronger in some areas and not as strong in others.</p><p>By understanding the current make of their team, you might learn that they already have a PM with strong industry experience, but they have a gap in customer development or interfacing with technical customers. That can be another opportunity to demonstrate how you are the best candidate for the job.</p><h3>5) Position your outsider experience as an asset</h3><p>After working too long in the same industry, product teams can become blind to what’s going in the rest of the technology or product world. The problem you are trying to solve might already have been solved in a different industry and there is no need to reinvent the wheel.</p><p>Your experience in other industries is extremely important, so make sure you highlight how your previous experience can give your new company an edge.</p><h3>6) Show that you’ve done your homework</h3><p>Even if you don’t have hands-on industry experience, you should be able to articulate why you are interested in the company and solving their customers’ problems. You should be familiar with what the state of the industry is, who the key players are, and what some of the basic pains are.</p><p>Read industry news, take courses, attend trade shows, and connect with people in the industry. This will also help YOU understand if you really want to be in that industry.</p><p>I’ll never forget one interview for a role in which I had no industry experience. The hiring manager asked: “What have you done to get familiar with our industry?” The good news is that I was prepared. I had taken a couple of courses online, attended several Meetups and conferences, and had been following the industry news. That was enough for the hiring manager to feel confident that I was serious enough to get the job.</p><h3>7) Have examples of how you ramped up in other companies</h3><p>Hiring managers want to know that you’ll be a self-starter who is willing to invest the time (even outside normal business hours) to get up to speed. Fast. Come to your interview prepared with examples of when you joined new industries and how you got up to speed.</p><p><strong>Note:</strong> Do you want more Product Management career advice? <a href="https://danielelizalde.com/newsletter/">Join my newsletter</a></p><h3>The Bottom Line</h3><p>My goal with this post is to debunk the myth that industry experience is not needed at all. That doesn’t mean you won’t be able to get a job. It just means you’ll be at a disadvantage versus equally skilled candidates who also have industry experience. As long as you have a plan to account for your gaps, you’ll be ahead of most PMs out there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dec3ebf271f8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[People Don’t Buy IoT, They Buy a Solution to a Problem]]></title>
            <link>https://medium.com/iotforall/people-dont-buy-iot-they-buy-a-solution-to-a-problem-9daf87459bed?source=rss-adec3aa69dfd------2</link>
            <guid isPermaLink="false">https://medium.com/p/9daf87459bed</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Daniel Elizalde]]></dc:creator>
            <pubDate>Thu, 27 Oct 2016 01:42:44 GMT</pubDate>
            <atom:updated>2017-08-07T01:48:48.213Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0xfk7tF1o5gKFStvwt0fkQ.jpeg" /><figcaption>Illustration by <a href="https://dribbble.com/igorkozak">Igor Kozak</a></figcaption></figure><p>Too many product teams and entrepreneurs think, “If I connect it, they will come.” The problem is that people don’t buy IoT, they buy a solution to a problem. In this post, I talk about an excellent example of IoT solving a customer problem, and share tips for evaluating if IoT is right for your product.</p><p>The Internet of Things (IoT) continues to be one of the biggest buzzwords around. You hear about it everywhere: from industry publications, tech publications, blogs, and even in the news. Every article I read usually starts by stating that by 2020 (or some year in the near future), we’ll have billions of connected devices.</p><p>And it’s true that more and more IoT products are being launched every day. But unfortunately, most of the products that make the news are not giving IoT a good reputation.</p><p>In fact, IoT has gained the stigma of being “The Internet of Useless Things”.</p><p>Everywhere we turn there seems to be a new “connected this” or “smart that”. Many applications are novel, but not very useful. I can think of many silly examples, and I’m sure you can too.</p><p>So here’s my point: <strong>The fact that we can connect any device to the Internet <em>doesn’t mean we should</em>.</strong> And if we’re not careful, we can fall into the trap of having technology looking for a problem, instead of starting with a problem and looking for the best way to solve it. This is Product Management 101.</p><p>It’s a shame the useless products get most of the airtime, because there are <em>many</em> applications today that are solving important problems — in healthcare, manufacturing, transportation, energy, and more.</p><p>So this is a call to action for all you IoT Product Managers: <strong>Leverage IoT only if it provides more value to your customer or your company.</strong></p><h3>IoT is a Tool, not a Product</h3><p>During the 2016 Mind the Product Conference in San Francisco, Des Traynor, Co-Founder of Intercom, made the point that Product Managers should keep an eye on technology trends, but only adopt them if they enable you to provide a better/cheaper/faster solution for your customer.</p><p>It’s important for Product Leaders to realize IoT is not a silver bullet, or a way to make easy money by jumping on the latest trend. IoT should be considered another tool in our toolbox that helps us provide more value to our customers.</p><blockquote>People don’t buy IoT, they buy a solution to a problem.</blockquote><p>In my <a href="http://techproductmanagement.com/iot-stanford/">Product Management for IoT</a> course at Stanford Continuing Studies, the students go through my <a href="http://techproductmanagement.com/iot-decision-framework/">IoT Decision Framework</a> to analyze the viability of their proposed solution.</p><p>On several occasions, students actually discovered that IoT was not the best solution, and their customer’s needs were better solved by other types of innovation, such as service or supply chain innovation.</p><p>Imagine how much value this analysis adds in the real world, enabling a Product team to pivot before wasting time and money on a solution that won’t provide additional value.</p><h3>Focus on Solving Customer Problems</h3><p>Now let’s take a look at an opposite example. The Brita Infinity Water Pitcher is a great example of a product team using IoT as a tool to solve customers’ needs.</p><p>During the 2016 IoT World Conference, I had the opportunity to hear the Brita PM explain the evolution of this product.</p><p>Brita knew that the main barrier to using their filtered water pitchers is running out of filters. To solve this problem, Brita went through several product iterations to alert customers that they would need to buy a new filter soon.</p><p>First, they added stickers to reminder customer what month they would need to change the filter, but that didn’t work.</p><p>Then they added a chip that measures the amount of water you pour and blinks when it’s time to order new filters. But that didn’t work either.</p><p>Brita then realized the problem was not reminding customers to buy filters. The problem was that people had to go out of their way to actually buy the filters. It was not convenient, or it was often forgotten on shopping trips, and therefore it never got done.</p><p>So they decided to create a pitcher that connects to Amazon and automatically orders filters when needed. The filters arrive just in time to the customer’s house, with no effort by the customer, solving the problem once and for all.</p><p>You see, Brita never set out to become an IoT company. They didn’t sit in their lab with IoT components trying to figure out what to build. Instead, they realized that IoT was a good tool to solve their user’s problem. Remember, people don’t buy IoT, they buy a solution to a problem.</p><h3>The Bottom Line</h3><p>What does this mean for us Product Leaders? Ultimately, our role as Product Leaders (IoT or not) is to deliver value to our customers and our companies. Our goal is to create products that solve a pain big enough that people are willing to pay for it.</p><p>So start by understanding your customer’s needs and then choose the best tool for the job. It might be IoT and it might not. And figuring that out early on will save you a lot of time and money.</p><p>I invite you to use my <a href="http://techproductmanagement.com/iot-decision-framework/">IoT Decision Framework</a> to evaluate if IoT makes the most sense for your product!</p><p><em>(This article was originally published on my blog TechProductManagement.com)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*R6Vs7D7zKjxMqtm_ZF1pEg.png" /></figure><h3>Want all the latest advances and tech news sent directly to your inbox?</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5e6c65%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F5e6c65%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href">https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href</a></iframe><figure><a href="http://eepurl.com/cPPD79"><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*F49VxnybKhjmi-bFQGj4kg.png" /></a></figure><figure><a href="https://iot-for-all.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvZqvtDLMZxtmq7cRtj4pA.png" /></a></figure><figure><a href="https://iot-for-all.com/rss-feeds/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugIM8aESdtjz13As4I2JkQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9daf87459bed" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iotforall/people-dont-buy-iot-they-buy-a-solution-to-a-problem-9daf87459bed">People Don’t Buy IoT, They Buy a Solution to a Problem</a> was originally published in <a href="https://medium.com/iotforall">IoT For All</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Protect Your IoT Product from Hackers]]></title>
            <link>https://medium.com/iotforall/how-to-protect-your-iot-product-from-hackers-ee343d7a3d14?source=rss-adec3aa69dfd------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee343d7a3d14</guid>
            <category><![CDATA[education]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Daniel Elizalde]]></dc:creator>
            <pubDate>Sat, 22 Oct 2016 02:29:25 GMT</pubDate>
            <atom:updated>2017-08-07T01:51:05.554Z</atom:updated>
            <content:encoded><![CDATA[<h4>IoT security is tough and risky. A security breach can put human lives at risk, because hackers can get control of real-world objects. To make things worse, IoT products give hackers a new attack point: the physical device. How can you ensure your IoT product is protected across all layers of the stack?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*z30VMK9r02pn3Z_Ezwv0Mg.png" /><figcaption>by <a href="https://dribbble.com/mitchellfox">Mitchell Fox</a> for <a href="https://dribbble.com/shapeshift">Shapeshift</a></figcaption></figure><p>Imagine this. You are drinking your Sunday morning coffee when you see in the news that hackers took control of a connected device. As the reporter tells the story and recounts the damages, you realize they are talking about <em>your</em> product! Hackers exploited a security hole you didn’t know you have. Things are not looking good for you or your product!</p><p>The reason I put you in the center of this scenario is to help you realize that thinking, “It’ll never happen to me,” can get you in trouble.</p><p>Think about it: before IoT, a cyber attack would focus on denial of service, millions of dollars lost in sales, identity theft, stolen credit card or social security numbers, etc.<br>But since IoT provides access to real-world objects, then an attack can cause real-world harm to people, and even result in loss of life.</p><p>Consider these scenarios. What if hackers take control of:</p><ul><li>An elevator at a skyscraper, trapping all passengers</li><li>Self-driving cars — <a href="https://www.wired.com/2015/07/hackers-remotely-kill-jeep-highway/">here’s a very scary experiment of hacking a car in motion</a></li><li>The controller of an aircraft turbine, forcing it to malfunction</li><li>A robotic arm at a factory, instructing it to hit everything around it</li><li>The locks of all the doors in a smart home, making it vulnerable to intruders</li><li>Medical equipment at a hospital, harming the people connected to them</li></ul><blockquote>An IoT security breach can put human lives at risk.</blockquote><p>This is why security must be top of mind. Attacks are very real, and we need to stay one step ahead. Instead of being an afterthought, security should be embedded in the way you build IoT products.</p><p>But as a Product Manager, you are probably not a security expert. So where do you start tackling such a big topic?</p><h3>Evaluate Security at Each Layer of the IoT Stack</h3><p>The term “security” is a big nebulous thing, so it’s hard to know where to start. That’s why I’ve included security as a Decision Area in my IoT Decision Framework. By evaluating security at each layer of the IoT stack, you’ll have a more focused view and will be able to plan an actionable security roadmap.</p><p><strong>Related post: </strong><a href="http://techproductmanagement.com/iot-decision-framework/">A Product Management framework for building IoT products</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rAona1Voota80j_B.png" /></figure><p>Based on the IoT Technology Stack, the two key security vectors you need to protect are:</p><ol><li>Physical tampering at the devices layer</li><li>Cybersecurity across the other four layers (embedded software, communications, cloud platform, and applications)</li></ol><h3>1. Protect Against Physical Tampering</h3><p>With IoT, we are installing millions of devices within hand’s reach, which opens a new opportunity for hackers to tamper with the device and get control of it.</p><p>Here’s a real-world example: A hospital invested millions of dollars in cybersecurity to prevent unauthorized access to their network. To their surprise, not long after the security revamp was completed, they found a Trojan horse in their network. The head of cybersecurity was appalled and couldn’t figure out where the attack came from since all the possible cyber attack points were protected. Servers were patched, passwords were enforced, firewalls were in place, you name it.</p><p>So how did the attackers get into the hospital’s network?</p><p>Here’s the kicker. One day, an unsuspecting nurse decided to charge her Android phone using one of those USB ports. The phone had a Trojan horse that found its way into the hospital network. Oops.</p><p>Every time I go out, I’m amazed by the number of easily accessible ports (USB, SD Cards, Ethernet, etc.) that you find all over the place, in hospitals, airports, retail businesses, and more. It’s scary when you start paying attention.</p><p><strong>Physical tampering can be done a lot of different ways. It includes anything from connecting to exposed ports, to interrupting the device’s power, device theft, removing parts, etc.</strong></p><p>As a Product Manager, you’ll need to come up with your own analysis of how someone could tamper with your device. Start by thinking:</p><ul><li>What would happen if somebody gets physical access to my device?</li><li>What type of damage could they do?</li><li>Would they be able to use that as a backdoor into my system or my customer’s network?</li></ul><p>Then think about how you can prevent those attacks. Here are some concrete examples:</p><ul><li>Ensure your product has no exposed ports or connectors.</li><li>Implement locks or other ways to ensure that only authorized people can get access to your product.</li><li>As much as possible, plan for your product to be installed outside normal reach (for example, in a secure room or on a tall ceiling).</li></ul><h3>2. Protect Against Cybersecurity Attacks</h3><p>Standard cybersecurity practices apply to all the remaining layers of the IoT stack: from embedded software all the way to applications. As Product Manager, your role is to make sure security is consistent across the full stack, since different layers of the stack are often developed by different engineering teams.</p><p>Cybersecurity has many considerations, ranging from encryption to identity management, authentication, authorization, etc. My advice is to walk the <a href="http://techproductmanagement.com/iot-primer/">IoT Technology Stack</a> with your team and evaluate what the risks and vulnerabilities are at each layer of the stack.</p><p>Then outline the steps you need to take to protect each layer of the stack. The result could look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oOKAVL3FqS3PCvvi5W10Gw.png" /></figure><h3>The Bottom Line</h3><p>As an IoT Product Manager, your goal is not to be the security subject matter expert. Instead, your goal is to ensure security is accounted for at each layer of the IoT stack by tackling physical tampering and cybersecurity vulnerabilities.</p><p>By using the <a href="http://techproductmanagement.com/iot-decision-framework/">IoT Decision Framework</a> to identify areas of risk, you’ll be able to identify gaps and create a strategy to secure your product.</p><p>Also remember that security is not a one-time thing. Hackers are always looking for new ways to exploit vulnerabilities and cause harm, so security needs to become a standard part of building and managing your product.</p><p>If you enjoyed this post, I’d really appreciate if you share it with your network or you can get more like this by <a href="http://techproductmanagement.com/newsletter/">subscribing to my newsletter.</a></p><p><em>(This article was originally published on my blog TechProductManagement.com)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*R6Vs7D7zKjxMqtm_ZF1pEg.png" /></figure><h3>Want all the latest advances and tech news sent directly to your inbox?</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5e6c65%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F5e6c65%2F&amp;image=https%3A%2F%2Fupscri.be%2Fmedia%2Fform.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href">https://medium.com/media/39ce2a0119753a28e90145cbca6d2ed5/href</a></iframe><figure><a href="http://eepurl.com/cPPD79"><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*F49VxnybKhjmi-bFQGj4kg.png" /></a></figure><figure><a href="https://iot-for-all.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvZqvtDLMZxtmq7cRtj4pA.png" /></a></figure><figure><a href="https://iot-for-all.com/rss-feeds/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ugIM8aESdtjz13As4I2JkQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee343d7a3d14" width="1" height="1" alt=""><hr><p><a href="https://medium.com/iotforall/how-to-protect-your-iot-product-from-hackers-ee343d7a3d14">How to Protect Your IoT Product from Hackers</a> was originally published in <a href="https://medium.com/iotforall">IoT For All</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>