Data Quality · Governance · AI Integrity

The machine does
only what you
tell it to do.

Garbage In, Garbage Out is one of the oldest principles in computing. It is also the least respected — at the moment when its consequences are largest.

GIGO Data™ works with organisations that cannot afford to discover the problem after the system has already run.

"Before GIGO Data™ had a name, it had a problem — and I had been watching it accumulate for forty-five years."

Adrian Wise Santos — Founder, GIGO Data™
45
Years Observing
the Same Failure Mode
4
Domains:
Aviation · Finance · Apple · Paris
3
Days to Resolve
AntennaGate vs. Six Weeks
1
Principle:
Input Quality Determines Everything
DATA QUALITY IS NOT A FEATURE — IT IS A PRECONDITION  ·  GOVERNANCE IS DESIGN  ·  WRONG INPUT · WRONG ANSWER · EVERY TIME  ·  WILLIAM D. MELLIN, 1957: "SLOPPILY PROGRAMMED INPUTS INEVITABLY LEAD TO INCORRECT OUTPUTS."  ·  THE SYSTEM DOES NOT COMPENSATE FOR INCORRECT INPUTS  ·  DETERMINING QUALITY AFTER THE SYSTEM RUNS IS NOT GOVERNANCE: IT IS DAMAGE CONTROL  ·  DATA QUALITY IS NOT A FEATURE — IT IS A PRECONDITION  ·  GOVERNANCE IS DESIGN  ·  WRONG INPUT · WRONG ANSWER · EVERY TIME  ·  WILLIAM D. MELLIN, 1957: "SLOPPILY PROGRAMMED INPUTS INEVITABLY LEAD TO INCORRECT OUTPUTS."  ·  THE SYSTEM DOES NOT COMPENSATE FOR INCORRECT INPUTS  ·  DETERMINING QUALITY AFTER THE SYSTEM RUNS IS NOT GOVERNANCE: IT IS DAMAGE CONTROL  · 

The work that happens before the system runs.

Most data problems are discovered after the fact — in a meeting, in a report, in a costly resolution. GIGO Data™ works upstream: on the intake, the structure, and the governance frameworks that determine whether a system's outputs can be trusted before they are acted upon.


This is not data cleanup. This is data architecture for accountability — the design discipline that sits between your organisation's questions and its systems' answers.


The work applies across AI governance, enterprise platforms, regulatory compliance, and any environment where the cost of being confidently wrong is one the organisation cannot afford.

  • 01
    AI Governance & Input Integrity
    Establishing epistemic standards for AI systems — ensuring that what goes in can be traced, justified, and audited before outputs are treated as decisions.
  • 02
    Data Quality Architecture
    Designing validation frameworks that surface input failures before they propagate — not after the system has executed them at scale.
  • 03
    Regulatory Readiness
    Preparing organisations for GDPR, the EU AI Act, and evolving accountability requirements — translating regulatory intent into operational governance structures.
  • 04
    CRM & Analytics Strategy
    Building the data collection and structuring layer that makes enterprise platforms answerable — from architecture through to the questions leadership needs answered.
  • 05
    Executive Advisory
    Strategic counsel for product leaders, compliance officers, and legal teams navigating AI requirements — grounded in forty-five years of cross-domain systems experience.
Garbage In,
Garbage Out.

An old principle.

The older it gets,
the more precisely it
describes what is
happening now.

Coined in 1957. Confirmed on every ramp, trading floor, enterprise platform, and AI deployment since.

In 1957, US Army Specialist William D. Mellin explained to a syndicated newspaper that computers cannot think for themselves — that sloppily programmed inputs inevitably lead to incorrect outputs. The phrase he reached for was Garbage In, Garbage Out.

The principle has never failed. Systems have failed to apply it. The failure mode is consistent: inputs are accepted without validation, scaled without accountability, and the consequences accumulate in the data until they surface somewhere expensive.

In the age of AI, the stakes are no longer operational. They are reputational, regulatory, and consequential for the people whose lives the systems govern.

Governance is not the audit that happens after the output. It is the design discipline that determines whether the output is trustworthy in the first place.

The same structural failure,
across four domains.

1989 – 1997
Aviation
At an airline, input failures surface in real time — on the ramp, with an aircraft that needs to push back in six minutes. The system does not compensate for incorrect inputs. It executes them, faithfully, at speed.
1997 – 1999
Financial Markets
The trading floor made invisible data expensive. The Deal Book — Customer Has / Customer Wants — was a human validation layer that sat before the machine ran. The bank's position is always derivable. The entry does not permit ambiguity.
1999 – 2009
Apple · Consumer Platform
AntennaGate resolved in three days instead of six weeks. Not a speed story. A data quality story. Structured inputs, properly designed, made the system answerable. Back-purposed data would have produced noise at scale — and a six-week delay the company could not afford.
Paris
European Governance
A different cultural contract: opacity requires justification, not the other way around. What GDPR would later formalise was already the standard — institutional responsibility for outcomes, and the right to understand what produced them.

Four questions. Every
consequential system.

These are not philosophical questions. They are operational governance standards for any system that shapes access, opportunity, or consequence for real people. A system that cannot answer them has no business making such decisions.

  1. What went into this system at the beginning — and how was it selected?
  2. Who decided what counted as a valid input, and on what basis?
  3. What happens when the input conditions change — and does the system have any mechanism for knowing that they have?
  4. If this system is wrong, what would that look like — and would anyone be able to see it in time?
"What I was doing, during the years between the observations and this series, was stress-testing the frame — carrying it across different conditions, continents, domains, and disciplines — and asking whether it held."
Adrian Wise Santos
Founder, GIGO Data™  ·  Principal, Product & Data Platforms  ·  Ex-Apple (10 yrs)
1981
Detroit Country Day School — Student Lab Monitor, first data governance role
1989 – 1997
America West Airlines — SJC · SAT · EWR · BFL · SFO
1997 – 1999
Wells Fargo Bank N.A. — Foreign Exchange Sales & Trading
1999 – 2009
Apple Computer, Inc. — Senior Product Analyst, AppleCare
Paris
ESMOD — Fashion Design · Cross-border governance exposure
2012 –
GIGO Data™ — Founded. San Francisco, CA

The lens came from forty-five years of watching the same structural failure repeat across aviation, financial markets, consumer technology, and European governance — and asking, in each domain, the same question: how do you know that what went in was fit for purpose?

At America West, bad inputs surfaced on the ramp, in real time, with an aircraft that needed to push back in six minutes. At Wells Fargo, the same failure was denominated in dollars, francs, and deutschmarks. At Apple, the AntennaGate resolution in three days instead of six weeks was not a speed story. It was a data quality story.

In Paris, a different regulatory culture asked the question at a systemic level: the state, the institution, the organisation — these owed the individual legibility. Opacity required justification. What GDPR would later formalise was already the cultural contract.

GIGO Data™ was founded on the conviction that this standard — built across enough domains, over enough time, to be stated with precision — belongs in the room where AI systems are designed, deployed, and governed.

Read the "I Have a Voice" Series on LinkedIn →

The publishing
series.

A twice-monthly series on epistemology, data governance, and what it means to build systems that can actually answer for themselves. Not hype. Not alarm. The kind of calm that comes from having seen the same problem resolve itself the same way, across enough contexts and enough years.

The conversation that happens
before the system runs.

If your organisation is navigating AI governance, data quality accountability, or regulatory compliance — and needs a perspective built from forty-five years of watching what breaks — this is where that conversation begins.

San Francisco, CA  ·  gigodata.com

We read every message.
GIGO Data OG Image