AI Governance · Module 5 · Experience

Anti-Patterns

The lesson catalogues fifteen anti-patterns of enterprise AI in three clusters: portfolio and strategy, governance and compliance, and engineering and operations. Participants learn to recognise each by symptom, cause, consequence and remedy, to see several as mode errors, to compare an unbounded agent's permission set before and after, and to detect anti-patterns from traces in registers and logs with fitness functions.

Lesson 21 of 26Chapter 2075 minutes

Read the chapterThe whitepaperThe slides

All courses / AI Governance / Module 5 / Chapter 20

Learning objectives

After the lesson the participant can:

Key concepts

Anti-pattern
Not a one-off mistake but a solution that looks reasonable, is adopted repeatedly and produces the same bad outcome every time. The chapter describes each through symptom and cause, consequence and remedy.
Pilot purgatory
Dozens of AI pilots over two or three years and none in production, because pilots are funded as experiments with no production budget, platform or owner. The remedy is to fund the platform as a product before funding the fifth pilot.
Compliance by checkbox
An AI Act readiness spreadsheet of articles with a status column in which no row links to a control, a test or an artefact. The remedy maps obligations to controls, controls to evidence and evidence to pipeline stages.
Unbounded agent
An agent whose prototype credentials were never narrowed and whose instructions serve as the security boundary. The remedy is bounded autonomy: a versioned permission manifest, a tool allow-list, per-action authorisation, approval gates for irreversible actions and spend limits enforced outside the model.
Mode error
A system in one usage mode governed as if it belonged to another, for example granting a tool that runs commands the trust appropriate to a chat assistant. Risk follows what the system can do, not how it was acquired.

Interactive exercises

Do them here and get feedback at once. Choose a card and then where it belongs, or drag it.

Interactive exercise 1 · Sort

Three clusters of anti-patterns

Sort each anti-pattern into the cluster the chapter places it in.

Interactive exercise 2 · Match

Anti-pattern and remedy

Match each anti-pattern with the remedy the chapter gives for it.

Teaching plan

10 minOpening: the teacher reads five symptoms aloud without naming the anti-pattern; participants note which they have seen in their own organisation.
20 minTeacher presentation of the three clusters and the lifecycle stage where each anti-pattern first shows, with the table of mode errors and remedies.
10 minGuided comparison of Hansa Mutual's invoice-enquiry agent, prototype and production: what the only boundary was before and what enforces the boundary after.
25 minExercise in groups: diagnose the participant's programme against the catalogue, write three fitness functions and rewrite one agent permission set.
10 minDebrief: groups practise naming an anti-pattern without causing offence, presenting a firing signal as an invitation to look.

Discussion

  1. The centre of excellence that says no is accountable for risk but not for value. What would it be measured on if it were rebuilt as a platform team and an enabling team?
  2. Hansa Mutual's first spreadsheet marked the logging obligation as compliant because logging was enabled. What would have to pass, and keep passing, for that claim to be true?
  3. Nordvik Region's anti-patterns come from doing too little too slowly and Hansa Mutual's from doing much, quickly, in one shape for many jurisdictions. Which set is closer to your organisation, and which single anti-pattern would you address first?

Written exercise

Exercise · 25 minutes

Diagnose a programme and write its fitness functions

Go through the fifteen anti-patterns and mark, for your own AI programme, each as present, suspected or absent, with the symptom you have observed for every one marked present or suspected. Choose the three that matter most and write a fitness function for each in the form of the chapter's suite: an identifier, the data source such as the portfolio register, network telemetry or the model registry, the query in plain words, a threshold and the chapter that holds the remedy. Then take one agent or automation in your estate whose boundary is a sentence in its instructions, and rewrite its configuration as a manifest: its own identity, the tools allowed with constraints, deny by default, budgets and a kill switch.

Deliverable: A fifteen-row diagnosis with observed symptoms, three fitness functions with source, query and threshold, and one bounded permission manifest.

Self-test

Choose an answer to see whether it is right, or open the answer below each question.

  1. What was the only boundary on Hansa Mutual's prototype invoice-enquiry agent?

    Show the answer

    D. A sentence in its instructions telling it never to issue credit notes
    The prototype ran with a shared service account and every tool the finance API exposes; its only boundary was a sentence in the instructions, which a retrieved document can contradict. The production manifest removes the credit-note tool altogether.

  2. How does the chapter advise responding to shadow AI?

    Show the answer

    B. Make the sanctioned path faster than the shadow path, and onboard discovered use, not punish it
    Shadow AI arises where unsanctioned use was forbidden without a faster alternative. The remedy is an AI gateway with approved models and logging, the inventory, and telemetry that finds unregistered use. Shadow AI is a demand signal to be read.

  3. According to the chapter, who should set the bar in an evaluation, as the governance remedy for evaluation by demo?

    Show the answer

    C. Model risk or the system owner, approved at the assigned tier, never the sponsor
    The remedy is an evaluation pyramid with acceptance criteria as code and gates in the promotion pipeline. The governance point is who sets the bar: model risk or the system owner, approved at the tier Chapter 13 assigns.