Guide from the media outlet **Every** (every.to/guides) published on **June 2, 2026**, co-signed by **Mike Taylor, Laura Entis and Claude**, proposing an **8-level maturity scale for AI adoption**. **Pivot thesis**: AI adoption **is not a race toward maximum sophistication** — ***« a higher level isn't necessarily better »*** ; one must identify the level that **matches one's own workflow and level of trust**, then regularly reassess whether moving up a notch adds **real value**. ***« The best way to find value in AI is to use it in a way that fits your work. »*** **Structuring axis**: at each level, *« you delegate more of your work to—and place more trust in—the AI »* (increasing delegation + trust). **The 8 levels**: **(1) Chatbot** — conversational interface with no embedded context (ChatGPT, Claude, Gemini); **(2) Copilot** — AI embedded in the workspace with access to the current file (Cursor, Claude in Excel, Gemini in Docs); **(3) Agent** — reactive system that executes step-by-step while requesting approval (Cowork, Codex); **(4) Autopilot** — one describes the **outcome** and the agent executes autonomously, review of the **final result** only (Lovable, Codex, Claude Code; tied to *vibe coding*); **(5) Workflows** — engineers building **harnesses** around agents (planning, review, confidence checks, guardrails; Compound engineering, Claude Workflows, Copilot AI Studio; shift from one-shot vibe coding → **agentic engineering**); **(6) Assistant** — **proactive, always-on** agents that monitor a domain and surface information without being prompted (OpenClaw, Hermes Agent, Claude Managed Agents; e.g. `heartbeat.md` every 30 minutes); **(7) Multi-agent** — simultaneous management of **several long-running agents** with distinct roles (Claude Managed Agents, OpenClaw, Codex Goals; *« firmly in senior engineering territory »*); **(8) Orchestrator** — an **agent manager** directs a team of sub-agents (planning, delegation, monitoring, consolidation; Gas Town, Paperclip, Symphony/OpenAI; *« highly experimental »* — even frontier engineers themselves hold this role). **Sweet spots by role**: **knowledge workers** typically operate between levels **1-4**, **engineers** between **5-8**. **Canonical parallel of intern onboarding**: *« Expect to put in a similar amount of effort with your agents before you can trust them… at the next level of autonomy »* ; and the marker phrase ***« You wouldn't brag that you had eight interns working overnight on a key project, and you hadn't checked their output. »*** The right level depends on **4 criteria**: output quality, cost, reliability (trustworthiness), stakes of failure; and **model capability** progressively shifts the "safe" level of autonomy. A framework directly usable to structure an **adoption doctrine** on the consulting side. Convergence with *systems around the model* (Dropbox/Okumura), *harness engineering* (Böckeler, Lattice, Wescale), Karpathy (vibe coding → agentic engineering), Cherny (/loop + Routines), and the *agent manager* doctrine (BFM/Girard).
#AI adoption#maturity scale#eight levels
**Mike Taylor** · **Laura Entis** et **Claude** (co-auteurs déclarés) · pour **Every** (every.to) · rubrique *Guides*. Mike Taylor est un auteur connu sur les sujets prompt/AI (co-auteur de *Prompt Engineering for Generative AI*) ; Laura Entis est journaliste/éditrice. La co-signature explicite de **Claude** comme auteur fait partie du positionnement éditorial d'Every (entreprise AI-native). Publié le **2 juin 2026**.
Op-ed by **Olivier Rafal** (Consulting Director Strategy, **WeNvision** — **SFEIR** group; former editor-in-chief of *Le Monde Informatique*) published on **June 1, 2026** in **CIO-Online**, structured around a **paradox**: in the AI era, software engineering **changes everything… and nothing changes**. **What changes = the operating model.** Roles are redefined: the **Product Owner** shifts from backlog breakdown to **generating context usable by AI**; the **developer** shifts from writing code to **framing, directing, and reviewing** agent execution; **QA** gains the ability to define **expected proof** upfront. Team structure shifts from *"double pizza teams"* (hand-off chains of ~8 people) to ***"sandwich teams"***: a **tight pairing of a business expert and a tech lead, both AI-augmented**, with other skills in support. Internal **Sfeir** figure: *"this pairing now drives roughly 80% of the production chain"*, with the remaining ~20% (architecture, data governance, security) centralized. Pivot quote: ***"The issue is not a tooling issue, but an operating-model issue."*** **What doesn't change = the discipline of the cycle.** The **SDLC** phases (define → build → verify → deploy → maintain) remain identical and non-negotiable; AI removes none of them, it **intensifies** them: ***"all the slack that human-paced work absorbed, one way or another, becomes, at AI speed, industrial-grade defects"*** (amateur-vs-professional sport metaphor). Hence **three inviolable *gates*** (human control): **specification, planning, delivery review**; validation **by proof** (not by AI's own assertions); **systematic capitalization** (each cycle enriches the next) → measured result: **−30% correction iterations after ~10 cycles**. Principle: ***"the faster the execution, the stricter the framework must be."*** Concepts drawn on: **harness** (agentic rules adapted to context), **vibe-coding** deemed **untenable in the enterprise**. **Third pillar = governance, FinOps & value-driven steering**: **variable and recurring** AI costs (~**€10/hour** per augmented seat), a shift from flat-rate licensing to usage-based billing (a 2010s cloud parallel); **FinOps** does not aim to cut costs but to *"optimize tool efficiency"* (cost weighed against value); aligning **business metrics** upfront (time-to-market, features, performance, eco-design). **Conclusion**: acceleration makes the fundamentals **non-negotiable**; the challenge is **organizational and cultural**, not technological — without securing the business relationship and collective discipline, an AI-boosted SDLC merely **amplifies problems** (hitting the wall faster). Extends the WeNvision doctrine from [[rafal-wenvision-ia-generative-produit-techno-pas-projet-2024-02-23]] and [[rafal-wenvision-tokenomics-foundation-finops-ia-2026-06-04]]; converges with *systems around the model* [[dropbox-okumura-beyond-code-generation-engineering-productivity-ai-agents-2026-05-28]], *harness engineering* [[osmani-agent-harness-engineering-2026-04-19]], agentic Salesforce, and the *agent manager* debate (BFM/Girard, SFEIR).
**Olivier Rafal** · *Consulting Director Strategy* chez **WeNvision** (groupe **SFEIR**). Ancien **rédacteur en chef du *Monde Informatique*** · et auparavant consultant analyste du marché IT (~10 ans). Tribune publiée dans la rubrique *Tribune* de **CIO-Online**. Publié le **1er juin 2026**.