Dr.Walter KurzMBA, M.Sc.

Authority, access, budget, the standing to refuse and a route to escalate: what has to be granted for the role to exist.

• Schwierigkeit

Board, statutory officers, process owners, technology and legal: what does not move to the officer.

• Schwierigkeit

Reporting line, access to the accountable body, and the conflict created when the officer also owns delivery.

• Schwierigkeit

The first ninety days: no register, no policy, no budget line, and systems already running.

• Schwierigkeit

Forty people and no lawyer, against a group with three assurance functions.

• Schwierigkeit

Asking for the budget and the people the apparatus needs, with a figure.

• Schwierigkeit

The inventory: system, purpose, owner, supplier, users, affected groups, data, risk class, status.

• Schwierigkeit

Embedded features and supplier-added AI, brought into scope.

• Schwierigkeit

Wiring intake, procurement, security review and change management into the register so it survives a year.

• Schwierigkeit

Turning principles into rules somebody can apply without asking the officer.

• Schwierigkeit

Acceptable use, written in language people read.

• Schwierigkeit

Thresholds, restricted uses, and uses the organisation will not make, translated from oversight intent into an operable taxonomy.

• Schwierigkeit

Who must know what before they may propose, approve, operate or use.

• Schwierigkeit

Who may decide what, at what risk level.

• Schwierigkeit

Data, evaluation, law, security, oversight, benefit and exit as the evidence pack per decision.

• Schwierigkeit

Designing a committee that decides rather than deliberates.

• Schwierigkeit

Triage, fast lanes and a proportionate path for low-risk uses.

• Schwierigkeit

Designing a path people use instead of going around the officer.

• Schwierigkeit

Making a decision reconstructable by somebody who was not in the room.

• Schwierigkeit

Bringing a running system back to the gate before it drifts out of its permission.

• Schwierigkeit

Supplier changes, new features and scope creep after go-live.

• Schwierigkeit

Detection, containment and correction, built before it is needed.

• Schwierigkeit

Running an exercise and acting on what it exposes.

• Schwierigkeit

Failure that arrives as complaints, appeals and quiet workarounds rather than as an alert.

• Schwierigkeit

Who is told, by when, and by whom.

• Schwierigkeit

Holding a position in front of the press and the people affected.

• Schwierigkeit

Designing a route that actually reaches the people who were harmed.

• Schwierigkeit

Channels for affected people and for staff, built before they are needed.

• Schwierigkeit

Stopping something, and surviving having stopped it.

• Schwierigkeit

Leaving a record that protects the organisation and the officer.

• Schwierigkeit

Holding responsibility for a system somebody else runs, including a shared one.

• Schwierigkeit

Supplying each function with what AI obliges it to hold, and noticing when an AI decision lands inside theirs.

• Schwierigkeit

The same, for the systems that answer outward.

• Schwierigkeit

Lines of defence, control testing and corrective action.

• Schwierigkeit

Performance, incidents, drift, benefit and new obligations, reviewed on a rhythm.

• Schwierigkeit

Assembling continuously so the pack already exists when it is asked for.

• Schwierigkeit

Cadence, contents, and how to carry the bad news.

• Schwierigkeit

Making an apparatus stick with people who did not ask for it.

• Schwierigkeit

Regulation, suppliers, technology and incidents elsewhere, feeding the register.

• Schwierigkeit

Putting the pieces together so the whole holds up when it is examined.

• Schwierigkeit

Someone brings the officer a proposal that opens with a technology and a vendor, and never says what is currently going wrong. Everyone in the room nods, because it sounds like progress, and nobody can say what would be different afterwards.

• Schwierigkeit

A proposal says it will "transform customer service" or "automate underwriting". The officer cannot tell what would actually change on a Tuesday, and neither can the people doing the work.

• Schwierigkeit

The officer is asked whether an initiative is worth doing and finds themselves arguing about the technology, because nobody has said where the money or the advantage would actually appear.

• Schwierigkeit

The programme is a year old and someone from finance has asked, reasonably, what it delivered. The pilot report says the system handles the task in four minutes. Nobody wrote down what it took before, nobody kept the old volumes, and the two people who would have known have moved on. The saving may be large. It is now unprovable.

• Schwierigkeit

Two proposals arrive. One saves money on work the whole industry does. The other would let the firm do something competitors cannot. They are presented in the same format, with the same kind of number, and are treated as comparable.

• Schwierigkeit

A vendor demonstration is impressive. The officer is asked whether this would give the firm an edge, and realises the same demonstration is being given to their competitors this week.

• Schwierigkeit

The strategy rests on "our unique data". The officer asks to see it and finds four years of records with the important field filled in half the time, no rights to use it for this purpose, and nothing feeding back from operation.

• Schwierigkeit

An investment case assumes a capability stays scarce for five years. The officer has watched the same capability go from a research demonstration to a checkbox in software they already pay for, twice.

• Schwierigkeit

