Drift versus Design

In the last quarter alone, your organisation probably approved three AI pilots, signed two vendor contracts, and published an AI policy that sits unread in a folder. Your teams are using tools you have not sanctioned. Your customers are interacting with systems you have not audited. And somewhere in your technology stack, algorithms are making decisions that used to require human judgement.

None of this happened because someone decided it should. It happened because no one decided it shouldn't. This is the defining pattern of the AI age: not malice, not incompetence, but drift, the gradual ceding of human agency to algorithmic defaults. The question facing every leader now is not whether to adopt AI, but whether to drift into it or design your way through it.

The incomplete story we tell ourselves#

The common view is that AI risk comes from bad actors: companies that deliberately exploit, governments that weaponise, individuals who deceive. This framing is incomplete because it ignores the far more prevalent source of harm, organisations and individuals who simply never made a choice at all. If organisations do not deliberately design how humans and AI systems work together, they will drift into arrangements that serve neither their people nor their purpose.

Defining the terms#

Drift is the passive acceptance of algorithmic defaults, vendor configurations, and emergent AI behaviours without deliberate human oversight. It transfers decision-making authority from humans to systems without anyone authorising that transfer, creating accountability gaps, skill erosion, and ethical exposure that compound over time. It shows up as tools adopted without workflow redesign, recommendations followed without review, outputs published without judgement, and policies written but never operationalised.

Design is the deliberate configuration of human-AI collaboration through explicit decisions about where judgement lives, how work flows, and what values govern system behaviour. It preserves human agency, maintains accountability, and ensures AI augments rather than replaces the capabilities organisations need. It shows up as clear delegation boundaries, redesigned workflows, explicit governance, skills investment, and regular audits of where decisions actually get made.

There is a second definition, at the scale of a person rather than an organisation, and both are meant: drift is humans becoming robotic, surrendering judgement, curiosity and agency to algorithms without noticing. The organisational version is what that adds up to across a few hundred people.

How drift happens#

Drift does not announce itself. It arrives through convenience. A team starts using an AI writing tool because it saves time. No one redesigns the editorial process. No one defines what "good enough" means. Six months later, the organisation's voice has homogenised, its writers have stopped developing, and no one can trace exactly when human judgement left the workflow. This pattern repeats across every function: hiring algorithms screen candidates on criteria no one chose, chatbots handle complaints with responses no one approved, sales teams follow playbooks that optimise for metrics disconnected from actual value. Each adoption seems sensible. The cumulative effect is an organisation that has outsourced its judgement without deciding to.

Design requires the opposite posture. It asks: what should humans decide here? What should systems handle? Where does judgement need to remain? What skills must we protect and develop? These questions demand answers before tools get deployed, not after damage becomes visible.

Drift sometimes looks like progress#

The version of drift that is easy to describe is the one where something goes wrong. The harder version, and the common one, is the one where the numbers improve.

> Drift sometimes looks like progress: more output, more happening, and you have handed over the things you were good at without redefining the role. > > Rahim Hirji, in an interview, September 2026

An engineer I spoke to put it more precisely than I could have. He is not vibe coding. He is careful, he reviews what comes back, and his output is higher than it has ever been. What he said was that he is doing a different job than he was three years ago, that nobody ever told him the job had changed, and that it feels hollow.

Nothing in that account is a failure, and any dashboard would show an improvement. What has happened is that the parts of the job he was good at, and that made it recognisable to him as his, moved to the machine one reasonable decision at a time, and the role description underneath did not move with them. That is drift with better numbers. It is harder to argue with than the version where something breaks.

The tell is the gap between the output and the person's own account of what they do. When those two separate, the role has changed and nobody has said so out loud.

What drift looks like from inside#

The patterns below are the ones I meet most often in organisations that are otherwise doing well. None of them is a failure of intelligence or effort, and all of them are recognisable from the inside once somebody says them out loud.

• Leaders defer judgement to systems they do not fully understand.
• Accountability becomes diffused across tools, processes and committees.
• Important decisions get postponed while tactical work accelerates.
• Capability building is discussed but never embedded into daily work.
• Early signs of leadership pipeline erosion are noticed, then ignored.

The last one is the one that costs the most and shows up the latest. It is set out at the missing rungs.

The cost of getting this wrong#

Drift accrues what might be called human capability debt: the accumulated cost of decisions not made, skills not developed, and judgement not exercised. Unlike technical debt, it often remains invisible until a crisis exposes it. Accountability debt: when something goes wrong, no one can explain who decided what. Skill debt: staff lose capabilities they no longer practise, and rebuilding takes years while losing it takes months. Dependency debt: each integration increases switching costs and narrows strategic flexibility. Trust debt: customers, employees and partners extend trust on the belief that humans remain responsible, and when that proves false, trust collapses faster than systems can be redesigned. Culture debt: organisations that drift into algorithmic dependence develop cultures of passivity, where initiative atrophies and professional judgement weakens from disuse.

What I have observed in organisations#

A 6,000-person professional services firm deployed an AI writing assistant across all client-facing teams. The rollout was celebrated as a productivity win. Twelve months later, client proposals had become indistinguishable from each other; the firm's distinctive advisory voice, built over two decades, had flattened into generic competence. When asked to write without the tool, several junior staff could not produce work at acceptable standards. They had been editing AI outputs rather than developing their own capability. No one had designed for this outcome. The tool worked exactly as intended. The drift happened in the space between adoption and oversight.

