Knowledge Hub

Read

Sign in to see your reading list.

Topics you save will appear here.

Every topic is free to read. A free account also lets you search the topics, react to a topic and comment under it.

  1. Mustafa Qizilbash

    Others

    Is Your CDO Part of the Board's Strategic Thinking, or Still Busy Managing Data?

    For many years, the Chief Data Officer has been associated with data governance, data quality, data platforms, architecture, reporting, and regulatory compliance. All of these are important responsibilities, but I believe we are reaching a point where the CDO needs to play a much bigger role. The CDO should be an integral advisor to the Board.

    Think about the decisions Boards are making today. Where should the organisation invest to create its next competitive advantage? Are we getting real business value from our Data & AI investments? How exposed are we to data, information security, privacy, and AI-related risks? Are we ready to introduce autonomous AI into critical business operations? Do we have the right information to understand our customers, markets, operations, and financial performance? And are we building capabilities that will remain relevant over the next five years, or simply investing in today's technologies?

    3 min read6 views2 reactionsMore

    Share this topic

    Is Your CDO Part of the Board's Strategic Thinking, or Still Busy Managing Data?

    React
  2. Mustafa Qizilbash

    Others

    Your Organisation Doesn't Have a Data Problem. It Has Too Many Versions of the Truth.

    Let me give you a familiar scenario.

    The Finance team reports 125,000 customers.

    The Sales team reports 138,000.

    Marketing has 142,000 in its dashboard.

    And the Customer Service team has a completely different number.

    Everyone is using data. Everyone has a dashboard. Everyone believes their numbers are correct.

    So, which number should the CEO use?

    This is not necessarily a technology problem. It is often a business definition, ownership, and alignment problem.

    What exactly is a customer?

    Does a registered user count as a customer? What about someone who has made one transaction? What about inactive customers? What about duplicate records across different business units?

    The same challenge exists with revenue, active users, products, suppliers, profitability, customer retention, and almost every important business KPI.

    Over the years, organisations have invested heavily in data platforms, warehouses, lakes, integration technologies, BI tools, and now AI.

    3 min read10 views3 reactionsMore

    Share this topic

    Your Organisation Doesn't Have a Data Problem. It Has Too Many Versions of the Truth.

    React
  3. Mustafa Qizilbash

    Others

    We Thought We Didn't Need Data People Anymore. Until It Was Time to Put AI-Built Solutions into Production.

    Visionaries and business users thought that because they understand their business, know their problems, understand their use cases, and now have Vibe Coding and AI-assisted development at their fingertips, they could build things themselves.

    So they began asking:

    "Why do we need Data people? We understand the business. We know what we want to build. And AI can help us build it."

    And to be fair, the early results look promising.

    POCs went well.
    Pilots went well.
    Applications were built. Dashboards were created. Workflows were automated.

    Everyone is excited.

    But now comes the interesting part.

    • Now it's time to bring in the actual enterprise data.

    • Now it's time for proper user acceptance testing.

    • Now it's time to fix data quality issues that nobody noticed during the POC.

    • Now it's time to optimise the code because compute consumption is increasing, cloud costs are approaching budget limits, and the expected ROI is taking a hit.

    • Now it's time to optimise storage, remove unnecessary data duplication, and manage growing volumes.

    • Now it's time to integrate with existing enterprise systems, deal with incompatible data structures, and resolve dependencies.

    • Now it's time to migrate from legacy technologies to newer platforms without disrupting business operations.

    • Now regulatory bodies are asking questions. We need to produce compliance reports, demonstrate data lineage, maintain audit trails, and prove where the data came from and how it was transformed.

    • Now business leaders want transparent and trusted KPIs. We need to reconcile different definitions, validate calculations, and ensure everyone is looking at the same numbers.

    4 min read7 views2 reactionsMore

    Share this topic

    We Thought We Didn't Need Data People Anymore. Until It Was Time to Put AI-Built Solutions into Production.

    React
  4. Mustafa Qizilbash

    Others

    Are We Using AI Agents to Build Solutions, or to Actually Run Them? There Is a Big Difference.

    Are We Using AI Agents to Build Solutions, or to Actually Run Them? There Is a Big Difference.

    I have been thinking about two very different ways organisations are approaching Agentic AI.

    Option 1: Use AI agents to build solutions.

    Give agents a business problem, requirements, architecture guidelines, and the necessary tools. Let them collaborate to analyse, design, develop, test, optimise, and document a solution.

    Humans remain responsible for the direction, architecture, validation, and final decisions.

    I have been thinking about two very different ways organisations are approaching Agentic AI.

    Option 1: Use AI agents to build solutions.

    Give agents a business problem, requirements, architecture guidelines, and the necessary tools. Let them collaborate to analyse, design, develop, test, optimise, and document a solution.

    Humans remain responsible for the direction, architecture, validation, and final decisions.

    3 min read10 views1 reactionMore

    Share this topic

    Are We Using AI Agents to Build Solutions, or to Actually Run Them? There Is a Big Difference.

    React
  5. Mustafa Qizilbash

    Others

    Sometimes the Best Technology Decision Is to Switch Something Off.

    I have seen organisations invest years building data platforms, introducing new technologies, and expanding their enterprise architecture. Over time, these investments become part of the technology landscape.

    Then something interesting happens.

    A new platform is introduced, but the old one stays. A new data warehouse is built, but the previous warehouse continues running. A new reporting solution is launched, but business users still depend on the old reports. Another integration layer is added because replacing the existing one is considered too difficult.

    Eventually, the organisation is operating multiple generations of technology, often solving similar problems in slightly different ways.

    And nobody really wants to switch anything off.

    There are understandable reasons. Dependencies are complicated, business users are comfortable with existing systems, migration carries risk, and nobody wants to be responsible for an outage.

    2 min read13 views2 reactionsMore

    Share this topic

    Sometimes the Best Technology Decision Is to Switch Something Off.

    React
  6. Mustafa Qizilbash

    Data Architecture

    Data & AI Cognitive Architecture - Chapter#1: Structural Failure of Enterprise Data Architecture

    Enterprise data architecture is failing. Not because organizations lack investment, or because the problem is inherently too complex, but because the structure required to hold these ecosystems together is either weak or absent. As data landscapes stretch across domains, platforms, and workloads, coherence simply does not sustain itself. Below diagram show the potentiate challenges faced by different persona(s) in an organization.

    Over the past decade, there has been no shortage of progress. Cloud-native platforms, lakehouse patterns, distributed processing, governance tooling - none of this is immature anymore. And yet the outcomes tell a different story. Environments expand, but alignment erodes. Governance becomes more visible, more documented, more discussed - but less effective in practice. Analytical capability grows, but trust lags behind, sometimes significantly. These are not isolated execution failures. They point to something more fundamental.

    7 min read9 viewsMore

    Share this topic

    Data & AI Cognitive Architecture - Chapter#1: Structural Failure of Enterprise Data Architecture

    React
  7. I Am Datapedia!

    Data Foundations

    What is Data?

    Data has become one of the most powerful words in our modern vocabulary. It drives our world, impacting decisions in industries, governments, and our daily lives. But what exactly is data? How do we define it in a way that captures its full impact and utility?

    A purple ribbon with white text

