WSLASHAIF

Adaptive Intelligence Framework

From experiment to organisation.

The WSLASH method for organising AI-driven development: who decides, who owns it, how much room people get and how you keep oversight. Based on more than ten years of practice in digital transformation and platform governance.

PROVE ENABLE ORCHESTRATE AMPLIFY ADAPT
AIF in half a minute

The who, the how and the when of AI.

In Dutch, with sound · 34 seconds
On-screen text, translated

Everyone focuses on the technology. Models. Agents. Platforms. Tools. Which model? Which platform? Which tool?

Meanwhile, every department builds on its own. No owner. Duplicate work. Pilots without an end. Unknown to security.

Who organises it? The difference is not in the technology, but in how it is set up.

The who. The how. The when. Phase 1 PROVE, phase 2 ENABLE, phase 3 ORCHESTRATE, phase 4 AMPLIFY, phase 5 ADAPT.

Organised creative power. AIF, Adaptive Intelligence Framework: the who, the how and the when of AI. A way of working by WSLASH.

The core

The easier building gets, the more the difference lies in the organisation around it.

AI makes building cheaper and faster. That shifts what is scarce.

This is not new: spreadsheets, macros and local databases went the same way. Handy became indispensable, overlap grew and nobody was the owner. AI speeds that up.

Scarce beforeScarce now
Technical executionChoosing the right problem
Build capacityOwnership and mandate
Access to toolsRules that fit the risk
SpeedCoherence and maintenance
Two ways to get it wrong

Both feel logical. Neither works.

The AI police

A central team has to approve everything. Makers stop reporting and keep building in the shadows. The organisation sees less and less.

or

The AI factory

A central team builds everything itself. The queue grows, the business is kept at a distance and everything depends on the same small team.

The third way

Controlled autonomy: teams build independently, in a space that fits the impact. The Center of Enablement makes that possible.

Free spaceTry things and learn, without sensitive data.
Guided spaceApplications for a team, with an owner and in the register.
Professional spaceOrganisation-wide or sensitive, with an independent review.
The model at a glance

Five phases and six domains

The phases describe how an organisation grows. The domains count in every phase.

Five phases

A phase is a state, not a project
PROVE

Prove that it works

Does this work for us?
ENABLE

Make it repeatable

How can more people build responsibly?
ORCHESTRATE

Govern the whole

How do we keep oversight and coherence?
AMPLIFY

Multiply what is proven

How do we grow the shared value?
ADAPT

Keep adjusting

How does adapting become normal?

Six domains

No order · No hierarchy · But interdependent

Value

Are we demonstrably building the right things?

Building is no proof of value. Use and results are.

Ownership

Who is accountable and has the mandate?

A name without time, mandate or budget is not an owner.

Guardrails

How does it stay safe and manageable?

Good rules make the right choice easy and the wrong one hard.

Foundation

What foundation do we build on?

Central where things must be shared, local where they are specific.

Competence

Can people do this responsibly?

Technical knowledge becomes easier to reach. Judgement and responsibility become more valuable.

Landscape

Do we see the whole and how it connects?

What may emerge locally must be visible centrally.

Mature means enough balance between the domains for what the organisation wants, the risks it runs and its size. It does not take the top score in every domain.

The Center of Enablement

A small core that lets others build

This is how AIF lands in the organisation. The Center of Enablement has three parts.

The coreProvides the foundation and the routes others build on, and guides the first applications.
Experts who join inStay in their own department and join intake and review when needed.
Accountable in the businessWhoever claims the value also takes care of use, quality, risk, cost and the lifecycle.
AIF and the rules

The law says what is required. AIF helps you organise it.

Method

AIF

From first experiment to established practice, with owners, rules and oversight.

How do we organise it?

Law

EU AI Act

European law for anyone who builds or uses AI. The obligations depend on your role and the risk.

What are we legally required to do?

AIF does not replace the law, but it does record what is running, who owns it and which trade-offs were made. That helps with the EU AI Act, and for Dutch government organisations with the BIO security baseline and the Algorithm Register.

Questions about AIF

What people often ask about AIF

Is AIF a standard or a certification?

No. AIF is a method, not a standard, a law or a certificate. Whether an organisation also seeks certification, for example against ISO/IEC 42001, is its own choice.

What is the difference between a phase and a level?

A phase is what you are working on, a level what you have demonstrably achieved. You can be in PROVE with ten apps, and in ORCHESTRATE with three.

Can we apply AIF ourselves?

AIF is the WSLASH method. Organisations work with it in an engagement in which WSLASH sets it up and guides the steps.

The goal is not as much AI as possible. The goal is organised creative power: the ability to create quickly, choose responsibly, steer with evidence and stay accountable over time.
AIF · Adaptive Intelligence Framework

Want to apply AIF in your organisation? That is something you do together with WSLASH.