The business case is approved on a build figure. A year later the bill has grown with usage, nobody budgeted for it, and success has made the finances worse.

• Schwierigkeit

The vendor quote is the number in the paper going to the board. It omits integration, evaluation, monitoring, support, retraining and the change effort, all of which land on the organisation. Two more that are always missing: somebody internally has to own this product, and somebody has to do the assurance and approval work.

• Schwierigkeit

The system is 92 percent accurate and everyone is pleased. Then somebody asks how the reviewer is supposed to know which cases are in the 8 percent. If telling requires redoing the work, the review costs close to the full task rather than eight percent of it, and the saving was never there.

• Schwierigkeit

The efficiency arrives exactly as promised. Within a year every competitor has it, prices have moved, and the customer has the benefit while the firm has the cost.

• Schwierigkeit

The pilot worked. Twelve months later the tool is installed, the benefit case still shows the original figure, and half the team have gone back to the old way of doing it.

• Schwierigkeit

A complete, professional, plausible AI proposal arrives with a decision expected this week. It is the officer's judgement that stands between it and the budget.

• Schwierigkeit

Choosing means foregoing. A plan that rules nothing out has committed to nothing, and this is the sitting where a learner writes the sentence most AI strategies avoid.

• Schwierigkeit

Turning a general wish to use AI into one sentence about how this organisation intends to win with it, and turning scattered pilots into a position.

• Schwierigkeit

Reading the change one level up: what happens to the sector when everyone has the capability, and where that leaves this organisation.

• Schwierigkeit

Turning a list of possible AI uses into a defensible order, on value, feasibility, data readiness, risk and reversibility.

• Schwierigkeit

How much money, across how many bets, over what time: the proportions that turn a ranked list into a portfolio.

• Schwierigkeit

The point where AI stops improving the existing business and starts altering the offering itself.

• Schwierigkeit

Seat, usage, outcome, bundle or tier, and what each does to customer behaviour and to your own economics.

• Schwierigkeit

Keeping an offering profitable when the cost of serving it rises with how much it is used.

• Schwierigkeit

The sourcing decision taken as an argument about what has to be owned to hold a position, rather than as procurement.

• Schwierigkeit

What the supplier owns after signature, and what it would cost to leave.

• Schwierigkeit

Whether timing is decisive for a particular move, and what each posture costs.

• Schwierigkeit

Writing a strategy that survives finding out which of its branches are foreclosed, restricted or expensive to defend.

• Schwierigkeit

Signing a strategy before anyone knows the capability will reach the required quality: staging, thresholds and kill criteria.

• Schwierigkeit

Producing the document itself: what an AI strategy contains and how the parts hold together.

• Schwierigkeit

Holding the position under the four questions a board actually asks: what it costs, what it returns, what a competitor could do about it, and who carries the risk.

• Schwierigkeit

The shift from running projects to running a function: what happens monthly, quarterly and annually, and who is in the room for each.

• Schwierigkeit

Building the path AI requests arrive through, and finding what is already running that nobody asked about.

• Schwierigkeit

The recurring decision: what gets funded this cycle, what continues, what stops, what scales.

• Schwierigkeit

Budgeting a cost that rises with adoption rather than a project that finishes, and handling the variance.

• Schwierigkeit

Measuring what a unit of output actually costs in operation, and watching that number move.

• Schwierigkeit

Changing the work rather than deploying a tool into work that stays the same.

• Schwierigkeit

Carrying the organisation through a change that alters what people do, and what is owed to them while it happens.

• Schwierigkeit

Producing evidence of benefit that a sceptical finance function accepts, rather than a number the programme produced about itself.

• Schwierigkeit

What to do when the benefit did not arrive: continue, pause, stop or scale, and defending the call.

• Schwierigkeit

Drift, degradation, and the supplier model change nobody told you about.

• Schwierigkeit

Running the relationship as a live thing: performance, changes, renegotiation, and the review the contract entitles you to.

• Schwierigkeit

How reversibility is lost quietly, and what has to stay in-house to keep a decision open.

• Schwierigkeit

Deciding what the organisation must be able to do itself, and building for that rather than for everything.

• Schwierigkeit

The standing account to the people entitled to ask: benefit, performance, risk position, and what went wrong.

• Schwierigkeit

Reading operating reality back against the thesis, concluding it is wrong, and forcing the revision.

• Schwierigkeit

Model, training, fine-tuning, prompt, token, context, inference, agent: the vocabulary of a technical meeting, defined well enough to follow one.

• Schwierigkeit

How a model is fitted to data rather than programmed with rules, and what follows from that difference.

• Schwierigkeit

What population a training set represents, and who is missing from it.

• Schwierigkeit

The gap between the outcome an organisation cares about and the measurable thing standing in for it: readmission measured as a billing code, a good hire measured as three years of tenure.

• Schwierigkeit

Trained, fine-tuned, prompted, grounded on your documents: which knob a supplier is turning, and what each one can and cannot fix.

