There is a difference between installing an AI system and living it as a continuous practice. The first one is a technical transaction. The second one is an organizational transformation. The 95% of AI projects that fail, fail exactly here: they installed without building the ritual of continuous integration.
The third section of the Red Belt is the ritual: the recurring practices that keep the ecosystem of automated intelligence alive, antifragile, and aligned with purpose. Without ritual, even the best design degrades. With ritual, even imperfect designs improve continuously until they become excellent.
We go through the ritual across the three planes.
1. The Red Belt ritual in business
The quarterly review rhythm
The most important concrete practice of the Red Belt: a formal quarterly review of every system with decision authority. Not annual (too late). Not monthly (too granular). Quarterly: the natural rhythm where you can see whether a system is improving or degrading.
Every system in the review:
- Performance: is it meeting the defined criteria? Better or worse than the previous quarter?
- Costs: does the ROI still justify the investment? Is there a way to reduce cost while maintaining capacity?
- Bias and fairness: does the system treat segments differently without a legitimate reason?
- Alignment with purpose: is the system still aligned with the values and strategic direction of the company?
- Decision: extend, adjust, replace, or pause?
The fourth question is the most important one and the most ignored. A technically excellent system that does not align with values becomes a growing risk. Another one that is technically average but perfectly aligned becomes a strategic asset.
The three roles of the ritual
The mature ritual distributes responsibilities:
-
The system operator: whoever executes day to day. Reports metrics, identifies problems, proposes tactical improvements.
-
The system owner: whoever has the authority to adjust, pause, or replace. Makes medium-term decisions based on the operator's data.
-
The quarterly review committee: a senior team (CEO, CFO, CTO, ethics lead if applicable) that decides on strategic alignment, ethics, and long-term budget.
The three roles need to be formally defined. The company where "the system runs by itself" actually has a system without governance, and that is what produces the disasters three years later.
Purpose as the anchor
A concrete practice to avoid "technical drift" (systems that deviate from their original purpose):
Every critical system has an explicit purpose document: why it exists, what problem it solves, what values it must embody, what it must never do. One page, written in clear language, signed by the CEO and the owner.
When the time comes to make decisions about extension, adjustment, or replacement, the purpose document governs. If a technical "improvement" violates the purpose, it does not get done. If a technical restriction preserves the purpose, it is kept even if it is costly.
2. The ritual applied to automation
The three-horizon cadence
Advanced automation systems need three simultaneous review cadences:
-
Daily, automatic monitoring: dashboards that show the day's performance. Configured alerts. Nobody reviews every daily metric, but the systems raise an alert when something deviates.
-
Weekly, review by the operator: 30 minutes where the operator reviews what happened during the week, identifies patterns, decides tactical adjustments. Documents it in a log.
-
Quarterly, review by the committee: 90 minutes where the senior team reviews the complete picture according to the five questions of the rhythm.
The three cadences are complementary, not substitutes. A company that only has the quarterly one loses tactical drift. One that only has the daily one loses strategic direction. The mature company has all three.
The antifragility metrics
The difference between a robust system and an antifragile system is measured. Concrete metrics:
- Rate of documented errors per month (it must go up initially, then stabilize: this indicates that the system is learning)
- Rate of improvements implemented based on errors (it must be >50%: it indicates that the learning cycle works)
- Time between the detection of an edge case and its incorporation into the model (it must go down quarter over quarter)
- Variation of performance under adverse conditions (it must go down: the system becomes more stable under stress)
If these metrics are not measured, the system may be degrading silently and nobody notices it until it is too late.
The most important operational difference between AI projects that survive 5 years and the ones that die in 18 months is not talent or budget. It is the culture of the documented error. In companies where errors are hidden or punished, systems degrade invisibly and quickly. In the ones where they are celebrated as fuel for learning, systems improve exponentially. This cultural difference is what sustains the Red Belt over time.
3. The Red Belt ritual with AI
The ethical-operational committee
For AI systems with decision authority over clients, employees, or material budget, the book proposes a quarterly ethical-operational committee:
Participants:
- CEO (or a representative with authority)
- Technical owner of the system
- Operational owner of the affected area
- External advisor (preferably with an ethical or legal perspective)
- If applicable: a representative of the client or of the affected team
Agenda:
- Specific cases where the system made questionable decisions
- Fairness and bias metrics by segment
- Complaints received that involve the system
- Changes in regulation or social expectations that affect the system
- Decision: adjust criteria, pause, replace, or continue
Without this committee, automated decisions become invisible. The company realizes the damage when it is public news or when a top client leaves silently.
Integration as a spiritual practice
The book takes a philosophical turn here that is worth leaving literal:
"The Red Belt is not about dominating technology. It is about being dominated by the purpose that technology serves. When a leader confuses the two categories, he builds technical empires without a soul. When he separates them, he builds companies where advanced technology becomes an expression of clear values, not a contradiction of them."
The concrete practice: every quarter, before the technical review, the senior team dedicates 30 minutes to reconnecting with purpose. Why do we run this company? Who do we really serve? What legacy do we want to leave? Without this anchoring, the Red Belt turns into empty technical obsession.
The five rituals of the Red Belt founder
The personal rituals of the mature leader:
-
Sunday night: 30 minutes alone, reviewing the week that passed and designing the priority of the next one. No screens. Only a notebook and reflection.
-
Monday morning: clear communication with the senior team about the priorities of the week. Not by message: in person or on a formal video call.
-
Quarterly one-on-one with each direct report: 90 minutes, with no external agenda. How are you? What do you need? What am I doing that helps you or gets in your way?
-
Annual senior team retreat: 2 to 3 days offsite, a deep review of strategy, dynamics, direction. This is where the Black Belt is incubated.
-
Personal journal: the Red Belt founder writes. Difficult decisions, dilemmas, lessons, gratitudes. Writing is the most underestimated thinking tool of mature leadership.
Three things are necessary for the salvation of man: to know what he must believe, to know what he must desire, and to know what he must do.
Mature leadership requires the same three: clarity about purpose, clarity about priorities, clarity about practice.
Signs that the Red Belt is complete
Five signs:
- The company has AI systems with measurable decision authority (not demos, not experiments: production)
- Every system has a formal human owner and a quarterly review ritual
- The antifragility metrics are measured and improving
- The ethical-operational committee works and has made difficult decisions (including pausing a system)
- The founder dedicates less than 20% of his time to operations and more than 50% to strategy and purpose
Five yeses = ready for the Black Belt. Mastery starts here.
Frequently asked questions
Installing AI is a technical transaction: buy, configure, launch. Integrating it is an organizational transformation: a ritual of continuous review, a culture of the documented error, antifragility metrics, an ethical-operational committee, an explicit purpose that anchors every decision. The operational difference is brutal: companies that only install see their systems degrade in 18 months (AI projects dead silently, vendor lock-in, growing costs with decreasing value). Companies that integrate see their systems improve year after year (more capacity, less relative cost, greater alignment with purpose). The 95% failure rate of AI projects is exactly this difference: installation without integration.
Three simultaneous cadences. Daily: automatic monitoring via dashboards with configured alerts (nobody reviews every metric, the systems raise an alert when something deviates). Weekly: 30 minutes where the operator reviews the week, identifies patterns, decides tactical adjustments, documents it in a log. Quarterly: 90 minutes where the senior committee reviews the complete picture with five questions (performance, costs, bias and fairness, alignment with purpose, final decision). The three are complementary, not substitutes. A company with only the quarterly one loses tactical drift. A company with only the daily one loses strategic direction. The mature Red Belt has all three and complies with them.
Four elements: 1) A formal human owner with the authority to adjust, pause, or replace (not just "IT"). 2) An explicit purpose document (why it exists, what problem it solves, what values it embodies, what it must never do) signed by the CEO and the owner. 3) Antifragility metrics measured quarterly (documented errors, improvements implemented, time to incorporate edge cases, variation under stress). 4) An organizational culture that celebrates documented errors as fuel for learning (it does not hide or punish them). Without these four, the project degrades silently and dies in 18 to 36 months. With them, the system improves exponentially and becomes a defensive strategic asset that is hard to replicate.
Five measurable signs: 1) The company has AI systems with measurable decision authority in production (not demos, not experiments). 2) Every system has a formal human owner and a quarterly review ritual that works. 3) The antifragility metrics are measured and improve quarter over quarter. 4) The ethical-operational committee works and has made difficult decisions (including pausing a system when the data justified it). 5) The founder dedicates less than 20% of his time to operations and more than 50% to strategy and purpose. Five yeses = ready for the Black Belt. Mastery is what comes afterward: applying all this knowledge with no apparent effort, teaching others, leaving a legacy.
The last belt
With philosophy, arsenal, and ritual complete, the Red Belt is mastered. Your company operates with antifragile automated intelligence, mature governance, productive digital levers, and solid fundamentals. The Black Belt comes next: it is not one more belt. It is the beginning. The mastery that gets transmitted. The legacy that gets built consciously. The founder who has already gone through six belts and is ready to leave a mark beyond his company.
Go deeper
Want to bring your team to the next belt?
Book a discovery call or explore the full book.