TEAF Light and the 1-1-1 principle

The biggest cause of failed adoption for an enterprise architecture framework isn't the quality of the framework — it's the temptation to cover everything before starting. TEAF Light starts from the opposite premise. It fits in three words: one process, one loop, one measurable objective. That's the 1-1-1 principle, and it's deliberately unambitious at the start — precisely so it can actually be sustained.

Why the full version discourages adoption

TEAF, in its full version, covers strategic governance, technical architecture, compliance, security, FinOps and business continuity. That's coherent on paper, but an organization that discovers the framework and tries to implement everything simultaneously hits the same wall as any overly ambitious initiative: scoping workshops drag on, nobody sees a result for months, and the project loses momentum before proving anything.

The 1-1-1 principle, precisely

One process. Not a complete map of the information system — a single business process, chosen because it's representative or because it hurts. One loop. The complete Intent → Learning cycle applied to that single process, not a partial loop that stops at the decision. One measurable objective. A concrete indicator, defined before starting, that will allow an objective statement on whether the cycle produced a result — not a qualitative impression of progress.

What that looks like in practice

Book IV illustrates the principle on an invoice-processing scenario: a precise process, a complete TEAF loop applied to that single scope, a measurable objective (processing time, error rate). The associated reference stack — Dolibarr, GitLab, PostgreSQL/pgvector, n8n, Python, Cloudflare — is chosen to stay accessible to a small team, in a few weeks, without a heavy platform to provision beforehand.

A starting point, not an end in itself

TEAF Light isn't a diminished version meant to stay that way indefinitely. It's an entry point: once a first complete cycle has genuinely run on a limited scope, the organization has internal operational proof — not yet generalizable scientific proof, but a concrete result to build on when expanding scope, one process at a time. The open-source teaf-light repository serves precisely as an executable companion to that first cycle, with its limitations documented rather than glossed over.

• The most frequent cause of failed framework adoption: wanting to cover everything from day one.
• The 1-1-1 principle — one process, one loop, one measurable objective — deliberately limits initial ambition.
• TEAF Light's reference stack is chosen to be operable by a small team in a few weeks.
• TEAF Light is a starting point: scope expands once a first cycle has actually proven something.