# Before You Adopt AI in Engineering, Answer These Five Questions > Source: > Published: 2026-05-24 00:00:00+00:00 # Executive Summary AI is already reshaping your delivery workflows, whether you see it or not. If you do not lead it, it will reshape them badly. This article gives executives a stage‑aligned diagnostic to identify their real maturity, expose hidden risks, and steer AI adoption with intent rather than drift. # What This Is Not - Not a hype piece - Not a vendor framework - Not a technical guide - Not a generic AI playbook - Not a promise of productivity This is a leadership instrument for understanding and directing AI adoption. # The Problem in One Sentence Most organisations believe they are progressing in AI; their workflows show they are still in unmanaged use. # AI Adoption Maturity Model Curiosity → Ad‑hoc → Uncoordinated → Stabilisation → Integration → Reconfiguration Each stage includes: - Stage signal: what you see - Failure mode: what breaks if you stay here - Leadership responsibility: what executives must do ## Stage 0 — Experimentation Stage signal: Small groups test AI tools in isolation; nothing links to delivery. Failure mode: No patterns survive; no organisational learning occurs. Leadership responsibility: Do not mistake curiosity for capability. If you stay here, AI adoption will happen without you. ## Stage 1 — Unmanaged Individual Use Stage signal: Engineers use AI daily but invisibly; quality drifts; no review. Failure mode: Shadow workflows reshape delivery without oversight. Leadership responsibility: Surface usage and risk before anything scales. If you stay here, quality and security will drift invisibly. ## Stage 2 — Team‑Level Awareness Stage signal: Teams feel friction: uneven output, duplicated prompts, unclear fixes. Failure mode: Teams believe they are maturing; leaders believe it even more. Leadership responsibility: Establish boundaries and shared expectations. If you stay here, teams will burn time managing friction instead of delivering. ## Stage 3 — Organisational Alignment Stage signal: Workflows stabilise; AI review stages and documentation improve. Failure mode: Premature scaling without observability or constraints. Leadership responsibility: Standardise workflows and measure impact. If you stay here, AI will outgrow your controls. ## Stage 4 — Integrated AI Engineering Stage signal: AI is a system component with constraints, observability, governance. Failure mode: Drift and quality collapse if leadership attention drops. Leadership responsibility: Maintain discipline; treat AI as infrastructure. ## Stage 5 — Organisational Redesign Stage signal: Processes, roles, and flow reshape around AI‑accelerated work. Failure mode: Redesign without stability leads to chaos. Leadership responsibility: Rebuild systems deliberately, not reactively. # Common Misdiagnoses Executives repeatedly misread their organisation’s maturity in predictable ways: - Mistaking Stage 1 for Stage 3 - Mistaking individual speed for organisational capability - Mistaking experimentation for adoption - Mistaking friction for progress - Mistaking tool usage for system change If any of these appear familiar, your organisation is exposed to silent quality drift, security risk, and delivery incoherence. # Five Essential Questions for Engineering and Executive Leadership These questions are the diagnostic. If you cannot answer one cleanly, you are not at the stage you think you are. ## 1. What AI use already exists, and which maturity stage does it actually represent? Stage signal: - 0–1: Usage is invisible, individual, unreviewed - 2: Teams feel friction but cannot coordinate - 3+: Workflows, review steps, and boundaries are explicit Executive signal: If you cannot see AI use, you cannot govern it. Invisible use is the most dangerous form of adoption because it reshapes delivery without review or audit. Leadership action: Surface all usage, tools, risks, and drift before scaling anything. ## 2. Where does AI reduce cognitive load or cycle time for whole teams, not just individuals? Stage signal: - 0–1: Productivity is anecdotal and personal - 2: Teams see uneven output and duplicated effort - 3: Shared workflows show measurable improvement - 4–5: AI contributes to throughput as part of the system Executive signal: Individual acceleration is not organisational capability. Individual use without team coherence increases delivery variance. Leadership action: Identify where AI improves team‑level flow; ignore individual anecdotes. ## 3. What controls, review steps, and boundaries are required at our current stage? Stage signal: - 0–1: No guardrails; risk accumulates quietly - 2: Teams ask for boundaries but cannot define them - 3: Review steps and constraints become standardised - 4: Governance and observability are built into the system Executive signal: Scaling without controls guarantees failure. Missing controls at Stage 1 allows unreviewed changes into critical workflows. Leadership action: Match controls to your actual stage, not your aspirations. ## 4. Which organisational foundations must be strengthened before we can safely move to the next stage? Stage signal: - 0–2: Documentation, testing, ownership, architecture inconsistent - 3: Foundations stabilise because AI workflows depend on them - 4–5: Strong foundations multiply value; weak ones collapse instantly Executive signal: AI amplifies whatever environment it enters. Weak foundations are already being stressed by AI‑accelerated work. Leadership action: Ensure the environment is AI‑compatible: clarity, ownership, documentation, testing, and architecture must be strong enough to absorb AI‑accelerated change. ## 5. How will leadership set expectations and pace adoption so it matches our capacity to absorb change? Stage signal: - 0–1: Expectations inflated; progress invisible - 2: Teams feel strain; leaders misread friction as maturity - 3: Communication grounded in measurable workflows - 4–5: AI adoption becomes organisational change, not tooling Executive signal: Most organisations believe they are at Stage 3 while operating at Stage 1–2. Pacing is a leadership responsibility, not a technical one. Leadership action: Set expectations that match reality; pace adoption deliberately. # Leadership Imperative AI adoption is already happening inside your organisation. Your only choice is whether it reshapes your workflows with structure or erodes quality, coherence, and trust without it. # If You Only Do One Thing Identify your true maturity stage. Everything else depends on that. # Related Work [AI Engineering Must Be Team‑Based to See Significant ROI](/articles/leadership/notes/ai-engineering-must-be-team-based-to-see-significant-roi.html)[Building Safe, Compliant, and Sustainable LLM Systems](/articles/leadership/notes/building-safe-llm-systems.html)[Transforming Your Business for AI](/articles/leadership/notes/transforming.html) # Further Reading - McKinsey — The state of AI: How organizations are rewiring to capture value (2025) https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai-how-organizations-are-rewiring-to-capture-value - OECD Digital Economy Outlook 2024 (Volume 1) https://www.oecd.org/en/publications/oecd-digital-economy-outlook-2024-volume-1_a1689dc5-en.html **If this piece was useful**, you’ll appreciate the free Phroneses newsletter — clear thinking on engineering leadership, organisational clarity, and reliable systems. Practical, honest, and built for people who care about doing the work well. I work with leaders and teams on clarity, capability, and momentum. [Work with me →](/pages/services.html)