Skip to main content

AI bias

[PLACEHOLDER]

Objectivity can be challenging. Machines are not shielded from this by any means.

As humans we are leveraging technology in a progressive manner, making our lives easier, becoming an extension of ourselves in our day-to-day existence. By trying to simplify things, complexity creeps in (it is ironic, I know!), and as we try to create something for the good, very often it can be used to go against the principle upon why they were created in the first place.

 

Photo by Pavel Danilyuk from Pexel

Therefore, as creators of this technology, usually with the best intentions, it is understandable when model predictions become susceptible to bias.

Those in charge of building the models need to be aware of the common human biases that will find their way into the data used, allowing them to take proactive mitigation steps.

To help remove those biases then we need to have structure. A framework that allows us to build AI systems in an ethical manner that can benefit our communities. AI ethics is that “set of guidelines that advise on the design and outcomes of Artificial Intelligence (AI)”.

AI and bias

Algorithm bias “describes systematic and repeatable errors in a computer system that create unfair outcomes” - Wikipedia.

Putting close attention to the algorithms, and the data, selected for the implementation of the solution “X” allows to identify, prevent and/or mitigate real concerns, such as systematic and unfair discrimination.
AI bias can happen due to cognitive biases, which is an unconscious error in thinking that leads you to misinterpret information from the world around you, affecting the rationality and accuracy of decisions and judgement.

The teams in charge of training the models can be ingesting those biases through the data collected.
Note: The use of incomplete data for data modelling training is another potential way to have AI bias as your outcome.

The use of incomplete data for data modeling training is another potential way to have AI bias as your outcome


AI bias types in ML 

Here are a group of bias types that can be found in data (Go to the Google Developers link in our references section for more details and examples): 

Automation bias Selection bias Group Attribution bias Implicit bias


Reporting bias

When the frequency of events, properties, and/or outcomes captured in a data set does not accurately reflect their real-world frequency.

Automation bias

a tendency to favour results generated by automated systems over those generated by non-automated systems.

Selection bias

Occurs if a data set's examples are chosen in a way that is not reflective of their real-world distribution.

Group Attribution bias

A tendency to generalize what is true of individuals to an entire group to which they belong.

Implicit bias

occurs when assumptions are made based on one's own mental models and personal experiences that do not necessarily apply more generally.


Reference

Trending posts

Reimagining Digital Experience Management: How Agentic AI is Transforming Adobe Experience Manager

 Adobe Experience Manager (AEM) has introduced powerful new Agentic AI capabilities designed to continuously improve and adapt digital experiences at the speed of AI. By integrating advanced AI orchestrators through Agent-to-Agent (A2A) and Model Control Protocol (MCP) tools, AEM enables brands to automate complex workflows and enforce compliance seamlessly across enterprise ecosystems. Through a suite of specialized agents, teams can transition from manual, weeks-long processes into fast, AI-assisted workflows powered by simple natural language prompts. Photo by Tunahan KALAYCI via Pexels   Here is a breakdown of the key agents driving AEM’s new Agentic capabilities, their value propositions, their guardrails, and their current availability status. 1. Brand Experience Agent. Overview. The Brand Experience Agent accelerates digital modernization through specialized sub-agents—the Experience Modernization Agent, Experience Production Agent, and Experience Development Agent. Tog...

Building MCP with TypeScript

MCP servers are popular these days. We’ve been researching and exploring a few code repos, some where missing modularity, others just not having pieces that we were looking for… therefore we decided to build our own, simple and foundational that could be a starting point for those trying to solve for the similar things we were… and we decided to share it with the community, via our public github. MCP host, server,data sources     Before we start.  Using Typescript and NodeJS was one of our requirements. This proved somewhat challenging because I don't code as frequently these days due to my leadership responsibilities, and I typically prefer working with C# or Python. Colleagues in my tech community have been working with their teams on some of their MCPs going the Python route. Therefore, I said, “I guess we are trying the other route” 😊. One of our reasons to go with TypeScript was due to the need of the integration with APIs, and based on the research, it seems t...

Steer for a talent transformation strategy (and avoiding AI fatigue)

 There was a debate on whether to feature the term “AI” in the title of this article. Honestly, a key motivation for pursuing the research that led to this post was sparked by the widespread excitement about AI appearing constantly in our LinkedIn feed, to the point of feeling the fatigue, and even a bit disappointed in the algorithm of this, and the others, social media and content curated apps.  We soon discovered that there is an entire concept called "AI fatigue", not exactly how we were feeling it, but more about the mixed emotions people in the workforce have regarding the use of AI tools. Photo by Mart Production via Pexels (background updated with AI and Adobe  tech) From micro blog posts to video podcasts, lately, most of the tech content we encounter revolves around AI. They often sound or read very similar, usually mentioning the same few top providers. The articles (and social posts... at least the popular ones with paid-campaigns behind it) tend to focus less...

Assembling MLOps practice - part 2

 Part I of this series, published in May, discussed the definition of MLOps and outlined the requirements for implementing this practice within an organisation. It also addressed some of the roles necessary within the team to support MLOps. Lego Alike data assembly - Generated with Gemini   This time, we move forward by exploring part of the technical stack that could be an option for implementing MLOps.  Before proceeding, below is a CTA to the first part of the article for reference. Assembling an MLOps Practice - Part 1 ML components are key parts of the ecosystem, supporting the solutions provided to clients. As a result, DevOps and MLOps have become part of the "secret sauce" for success... Take me there Components of your MLOps stack. The MLOps stack optimises the machine learning life-cycle by fostering collaboration across teams, delivering continuous integration and depl...

This blog uses cookies to improve your browsing experience. Simple analytics might be in place for pageviews purposes. They are harmless and never personally identify you.

Agreed