<?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 Rocket Wagon on Medium]]></title>
        <description><![CDATA[Stories by Rocket Wagon on Medium]]></description>
        <link>https://medium.com/@rocketwagon?source=rss-c20cdef0c4a1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*P0CRUAMUOqY-ujazdTXSHg.gif</url>
            <title>Stories by Rocket Wagon on Medium</title>
            <link>https://medium.com/@rocketwagon?source=rss-c20cdef0c4a1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:19:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rocketwagon/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[Principles of Innovative Product Success: Part 1]]></title>
            <link>https://medium.com/@rocketwagon/principles-of-innovative-product-success-part-1-46237fae21e1?source=rss-c20cdef0c4a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/46237fae21e1</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[innovation-strategy]]></category>
            <category><![CDATA[okr]]></category>
            <dc:creator><![CDATA[Rocket Wagon]]></dc:creator>
            <pubDate>Fri, 01 Nov 2019 15:31:30 GMT</pubDate>
            <atom:updated>2019-11-01T19:09:00.945Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://www.linkedin.com/in/russelltaff/">Russ Taff</a>, Sr. Product Manager, <a href="https://rw.co/">Rocket Wagon</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1qC3flSz_kK-yriTD8F-VQ@2x.jpeg" /></figure><p><strong><em>COMPLEX PROBLEMS REQUIRE CONTINUOUS EXPLORATION</em></strong></p><p><em>At Rocket Wagon, we work on complex problems that span from personal healthcare to education, sustainable energy to retail and much more. We design and build digital and connected products intended to disrupt industries and move markets by taking complicated constraints and turning them into empowering opportunities.</em></p><p><em>To consistently deliver successful innovative products for our clients, we have built a scalable product practice that involves the entire company and always starts with one word: why?</em></p><h3>Start with Why</h3><h4>Avoid the feature factory mentality with a simple inspiring question.</h4><p>We believe that the first step in building best practices is to avoid reinventing the wheel; it’s far more effective to stand on the shoulders of giants. To this end, we try to approach every challenge with Simon Sinek’s resounding bit of simplicity: <a href="https://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action?language=en"><em>Start With Why</em></a>. For our team, this is the practice of uncovering, understanding or reminding ourselves why we are working on something. The concepts of <em>Start With Why</em> applies daily to our internal workstreams and methods, but in this post we’ll discuss how we enable and encourage our clients to <strong>find their why</strong> and build around it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/510/0*n78WiZIuGg-fTjLn.png" /><figcaption>From ‘<a href="https://gumroad.com/l/GoldenCircle">Share the Golden Circle’</a> by Simon Sinek</figcaption></figure><p>When our clients propose a new problem set, we always start with the same question. The goal of asking “Why?” is to inspire our clients to change or build with purpose. This “purpose” should <em>not</em> be to release a product or feature. Instead, the “purpose” should be to deliver meaningful ROI and inspire our users to loyalty.</p><blockquote><em>Note: We can often determine what is </em>meaningful<em> by examining our team or business OKRs. We’ll address OKRs in a little bit.</em></blockquote><p>One core mission for our Product Managers is to maintain stakeholder focus on <strong>outcomes over outputs</strong>. If we release a slew of features on time that return very little — or even worse, are not measurable — they are far less valuable than a single release that can be measured accurately and further optimized.</p><p>If we understand <em>why</em> we are building a thing for our users, then we can determine <em>what</em> we want to build and subsequently <em>how</em> we will go about building and measuring that thing. In other words, we can only know what it is we want to measure when we can clearly define why we are measuring it at all.</p><blockquote>“Teams today are all too often feature factories, with little regard for whether or not the features actually solve the underlying business problems. Progress is measured by output and not outcome.”</blockquote><blockquote><em>– </em><a href="https://svpg.com/when-performance-is-measured-by-results/"><em>Marty Cagan, SVPG</em></a></blockquote><p>This feels obvious, right? In most cases, “obvious” is not a universal truth. In the standard Product (and consulting) mechanism, stakeholders vying for visibility oftentimes become emotionally attached to their product or feature deliverable. They will tie their success to the <em>delivery</em> of a product that is reasonably within budget and on time. Anything else will look like varying shades of failure, and the user reaction or adoption is relegated to secondary importance.</p><p>To address this, we keep our stakeholders inspired by the “Why” at all times. By inspiring others we establish a following. Whether they’re clients, employees or users, excited followers are the most loyal. Backed by loyalty and a shared understanding, we have the capacity to deliver effective change.</p><p>To summarize, “Why” helps us with three key goals:</p><ol><li>Understand the value we are working to deliver for our users</li><li>Determine if we actually delivered that value</li><li>Motivate, captivate and inspire our stakeholders</li></ol><p>Once we have helped our teams establish the <strong>why</strong>, it’s critical that we build an actionable framework around it. This is where the OKRs come in.</p><h3>Stay Connected with OKRs</h3><h4>Objectives and Key Results shouldn’t be scary — they should inspire us to shoot for the stars.</h4><blockquote><strong>BACKGROUND</strong></blockquote><blockquote><em>If you’re unfamiliar with OKRs, take a few minutes to read </em><a href="https://medium.com/startup-tools/okrs-5afdc298bc28"><em>this article</em></a><em> explaining the basics of how they work.</em></blockquote><p>Let’s face facts: OKRs can be pretty daunting. By nature, they should be nearly impossible to hit 100% because they are intended to be <em>aspirational</em>. For example, if I want to decrease user churn on my mobile app, I might set an Objective of “Reduce Churn 85% by the start of next quarter”. This seems borderline unreasonable, as there’s almost no way I can affect such a massive change in a key metric in this short a period.</p><p>[Note: A key here is being <em>quantitative, </em>as <em>“..,</em><a href="https://medium.com/startup-tools/okrs-5afdc298bc28"><em>qualitative goals tend to under-represent our capabilities because the solution tends to be the lowest common denominator”</em></a><em>.]</em></p><p>A truly unattainable goal may seem like a counter-intuitive way to track success of your product — especially when working with stakeholders. We don’t believe that to be true. In fact, we believe that they actually inspire our stakeholders by <em>reminding them that success is an iterative process</em>. As a result, the OKRs we build always ladder up to our “Why”, with room to measure, ideate and optimize for success.</p><p>Let’s take a look at our initial example of “Reduce churn 85% by the start of next quarter”. Here’s how we might deliver this OKR to the client:</p><ul><li><strong>Objective: </strong>Reduce Churn 85% by the end of next quarter</li><li><strong>Key Result: </strong>Maintain 10% reduction in churn week-over-week as seen in Google Analytics.</li><li><strong>Key Result: </strong>Contact and record a statistically significant percentage of all churned users each month to determine the top reasons for leaving.</li><li><strong>Key Result: </strong>Deliver one additional loyalty-based feature that is adopted by 25% of users in the first week.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*GUuUzfQG921egZ4w.png" /></figure><p><strong>Why</strong>: Our user count is not growing as quickly as it should be given the amount of investment we’ve added on the acquisition side of the business. This represents a potential threat to revenue based ROI. We need to supplement this investment with a retention effort that will help stem the losses and hopefully provide some important insights into how we can continue to build a valuable product for our users.</p><p><strong>What: </strong>A program designed to understand user churn that helps define the business and user requirements for future feature development. As we see the highest retention with our loyalty program users, let’s continue to invest there to see if an additional feature will be attractive to potential loyalty users.</p><p><strong>How: </strong>Contact churned users by email, offer them an incentive for filling out a survey related to their leaving the app. Employ statistically sound methodology for examining the data. Further investigation is needed for the loyalty feature. **</p><blockquote>**<strong>CAVEAT</strong></blockquote><blockquote>There does not (and should not) be a <em>solution</em> that is pulled from OKRs; that is the job of the design and development team to determine.</blockquote><p>It’s critically important that there is a conversation between the Product Manager and our client stakeholders regarding OKRs, before the Product Development Cycle kicks off. It is the job of the Product Manager to ensure that the the OKR accurately represents the <em>business</em> goals, and that everybody involved agrees with the aspirational goal and roadmap to achieve it.</p><p>In any event, you’ll need a meeting whereby you can establish the why and discuss the OKRs. Product governance committees are a great way to do this.</p><h3>Product Governance Committee</h3><h4>Keep your key stakeholders connected to the core vision.</h4><p>At the start of every quarter, our Product Managers interface with our client’s Executive team to build a prioritized roadmap for the upcoming 90 days. This “Steering Committee” serves as an assessment of the shared <em>Why</em> alignment, as well as a discussion about the company-wide OKRs.</p><p>Our team prepares for the Steering Committee meeting by collecting a high-level assessment of the top Backlog features or Technical Debt from the Solutions Architect or Team Tech Leads. We also make every effort to provide insights into the predicted outcomes and market impact based on a number of different metrics. Coming in to the Steering Committee meeting with this perspective is critical in helping the Executive team to understand how trade-offs will impact their outcomes. All of these decisions will inform the ongoing prioritization at a micro-level between the PM and the daily stakeholders, or the “Working Committee”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*PaeQ9sFNbvGKfnkh.png" /></figure><p>Every two weeks, the Product Manager will meet with the Working Committee team to discuss this ongoing prioritization. This maintains the fidelity of an iterative design + development process by offering the opportunity for feedback and optimization. We make sure to always maintain a perspective on the “Why” and ensure all parties are continually aligned in Working Committees. During and after releases, we discuss what outcomes we’re tracking, and discuss any available stats that will help inform our ongoing exploration.</p><h3>Ongoing Exploration</h3><p>In our next post, we’ll explore how we take a) the “<em>why”</em>, b) the <em>OKRs,</em> and c) the insights gained from outcomes to create a best-in-class, modern development cycle.</p><p><em>Original posted on </em><a href="https://rw.co/our-thinking/principles-of-innovative-product-success-part-1/"><em>rw.co/our-thinking</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46237fae21e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bring Data to the Center to Unlock Innovation]]></title>
            <link>https://medium.com/@rocketwagon/bring-data-to-the-center-to-unlock-innovation-b5bcaddb23a3?source=rss-c20cdef0c4a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5bcaddb23a3</guid>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[big-data]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[interoperability]]></category>
            <dc:creator><![CDATA[Rocket Wagon]]></dc:creator>
            <pubDate>Fri, 01 Nov 2019 15:21:24 GMT</pubDate>
            <atom:updated>2019-11-01T15:22:16.017Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GTvonY7qvv7NH2Tl.jpg" /></figure><p><strong>The future of business will be fueled by data — driving nearly all decisions in real-time. Today’s technology juggernauts have achieved their success by letting data flow freely within their organization. It’s time you put data at the center of your organization to unlock its full innovation potential.</strong></p><h3>Data Fuels Connected Value</h3><p>According to BCG, <a href="https://media-publications.bcg.com/MIC/BCG-The-Most-Innovative-Companies-2016-Jan-2017.pdf">80%</a> of the most innovative companies utilize data to drive advantages in their organization and industry. Companies like Philips, Nike and Google continue to invest in their data strategies, letting data flow freely throughout their organization to improve their product offerings and to reap rewards in terms of customer insights, building new capabilities, and business model innovation. However, most companies continue to be application-centric when developing new products or service offerings, sticking to a specific use case in which each application has its own database and is responsible for collecting and storing the data it needs.</p><p>Putting data at the center means that data is the primary driver of value in your products, experiences, marketing tactics, operations — your entire company. Data and the insights generated from it is often more valuable than a company’s core product or applications alone, furthermore, data-centered strategies can create significantly higher gross margins and revenue efficiency.</p><p><strong><em>Fully unlocking the value of data often requires rethinking your overall offerings and business model with data and the ability to leverage it as a core advantage.</em></strong></p><p>A great example of data being the primary driver from the beginning and starting with the question of “How and why should we leverage the data we produce?” is <a href="https://www.propellerhealth.com/">Propeller Health</a>. They have reinvented how over 80,000 people manage their chronic respiratory illnesses by embedding a sensor in inhalers to collect real-time data on when and how often people use their medication. By integrating usage data with external data like weather and air quality, Propeller is able to provide a real-time, personalized treatment plan. Many people using Propeller have seen fewer symptoms, flare ups, and unplanned asthma attacks after one month — leaving the potential to save billions in health care costs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/0*84Th1MHx098Q8oOF.jpg" /><figcaption>Source: <a href="https://www.propellerhealth.com/">Propeller Health</a></figcaption></figure><p><strong>FACT</strong></p><blockquote>The longest-tenured companies on BCG’s most innovative companies list use platforms to gain access to different capabilities and sources of data, which they then use to build new business models or develop new products and services. (<a href="https://www.google.com/url?q=https://www.bcg.com/en-us/publications/2019/most-innovative-companies-collaborative-platforms-ecosystems-changing-nnovation.aspx&amp;sa=D&amp;ust=1569869731205000&amp;usg=AFQjCNFN6DL1apaQ6SdgKessPKTKsMRcXw">Source</a>)</blockquote><h3>Exponential Growth of Data is Disrupting All Industries</h3><p>To most, the field of data analytics is not new, but it’s becoming more important than ever to understand as part of your organization’s overall strategy. From applications and internet connected services, to internal systems and employees, data is being generated in extraordinary quantities. The issue is that many organizations face is that they are unable to fully make sense of this data fast enough before it loses its value. Data is in-fact perishable. Its value is time-sensitive and has a limited shelf life.</p><p>According to IDC, every person online will create 1.7 megabytes of new data every second by 2020. Furthermore, the world overall uses <a href="https://www.adweek.com/digital/10-takeaways-from-domos-7th-annual-data-never-sleeps-infographic/">4,416,720 gigabytes of internet data per minute</a>. At this rate, the concept of ‘perishable data’ is more relevant than ever. Businesses need to prepare themselves in order to translate captured data into actionable insights as fast as they can.</p><p>As a brand, you’re probably swimming in an ocean of customer data, but are you a data-centric company, or are you actually just a company that has a lot of data? While every department knows that data is critical to the business, few have plans in place that make the most of it.</p><p>A great example of a brand pivoting to better utilize their data came in 2008 when Nike decided to shift to a data-driven marketing strategy called “<a href="https://fortune.com/2015/11/12/nike-ceo-mark-parker/">category offense</a>” to better segment their customers. Rather than segment their audience by geography, they started segmenting the athletes they serve by the sports they play. The thinking behind this is that soccer players have more in common with each other than people who simply live near one another. As a result of transitioning to a data-centric strategy, Nike’s sales rose more than 70% over the next 7 years.</p><figure><img alt="Source: Forbes" src="https://cdn-images-1.medium.com/max/545/0*kv_lkDP99t-qhhcG.png" /><figcaption>Source: <a href="https://fortune.com/2015/11/12/nike-ceo-mark-parker/">Forbes</a></figcaption></figure><p>ACTIVATING DATA IS A HUGE CHALLENGE.</p><p>Similar to Nike before their shift, many organizations are losing valuable insights as there are many disjointed sources generating and collecting data on their own, contributing to only bits and pieces of the big picture instead of rendering a broad view and the benefits that come along with it.</p><h3>Four Categories of Data-Driven Benefits</h3><p>The benefits of connected innovation come from producing four categories of “intelligent” deliverables as shown below, each built on top of one another, and in order of increasing complexity and sophistication. This approach is part foundational and part innovation, like a balanced portfolio.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/0*2eQIcutvcCMUuIx5.jpg" /></figure><p><strong><em>DEFINITIONS</em></strong></p><blockquote><strong>1. Descriptive analytics:</strong> Generating insights and identifying patterns and trends from historic data</blockquote><blockquote><strong>2. Predictive analytics: </strong>Building models to make predictions that drive better decision-making and improve outcomes</blockquote><blockquote><strong>3. Prescriptive analytics: </strong>Maximizing outcomes and making automated recommendations and decisions</blockquote><p><strong>1. Actionable insights<br></strong>Starting with actionable insights, data-centric solutions can be used to drive deep actionable insights, which can be surfaced in mobile, desktop, or other user experiences. This allows real-time actionable intelligence to be delivered to business operations.This level of intelligent data is similar to traditional business intelligence and descriptive analytics, and is built from development of key metrics, aggregations, statistical analysis, and informative data visualizations.</p><p><strong>2. Optimization<br></strong>After actionable insights, data can be used to optimize realization of company goals and impact. This is possible by leveraging machine learning and artificial intelligence techniques for predictive and prescriptive analytics purposes, e.g., predictive models, targeting, personalization, and recommendations. This level is able to generate a deeper understanding of the data than what humans are able to discover on their own. It also usually generates exponentially more value than traditional BI, statistical, and data visualization-driven insights.</p><p><strong>3. Augmentation<br></strong>With a foundation established for generating insights and optimizing business outcomes, augmentation is the next step. Augmentation, a.k.a., human augmented intelligence is an application of AI to automating tedious, boring, and repetitive tasks that people need to do in their daily work. By automating these tasks, workers are able to focus on increased value-add tasks, productivity, creativity, and overall work enjoyment. It also enables companies to be able to do more, both faster and more intelligently.</p><p><strong>4. Automation<br></strong>Finally, AI-based automation is a complete automation of critical processes or tasks that were previously done by humans. Collectively we refer to this four tiered approach to value generation as ‘Applied AI.’</p><h3>Build Your Data Foundation</h3><p>Companies that invest in data-centricity can drive messaging, efficiency, and superior customer experiences across all functions, not just in marketing. The ability to turn data into value requires building a data foundation that includes the following components:</p><ul><li>Data source identification</li><li>Data ingestion, integration, preparation (ETL, cleaning, processing), and analytics-optimized storage</li><li>Data access and querying</li></ul><p>With an established connected data foundation, we can start to unlock deep actionable insights and intelligent solutions to drive better decision making, predictive and prescriptive analytics, augmentation, and automation.</p><p>With an effective data foundation in place, the data generated by connected systems can be applied to drive real value. Rocket Wagon help’s customers with a crawl, walk, run approach to creating intelligent connected solutions.</p><p>Our recommended approach is as shown.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Henj3Y_jyITX5Cge.jpg" /></figure><p>Building your connected data foundation unlocks many opportunities to drive real business value. This starts with the ability to generate deep, actionable insights. We then help companies focus on cause and effect through experimentation and causal inference strategies. From there we leverage AI, machine learning, and data science to enable advanced use of data to drive bigger results.</p><h3>A Connected Data Strategy and Expert Team For The Win</h3><p>Ultimately, most companies pursue incremental improvements to existing technologies, while often failing to realize the full value and potential of the data they own. This is especially true of emerging digital and IoT connected products built without a data strategy in mind. Every product, whether digital or cyber-physical, should be built to leverage the data they collect in a way that maximizes impact, revenue efficiency, differentiation and competitive advantage.</p><p>Becoming a data-centric company and realizing the high efficiency revenues that come along with it requires adopting an agile approach to developing and executing a data strategy. As we said above, this starts with building an intelligent connected data foundation that can power deep actionable insights and advanced analytics. A data foundation is not the only ingredient for data success. You also need an expert team of machine learning engineers and data scientists, both of which are in very short supply. This expert team is able to drive real differentiation and competitive advantage when combined with the right data foundation, processes, and a wide range of domain experience and expertise. Experts in applied AI also help choose the right tools, approaches, and mitigate risks.</p><p>The complexity and amount of effort to get to this desired state is not lost on us. Gathering insights out of data after all is a science, and science takes time! A successful data strategy needs to be driven by executives who understand the process and who are focused on the end result where the true value lies — transforming business data into assets that help organizations improve revenue, reduce costs, seize business opportunities, improve customer experience, and more.</p><p>Once you’re there, the time and team expenditures can easily be justified as your data strategy connects you to opportunities that form your business’ future.</p><p><em>Originally posted on</em> <a href="https://rw.co/our-thinking/data-to-the-center/">rw.co/our-thinking/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5bcaddb23a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part Six: Lean Product Development for the Internet of Things]]></title>
            <link>https://medium.com/@rocketwagon/part-six-lean-product-development-for-the-internet-of-things-4c353a63c695?source=rss-c20cdef0c4a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c353a63c695</guid>
            <category><![CDATA[disruption]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[lean-development]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Rocket Wagon]]></dc:creator>
            <pubDate>Wed, 24 Apr 2019 21:55:02 GMT</pubDate>
            <atom:updated>2019-04-24T21:56:12.705Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OfUbcn83Me3CXIXTfWVUZw.jpeg" /></figure><p><strong>More than one-third of all IoT projects never make it past the proof-of-concept phase, according to a 2017 Cisco report. It’s a sobering statistic, considering that same year, 73% of executives were, at the time of the poll, either researching or launching an IoT initiative. That’s a lot of failed products, not to mention hundreds of millions of dollars down the drain — most of which could have been avoided with a specialized product development practice.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/0*BmZSJBZxVTTTk6cU.jpg" /></figure><h3>The tenants of Lean</h3><p>Lean product development practices allow engineering teams to quickly optimize products while simultaneously shipping new features, eliminating waste and continuously improving the quality of the deliverable. This process allows software teams to rally behind a philosophy of‘done is better than perfect.’ But creating connected products is far more complex than software alone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BMUOqOG9yW49ZdbQUjkfTw.jpeg" /><figcaption>RW Lean Product Development for IoT</figcaption></figure><h3>Rapid iteration in IoT and the dangers of moving too quickly</h3><p>In theory, the goals of rapid, iterative development, constant optimization, and waste elimination are the same for IoT as in traditional lean product development. But in reality, the complexity and potential for wasted time and money grows exponentially. The success of connected products hinges on their hardware design, and early mistakes can be extremely costly later when materials sourcing, supply-chain management, and retailer negotiations begin.</p><p>Hardware teams live by a hard rule of ‘measure twice, cut once’ because manufacturing and supply chain considerations are incompatible with a ‘ship now, fix later’ mindset. Once a product moves into manufacturing, iteration on hardware and firmware must cease. Changes made during manufacturing mean that your assembly line sits idle, you have to quickly re-allocate your engineering team, your bill of materials cost increases, you face component shortages, and you introduce risk due to lack of testing and long-term validation of changes. These changes are likely to add months (if not years) onto your development time.</p><p>The failure to appreciate these critical decisions will ultimately undermine your execution, and greatly increase your risk of spending an eternity in a special kind of hell: Prototyping purgatory. But this doesn’t mean that iteration must stop completely, or even slow down — it just means that certain decisions must be thoroughly tested and solidified up front.</p><blockquote>DEFINITIONS</blockquote><blockquote><strong>1. POC: </strong>Proof that an idea is feasible.</blockquote><blockquote><strong>2. Prototype:</strong> A working model for delivering an experience to the consumer.</blockquote><blockquote><strong>3. MVP:</strong> A working, consumer-ready product that provides just enough functionality provide real value to the consumer.</blockquote><h3>Where to start: Proof of concept, prototype, or MVP?</h3><p>While sometimes used interchangeably, each is actually a critical phase of the product development lifecycle. Each is optimized for for different challenges, and all three are necessary to create a successful IoT product. Proofs of concept identify technical and delivery risks and test a hypothesis of a solution, without integrating or testing anything else that isn’t related to that specific risk. In a prototype, the learnings from all of the proofs of concepts are merged into a development device that allows multiple different teams to collaborate on iterative product development, with each successive prototype incorporating the new design and learnings from each of the teams in order to test the entire product as a complete system. Once a prototype meets all of the design criteria, including user testing, quality testing, manufacturability analysis, and failure mode analysis, it can be considered an MVP and released to manufacturing.</p><p>Consider a smart shelving unit that tracks inventory levels and out-of-stock events. Proofs of concept for this product include the sensors that track weight, the mechanism that pushes products forward on the shelf, and the physical shelf itself. These POCs would then be assembled into a working prototype, as software teams build an ‘essentials-only’ ecosystem around it, including user touchpoints, an IoT platform, data collection and analysis, and more. Finally, the MVP is created, expanding the prototype to include functions such as onboarding, user management, and any other features necessary for this product to be considered usable.</p><p>Consider each of these deliverables as distinct development phases — all rapid, iterative, lean, and designed to dramatically reduce risk.</p><h3>Create your proof of concept(s)</h3><p>Do not rush this step. This phase is designed to determine whether or not an idea is feasible and, if so, how to build it. Hardware and software teams should begin delineating which functionalities will fall to which disciplines, and mechanical and hardware engineers should work with industrial designers to create multiple proofs of concepts — one for each of a product’s necessary hardware components.</p><p>While solving for as many narrow hypotheses as possible, hardware teams must begin de-risking, solving for a multitude of product considerations such as connectivity, sensor selection, firmware design, mechanical design, and industrial design. They must devote time to testing and experimentation to ensure the best possible solutions, because at the end of this phase, each POC should satisfactorily validate a single, high-level product need.</p><h3>De-risk while building a prototype around your POCs</h3><p>Now that each hypothesis has been answered and key product considerations solved for, the POCs can be assembled into a working model of a single product. This prototyping phase allows multidisciplinary teams to work out the kinks of a product’s key features while putting together the physical and digital components.</p><p>Two separate, iterative development tracks are necessary at this phase: One that encompasses industrial design and hardware engineering, and another for UX design and software engineering.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GxScarLRp0oKnx8A.jpg" /></figure><p>In each of these tracks, the two disciplines will design and build separately before coming together to test and iterate. This cycle must happen multiple times to ensure a fluidity of experience before the two tracks come together. At this point, the team must test the hardware, software, industrial design, and UX design together and iterate again. Then, the two tracks must break off once more to continue iterating and testing separately. If it sounds like a lot of work, it is. But without multiple rapid rounds of iteration, your team is far more likely to miss areas ripe for optimization.</p><p>At this stage, it’s ideal to work with local, small-batch manufacturers to keep costs down and turnaround times high.</p><h3>Create your MVP and prepare for manufacturing</h3><p>Now that you have your prototype, it can be fleshed out as an MVP. This is where all additional components needed for a sellable product are created, including features like user management. Iteration continues during this phase, but hardware and materials considerations must be finalized at this point to begin preparation for real manufacturing and supply-chain processes with large-scale distributors and manufacturers. Thorough cost-benefit analyses must be performed to ensure the best solutions for the best price.</p><blockquote>IMPORTANCE OF QA</blockquote><blockquote>Your connected product will require hundreds of continuous test runs, full API circuit tests, and more. Ongoing QA efforts are imperative to uncovering and fixing issues with connectivity, security, interoperability, and a seamless user experience.</blockquote><h3>Don’t get discouraged</h3><p>With careful planning and iterative processes, you can ensure your connected product makes it to market. It may seem like a long road, but the ends justify the means — it’s the only way forward in a connected world. “IoT is seen as the future of everything,” says Stephan Fabel of InformationWeek, “from smart-city advances like traffic congestion relief and intelligent street lighting, to better energy management, to industrial robotics and asset tracking, to monitoring of medical equipment and patient condition (not to mention the array of home consumer applications).” (Fabel, 2018)</p><p><em>View the rest of the series and the original article at </em><a href="http://bit.ly/LeanProduct_IoT"><em>https://rw.co/our-thinking</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c353a63c695" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part Five: Building Tomorrow with the New Technology Stack]]></title>
            <link>https://medium.com/@rocketwagon/part-five-building-tomorrow-with-the-new-technology-stack-b096bbbef8dc?source=rss-c20cdef0c4a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/b096bbbef8dc</guid>
            <category><![CDATA[tech-stack]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[technology-strategy]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[value-creation]]></category>
            <dc:creator><![CDATA[Rocket Wagon]]></dc:creator>
            <pubDate>Thu, 11 Apr 2019 17:43:42 GMT</pubDate>
            <atom:updated>2019-04-11T17:43:42.520Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*51Rl7T2K9yiMdERpi2UH9Q.jpeg" /></figure><blockquote><strong>The promise of IoT offers vastly more opportunities for operational efficiencies, functionality, enhanced reliability, and products that transcend traditional consumer touchpoints and product boundaries. (</strong><a href="https://hbr.org/2014/11/how-smart-connected-products-are-transforming-competition"><strong>Porter &amp; Heppelmann, 2014</strong></a><strong>) But with these capabilities comes a significant challenge — adopting a technology stack that’s capable of performing these functions securely and reliably, and with the ability to scale.</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r5TJz1N8EvyvEb3Q8GKTYw.jpeg" /></figure><p>The technology landscape is rapidly changing to support IoT initiatives. Increased processing power, the miniaturization of devices, dramatically lower sensor costs, the ascent of cloud computing, and the ubiquity of wireless connectivity are all lowering the barrier to entry. So it’s no wonder Gartner predicts that by 2020, more than 20 billion such products will be online.</p><p>Simply put, if you’re in the business of making products, or in business at all, and you want that business to survive, then at least some of those 20 billion products should be made by you.</p><h3>Architecting connected ecosystems requires a new technology stack</h3><p>Building a successful connected product is far more complex than your standard digital service or CPG product. IoT requires the architecting of a complex ‘connected ecosystem’, comprised of multiple edge devices, a responsive platform, and the careful analysis of multiple data streams.</p><p>This means that, much like the ‘smart shelves’ example, user data must be distributed seamlessly across multiple platforms or devices. And in an age where user privacy is of utmost importance, with significant data leaks leading to PR nightmares, the technical complexity only increases exponentially from here.</p><p>The new technology stack breaks your IoT product into two distinct layers.</p><h3>1. The Edge layer</h3><p>Edge devices allow users to connect to and transfer data across a network, moving computing closer to consumers. This, in turn, allows them to remain engaged with your product, so you can collect as much data as possible. The most common kinds of edge devices include:</p><p><strong>Third-party standardized edge devices:</strong> These include standard mobile phones and web browsers.</p><p><strong>Third-party non-standardized edge devices: </strong>These collect unique data to enable smarter connected services for customers.</p><p><strong>First-party edge devices: </strong>These are edge devices that your company develops itself.</p><h3>2. Platform layer</h3><p>Regardless of type, the edge device operates by connecting to a cloud-based IoT platform. This platform collects data from the edge device, stores it, and uses it to unearth business insights and trigger automatic processes.</p><blockquote>“The relationship between a platform and the apps that are built on it is symbiotic. They need each other more than one needs the other.”</blockquote><p>— IoT expert, <a href="https://medium.com/@julien51/platform-moats-efbc12e055f0">Julien Genestoux</a></p><p>A robust IoT platform enables companies to rapidly develop multiple connected products and iterate on those products quickly — a very attractive proposition for organizations in the product space. To serve these organizations, several top companies have developed Platform as a Service (PaaS) IoT frameworks — vendors like AWS, Google Cloud, Azure, Cisco Jasper, GE Predix, IBM Watson, and Salesforce.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QhfjpiXIHW5bkeNztzljLQ.jpeg" /></figure><h3>Introducing dramatic changes to your platform</h3><p>To compete successfully in the connected world (and to protect your company’s reputation) your IoT platform must be built, or rearchitected, with the following in mind:</p><ul><li><strong>Edge device management:</strong> Your digital platform must be able to connect with, monitor, manage, control, and extract data from connected devices, of which there may be an enormous number, and which may be located in remote areas with spotty connectivity.</li><li><strong>Security: </strong>Your platform must handle security and encryption for end-to-end communication, and it must be bulletproof.</li><li><strong>Over-the-air updates: </strong>Your platform must be able to send updates to and from edge devices on the fly, potentially without user intervention.</li><li><strong>Interoperability: </strong>Loosely defined, interoperability is the ability of two or more entities to interact and exchange information. Your platform must maximize interoperability across your entire ecosystem.</li><li><strong>Scalability:</strong> Network resources must be used efficiently. Your platform must feature standards-based solutions for utilizing automation and horizontal device management.</li></ul><blockquote>RELATED</blockquote><blockquote>Designing delightful experiences around all this technology presents its own challenges. But we’ve got you covered. <a href="https://rw.co/our-thinking/connected-solution-design-mastering-storytelling-and-tension/">Learn more.</a></blockquote><h3>Tackling the new technology stack</h3><p>As you build, you must ensure that your edge devices and platform address a multitude of considerations simultaneously. Enter the new technology stack. In order to collect, analyze, and redistribute your users’ data, consider the following to be the bare minimum of technologies you must implement:</p><p><strong>Device hardware:</strong> This refers to both the smart connected product itself as well as the integrated sensors and components within the product. Examples of the connected device hardware include such things as home appliance, vehicle, industrial machine, commonly referred to as an edge device. Device hardware within products include microcontrollers to collect, store, and pre-process data; sensors to monitor and measure values such as temperature, humidity, vibration, acceleration, light, sound, and so on; and other electronic components.</p><p><strong>Embedded software:</strong> Embedded in the microcontroller of every smart connected product is firmware — that is, software that dictates how frequently the device collects data, how it processes that data, how it formats that data before sending it on to the network, and when it sends it.</p><p><strong>Connectivity capabilities:</strong> Smart connected products use various network tools to communicate with the outside world. There are many options for connectivity, and each has its own trade offs, pros and cons with respect to power consumption, range, bandwidth, obstacle penetration, and data cost.</p><p><strong>Cloud resources:</strong> Smart connected products connect to cloud resources by way of a data gateway. These cloud resources include an IoT platform (which connects everything in an IoT system), other software, a database, security tools, and those tools needed to facilitate integration with enterprise business systems, such as CRM systems.</p><p><strong>Big data collection and analytics: </strong>Collecting massive amounts of data is just the first step — filtering, structuring, and serving it up to the right audience at the right time also requires significant effort.</p><p><strong>Horizontal data integration: </strong>The data collected by smart products has the potential to add tremendous value across your entire organization. Digitize and automate your internal value chain with intelligent, cross-company data integration strategies.</p><h3>Making sense of the data</h3><p>This technology stack, say Porter and Heppelmann, “enables not only rapid production application development and operation but the collection, analysis, and sharing of the potentially huge amounts of longitudinal data generated inside and outside the products that has never been available before.” (<a href="https://hbr.org/2014/11/how-smart-connected-products-are-transforming-competition">Porter &amp; Heppelmann, 2014</a>)</p><p>And unlike the 3 billion humans currently online — each of whom tends to produce data once every few minutes on average — networked devices produce data 60 times per second. Multiply that by 20-odd billion devices and you have a lot of data — data that must be aggregated, cleaned, and analyzed in order to be useful. Thus, your platform must also maximize data provided by edge devices by translating it into valuable business insights and smarter services for customers.</p><p>This is what makes possible the ultimate goal of IoT: <strong>Creating value through data while solving for customer needs.</strong></p><h3>The future of everything</h3><p>IoT and the Fourth Industrial Revolution is rapidly changing every industry, from connected health solutions that monitor patients’ vitals to smart cities that relieve and manage traffic congestion to asset tracking within intelligent logistics, among others. (<a href="https://www.informationweek.com/big-data/ai-machine-learning/ai-and-iot-techs-new-bffs/a/d-id/1332108">Fabel, 2018</a>)</p><p>Your company can’t afford to get left behind. But embracing IoT means mastering the new technology stack — including edge devices and the IoT platform — that supports it. Rocket Wagon was purpose-built to help you do just that.</p><p><em>View the rest of the series and the original article at </em><a href="http://bit.ly/NewTechStack"><em>https://rw.co/our-thinking</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b096bbbef8dc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part Four: Connected Solution Design: Mastering Storytelling and Tension]]></title>
            <link>https://medium.com/@rocketwagon/part-four-connected-solution-design-mastering-storytelling-and-tension-44d7a0b01ceb?source=rss-c20cdef0c4a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/44d7a0b01ceb</guid>
            <category><![CDATA[layeredge]]></category>
            <category><![CDATA[experience-design]]></category>
            <category><![CDATA[disruption-thinking]]></category>
            <category><![CDATA[connected-enterprise]]></category>
            <category><![CDATA[iot]]></category>
            <dc:creator><![CDATA[Rocket Wagon]]></dc:creator>
            <pubDate>Thu, 28 Mar 2019 17:00:56 GMT</pubDate>
            <atom:updated>2019-03-28T17:00:56.061Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1qC3flSz_kK-yriTD8F-VQ@2x.jpeg" /></figure><p><strong>Start with ‘Why’. It’s an extremely popular book by Simon Sinek, as well as an enduring rallying cry of storytellers and strategist everywhere, due to its ability to cut to the heart of the matter. Because at the end of the day, no one buys what you do, or how you do it. They don’t even buy IoT. The only thing that consumers care about is the outcome and the value it brings to them. They buy the why should I care.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Z4vGP77zZKq_LYCr.jpg" /><figcaption><a href="https://startwithwhy.com/">https://startwithwhy.com/</a></figcaption></figure><h3>IoT is not a strategy</h3><p>It’s an important distinction in an age where approximately 95% of new products fail, and 87% of consumers possess a foggy-at-best awareness of what IoT really is. No one will buy your smart tupperware because it’s smart tupperware — if it doesn’t solve a real-life problem, you’ve already committed a fatal error. The potential value driven by IoT is too great to waste on cheap tricks, especially with your company’s future on the line.</p><blockquote>RELATED</blockquote><blockquote>According to the Harvard Business Review, digital disruption is rapidly increasing the churn on the once-stable S&amp;P 500, predicting that three quarters of its current rank-and-file members will be replaced by 2027.</blockquote><h3>The connected world is changing the face of design</h3><p>Designing for a connected world demands a different approach from designing for digital or physical products alone. The challenge of creating a coherent connected experience is multi-faceted and complex — for example, there are far fewer standards for design in IoT, products often have physical and digital interfaces, and suddenly factors like location and connectivity matter deeply.</p><p>But where do you start? Defining what makes a successful user experience is still key.</p><h3>The UX of ‘invisible’</h3><p>In the words of former Apple exec and BeOS founder Jean-Louis Gassée, “Simple is hard. Easy is harder. Invisible is hardest.”</p><p>A well-designed connected experience should appear seamless and completely invisible to the user. And predictably, the attribute that creates the most value is the most difficult to pull off. To illustrate, we need look no further than an experience so essential to the digital world that it’s become a verb:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/0*p9UlGulpcOxu85h1.jpg" /><figcaption>Google.com</figcaption></figure><p>Google’s search engine is driven by some of the most sophisticated technology and advanced engineering in the world. The product has revolutionized how businesses present themselves online and how we, as consumers, discover information, goods, and services. Yet this interface presents a simple search field, which captures roughly 3.5 billion daily searches submitted by 1.2 billion users.</p><p>This is the ultimate goal of designing for IoT: hiding immense complexity behind a simple, seamless experience. But the technical landscape upon which we imagine this experience is very different, requiring immense coordination of backend infrastructure and front-end design.</p><h3>The art of system-design thinking</h3><p>Before your design team can start putting together journey maps and flows, this larger ecosystem must be designed to take certain technical considerations into account. This is because in IoT, the user interactions are intrinsically tied to how the connected product works.</p><p>As such, IoT shifts designers to think in terms of context and connected worlds, and turns hardware and software engineers into designers themselves. User experience grows beyond a one-to-one relationship to become a web of touchpoints and conversations. All technical components must remain as invisible as possible — as does the burden of transporting, processing, storing, and analyzing data. And your product must do all of this without noticeable lag or requiring too much user participation.</p><h3>A tale of two layers</h3><p>Your multidisciplinary team must design these technical considerations to seamlessly communicate across two distinct layers.</p><h3>Edge Layer</h3><p>This is the experience layer, and how your users interact with your IoT product. It’s important to keep in mind that this layer may be comprised of many touchpoints. A user may interact with, for example, a smart home speaker, a companion app, the physical sensor itself, an email app, and push notifications — all for a single device. Because of the distributed nature of an IoT product’s potential touchpoints, the user experience must be mapped out across multiple devices while promoting continuity of design between them so as to appear seamless.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WhsTQvqNCa9cv2gd.jpg" /></figure><blockquote>RELATED</blockquote><blockquote>Unfamiliar with the edge? We break down IoT’s many technical considerations in The New Tech Stack. <a href="https://rw.co/our-thinking/building-tomorrow-with-the-new-technology-stack/">Read more.</a></blockquote><h3>Infrastructure (platform) layer</h3><p>This is the underlying layer that powers the user experience — it’s comprised of the platform, tools, services, and underlying product framework. It’s where architecture, hardware engineering, advanced software engineering, service design, and manufacturing considerations such as BOM (bill of materials) cost all come into play.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FXdnqcEqdWVz2fLb.jpg" /></figure><h3>Success requires tension between infrastructure and edge layers</h3><p>The cost of mistakes get higher and higher as the product gets closer to its launch — thanks largely to hardware components and manufacturing considerations — it’s important to aggressively manage all trade-offs proactively. The ideal system design must be tested against the needs and expectations of all team members early and often to ensure that these trade-offs do not negatively affect the user.</p><p>This list is merely a sample of the considerations your team must make when designing or tweaking the experience provided by any physical product:</p><ul><li><strong>Systems blueprint:</strong> Should a specific feature appear on the mobile app or a connected device? Implementation considerations must be a part of the design process, and require a careful mapping between each human touchpoint, and engineering capabilities — certain features may be handled by firmware, and some by hardware. The pros and cons must be thoroughly assessed for each.</li><li><strong>Behavior flow: </strong>Your user experience must be mapped out to match your systems blueprint. The technical considerations therein will determine what edge devices a user interacts with, how, and when.</li><li><strong>Edge cases: </strong>With so many potential moving parts, the number of edge cases your user may face increases — loss of connectivity, lack of interoperability, third-party integrations, empty states, complex tutorials, and more must all be considered when creating IoT interfaces.</li><li><strong>Actionable insights:</strong> If you intend to use any of your data collected to gather insights on product use, internal processes, or manufacturing processes (and you should), you will need a way to analyze and view potentially disparate data types, and ensure that data delivered to the right people at the right time.</li><li><strong>Costs:</strong> If the BOM costs make a product prohibitively expensive for prospective customers, the selected materials may need to be reassessed, or the revenue model may require changes.</li><li><strong>Maintenance and support:</strong> The total cost of DevOps teams and any additional support or maintenance needed may drive up costs, or prove too massive for a product to be viable.</li><li><strong>Scalability</strong>: Where do you see your MVP in one year? In five? Ensuring your design system and technical ecosystem are both scalable will better ensure future success as your product and audience grow.</li></ul><blockquote>RELATED</blockquote><blockquote>Interested in how this all comes together? <a href="https://rw.co/our-thinking/lean-product-development-for-the-internet-of-things/">Read: Lean Product Development for IoT</a>.</blockquote><h3>Never design in isolation</h3><p>Each of these considerations are equally important, so all are integral to designing a connected solution that successfully crosses the chasm. For that reason, designers must work in tandem with software architects and hardware specialists to ensure feasibility from technical, financial, and organizational standpoints.</p><p>Organizations can’t look to partners capable of only delivering on one aspect of the solution, because each is a major driver of the solution’s success. The ideal partner is one that is multidisciplinary, one that can see the whole picture, and deliver a truly connected solution.</p><p><em>View the rest of the series and the original article at </em><a href="http://bit.ly/storytelling_tension"><em>https://rw.co/our-thinking</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44d7a0b01ceb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part Three: The Four Imperatives of Successful IoT]]></title>
            <link>https://medium.com/@rocketwagon/part-three-the-four-imperatives-of-successful-iot-5a4fd97dd38c?source=rss-c20cdef0c4a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a4fd97dd38c</guid>
            <category><![CDATA[disruption]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[Rocket Wagon]]></dc:creator>
            <pubDate>Tue, 12 Mar 2019 19:55:08 GMT</pubDate>
            <atom:updated>2019-03-12T19:55:08.086Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RiKKn92ZuyUPyGf5WMFM3A@2x.jpeg" /></figure><p><strong>A study from the John M. Olin School of Business at Washington University estimates that 40% of today’s Fortune 500 companies on the S&amp;P 500 will no longer exist in 10 years. We have emerging technology to thank for this — 73% of enterprises believe disruption to their industry will be driven specifically by IoT (Gartner).</strong></p><p>The promise of IoT is vast; so, too, are the multitude of ways in which this technology can be employed. In 2018, 70% of Fortune 100 companies were innovating with IoT technology — Cisco created Smart Grid technologies, Rolls Royce optimizes jet flight patterns, and both Google and GE have been dabbling in IoT for years.</p><p>Suffice it to say that there’s no single blueprint for creating a successful IoT ecosystem. But when your options are hope for the best or get busy innovating, where do you start?</p><blockquote>|KEY INSIGHT |</blockquote><blockquote>The inability to prioritize IoT leads to insufficient investments that focus on incremental wins that augment or optimize an existing product or process. These single use case business solutions, such as attaching a dashboard to product, rarely achieve the full potential of IoT.</blockquote><h3>Find the Signal in the Noise</h3><p>It’s imperative that companies begin by asking the right questions. Jeff Bezos said it best when he stated, “I very frequently get the question, ‘What’s going to change in the next 10 years?’. I almost never get the question, ‘What’s <em>not</em> going to change in the next 10 years?’.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*y83Zz9aTFsU5I5Bc.jpg" /><figcaption>Source: <a href="https://www.peterhapak.com/J-Bezos">Peter Hapak</a></figcaption></figure><p>This is the difference between a strategy and a vision. You must find your company’s signal in the noise, and create a shared vision around those industry factors and consumer needs that will always stay the same. This is how you prioritize ideas and ensure you’re making smart investments in your company’s future.</p><p>When companies fail to set a unified vision, they push IoT strategies that attempt to address too many problems at once. The managers in charge of such initiatives will not feel equipped or empowered to make the deep organizational changes that are required for success. This often makes IoT look like “yet another IT project” or a political power grab by one department or another, instead of an opportunity to truly evolve as a company.</p><p>Additionally, the resulting incrementalism of this approach leads to “random acts” of IoT that fail to live up to the awesome potential of this technology — and that’s if these projects even make it past the near-inevitable prototyping purgatory, in which nothing ever gets launched. These kinds of isolated projects look like progress, but they don’t produce results or lay a proper foundation for the future. They do, however, lead to a predictable result: Death by 1,000 cuts. And this, more often than not, leads the company to entirely abandon their IoT efforts and their greatest chance of outlasting disruption.</p><h3>Put Data at the Center</h3><p>So how do you avoid the trap of ‘random acts’? In order to embrace the full power of IoT, companies must rethink how they collect and use data. It can no longer be viewed as an afterthought; collecting and analyzing data to drive your company forward must be your new strategy — the means through which you gather it becomes your products and services, and new data-centric revenue streams offer extremely efficient gross margins.</p><p>Consider a CPG company with $2B in revenue and a 15.0% net income that introduces $50M in new data monetization revenue. As IoT-sourced data often comes with nominal overhead costs, this new revenue stream could have the same impact on net income as increasing traditional product revenue by 17.0%. Not many businesses can create that kind of impact through traditional growth channels.</p><p>Moreover, companies like Amazon, Google, and Facebook empower rapid innovation by facilitating information exchanges between an ecosystem of interdependent groups. Data flows freely from a central hub to every group in these global juggernauts, driving innovation and efficiency in processes, sales pipelines, products, and more. This level of data fluidity is the foundation of IoT success because it allows all enterprise data to be leveraged for the greater good of the company.</p><blockquote><em>Data analysis and distribution throughout your organization creates a true connected ecosystem, the pinnacle of IoT efficiency. Read about how to cross the connected chasm here.</em></blockquote><h3>Drive Unprecedented Collaboration</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RInPb9N_uXvD1Cem.jpg" /></figure><p>Most people think of IoT transition as a technical challenge, and it is. But most IoT transitions don’t fail because of technology alone. They fail because of people.</p><p>IoT crosses the boundaries between departments — and that doesn’t always turn everyone into happy campers. Success requires close collaboration across strategy, product, industrial design, experience design, mechanical engineering, data science, engineering, and more. But cultural disconnects between teams can create significant barriers in product development. Hardware and software teams, for example, have competing ideologies — the former lives by a mantra of ‘measure twice, cut once’ because of the high cost associated with hardware development and manufacturing, while software teams often strive for a ‘ship now, iterate later’ approach.</p><p>Without clarity of leadership, responsibilities, respect, and vision, these teams may not foster the communication necessary to succeed in IoT. The key to success is engaging the highest levels of the organization through the process so that everyone involved has the air cover to step out of their comfort zones. Because these kinds of institutional changes can be uncomfortable. With clear support throughout the entire organization, the transitional road bumps can return to being a technical challenge, not a human one.</p><h3>Inoculate from Corporate Antibodies</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ASrTnfVbCCK4T-5d.jpg" /><figcaption>Source: Nasa.gov</figcaption></figure><p>Corporate anti-bodies are the organizational forces that push for the safety of mediocrity and the predictability of a company’s decline over any measure of risk. In the eyes of a corporate anti-bodies, unpredictable growth is worse than a measured predictable decline. And they will strive to deliver IoT transitions to an early grave.</p><p>Corporate anti-bodies thrive on the fact that IoT is confusing for many executives. Alternating between doubt and impatience with IoT initiatives, corporate anti-bodies return the organization to the safety of the status quo — even when staying the same means that competitors dominate new revenue streams and markets.</p><p>Inoculating IoT initiatives requires an organizational strategy that evolves as the initiative moves from strategy to solution design to prototyping to piloting to commercialization. Executives must demonstrate leadership in the face of uncertainty to prove out business models that may require reworking later.</p><h3>It’s time to get innovating</h3><p>As the next technology wave, IoT must be a critical element of corporate strategies and must be on the C-Level agenda to support and drive. Today’s connected world will drive changes outside your organization that will move exponentially faster than the mobile revolution, so any corporate vision without IoT is incomplete and brings significant risk with it. Being mindful of these 4 imperatives helps you plan and execute an IoT strategy that not only delivers on business success — they can also help you clear the way for quicker adoption and greater creativity.</p><p><em>View the rest of the series and the original article at </em><a href="https://rw.co/our-thinking/the-four-imperatives-of-successful-iot/"><em>https://rw.co/our-thinking</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a4fd97dd38c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 2: Stop Selling Products to Cross the Connected Chasm]]></title>
            <link>https://medium.com/@rocketwagon/part-2-stop-selling-products-to-cross-the-connected-chasm-7023da180aae?source=rss-c20cdef0c4a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/7023da180aae</guid>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[industry-4-0]]></category>
            <category><![CDATA[disruption]]></category>
            <dc:creator><![CDATA[Rocket Wagon]]></dc:creator>
            <pubDate>Mon, 04 Mar 2019 16:47:31 GMT</pubDate>
            <atom:updated>2019-03-28T17:02:41.307Z</atom:updated>
            <content:encoded><![CDATA[<h3>Part Two: Stop Selling Products to Cross the Connected Chasm</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*I7dV5laAxR4jhxqx.jpg" /></figure><p><strong>Back in 2008, Blockbuster CEO Jim Keyes stated, “Neither RedBox nor Netflix are even on the radar screen in terms of competition.” Sure it sounds ridiculous now, but be honest — would you have imagined back in 2002 that your neighborhood video store would soon disappear?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/0*rgCFkJ5SPjhZo7Oi.jpg" /></figure><p>Luckily, attitudes towards disruption have changed immensely since Keyes uttered these famous last words — according to <a href="https://assets.kpmg.com/content/dam/kpmg/pe/pdf/Publicaciones/Estudios-encuestas/CEO-Outlook-2018-GLOBAL.pdf">KPMG’s annual CEO report</a>, 95% of CEOs see disruption as an opportunity. Furthermore, 71% of CEOs are ready to lead their organization through radical transformation in order to remain competitive. If you haven’t already, join them.</p><h3>Stop selling products</h3><p>Selling the same product in the same old way is no longer enough to keep a company afloat. Nor is selling a <em>better</em> product enough to increase market share. Improving the in-store experience, or the video packaging, would not have stopped the mass exodus from stores to streaming services. And it certainly wouldn’t woo Netflix’s 118 million subscribers back into Blockbuster stores from the comfort of their couches.</p><p>Disruption is lurking around every corner, and mass adoption of IoT initiatives increases the risk of disruption exponentially. Countless industries are already being revolutionized by emerging technology, and its projected that approximately <a href="https://www.zebra.com/content/dam/zebra_new_ia/en-us/solutions-verticals/vertical-solutions/retail/vision-study/retail-vision-study-2017-en-gb.pdf">79% of retail companies alone will implement IoT technology by 2019</a>.</p><p>In order to succeed in this rapidly changing, connected world, your company needs a vision for the future that takes advantage of the full promise of the Fourth Industrial Revolution. Innovation teams can no longer rally around the familiar cry of “How can I sell more ___?” Companies must instead create a portfolio of strategic initiatives that will drive the company in the right direction. In other words, you must shift your focus from an outdated product model to a service model to survive.</p><blockquote><strong><em>Welcome to the Fourth Industrial Revolution. After steam, electricity, and wired computers comes the cyber-physical revolution, which blurs the lines between the physical, digital, and biological spheres via emerging technology.</em></strong></blockquote><h3>Drive profitable outcomes with service models</h3><p>Often called ‘outcome-based’ models, service models shift a company’s focus from the product they create to what their customer is really looking for: A solution to their problem. An outcome.</p><p>To put this into perspective, look at the most common revenue models associated with this shift in thinking:</p><p><strong>1. Consumption model:</strong> In this model, consumers are charged for actual usage instead of a flat monthly fee. A simple example would be a soda machine that charges consumers only for the number of ounces they drink. Usage-based insurance, also known as ‘pay as you drive’ insurance, is far more complex. This type of car insurance company charges consumers based on a multitude of factors — among them, driver behavior, distance driven, and the type of vehicle — creating a dynamic premium based on real user information.</p><p><strong>2. Asset sharing: </strong>This model allows companies or consumers to share the cost of expensive assets, creating additional value across existing resources. Famous examples include Zipcar and AirBnB, but this model’s potential B2B applications should not be overlooked — manufacturing startup DOZR, for instance, enables contractors to rent industrial equipment from other construction companies that are not currently using it.</p><p><strong>3. Replenishment:</strong> Auto-replenishment drives sales, increases brand loyalty, and allows companies to accurately and automatically track inventory. Amazon’s Dash Replenishment Services, for example, allows connected devices to measure product consumption and automatically reorder products for consumers when they’re running low.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*24MvOA6sdlwZKqhg.jpg" /></figure><h3>The ultimate goal: a connected ecosystem</h3><p>How does an ecosystem differ from a connected product? Instead of providing a single source of data, an ecosystem of connected products and services drives significant value at every stage of the consumer journey and your internal value chains via multiple data streams. Take Caterpillar as an example of one such connected ecosystem done right:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zw6qEjFomyOXo6h8.jpg" /><figcaption>Source: CAT® Connect Technology and Services</figcaption></figure><p>With their <a href="https://www.cat.com/en_US/by-industry/construction/cat-connect.html">Cat Connect services</a>, this iconic brand has adopted multiple service models, transforming their manufacturing equipment into a fleet of connected products. Caterpillar’s customers use this smart equipment to monitor jobsite efficiency, equipment maintenance needs, fuel consumption, and more. This allows them to reduce costs while improving safety and production on their jobsites.</p><p>These new services create a reputation for innovation for Caterpillar, driving loyalty for the brand and attracting new customers. Additionally, the data Caterpillar collects from all this smart manufacturing equipment drives optimization in their product lines, as well as within their sales pipelines.</p><blockquote><em>| KEY FACT |</em></blockquote><blockquote><em>The total economic impact of the connected world has been estimated to be as much as $11 trillion by the year 2025. For reference, the gross domestic product of the United States reached $19.39 trillion in 2017.</em></blockquote><h3>To begin crossing the connected chasm, start with one step in the right direction</h3><p>Service models don’t change business goals like increased business opportunities, more efficient processes, greater customer loyalty, enhanced asset utilization, and increased market share. Service models simply change <em>how</em> you achieve them. It’s imperative that you keep one eye on the potential for emerging technology to create change, but the other eye on those factors that will always remain constant in your industry.</p><p>Follow Caterpillar’s example: Map your business goals to service-model solutions, creating a portfolio of strategic initiatives that solve real needs and bring you closer to a connected ecosystem. Then, create momentum behind them to ensure success, and to stop organizational forces from deprioritizing these new ideas in favor of maintenance or older ways of thinking.</p><p>Strong leadership is immensely important for change management. Without clear communication on progress and vision, your IoT initiatives face far greater risk of failure –internal excitement atrophies, and teams start waiting for this ‘fad’ to blow over so they can keep prioritizing incremental optimization. Create a manageable, measurable first step as your company’s first domino on the road to true transformation to get your team on board, without losing sight of the real prize: a well-oiled connected ecosystem.</p><h3>Doing nothing is still doing something.<br> Spoiler alert: It’s the wrong thing.</h3><p>So what happens if you decide to wait on innovation? The head-in-the-sand approach may seem reasonable on the surface — there’s risk in revolution, after all. But the greater risk is in inaction, and striving to squeeze more profit out of an outdated business model.</p><p>According to <a href="https://www.idc.com/getdoc.jsp?containerId=US43193617">IDC FutureScape’s Worldwide IoT 2018 Predictions</a>, almost 50% of new IoT enterprise applications will leverage outcome-focused functionality based on deep data insights. If you want to succeed in tomorrow’s markets, you must shift your thinking today and embrace change as the core of your new innovation strategy.</p><p><em>To see the entire series and original post visit </em><a href="http://bit.ly/Product2Service">rw.co/our-thinking</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7023da180aae" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Presenter as a Function: Structured Concurrency Edition]]></title>
            <link>https://medium.com/@rocketwagon/presenter-as-a-function-structured-concurrency-edition-27ecfd47b7c2?source=rss-c20cdef0c4a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/27ecfd47b7c2</guid>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Rocket Wagon]]></dc:creator>
            <pubDate>Mon, 04 Mar 2019 16:22:33 GMT</pubDate>
            <atom:updated>2019-03-07T22:03:44.001Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XwEpgAyjpF0rGhEdUvm_mQ.jpeg" /></figure><p><strong>By </strong><a href="https://www.linkedin.com/in/mlangreder/"><strong>Matt Langreder</strong></a><strong>, Sr. Software Engineer</strong></p><p>Since my <a href="https://medium.com/@rocketwagon/presenter-as-a-function-reactive-mvp-for-android-using-kotlin-coroutines-442fc4c77119">previous post</a>, Kotlin has hit version 1.3 and coroutines have hit 1.0. These new releases have now brought <a href="https://medium.com/@elizarov/structured-concurrency-722d765aa952">Structured Concurrency</a> into the fold. I’m not going to cover in detail the changes to the language and frameworks here but I did want to show an updated example from my previous post. By utilizing <a href="https://medium.com/@elizarov/structured-concurrency-722d765aa952">Structured Concurrency</a> we can improve on our previous example in a number of ways.</p><h3>Note</h3><p>This post is not covering things such as debouncing clicks and other common UI paradigms. You can check the <a href="https://github.com/Kotlin/kotlinx.coroutines/blob/master/ui/coroutines-guide-ui.md#basic-ui-coroutines">UI Coroutines Guide</a> for examples and ideas of how to properly handle your specific UI interaction needs.</p><h3>Coroutine Scope</h3><p>With the introduction to coroutine scope, we no longer need to manually manage our coroutine Jobs. Our Previous activity looked like this:</p><pre>class SignInActivity : AppCompatActivity() {</pre><pre>    private val clickEventChannel = Channel&lt;SignInClickEvent&gt;()<br>    private var viewModel: SignInActionChannels? = null</pre><pre>    override fun onCreate(savedInstanceState: Bundle?) {<br>        super.onCreate(savedInstanceState)<br>        setContentView(R.layout.activity_signin)</pre><pre>        email_sign_in_button.onClick {<br>            clickEventChannel.send(SignInClickEvent.SignInButton)<br>        }<br>    }</pre><pre>    override fun onResume() {<br>        super.onResume()</pre><pre>        viewModel = signInPresenter(clickEventChannel)</pre><pre>        launch(UI) {<br>            viewModel?.signInActionChannel?.let {<br>                for (signInAction in it) {<br>                    when (signInAction) {<br>                        SignInAction.SignInSuccessful -&gt; {<br>                            toast(&quot;Sign In Success!&quot;).show()<br>                        }<br>                    }<br>                }<br>            }<br>        }<br>    }</pre><pre>    override fun onPause() {<br>        super.onPause()<br>        viewModel = null<br>    }<br>}</pre><p>In hindsight, this had some nasty pitfalls. In the example above we were just throwing away our channels instead of properly cancelling the coroutines we were using.</p><p>Let’s take a look at an updated version utilizing CoroutineScope. This will allow us to easily track and manage our presenter coroutines:</p><pre>class SignInActivity() : AppCompatActivity(), CoroutineScope {</pre><pre>private lateinit var job: Job</pre><pre>override val coroutineContext: CoroutineContext<br>        get() = job + Dispatchers.Main</pre><pre>private val clickEventChannel = Channel&lt;SignInClickEvent&gt;()</pre><pre>override fun onCreate(savedInstanceState: Bundle?) {<br>        super.onCreate(savedInstanceState)<br>        setContentView(R.layout.activity_signin)</pre><pre>job = SupervisorJob()</pre><pre>email_sign_in_button.onClick {<br>            clickEventChannel.send(SignInClickEvent.SignInButton)<br>        }<br>    }</pre><pre>override fun onResume() {<br>        super.onResume()</pre><pre>launch {<br>            signInPresenter(clickEventChannel).signInActionChannel.let {<br>                for (signInAction in it) {<br>                    when (signInAction) {<br>                        SignInAction.SignInSuccessful -&gt; {<br>                            Toast.makeText(this@SignInActivity, &quot;Sign In Success!&quot;, Toast.LENGTH_SHORT)<br>                                    .show()<br>                        }<br>                    }<br>                }<br>            }<br>        }<br>    }</pre><pre>override fun onPause() {<br>        super.onPause()<br>        coroutineContext.cancelChildren()<br>    }<br>}</pre><p>There are a few items of note in this new example. First, our SignInActivity is now implementing CoroutineScope. Because of this, we now need to override coroutineContext in order to provide a coroutineContext for our activity.</p><p>We can now take advantage of calls to coroutine builders such as launch which will automatically use the proper coroutine scope. Further there is now a cascading effect on our presenter functions. Any function that utilizes these builders will all be tracked together via one coroutine scope.</p><p>Let’s take a look at our updated presenter function:</p><pre>fun CoroutineScope.signInPresenter(clickEventChannel: ReceiveChannel&lt;SignInClickEvent&gt;): SignInChannels {<br>    val signInActionChannel = Channel&lt;SignInAction&gt;()</pre><pre>    // We don&#39;t want our presenter running on the main thread<br>    launch(Dispatchers.IO) {<br>        for (signInClickEvent in clickEventChannel) {<br>            when (signInClickEvent) {<br>                SignInClickEvent.SignInButton -&gt; {<br>                    // Do some real sign in, for the example we will just delay<br>                    delay(timeMillis = 1000)<br>                    signInActionChannel.send(SignInAction.SignInSuccessful)<br>                }<br>            }<br>        }<br>    }</pre><pre>    return SignInChannels(signInActionChannel)<br>}</pre><p>The major change here is that our presenter function is now an extension function on CoroutineScope. This allows us to call signInPresenter from classes implementing CoroutineScope. This will launch our signInPresenter in the scope of its caller, so we&#39;ll get automatic propagation of scope cancellation from our activity. Another way to implement this is to provide a CoroutineScope as a parameter to signInPresenter. After evaluating these two patters internally we chose the first option.</p><p>I hope this was a useful update to my previous post on Presenter as a Function, and sheds light on how the updates brought along with Kotlin 1.3 and Coroutines 1.0 have really improved our ability to manage our coroutine jobs.</p><p>You can see the updated code <a href="https://github.com/rocketwagon/android-paaf/tree/kotlin_1_3">here</a>.</p><p><em>Original post on </em><a href="http://bit.ly/PaaF_Structured"><em>rw.co/our-thinking</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27ecfd47b7c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Will Your Organization Die at the Connected Chasm?]]></title>
            <link>https://medium.com/@rocketwagon/will-your-organization-die-at-the-connected-chasm-ba2437e874fb?source=rss-c20cdef0c4a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba2437e874fb</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[industry-4-0]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[disruption]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Rocket Wagon]]></dc:creator>
            <pubDate>Tue, 05 Feb 2019 19:35:34 GMT</pubDate>
            <atom:updated>2019-03-04T17:02:29.873Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7S0mQ2yPkI1fYd8A2fAjkw.gif" /></figure><p><strong>Since the introduction of mainframe computing in the 1950s, progressive waves of technological innovation have shaped — and reshaped — the landscape in every industry. Yet the changes precipitated by advances in mobile, internet, and PC technology will pale in comparison to today’s “connected tech” wave.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YeGsoCEWpIsAvNi9XetMTQ.png" /></figure><blockquote>DEFINITION</blockquote><blockquote><em>Internet of Things refers to the interconnection of physical objects (“things”) which use internet connectivity, sensors, actuators, or other embedded electronics to send and receive information.</em></blockquote><h3>Ride the IoT Wave, or Get Crushed By It</h3><p>For one thing, the scale of this wave is different; tsunami might be a better analogy. There are estimated to be over <a href="https://www.gartner.com/newsroom/id/3598917">11 billion devices</a> connected to the internet today compared to 6 billion just two years ago. Gartner predicts 20 billion connected devices by 2020, as the pace of adoption accelerates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/667/1*gvN39zcijKOzXP7fOMGhBw.png" /></figure><p>At the same time, S&amp;P 500 corporate turnover (a proxy for corporate longevity) is increasing according to <a href="https://plus.credit-suisse.com/rpc4/ravDocView?docid=EGovVG">Credit Suisse reports</a>. The need to innovate has never been more urgent or more critical to survival as connected technology drives <a href="https://www.investopedia.com/terms/c/creativedestruction.asp">creative destruction</a> across industries. Those without a strategy to ride the IoT wave will be crushed by it.</p><h3>Look Before You Leap</h3><h4>Before strategy, spend time on vision; if you use the wrong lens the results can be devastating.</h4><p>Take Kodak as an example of a company that failed to navigate the previous waves of technological change. At its height the company owned <a href="https://www.forbes.com/sites/tendayiviki/2017/01/19/on-the-fifth-anniversary-of-kodaks-bankruptcy-how-can-large-companies-sustain-innovation/#4b82b8316280">80% of the market for its core business</a> (film) and even invented the technology (digital cameras) that led to its demise. Kodak did not fail to realize the forces of disruption or fail to invest in innovation. It failed to ask the right questions. Rather than use digital technology to promote sharing of “Kodak moments”, the company instead focused on encouraging consumers to print digital photos in an effort to protect its film-based business model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EjAnHaZdJs2bdmH9J7ALGQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/TzCiYbV2COs?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Camille Minouflet</a> on <a href="https://unsplash.com/search/photos/camera-film?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Though the company survived it’s 2012 bankruptcy filing, it is a shadow of its former self, a victim of incrementalism. Compare this protectionist strategy with Lego, a company which began as a wooden toy business over 80 years ago. Instead of asking how it could protect its core business during a difficult period in the early 2000s, it asked a much different question: What if plastics were banned in five years? Focusing on a radically different vision for its future gave Lego broad latitude to think “beyond product” (and beyond retail) to pursue a wide variety of revenue sources including e-commerce, film production, digital platforms for children, and robotics. This strategy led to double-digit growth for much of the last decade, and Lego is now (as of 2017) the world’s largest and most profitable toy manufacturer, as well as the world’s.</p><h3>Crossing the Connected Chasm</h3><p>It takes more than vision to succeed, of course. Companies that want to capture their share of the <a href="https://www.accenture.com/t20170302T235159Z__w__/us-en/_acnmedia/PDF-44/Accenture-Connected-Business-Online.pdf">$14 trillion</a> that is projected to be added to the global economy by 2030 must first cross the “connected chasm”. And that requires a mindset shift. Companies must move beyond a traditional “revenue per unit sold” mentality to understand that data generated by a connected product or system of connected products may be more valuable than the product itself. Without this understanding, companies produce limited results and don’t build traction towards a vision. They get stuck at the chasm.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZPWwmBP5pxg7LH30vaQvXQ.jpeg" /></figure><p>Getting in the right mindset is about looking holistically at the transformational opportunities connected devices represent. Opportunities to get real time intelligence about your supply chain, your products, your sales process, even your customers themselves. Once you’ve taken the time to understand the full potential of IoT and the new ways of business enabled by the technology, your first project should take you towards that vision.</p><blockquote><em>RELATED</em></blockquote><blockquote><em>In </em><a href="https://www.amazon.com/Crossing-Chasm-3rd-Disruptive-Mainstream/dp/0062292986"><em>Crossing the Chasm</em></a><em>, Geoffrey A. Moore describes the chasm as the gap between early adopters and the early majority in the technology adoption lifecycle.</em></blockquote><h3>Taking the Right First Steps</h3><p>If you have the right vision and the right mindset, don’t worry if the connection between the first project and the vision is not immediately obvious to an outsider.</p><p>Take SpaceX as an example. The company designs, manufactures and launches advanced rockets and spacecraft with a goal of enabling people to live on other planets. With that vision set, they evaluate smaller projects against that goal. While the media is talking about a Tesla getting launched into space on the Falcon Heavy rocket, SpaceX is thinking about how a <a href="https://www.spacex.com/falcon-heavy">rocket capable of carrying a large payload</a> can be used to ship supplies over long distances (like to Mars.) While Chicago hires The Boring Company to build a high speed train to O’Hare International Airport, Elon Musk learns how to construct <a href="https://www.boringcompany.com/faq/">a large network of tunnels</a> so colonists can live underground (on another planet.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1kmOPkcH5w4IjcqmWMdcyQ.jpeg" /><figcaption>Source: SpaceX</figcaption></figure><p>Whatever your vision, this is no longer the time to weigh options and analyze. The pace of change and IoT adoption is accelerating. This is the time to set your vision, get in the right mindset, and take the right first step.</p><p><em>This article was originally posted on Rocket Wagon’s website: </em><a href="https://rw.co/our-thinking/will-your-organization-die-at-the-connected-chasm/"><em>https://rw.co/our-thinking/will-your-organization-die-at-the-connected-chasm/</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba2437e874fb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Want to Be The Next Victim of Digital Disruption?]]></title>
            <link>https://medium.com/@rocketwagon/want-to-be-the-next-victim-of-digital-disruption-32d18a5132e4?source=rss-c20cdef0c4a1------2</link>
            <guid isPermaLink="false">https://medium.com/p/32d18a5132e4</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[disruption]]></category>
            <category><![CDATA[digital-disruption]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Rocket Wagon]]></dc:creator>
            <pubDate>Thu, 11 Oct 2018 19:52:20 GMT</pubDate>
            <atom:updated>2018-10-11T19:52:20.280Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://rw.co/leadership/bill-seibel/">Bill Seibel</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/634/1*5bkENvw_eEOJzKqhu3UUPw.jpeg" /></figure><p>In today’s global, complex, diverse, and fast-moving business world, it’s difficult to find any one thing that a majority of CEOs agree on. And yet, <a href="https://www.delltechnologies.com/en-us/press/unveiling-the-digital-transformation-index.htm">a Dell survey of 4,000 senior business leaders succeeded</a>. Their research found 78% of C-level decision makers believe digital startups will pose a threat to their organization now or in the near future.</p><p>Is that a rational fear? How many ‘disruptors’ can you name? Netflix, Amazon, Uber, and Airbnb immediately come to mind. And the ‘disrupted’ are also well known — Kodak, Blockbuster, Tower Records, Wang… You can probably recall a handful of others. But is the list long enough to cause entire executive suites to lose sleep and spend billions of dollars? Should the risk and/or the potential of digital disruption warrant a prominent place on every CEO’s agenda?</p><p>In analyzing the tenure of S&amp;P 500 companies, I hoped I might find an answer to these questions. The S&amp;P 500 began tracking stocks in 1923. Economists have long considered it a bellwether of the U.S. economy, and a leading indicator of business cycles. I hypothesized that the amount of churn in membership would serve as an indicator of business disruption. For example, if three companies were replaced in one year, and ten businesses in the next, then disruption was increasing. An <a href="https://www.innosight.com/insight/creative-destruction/">innovation consulting firm called Innosight</a> had already gathered the data I was looking for:</p><ul><li>In 1958 the average tenure of an S&amp;P 500 company was 61 years;</li><li>By 1980, it narrowed to 25 years;</li><li>Today, it’s 18 years;</li><li>And by 2027, if current churn rates continue, 75% of the current S&amp;P 500 will be replaced.</li></ul><h3>Finding the Source of Disruption</h3><p>Evidently, businesses are being disrupted. And the pace of disruption is increasing. But where is it coming from?</p><p>I found the answer in research conducted by CB Insights, who created a <a href="https://www.cbinsights.com/research/industry-market-map-landscape/">telling Market Map</a>landscape of companies across a wide range of industries. A Market Map lists all of a company’s products and services and then identifies all the startups that are attacking each one of them. Every example shows what happens when a company ‘unbundles’ their products and services. There will be dozens of well-funded startups, each experimenting with a new business model, with a team that is working around the clock, dedicated to disrupting one small segment of that company’s business. Disruption does not have to come hard and fast, like Uber and Airbnb. More often it comes as death by a thousand cuts.</p><p>There is a wealth of supporting data here. Dell’s survey of business leaders also reveals that 62% have already seen new competitors enter the market as a result of the emergence of digital technology. Gartner adds that <a href="https://www.gartner.com/newsroom/id/3142917">125,000 large organizations are now launching digital business initiatives</a> and that CEOs expect their digital revenue to increase by more than 80% by 2020. Digital disruption <em>is</em> real. CEOs’ fear of digital startups is rational. Responsible business executives can no longer adopt the “<em>Don’t Worry, Be Happy”</em> attitude.</p><p>Once this disruptive reality is confronted, how should CEOs respond? Reportedly, 63% did by appointing a Chief Innovation Officer, or a VP of Digital Disruption. I interviewed 20 newly anointed innovation executives, and found:</p><ul><li>None had clear goals or defined objectives;</li><li>None of them had yet to <em>find</em> a business sponsor;</li><li>None of them controlled a budget large enough to even begin to explore a new initiative;</li><li>And all of them agreed, “We have no clear path to follow to create a new vision.”</li></ul><p>No goals. No sponsors. No funds. No clear path to developing a vision. Appointing a Chief Innovation Officer alone is not a sufficient strategy. It’s simply kicking the <em>digital disruption can</em> <em>down the road</em>.</p><p>CEOs also responded by initiating a formal digital transformation initiative of some form. <a href="https://www.forbes.com/forbesinsights/hds_digital_maturity/">Forbes Insights surveyed 573 global business leaders</a> and found 90% of them did just that. But Forbes goes on to say the majority (84%) of these programs have failed to generate the desired results.</p><p>This reminds me of the beginning of the mobile technology wave. In 2010–2011, most large enterprises developed a mobile strategy. In many instances, CEOs acted because they felt pressured by their boards, customers, and employees to ‘do something.’ Creating a mobile strategy checked the I’m-doing-something box while avoiding the investments, risks, massive changes, and long-term focus characteristic of true business transformation. Some enterprises skipped the strategy phase altogether. Instead, they ‘innovated’ by conducting experiments and proofs-of-concept. These ‘Random Acts of Mobile’ rarely generated any real business benefits.</p><p>Other CEOs were intrigued by the potential of mobile as a platform to run their business, and potentially transform the way it’s conducted. They defined clear objectives, made the required investments, and successfully executed the projects that emerged. Two examples of getting it right:</p><ul><li>Panera transformed its in-store experience and launched a highly profitable catering business. That led to their acquisition by JAB for $7.5B.</li><li>The ‘patent cliff’ that lay ahead for its Abilify schizophrenia drug created a tremendous sense of urgency for Otsuka Pharmaceutical. Their leadership believed that even though the drug would become generic, they could create a smart pill to differentiate Abilify from low-priced competitors. In November 2017, the FDA approved Abilify MyCite as the first trackable digital medicine.</li></ul><p>Deciding to be a digital disruptor requires unwavering leadership and a tremendous amount of courage. A CEO must be willing to commit to significant investments and to embrace both change and risk failure — even when the business impacts may not be fully felt until their successor is in place. No wonder it’s so easy to kick the <em>digital disruption can</em> down the road.</p><h3>The Four Easy Rules</h3><p>To summarize, <em>four easy rules to follow to become a victim of digital disruption</em>:</p><ol><li><strong>Don’t Worry. Be Happy</strong>. Business disruption is real, and it’s accelerating. It seldom comes hard and fast, like Uber. Instead, it targets segments of a company’s products and services and presents itself as death by a thousand cuts. CEOs can decide to be either a disruptor or a defender. Both strategies are viable. Both require unbundling an enterprise’s products and services and exploring how innovation can impact each.</li><li><strong>If we launch a formal program, innovation will come.</strong> In 84% of cases, these initiatives fail. Take a reactive, near-sighted approach if you’d like to make like the unsuccessful majority.</li><li><strong>Kick the Can Down the Road</strong>. Appoint a VP of Innovation or a VP of Digital Disruption without defining goals or objectives, assigning a business sponsor, or providing sufficient funding.</li><li><strong>Approach Business Transformation as a <em>Random Act of Innovation</em></strong>. It’s a safe bet you won’t transform your business with a suggestion box complete with t-shirt prizes for ‘winning’ ideas. And it’s not about an innovation lab tucked away in the corner, equipped with a foosball table and free snacks, either. It’s about being one of the CEOs who understands the long-term focus, investment, patience, focus and commitment that success in digital disruption demands.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/336/1*ZlMDNwatRt7Dp6ABd1bPoQ.jpeg" /><figcaption>Bill Seibel is Executive Chairman of Rocket Wagon. Previously, Bill was the Founder and CEO of Mobiquity. In four years, Mobiquity grew to 600 employees across twelve offices in four countries — making it the fastest growing and one of the largest mobile professional services firms in the world.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=32d18a5132e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>