The Spektor Method
Six phases, always in the same order. The depth changes, never the sequence.
This page keeps two things apart: how we work and how you buy. You choose how much of the path to take. How we work does not change.
How we work
Every engagement moves through the same six phases. Each one produces a decision, not just a document.
- 01
Map.
Which AI tools are in use, by whom, with which data, with what impact on processes, customers, workers and candidates. Unauthorised uses surface too: personal accounts, experiments, data uploaded outside the perimeter.
Decision made possible: where to act first.
- 02
Calibrate.
From the map come the groups of people to train, the depth for each group and the priority of the rules: measures proportionate to roles and actual uses, as the law requires. This is why mapping always comes before training.
Decision made possible: who to train, how, and in what order of priority.
- 03
Train.
Two voices. One works with senior management and the control functions on framework, risk and responsibility. The other works with the operational functions on real workflows, on checking outputs, on the tools the organisation actually uses.
Decision made possible: when to trust an AI output and when not to.
- 04
Codify.
The rules that make binding what the training has taught: acceptable-use policy, procedures, internal responsibilities, the AI register. Never rules detached from what people have learned.
Decision made possible: which tools and uses are authorised, and who answers for them.
- 05
Demonstrate.
The evidence file: approved plan, attendance records, materials, results of the checks, versions, the link to the rules. It is what senior management can show.
Decision made possible: how to demonstrate AI governance before the board, the authorities and customers.
- 06
Maintain.
Tools and regulations change. Rules, materials and evidence stay up to date, and new uses are caught before they slip outside the rules.
Decision made possible: how to adapt without starting again from zero.
Two principles apply to every phase.
The decision test.
Every document we deliver must make a decision possible. If it does not, it is documentation, not governance.
The implementability principle.
Every recommendation must be applicable in your real processes, with your people.
The path
The path is not a package. It is a sequence in which each step grows out of what the previous one produced.
- 1
Executive Briefing.
Ninety minutes with those who lead the organisation, preceded by a preliminary picture of your organisation. What comes out is a written memo. Any proposal to continue comes after the memo, in writing.
- 2
Kickoff.
The first project: the six phases applied to your organisation. Two versions, Core and Extended, which differ in the depth of each phase, never in whether a phase is present. The version depends on what emerges in the Briefing (functions, tools, use cases, data involved), not on a negotiation. The Kickoff follows a Briefing.
→ Kickoff
- 3
Specialist Programmes go deeper into the domains that the Kickoff makes necessary: the use of AI in legal departments, in human resources, in procurement, in software development. For the last of these, the programme defines internal standards for reviewing AI-generated code, criteria for human oversight and rules of use for AI-assisted development.
- 4
Maintenance.
It is part of the Kickoff from the start. Every six months the system is reviewed: rules, materials and evidence, brought up to date with tools and regulations.
- 5
Advisory.
For organisations that, after Maintenance, want a continuing point of reference: a senior opinion when it is needed, participation in committees and management meetings at an agreed cadence, assessment of new use cases, a second view on suppliers and projects. Spektor looks after the method. Responsibility stays with the organisation.
The rules
No operational training outside a Kickoff.
Training without rules and responsibilities increases the use of AI, not control over it. This is why we do not offer training on its own.
No free Briefing.
The Briefing is a working session prepared on your organisation, with a defined cost and format. It is not an introductory meeting.
A review every six months.
Tools and regulations change faster than documents. For as long as Maintenance is active, the system is reviewed every six months.
Requests receive a reply within five working days.