<?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 Isa Ette on Medium]]></title>
        <description><![CDATA[Stories by Isa Ette on Medium]]></description>
        <link>https://medium.com/@isa_ette?source=rss-8e333230185d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*04jZzsqq4Qgd6wYh_ZDDSw.jpeg</url>
            <title>Stories by Isa Ette on Medium</title>
            <link>https://medium.com/@isa_ette?source=rss-8e333230185d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 11:24:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@isa_ette/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[Jumpstart with AI, wherever you are]]></title>
            <link>https://medium.com/@isa_ette/jumpstart-with-ai-wherever-you-are-3c5bdb3c32f?source=rss-8e333230185d------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c5bdb3c32f</guid>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Isa Ette]]></dc:creator>
            <pubDate>Mon, 18 Mar 2019 13:45:52 GMT</pubDate>
            <atom:updated>2019-03-21T10:09:26.747Z</atom:updated>
            <content:encoded><![CDATA[<h4>My overly short strategy recommendation</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3DGBah5h8TmewU0qoT1_1w.jpeg" /></figure><p>The following is based on a talk originally prepared for the AI-Mondays event series in Berlin, March 2019.</p><p><em>Disclaimer: At iX we work for IBM’s clients and function as IBM’s inhouse digital agency. This is how I came to be interested in the application of AI and it’s impact on companies’ business strategy. All views expressed are my own. I look at a company’s digital portfolio as a strategic asset — technical feasibility, the pros and cons of implementation, are discussed elsewhere.</em></p><p>At iX, we help our clients to establish the work practices to build and develop digital products at scale, often including AI-components. Many companies struggle with the task of including AI in their processes and digital services. Yet the problems they face on the way do not originate in technical feasibility. What we see is that inconsistency of investment decisions and dedication of means to the digital portfolio that inhibits companies from reaching their digitization goals. (For those who do not want to read on, my further argument can be summed up as “avoid that digital products be built in isolation and silos”.)</p><blockquote><strong>It’s the lack of orchestration, investing in singular initiatives that stand in isolation, what hampers companies’ success in applying AI for real.</strong></blockquote><p>Before embarking on an AI initiative, companies must understand which technologies perform what types of tasks.<strong> </strong>Breaking things down a lot, we can distinguish three <a href="https://hbr.org/2018/01/artificial-intelligence-for-the-real-world">fields of AI application</a>:</p><p>1) <strong>Robotic Process Automation (RPA)</strong></p><p><em>what? </em>automation of digital and physical tasks = consuming and merging information from multiple IT systems</p><p><em>popular use cases</em>: change in customer data across data bases (no human intervention needed)</p><p>2) <strong>Cognitive Insight</strong></p><p><em>what?</em> Prediction = use of algorithms to detect patterns in big volumes of data and interpret their meaning</p><p><em>popular use cases</em>: image recognition, speech recognition, probabilistic matching</p><p>3) <strong>Cognitive Engagement</strong></p><p><em>what?</em> Engaging with employees or customers via AI-powered means</p><p><em>popular use cases</em>: 24/7 customer service, intelligent agents, smart routing</p><p>A combination of all three types is thinkable, e.g. if there is an AI-powered aftersales service that forwards the most difficult quests to a human sales rep (Cognitive engagement) but can perform standard actions, say a change of address, automatically (RPA), plus accepts input via speech in various languages (Cognitive insight). All this seems powerful and promising, all the building blocks are there. <strong>Still, there is much more talking about AI than actual AI-empowered products and services out there. Why is that?</strong></p><p>Surely part of the answer lies within that any digital product that includes AI- elements is a compromise. It’s a function of time and money, the quality of data at hand and conceptual decision-making — not just regarding one singular initiative but the overall strategic course of an organization regarding its digital portfolio.</p><h4>Data Quality, Data Bases and Data Curation</h4><p>When building AI-driven services or products, the way data is collected and stored, is super important. A company’s available data sets usually are composed of proprietary data mixed with externally acquired data. Data sets are the core ingredient to AI-based services and therefore must be well-curated, no matter which digital products or services are already existing, which are currently under development or at planning stage. Even if there is no service with AI components to-day, working for the availability of the data is a save bet and a viable way to start any AI-journey.</p><p>First step is to set up the data bases — permissions, accessibility, curation, storage — in an integrated form. From a management perspective, that means specifically working on</p><ul><li><strong>Accessibility </strong>Can the right people access what they need to access? Is <a href="https://www.cs.cmu.edu/~jasonh/courses/ubicomp-sp2007/papers/05-privacy-principles.pdf">personal data sufficiently protected</a>?</li><li><strong>Unification of systems</strong> How can internal systems be unified? How can seamless communication be warranted?</li><li><strong>Data integrity </strong>Is the current setup compliant<strong> </strong>with <a href="https://eugdpr.org/the-regulation/">regulation</a>? What about data ethics’ considerations?</li><li><strong>Scalability</strong> What to do if demand grows over time? Is the underlying architecture fit to be altered in part if necessary?</li><li><strong>Interoperability </strong>How can different systems be bridged? Where could the provision of APIs be helpful (for us and others)?</li></ul><h4>Business strategy &amp; AI</h4><p>The above considerations are rather uncontroversial: you need the right data, properly stored and curated in order to work with AI. Once well-cared for data bases are in place, companies still need to figure how to start with AI applications and <em>what</em> to build and invest in.</p><p>In connection to the quality and complexity of the data basis at hand, several concepts involving data and AI-elements come to mind. For <em>The IBM Automotive Playbook </em>(excerpt to be found <a href="http://ai-monday.berlin/wp-content/uploads/2019/03/Automotive_Playbook_sneakpeek.pdf">here</a>) we created a graph that represents the different stages of development towards an AI-driven digital service portfolio. We visualized it as a journey, with steps to be followed from left to right.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cSU62RAZDDfPlj2iJmpTiQ.png" /><figcaption>The IBM Automotive Playbook, page 26/27</figcaption></figure><p><strong>Data as a Service </strong>— If you and your company are just starting off with AI/data-driven services you should seek to build a sustainable data basis first. From there you might consider simply selling raw data. Next step would be to process, possibly merge and enrich the data and sell it in this more advanced version. About here, AI first comes into play: if the curated, merged and enriched data is analyzed, AI is actually applied.</p><p><strong>Data as Enabler</strong> — If the relevant data bases are in great shape and you have gained experience, deriving relevant insights from AI-based analysis, changes to the company’s operations and internal processes can be considered. In all probability, there is many areas where AI-generated summaries, pointers or connections can help to improve business-as-is. If that in turn has been applied successfully, you can start to rework customer facing solutions.</p><p><strong>Data Ecosystem</strong> — Lastly, if there is both experience with AI regarding customer touchpoint management and internal process automation in the company, AI can be the enabler to reshape value chains and ecosystems. This is when the organisational structure of the company or several market players (ecosystem) is reframed to accommodate AI fully, which may lead to new business. Understandably, the invest required and the business potential grow with more complex endeavors, as is indicated in the graph.</p><p>From what we see with our clients, it is not advisable to try to jump into an overly ambitious project involving AI from scratch, that is, without a clear vision and a bullet-proof data basis. Such attempts will be pricey and eventually not work out as intended. Pushing singular initiatives involving AI without an overarching strategy, of which every project is a step towards a defined objective, does not pay off. Instead, this approach recreates the siloed organisational nature, that companies seek to shed in the course of Digital Transformation and that inhibits innovative development.</p><blockquote>In order to apply AI company leads need to think longer term. Investing in preconditions early, such as well-maintained data bases, and following a company-wide AI-strategy is proper groundwork for AI-application.</blockquote><h4>Take-away</h4><p><strong>What?</strong> Think about the way you curate and store the data relevant to your business and (prospective/future) digital products or services. Working conceptually on the design of new digital business that is in accordance with your company’s level of digital capability is what you can start with today.</p><p><strong>Why?</strong> It’s a safer and much more sustainable approach to grow a company’s AI-powered ecosystem and digital portfolio carefully and with due time. Strive for organic development in your digital portfolio in order to prepare the ground for value creation via AI.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c5bdb3c32f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI & microwaves: let’s star the manual]]></title>
            <link>https://medium.com/aperto-an-ibm-company/ai-microwaves-lets-star-the-manual-de237c0f2d72?source=rss-8e333230185d------2</link>
            <guid isPermaLink="false">https://medium.com/p/de237c0f2d72</guid>
            <category><![CDATA[business-design]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Isa Ette]]></dc:creator>
            <pubDate>Fri, 30 Nov 2018 14:27:59 GMT</pubDate>
            <atom:updated>2018-12-10T06:42:36.073Z</atom:updated>
            <content:encoded><![CDATA[<p>Why user friendliness and applicability are not the same thing</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*k3UEzwv1lRcV9FKVjAH1iA.jpeg" /></figure><p>Cassie Kozyrkov moves onstage with the ease of a veteran presenter. Chief Decision Scientist at Google Cloud, she has given her lecture “<em>Decision Intelligence / ML ++</em>” already numerous times (<a href="https://www.youtube.com/watch?v=iLu9XyZ55oI">watch it here</a>). At Data Natives 2018 in Berlin, her call for engaging with machine learning (ML) algorithms playfully is a standalone event with one key message:</p><blockquote><em>You don’t have to know how a microwave works. You just want to use it to cook. ML is just like that.</em></blockquote><p>There is a murmur, eyebrows lifting, then frowns relax over Cassie’s melodic speech. Her talk and person are incredibly likeable but has me wonder — is her enthusiasm for the opportunities that ML provides to laymen actually genuine? And is her message, coming from Google, not somewhat incomplete?</p><p><strong>To code or not to code</strong></p><p>The <a href="https://datanatives.io/">Data Natives conference</a> attracts professionals who deal with data on code level, mostly developers and data scientists. As designers, my colleague and I formed a minority. Although the call to “just play around with ML” is highly appealing to non-coding Mugglers, I want to argue that the matter is not quite as simple as Cassie puts it.</p><p>As she explains in her talk, and we may all agree, the building-microwaves-from-scratch focus in public education for ML is not preparing interested parties to navigate ML-application. With its new ML service offering on Cloud, Google now seeks to provide all the “ingredients to cook” with the “microwave” it offers in tune. Selling point: users don’t have to bother about the application’s inner workings but just get started.</p><p><strong>Democratizing machine learning</strong></p><p>Using the Google Cloud ML Engine, everyone can “make algorithms learn from example”, Cassie further explains, which is, no doubt, easier than writing code for a certain purpose. However, Cassie’s analogy can be used to illustrate the risks of democratizing ML-application just as well: For microwaves, instructions have been written that advise the public to e.g. not put things in that do not belongthere (metal, living creatures etc.). With the new offering that Cassie markets, people that are not very familiar with AI-based technologies on a theoretical level are enabled to apply ML to their liking. Which is great, but:</p><blockquote><em>Offering this service without clear instructions of what not to put in the system and how to interpret and classify the results seems shortened rather than empowering.</em></blockquote><p><strong>More hints and doubts</strong></p><p>Pointing out, as Cassie does, that the decision-making process of humans is highly obscure and therefore no one is to be trusted more or less than Google’s AI is false equivalence to my ears. Also, her choice of expression, encouraging users to seize the opportunity to “tinker” and “fiddle with” the ML-algorithm on Google Cloud, seems indicative of a lack of foresight.</p><p>There is evidence that playful engagement and open-sourcing of new technologies can be a means to crowd-sourced innovation and finding application niches. Still, it is abbreviated (and, in the light of people’s dealing with microwaves, unwise I may add) to just create a new offering and then to point to its general application friendliness rather than investing effort in the service’s theoretical embedding. In this case, e.g. by defining and excluding use cases and creating supporting educational material for the application of Google Cloud’s ML engine.</p><p><strong>Conclusion</strong></p><p>What should we take from Cassie Kozyrkov’s talk? I suggest it be that making technology accessible to people does not suffice. Those who take decisions, who build complex services and products to which AI or ML are building blocks, need to be familiar with the application <em>and </em>the applicability of relevant technology.</p><p>Therefore, designers’ abilities are called for more than ever. I hold that they are needed to set application boundaries conceptually and write proper manuals for ML.</p><p><strong>Read on</strong>: Jess Holbrook and Josh Lovejoy’s<a href="https://medium.com/google-design/human-centered-machine-learning-a770d10562cd"> article on Human-Centred Machine Learning</a> (published via <a href="https://medium.com/google-design">Google Design</a>) makes a case for designing for ML environments bearing the human factor in mind.</p><p><strong>Kudos</strong> for inspiration and bringing me to #dn18<strong> </strong>go to my colleague und co-author <a href="https://medium.com/u/76c22af730a4">Thomas Otto</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de237c0f2d72" width="1" height="1" alt=""><hr><p><a href="https://medium.com/aperto-an-ibm-company/ai-microwaves-lets-star-the-manual-de237c0f2d72">AI &amp; microwaves: let’s star the manual</a> was originally published in <a href="https://medium.com/aperto-an-ibm-company">Aperto Stories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>