What TEAF has proven in the field — and what remains to be validated

One year after the collection's publication, one question keeps coming back: has TEAF actually been tested anywhere, or does it remain a theoretical construct? The honest answer has two parts, and conflating them would be the worst way to answer it.

What the field confirms

The TEAF loop and the TEAF Light 1-1-1 principle have been implemented in organizations across very different sectors — IT, human resources, industry, logistics, business consulting, real estate. That sectoral diversity isn't a coincidence: the collection's original diagnosis (a desynchronization between the pace of governance and the pace of execution, accelerated by AI) isn't confined to any single sector, and field feedback confirms it. With hindsight, the method holds up against the problem it was built to address.

No organization is named, in the books or anywhere else. Two distinct reasons explain this, and they shouldn't be conflated. On one hand, some organizations asked for anonymity — a common requirement in architecture consulting, where engagements touch sensitive systems and trade-offs. On the other, some organizations would be open to speaking publicly, but prefer to wait until TEAF has more established recognition before being associated with it: committing early to a still-young framework is a risk they don't want to carry alone. Both are legitimate, and neither undermines the reality of the field experience.

What the field doesn't prove

Field experience isn't scientific validation, and the collection has never claimed otherwise. Book IV admits this explicitly, in the chapter covering the invoice-processing POC: no TEAF engagement has, to date, produced verifiable before/after figures on a pilot. The scenarios in Books III and IV — Ferrand Industries, Aravis Systèmes, Métropole de Rovain, Nélia, Banque Ansel, the invoice POC — are explicitly fictional and pedagogical. They illustrate a measurement method, not a real client outcome.

Concretely, what's still missing: a standardized, published measurement protocol; before/after data collected systematically rather than anecdotally; validation by a party independent of the limited scope on which TEAF Light has been tested so far. Without that, the claim "results confirm the approach" remains a conviction grounded in experience, not reproducible proof.

Why say it rather than hide it

An enterprise architecture framework claiming to have proven everything in its first version would, in fact, be less credible: no governance method gets validated in a year on a limited scope. Methodological rigor means clearly separating what comes from field experience — solid, but qualitative — from what would constitute scientific proof — not yet built. That distinction is also what lets a reader or a candidate organization evaluate TEAF for what it is today, without overselling or false modesty.

The next step

The collection's V2 revision has, as a first goal, gathering constructive criticism from other organizations — practitioners, architects, CIOs who have tested all or part of the method — before locking in new content. In parallel, the structural next step is laying the groundwork for a more rigorous validation of the concept: a reproducible measurement protocol, applicable beyond a single context, with data that can eventually be presented without relying on anonymity. No timeline is announced for this validation — a public deadline that isn't met would hurt TEAF's credibility more than the current absence of scientific proof.

• TEAF has been implemented in real organizations across different sectors — IT, HR, industry, logistics, consulting, real estate.
• Names stay anonymous for two distinct reasons: requested confidentiality, or waiting for the framework's recognition to grow.
• Field experience is not scientific validation — the collection admits this explicitly rather than glossing over it.
• V2 aims to incorporate constructive criticism from other organizations; scientific validation of the concept remains the next step, with no announced date.