<?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 BasisAI on Medium]]></title>
        <description><![CDATA[Stories by BasisAI on Medium]]></description>
        <link>https://medium.com/@basisai?source=rss-fab5599ab0c3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*EUpVab9FvW9-sTLQLuyu2Q.png</url>
            <title>Stories by BasisAI on Medium</title>
            <link>https://medium.com/@basisai?source=rss-fab5599ab0c3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:45:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@basisai/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[These Anti-Patterns are Slowing AI Adoption in Enterprises in 2020]]></title>
            <link>https://ai.plainenglish.io/these-anti-patterns-are-slowing-ai-adoption-in-enterprises-in-2020-b3b3406bbe71?source=rss-fab5599ab0c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3b3406bbe71</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[mlops]]></category>
            <category><![CDATA[antipattern]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[BasisAI]]></dc:creator>
            <pubDate>Tue, 14 Apr 2020 03:08:17 GMT</pubDate>
            <atom:updated>2020-04-21T07:47:44.989Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Anti-Patterns" src="https://cdn-images-1.medium.com/max/1024/1*d3W1Zc2tZna86HFadVbWog.jpeg" /></figure><p>Claims about the promise of artificial intelligence (AI) to deliver real-life business benefits are abundant. By performing functions that enable hyper-personalisation of the customer experience, or optimisation of assets utilisation by harnessing sensor data, AI can augment business processes and capabilities exponentially. Yet adoption of AI at enterprise level has been slow, with many organisations across different industries facing foundational barriers in generating value from AI at scale.</p><p>In a McKinsey global survey on the adoption of AI*, only one-fifth of respondents report embedding AI into multiple business units and functions successfully. At <a href="https://basis-ai.com/">BasisAI</a>, we have seen many enterprises find it difficult to go beyond the experimental or pilot stage. One critical challenge is the presence of <em>anti-patterns</em> in enterprise AI strategy, which ultimately slow adoption and harm the path to scalability.</p><h3>What is an anti-pattern and what effect does it have on enterprise AI strategy?</h3><p>Anti-patterns are the opposite of design patterns which serve as common, effective and reusable solutions to a problem. In software development, design patterns help to design object-oriented software, but patterns that are considered bad software development practices are referred to as anti-patterns. In a business context, this translates to a pattern of behaviours or processes which might produce quick results in the short term but have a fundamentally negative effect on an organisation’s ability to generate material impact and scale in the longer term.</p><p>According to the authors of Design Patterns*, there must be at least two key elements present to formally distinguish an actual anti-pattern from a simple bad habit, bad practice, or bad idea:</p><ol><li>A commonly used process, structure, or pattern of action that despite initially appearing to be an appropriate and effective response to a problem, has more bad consequences than good ones.</li><li>Another solution exists that is documented, repeatable, and proven to be effective.</li></ol><p>To eliminate anti-patterns, we need to recognise them. We share four primary anti-patterns that slow the embedding of AI solutions into the organisational core:</p><h3>AI Superheros</h3><p>An <em>AI Superhero</em> is a member of the team who understands every aspect of the development and deployment of an AI system. This person has a broad range of skills, from machine learning research, software engineering, development operations, to project management. For specialised application domains, the AI Superhero may even have expertise in a specific field, such as finance or biotechnology.</p><p>Remarkably, this person can translate a business problem into a machine learning problem, and write the necessary code to scale the solution, making them a hugely valuable team member at the early stages of AI development.</p><p>But over-reliance on the AI Superhero can cause problems. Being highly sought after, he or she may leave the enterprise before internal capability is built. Or the business could scale up too quickly for the rest of the team to keep up. A simple solution to this problem is to hire additional employees, one for each of the AI Superhero’s skills. However, this is a time consuming and expensive process.</p><h3>Using a ‘Black Box’</h3><p><em>Black Box AI</em> is an artificial intelligence system whose inputs and processes are not visible to the user, as opposed to a bespoke solution that allows for explainable AI. Black Box AI is often a proprietary engine that is pre-trained, or one that makes use of an Application Program Interface (API) through business cloud services such as Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure. These solutions can be useful for generic cases, such as image classification or machine translation, where training data is vast and easy to acquire.</p><p>But the problem with Black Box AI occurs when the business context for your company differs greatly from the generic black box models that have been pre-trained. For example, if you need to process language that has local dialects or involves technical discussions, then natural language processing (NLP) models trained on general language, typically obtained from open information on the internet, is unlikely to work well.</p><h3>Throwing Models Over the Wall</h3><p>This anti-pattern develops when the segregation of employee skill-sets is too strong — the opposite of the AI superhero anti-pattern.</p><p><em>Here is a common scenario.</em></p><p>A machine learning researcher or data scientist builds a complex, functioning machine learning model. This is handed off to a machine learning engineer who refactors the code without fully understanding the mathematical intricacies. A DevOps engineer then containerises and deploys the application.</p><p>The model is now running at scale, but not as well as expected. The team comes together to solve the problem. But the machine learning researcher struggles to understand the refactored and containerised version of the original code. Debugging the model becomes very difficult. The model may be running slowly because it does not have access to sufficient computing power. Furthermore, issues with the model may not be immediately apparent to the DevOps engineer. Any issues that are flagged then need to be fed back to the machine learning researcher and there is often no clear process for how to monitor and feedback on model performance, an aspect of the machine learning development cycle which is critical to generating well-performing AI engines with the greatest predictive power.</p><p>The problem can be exacerbated when the development team does not use version control or document their code well. This makes it hard to interpret the code when a key member leaves the team, or when there is a bug, or a significant drop in model performance. Throwing models over the wall to DevOps teams is therefore often a primary reason why enterprises find it so hard to get machine learning applications into production.</p><h3>Quick Wins</h3><p>The promise of quick wins in AI adoption needs to be tested against the path to scalability. In the interest of time, AI solutions are often developed by a data scientist. The AI solution may work well on the data scientist’s laptop, but it is unlikely to work at enterprise-level. When machine learning occurs in a vacuum, it can slow down the incorporation of the AI solution, ultimately limiting its business impact.</p><p>What this might look like is a data scientist building an end-to-end pipeline in a Jupyter Notebook. The notebook can perform data acquisition, preprocessing, model training and validation on a small subset of data. It uses non-scalable data frameworks such as R dataframes or Pandas. While this notebook may produce desirable results, its technical debt is very high because it is not compartmentalised and needs to be run in a specific sequential order. This often requires extensive refactoring to make it more robust to changes in the data structure. This approach may be good for prototyping, but the lack of scalability requires a significant time investment before deployment.</p><h3>How to avoid anti-patterns in scaling enterprise AI</h3><p>To help circumvent these issues, we suggest four strategies. <em>Continue reading article at </em><a href="https://blog.basis-ai.com/anti-patterns-in-artificial-intelligence-strategy-adoption"><em>basis-ai.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3b3406bbe71" width="1" height="1" alt=""><hr><p><a href="https://ai.plainenglish.io/these-anti-patterns-are-slowing-ai-adoption-in-enterprises-in-2020-b3b3406bbe71">These Anti-Patterns are Slowing AI Adoption in Enterprises in 2020</a> was originally published in <a href="https://ai.plainenglish.io/">Artificial Intelligence in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Apple Card: Why enterprises need AI governance]]></title>
            <link>https://medium.com/@basisai/the-apple-card-why-enterprises-need-ai-governance-399c09f2ff53?source=rss-fab5599ab0c3------2</link>
            <guid isPermaLink="false">https://medium.com/p/399c09f2ff53</guid>
            <category><![CDATA[apple-card]]></category>
            <category><![CDATA[black-box]]></category>
            <category><![CDATA[ai-governance]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[BasisAI]]></dc:creator>
            <pubDate>Wed, 20 Nov 2019 07:41:40 GMT</pubDate>
            <atom:updated>2020-04-14T03:10:24.099Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Apple Card credit card, issued by Goldman Sachs. Image Credit: Unsplash" src="https://cdn-images-1.medium.com/max/1024/1*Oijzei6ArYgcJnvuVoi1Eg.jpeg" /></figure><p>Goldman Sachs is the latest in a series of high profile companies under scrutiny for developing AI algorithms with alleged implicit biases, such as gender or race discrimination. Do biases in these algorithms really exist? It’s certainly possible — yes — but because of the nature of the technology, we often can’t see into AI engines to know exactly what the drivers are behind certain outcomes. In this post we discuss why we continue to see bias issues within AI, what the “black box” is and how enterprises can employ AI governance and build trusted AI systems.</p><p>In this latest example, the Apple Card (issued by Goldman Sachs) appeared to be giving lower credit allowances to women, irrespective of credit rating. The concern surfaced in a <a href="https://twitter.com/dhh/status/1192540900393705474">string of recent tweets</a> authored by Tech entrepreneur and Ruby on Rails founder, David Heinemeier Hansson, claiming that his wife had received a credit limit 20x lower than his, despite her more favourable credit score. Goldman defended itself by saying that its “credit decisions are based on a customer’s creditworthiness and not on factors like gender, race, age, sexual orientation or any other basis prohibited by law” but without being able to say more, it eroded trust in the application of algorithmic decision making.</p><figure><img alt="Tweet by @DHH about wife’s credit worthiness" src="https://cdn-images-1.medium.com/max/1024/1*eynljR5fAFiTGAbSiXaNKw.png" /></figure><h4>How can bias creep into AI algorithms?</h4><p>Machine learning is about learning from past data and enabling decision automation. As a technology, artificial intelligence is neutral in the sense that it is a mathematical tool devoid of the kind of prejudice and emotional blindspots that drive human bias. But it is also blind to the fact that it may be inappropriate to use race or gender as a basis for awarding credit; to the algorithm, it is just another variable. Algorithms are <em>amoral</em> — it is the organisations and human beings that apply AI that run the risk of immorality.</p><p>The danger with black box systems is that unintended biases can creep in and remain unverified. With machine learning systems, one source of bias is the data used to train the algorithms which may well be a reflection of societal prejudices inherited by the algorithm. For example, if you are training predictive policing algorithms based on the historical arrest and conviction patterns of a police force already rife with institutional bias, the algorithm is simply going to inherit the existing bias.</p><p>Furthermore, powerful machine learning algorithms may mine and pick out underlying proxies that are highly correlated with the prohibited variable in a dataset (i.e. gender and race), even if the sensitive variable is omitted. Let’s apply this to a bank trying to train a model to assess credit worthiness. The bank may indeed have removed gender from the training dataset but if it kept in “maiden name”, for example, then the algorithm could pick up non-empty values in this variable as a proxy for being female. This is why models need to be audited regularly for implicit biases.</p><h4>In what ways are AI systems black boxes?</h4><p>It has become almost trite to say that AI systems are black boxes. But there are many reasons why they are, or why they appear that way to enterprises and their customers.</p><p>Firstly, deep learning and other advanced machine learning algorithms can be difficult to understand, even to practitioners. The nonlinearity and sheer number of features driving the models can be pretty overwhelming. We can visualise 2 or 3 dimensions and how 2 or 3 features might interact to generate a prediction, but it becomes hugely complex when you reach a hundred (or a million) of these features.</p><p>But it is not inevitable that deep learning models are inexplicable — methods do exist to allow us to peer into these black boxes. The interactive visualisation <a href="https://playground.tensorflow.org/#activation=tanh&amp;batchSize=10&amp;dataset=circle&amp;regDataset=reg-plane&amp;learningRate=0.03&amp;regularizationRate=0&amp;noise=0&amp;networkShape=4,2&amp;seed=0.79196&amp;showTestData=false&amp;discretize=false&amp;percTrainData=50&amp;x=true&amp;y=true&amp;xTimesY=false&amp;xSquared=false&amp;ySquared=false&amp;cosX=false&amp;sinX=false&amp;cosY=false&amp;sinY=false&amp;collectStats=false&amp;problem=classification&amp;initZero=false&amp;hideText=false">Tensorflow Playground</a>, gives you insight into what each neuron in the neural network is “thinking” and how those thoughts contribute to the final decision. Methods such as <a href="https://homes.cs.washington.edu/~marcotcr/blog/lime/">LIME</a> also allow us to understand which pixels are driving the decision of computer vision algorithms when they classify objects.</p><p>Secondly, for commercial reasons, providers of AI systems may prefer them to be black boxes. There can often be a good reason for wanting to prevent a client from learning about how the system works, for example, protecting intellectual property or avoiding <a href="https://openai.com/blog/adversarial-example-research/">adversarial attacks on the AI</a>. On the flip side, there may be no good reason at all, such as pretending that the black box is driven by sophisticated machine learning, when in fact it isn’t at all.</p><p>Thirdly, the absence of internal capability in enterprises can lead to black boxes. A solution provider can provide all the underlying code and data, but if the enterprise doesn’t have internal teams who can make sense of it, then it’s effectively a black box. It’s the lack of knowledge that creates the opacity.</p><p>The other phenomena we see is how, with internally developed solutions, the lack of the right process can lead to black boxes. AI scientists are often not trained as software engineers and are unfamiliar with checking their code into Git, which maintains robust version control of code. And to add to the complexity, machine learning engines have many more elements to keep track of than just code, not limited to: training data, model parameters, details about how the predictions are served and presented to other systems. Most organisations don’t have a systematic platform that helps maintain a robust digital audit trail and, more importantly, a process that enables error detection and the ability to take action to fix or rollback a model when mistakes happen.</p><h4>Towards responsible artificial intelligence</h4><p>In order to create trust in the use of AI systems, it is not enough to treat these systems as an ‘intelligent’ black box, satisfied with knowledge of the inputs and outputs of a machine learning model, without the internal workings. Robust AI engines require oversight, ongoing monitoring and compliance. Ultimately, it is up to humans to ensure that machine learning systems are put to good use and are accountable.</p><p>Cases such as the Apple Card are continually raising the profile of the issue surrounding big tech and AI governance. Fintech companies, among many other industries, are employing an increasing number of practical uses of machine learning, including credit risk and evaluation. But the need for governance and explainability is becoming more and more pertinent as consumers demand to know how and why “unfair” or incorrect decisions are being made about important things in their life such as credit worthiness.</p><p>‘AI governance’ might be becoming the next term on your buzzword bingo card but the reality is that business use of AI has grown by 270%* in the last 4 years, at a much faster rate than the employment of strategies by companies to safeguard against machine learning mishaps. The term refers to the ability of an organisation to ensure that their decision-making algorithms work as intended, continuously and throughout their use.</p><p>For enterprises, this means:</p><ul><li>Oversight: the ability to continuously track the performance of the entire multitude of AI systems on metrics that matter to the organisation, including accuracy which drives business outcomes, and bias which ensures ethical responsibility</li><li>Maintainability: the ability to identify when things go wrong, to be able to quickly diagnose and fix these mistakes</li><li>Auditability and explainability: the ability to analyse, trace and investigate drivers of how decisions are made</li><li>Enable trade-offs: Governance issues inevitably involve judgement, but a well-governed system has the means to surface key information to enable senior decision makers to make trade-offs in their decision making, and execute them across the organisation. For example, the ability to systematically generate fair, unbiased models, and quantify the fairness and resultant loss of profit.</li></ul><h4>So how can enterprises employ AI governance?</h4><p>The good news is that governance is possible and the “black box” can be opened up. Plus, there are a number of ways in which companies can implement robust governance in their AI practises. We’ve summarised 4 key strategies to consider in responsible AI application:</p><ol><li><strong>Build core teams that can take ownership of your AI decision-making systems while retaining control on your data</strong></li></ol><p>Too many organisations see AI systems as a commodity or a widget that is universally applicable. But decision-making more often than not needs to be contextualised to your business. Be very careful when using pre-trained or automatically trained models because when their assumptions vary from your business context, this is where things go awry. We recommend you build a compact core data and machine learning team to drive your AI initiative; or, if you don’t have the right team, <a href="https://basis-ai.com/about">work with a team of experts</a> who can help you build and maintain bespoke models and who are prepared to take a capability building approach, rather than just selling you a black box.</p><p><strong>2. Use version control and digital audit trails</strong></p><p>Make sure your systems enable version control and allow tracking of all parts of the AI development and deployment lifecycle, so you know which model was giving which results, and when. Had the Apple Card/Goldman situation been a result of a newly deployed AI algorithm, these organisations should have <a href="https://basis-ai.com/product">the right technology</a> in place to investigate and switch back to an older version of the model in a few clicks. Digital audit trails make it easier to roll back, explain and debug.</p><p><strong>3. Ongoing monitoring of AI in production</strong></p><p>AI models degrade. If Apple Card’s algorithm was an old AI model that happened to degrade over time, monitoring is crucial in being able to flag up when the model performance was degrading. Make sure things are still working as intended when in production, and audit your models for implicit biases. Just removing race isn’t going to work if you have postal code as a field and certain postal codes have high correlation with race — the AI model will pick up postal code and this will become a proxy for race.</p><p><strong>4) Invest in tools that help you to do all of the above</strong></p><p>AI scientists and machine learning engineers need help to automate and govern their work. There’s also an increasing need to bridge the gap between data science and DevOps.</p><p>BasisAI’s platform, <a href="https://basis-ai.com/product">Bedrock</a>, helps enterprises to enable better governed AI systems, while accelerating their machine learning efforts.</p><p>If you want to learn more about AI governance, or Bedrock, get in touch with our team of data scientists at <a href="/service/mailto:contact@basis-ai.com">contact@basis-ai.com</a>, or learn more at <a href="http://www.basis-ai.com./">www.basis-ai.com.</a></p><p><em>*Gartner, Jan 2019</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=399c09f2ff53" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>