<?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 Bill Brown on Medium]]></title>
        <description><![CDATA[Stories by Bill Brown on Medium]]></description>
        <link>https://medium.com/@billbrown_41835?source=rss-8de00d4c26de------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RO5DzDAKomioTmWOozqxKg.png</url>
            <title>Stories by Bill Brown on Medium</title>
            <link>https://medium.com/@billbrown_41835?source=rss-8de00d4c26de------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 03:53:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@billbrown_41835/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 IoT projects fail]]></title>
            <link>https://medium.com/@billbrown_41835/why-iot-projects-fail-99ae50d21556?source=rss-8de00d4c26de------2</link>
            <guid isPermaLink="false">https://medium.com/p/99ae50d21556</guid>
            <category><![CDATA[i̇ot]]></category>
            <category><![CDATA[iot-app-development]]></category>
            <category><![CDATA[iota]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[iot-platform]]></category>
            <dc:creator><![CDATA[Bill Brown]]></dc:creator>
            <pubDate>Wed, 31 Jan 2024 00:51:31 GMT</pubDate>
            <atom:updated>2024-02-14T11:17:52.495Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LxZhc2Kg8a7dPLzGcBpfVQ.png" /></figure><p>Over the last ten years, I’ve waded knee-deep into a sea of IoT banter, and here’s the splashy takeaway: Folks are busy juggling flaming torches, only to realize they’ve been holding the matches upside down. Organizations and teams are so caught up dotting the ‘i’s in ‘IoT’ that they’re forgetting to cross the ‘t’s in ‘strategy’. It’s like throwing a party and spending all your time in the kitchen — sure, the hors d’oeuvres are important, but if you don’t mingle, you’ll miss the magic. Let’s not snack on distractions; it’s time to feast on what truly sizzles.</p><p>You have probably heard many explanations for why an IoT project/program failed to meet expectations, but none of them in my opinion are accurate and this post is going to share what I find to be the root cause of failed IoT efforts and how to avoid them. To summarize, in my opinion, organizations who are unsuccessful in implementing IoT solutions often overlook the complexity, security, expectations, and necessary expertise required to build an IoT platform.</p><p>Let me see if I can explain. If your company manufactures a digital temperature sensor for your barbecue grill, and they want to connect it to the internet for monitoring on a mobile device, they probably have the expertise necessary to add a wifi module and potentially write the firmware enabling the device to connect to a cloud. But there are so many questions that need to be answered before you can get that far, such as and not limited to;</p><ul><li>which cloud</li><li>which connectivity protocols should be will be use. Wifi, BLE, LoraWan, etc…</li><li>how will you secure the device and prevent unauthorized access</li><li>which software protocol will is your best option for sending | receiving data</li><li>how will devices ensure reliable connectivity</li><li>how will the device be installed and provisioned</li><li>how will firmware upgrades be handled</li><li>how will you measure success?</li></ul><p>The list above is just a subset of questions that need to be asked and only from the device point of view. Arguably, the most significant oversight organizations encounter is underestimating the intricacies of an End to End IoT Solution. The challenges organizations grapple with encompass foundational aspects, from constructing comprehensive business, operational, and monetization strategies to formulating clear pricing plans. This underestimation often results in ambiguous goals, misaligned cost structures, and ultimately unfulfilled stakeholder expectations and desires. Moreover, it’s essential to note that this isn’t solely a challenge for business leaders. Technology teams, too, occasionally underestimate system complexities. It’s vital to have skilled professionals with the right expertise to address the myriad aspects like performance, stability, maintainability, observability, deployment, scalability, data strategy, and the overall cost of both technology and team to craft the solution.</p><p>Navigating the technical intricacies is essential for successful IoT deployments. Each technology not only demands a software developer but one who is deeply familiar with that specific technology. As I can’t speak to each technological components that makes up an IoT platform in this document/post, I can pick one to use as an example. Observability stands as a cornerstone for any contemporary micro-service solution. However, in many cases it is not architected as part of the overall solution but an after thought driven by identifying defects and performance challenges encountered during the development cycle. Its costs can surpass the expenses of the primary IoT ecosystem which is core to your operations and software solutions. Overlooking comprehensive observability can result in limited feedback and challenges in pinpointing bottlenecks or determining the root cause of outages or service degradation. While there’s an array of both open-source and commercial observability tools available, it’s pivotal to ensure your engineering team can effectively and economically harness these tools. Aspects like architectural methodologies, deployment tactics, data models, messaging, and streaming solutions, and so much more, all mandate specialized expertise for optimal outcomes.</p><p>While writing this, I’m acutely aware of those future readers who may prematurely conclude that expertise in all necessary areas would be financially untenable. To those readers, I assert: without such expertise, your solution risks malfunctioning, failing to scale, lacking support, and ultimately joining the ranks of unsuccessful IoT projects.</p><p>Fortunately, there is a viable model. Should your resources be limited, avoid attempting to construct your own platform. Instead, prioritize identifying the specific use cases and requirements your IoT solution demands, then seek a partnership with a provider that offers an established, scalable platform with embedded IoT services.</p><p>It’s crucial to recognize that services like Amazon’s AWS IoT Core and Microsoft’s Azure IoT should not be mistaken for comprehensive IoT platforms. These are component services, requiring skilled developers to assemble them effectively, cognizant of the inherent challenges.</p><p>What I’m advocating for is a robust, ready-to-use IoT platform that delivers a comprehensive solution — essentially, IoT out-of-the-box — yet allows for the integration of your unique business logic. In essence, your focus shouldn’t be on the underlying infrastructure, but rather on addressing your business needs and relying on a trusted partner to supply a solid foundational platform to build upon.</p><p>Imagine an IoT project is like a rock band — it might seem like all you need is a few gadgets (instruments) and some tech wizards (musicians) to jam out a killer product. But without a maestro IoT Leader (think of a leather-jacket-clad, tech-savvy version of Mozart) who’s rocked this stage before, faced the tech equivalent of stage-divers and broken strings, and who can turn your wish-list into a chart-topping hit of requirements, well, you’re just going to end up with a cacophony of disconnected devices.</p><p>With this rockstar leader conducting your digital symphony, not only will your IoT Ensemble hit every note for your stakeholders and keep the budget from blowing up like an amp in a power ballad, but it’ll also be as secure as the VIP backstage area — you know, the kind that’s been backstage-pass-proofed. Plus, as your fan base grows, so too will your setup, with a tech crew (support team) that’s as dedicated as roadies during a world tour. In essence, you’re not just getting a one-hit-wonder gadget; you’re getting a whole album of world-class solutions, all for the price of an indie band’s concert ticket.</p><p>If you’ve got an IoT project and your just looking to talk, I’m ready to listen, understand and offer recommendations.</p><p>Bill Brown</p><p>CEO/CTO Ingress Software</p><p><a href="/service/mailto:Bill@ingressSoftware.com">Bill@ingressSoftware.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99ae50d21556" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>