• Schwierigkeit

Predictive, generative, retrieval and acting systems, and what each is genuinely for.

• Schwierigkeit

Problems that do not need a language model, and how to notice them before the project starts.

• Schwierigkeit

Why the same question can produce different answers, and where that rules a use in or out.

• Schwierigkeit

Fluency without a truth check, read as a mechanism rather than as a bug.

• Schwierigkeit

Calibration: how a system's expressed confidence relates, and fails to relate, to whether it is right.

• Schwierigkeit

Context limits, cut-off dates, and the document that was silently truncated.

• Schwierigkeit

Data, objective, deployment context and user behaviour as the four sources, and how to tell which one you are looking at.

• Schwierigkeit

What happens at the edge of the training distribution, and how to predict where a system will fail first.

• Schwierigkeit

Bias as a mechanism rather than an accusation: how the composition of data shapes what a system produces.

• Schwierigkeit

Where ground truth came from, who produced it, under what conditions, and how much to trust it.

• Schwierigkeit

Why a system does not know your documents until it is made to, and what grounding does and does not fix.

• Schwierigkeit

What changes once a model holds tools, credentials and the ability to take actions.

• Schwierigkeit

Images, voice, documents and synthetic media: what these systems do well, where they fail, and where fabricated media becomes a live risk.

• Schwierigkeit

Precision, recall, and what a rare event does to both.

• Schwierigkeit

False positives against false negatives, chosen deliberately and in advance.

• Schwierigkeit

How to read an evaluation claim, and what a benchmark result does not establish about your own use.

• Schwierigkeit

What a demonstration is selected to show, and what turns it into evidence.

• Schwierigkeit

Attack surface as a consequence of the mechanism: a system that takes instructions from text cannot fully separate instruction from content.

• Schwierigkeit

Injection through content the system reads: an email, a document, a web page becoming an instruction.

• Schwierigkeit

Memorisation and extraction: what a model can reveal about what it saw.

• Schwierigkeit

Poisoning, and the provenance of a model or dataset somebody downloaded.

• Schwierigkeit

Where the officer's own competence ends, and how to get an answer they can rely on.

• Schwierigkeit

Drawing the edge of the thing being commissioned: user, task, data, decision, output, handoff.

• Schwierigkeit

From source data through to a person acting on an output, and what sits between.

• Schwierigkeit

Setting the standard a system must meet before anyone builds or sells one.

• Schwierigkeit

Uses whose minimum standard comes from regulation, professional duty or the consequence of error, rather than from the organisation's preference.

• Schwierigkeit

Assembling evaluation material out of the organisation's own reality, including the awkward cases.

• Schwierigkeit

Data held back, and who marks the paper.

• Schwierigkeit

Rubrics, expert review, and what to do when the experts disagree.

• Schwierigkeit

Results broken down by subgroup, language, name, and edge population, rather than averaged.

• Schwierigkeit

Specifying an adversarial test and reading the report it produces.

• Schwierigkeit

A trial with a stated question, an end date and a stop available.

• Schwierigkeit

Coverage, rights, freshness, lineage and operational availability of the data a system will depend on.

• Schwierigkeit

Requiring proof of where data and models came from before taking delivery.

• Schwierigkeit

Where a person sits in the process, and what authority they actually hold.

• Schwierigkeit

Volume, seconds per case, and oversight that is arithmetically impossible.

• Schwierigkeit

Automation bias, and how the interface causes it.

• Schwierigkeit

Uncertainty, sources, and what the screen has to show for the output to be used properly.

• Schwierigkeit

Fallback, containment, blast radius, appeal and rollback: what happens when it is wrong, decided before it is.

• Schwierigkeit

Outage, rate limit and degraded mode, and what the organisation does that morning.

• Schwierigkeit

Permissions, credentials and the boundary around a system that can act.

• Schwierigkeit

Prompts, retrieval stores, logs and integrations as part of the security surface.

• Schwierigkeit

Drift, quality, incidents and supplier change: what is monitored and what triggers a look.

• Schwierigkeit

Logging, versioning and audit trail designed in, including how to do it without retaining what should not be kept.

• Schwierigkeit

Prompt and configuration changes treated as releases.

• Schwierigkeit

Disruption, training need and process ownership: the cost of integration into work as it is done today.

• Schwierigkeit

Accessibility, language, and the person who cannot use the channel at all.

• Schwierigkeit

Designing or joining a system that serves several institutions at once.

• Schwierigkeit

Suspension, retirement, what happens to the data, and what takes over.

• Schwierigkeit

Producing something a supplier can answer and the organisation can hold them to.

• Schwierigkeit

Running acceptance against stated evidence rather than supplier confidence, and being willing to refuse.

• Schwierigkeit

Builds the person an organisation holds accountable for its AI: what it does with AI, on what evidence, within what rules, and at what risk. Seven parts and thirteen modules, of which ten are self-learning and three are taught live with a human counterpart, completed with an oral examination.