AI-generated content may be incorrect.Mustafa Qizilbash
    “Features and Activities of an Object is Data.”

    This phrase encapsulates data’s essence. But let’s break down what it really means.

    Origins and Traditional Definitions

    The word "data" originates from the Latin word datum, which means "something given". This concept persists in how we perceive data today: it’s a foundational input, a starting point. In French, for example, data is referred to as données, highlighting its roots as something "given" or granted for analysis.

    If you look up data in Wikipedia, you might find it defined as "individual facts, statistics, or items of information, often numeric." More formally, data is a set of values related to qualitative or quantitative variables about one or more entities or objects. In this sense, each "datum" represents one specific value or measurement.

    7 min read3 viewsMore

    Share this topic

    What is Data?

    React
  8. Bill Inmon

    Where Is Business Value Hiding in AI?

    By W H Inmon

    Everywhere you read, every news show you watch, every ommercial you see there is this overwhelming fascination and fixation with AI. The AI vendors have sold the world on the idea that AI is the future of mankind.

    In a word, people and the world are stoked.

    NEW POSSIBILITIES

    And what is it about AI that gets people so excited? There are many facets of AI that appeal to people. AI can talk with you. AI can create presentations. AI can answer questions for you. AI can look things up and find a multitude of facts – both obscure and contemporary.

    The interface, the capabilities, the range of possibilities of AI are just staggering. And people have never seen this before.

    AI has opened up a whole new world.

    Now, people that have never touched a computer before can do sophisticated analysis on the computer.

    SELLING AI

    And who has AI been sold to? AI has been sold at the highest levels of society – to the board of directors, to politicians, to decision makers everywhere. Unlike previous technologies that have been sold to technicians, AI has been sold at an entirely different level.

    10 min read1 viewMore

    Share this topic

    Where Is Business Value Hiding in AI?

    React
  9. I Am Datapedia!

    Data Foundations

    What is an Entity?

    In the world of data and databases, the term entity is foundational yet often misunderstood. To build reliable data systems, it is essential to understand what an entity is and how it is structured. This chapter explores the concept of an entity and breaks it down into its three core components: Entity Type, Entity Attributed and Entity Instance.

    Let’s decode it.

    What Is an Entity?

    An entity is anything that can be uniquely identified and described. In data modelling, an entity typically refers to a real-world object, person, concept, or event that holds relevance within a system, such as a student, a book, or a transaction.

    Entities are the fundamental building blocks of structured data models. To model and manage them effectively, we categorize entities into two levels:

    • Entity Type: the blueprint or template
    • Entity Attribute: the properties
    • Entity Instance: the real-world, data-filled object

    A screenshot of a computer screen

Description automatically generated

    1. Entity Type – The Blueprint

    4 min readMore

    Share this topic

    What is an Entity?

    React
  10. I Am Datapedia!

    AI and Machine Learning

    Entity Recognition

    Entity Recognition, commonly known as Named Entity Recognition (NER), is a technique used to identify and extract meaningful entities from unstructured text. It is also referred to as entity identification or entity extraction. While entity recognition has long been appreciated in data modeling, particularly during conceptual modeling when identifying core business entities, it plays an equally critical role in the data science domain.

    In traditional structured systems, entities such as Customer, Product, Order, or Invoice are clearly defined within database schemas. However, modern organizations generate enormous volumes of unstructured data from social media posts, emails, PDF files, Word documents, comment columns, chat transcripts, and even video or audio content converted into JSON or text formats. For data modelers, this unstructured layer represents one of the greatest challenges when designing robust data models.

    4 min readMore

    Share this topic

    Entity Recognition

    React

Build a strong foundation in Data & AI

Follow the Data Foundations learning path (Beginner to Advanced).

View learning path