Contrast this with a financial services group that mapped every workflow the AI would touch before deploying it, defined clear delegation boundaries, established review cadences, and built skill-development pathways that assumed augmentation rather than replacement. Eighteen months in, their productivity gains matched the first firm's, but their staff reported higher confidence in their professional judgement and client satisfaction had increased. Same technology. Different philosophy. Radically different outcomes.

Where is your organisation?#

Most organisations sit between pure drift and deliberate design. Uncontrolled drift (red): AI tools in use with no central visibility, no governance operationalised, staff unable to articulate what they should and should not delegate. Reactive governance (amber): policy exists but is not operationalised, some tools sanctioned and many used without approval, occasional reviews but no systematic oversight. Active design (green): clear delegation boundaries defined and communicated, workflows redesigned before deployment, regular decision audits, capability investment explicitly linked to automation, leadership modelling designed behaviour. If you are in red, stop new deployments and audit what is in use; you need visibility before you can govern. If you are in amber, pick one high-stakes workflow and apply full design discipline as a template.

The strongest objection#

The most credible objection is speed. In fast-moving markets, deliberate design can look like a luxury, and competitors who move faster may win. This contains truth: design does require more upfront investment than drift. But what I observe consistently is that organisations which drift into AI adoption eventually face remediation costs that dwarf the time saved. They rebuild workflows, retrain staff, recover from incidents, and repair trust. The organisations that design first do not face those costs. Over any reasonable horizon, design is faster than drift-then-fix. The tortoise beats the hare, not through speed but through not having to run the same race twice.

The choice you are already making#

You are already choosing. Every week that passes without deliberate design is a week of drift. Every tool adopted without workflow redesign is a boundary ceded. Every policy written but not operationalised is governance theatre. The question is whether, twelve months from now, you will look back at a series of deliberate choices or a trail of accumulated defaults. Drift feels like keeping options open; design feels like commitment. But drift is also a commitment, a commitment to let circumstances decide what you could have chosen. One direction leads to organisations that remember what human judgement is for. The other leads to organisations that forgot they had a choice.

Related SuperSkills research#

The four postures and the decisions that follow are set out in how leaders should respond to AI.

Further reading#

The use, misuse, disuse and abuse taxonomy set out by Parasuraman and Riley in Humans and Automation (Human Factors, 1997) remains a sharper vocabulary for this than most current writing about AI. It is in the essential works.

The individual instrument, and what it can and cannot tell you#

Everything above is written for an organisation. There is also a personal version, and it has existed since 31 May 2026 without appearing anywhere on this site.

Rahim Hirji built the Drift versus Design Diagnostic as a companion to the book and shortened the name to the Triple D, in the essay Have You Done the Triple D?. His own description of the naming is worth keeping: he thought about changing it, and decided he rather liked that you would remember it.

The instrument runs to ninety-four questions across nine parts, answered at speed on the instruction that the first response is the one that counts. It returns a score out of a hundred, a band running from Deep Drift, where defaults and other people's priorities are setting the direction, to Deep Design, where the person is authoring their own, and one of nine archetypes, each carrying a strength and the shadow that travels with it: the Explorer, the Anchor, the Architect, the Connector, the Bridge, the Guardian, the Amplifier, the Conductor and the Weaver.

Two things about it belong on the record here. Hirji says in the same essay that it is not a psychometric instrument and is not trying to be one, and that is the correct description: nothing published reports a reliability coefficient, a validation sample or a test-retest figure for it, so the bands and archetypes are a structured prompt to think rather than a measurement of a person. The same caution already sits on how good are you at using AI, which is the research's other self-score. The second thing is the one that matters for this page: drift is not only something organisations do. The ninety-four questions exist because the same mechanism, the small unchosen default compounding into a direction, runs at the scale of one morning and one phone.

The instrument is not linked from this page. The address given in the essay could not be reached and confirmed from the machine that wrote this, and an unverified link is worse than none.

Development of the idea#

The framework was set out in the Box of Amazing essay Drift vs Design on 16 November 2025, and developed into the matrix in The Architecture of Drift on 15 March 2026. The organisational version appeared in CEOWORLD in July 2026 with the four postures. The personal diagnostic followed on 31 May 2026. Related essays include The Decision You Never Made (7 September 2025) and On Expectation (1 February 2026). See also the timeline.

A current example of drift in miniature: AI notetakers arrived in most organisations by default rather than by decision. See should AI attend my meetings?

Asked of one person rather than of an organisation, the same question is the Triple D, the Drift versus Design Diagnostic: ninety-four questions in nine parts returning a score out of a hundred, a band from Deep Drift to Deep Design and one of nine archetypes. It is free and takes about twelve minutes. It is a structured prompt to think and not a validated instrument, and the page says so.

About this research#

Written by Rahim Hirji, author of SuperSkills (Kogan Page, 2026), keynote speaker on AI and human capability, and founder of The SuperSkills Intelligence Company.

How this research works · Reviewed quarterly · Found an error? Tell me and it is corrected on the page.

Listen. Heard on Become a Global Leader, 192 - Are you outsourcing your judgement to AI? with Rahim Hirji. Heard on The Growth Hacking Culture Podcast, AI Deskilling: Why Your Team Is Getting Worse at Thinking. Heard on Inside Learning, Super Skills: The 7 Human Skills for the Age of AI with Rahim Hirji. Heard on Lead with Purpose, Drift or Design: Rahim Hirji On The Question AI Can't Answer for You [015]. Heard on Solutionary Voices, How to Resist Algorithmic Drift.