Pilot route

Test together. Develop the ecosystem.

New building blocks develop from recognisable practical questions. An exploration or pilot examines how an application works in your organisational context, what people learn and what needs improving before the next step.

Illustration of a clearly defined practical trial in public space

From exploration to shared development.

  1. Define
  2. Learn
  3. Evaluate

Define the question, establish the organisational context needed and test under agreed conditions. Evaluate the results and enrich the building block and profile. Wider availability is a subsequent decision, not an automatic outcome.

Possible routes

Choose the route that fits your question.

A process exploration sharpens the question, a pilot tests one module and a knowledge route makes experience useful for future challenges.

Exploration

Process and needs exploration

Map the current work process, roles involved and desired result.

Lead time
Timing by agreement
Outcome
A defined scope and advice on a possible next step
Plan an exploration
Pilot

Defined practical trial

Test one module with a concrete case, representative users and review points.

Lead time
Timing by agreement
Outcome
Evaluation of usefulness, quality, risks and next steps
Discuss a pilot
Knowledge

Unlock knowledge and experience

Explore which lessons, formats or project information can be made reusable.

Lead time
Scope by agreement
Outcome
A proposal for responsible capture and reuse
Discuss knowledge sharing

Pilot process

From pilot question to an explicit go, adapt or stop decision.

Every step produces something tangible: a defined scope, pilot plan, configured case, user findings and an evaluation.

  1. 01

    Intake

    Describe the problem, users, desired outcome and executive context.

  2. 02

    Pilot plan

    Record the scope, roles, data, controls, planning and evaluation criteria.

  3. 03

    Configuration

    Prepare the case, access, guidance and human review steps.

  4. 04

    Trial

    Work with the application and collect structured findings.

  5. 05

    Evaluation

    Assess results and risks; your organisation decides whether to stop, adapt or continue.

What to expect from a pilot

A pilot is a learning route, not a proven implementation in advance. Openness about assumptions and limitations is part of the approach.

01

A clearly defined case

A specific application with recognisable users and a limited data set.

02

Named points of contact

Contacts for content, technology, data and decision-making.

03

Human oversight

Professionals review input and output; no automated decision-making takes place.

04

An honest evaluation

Limitations, errors and unintended effects are recorded too.

Frequently asked questions

Before starting a pilot

Is participation non-binding?

An initial meeting is non-binding. A pilot only starts after approval of a proposal covering scope, effort, cost, conditions and responsibilities.

Which data is used?

Only data needed for the agreed case. The exact data set, access and retention period are recorded before the start.

Is a pilot the same as production use?

No. A pilot is defined and aimed at learning and evaluation. Production use requires a separate decision and suitable operational arrangements.

What happens to the findings?

Participants receive an evaluation. Publication or reuse of an organisation name, quotation or result only takes place after explicit agreement.

Can several municipalities collaborate?

Yes, when the purpose, roles and data arrangements are clear for all parties. Feasibility is assessed for each route.

Your case

Which case would you like to test in a controlled way?

Describe the work process, roles involved and what you want to learn. Together, we determine whether an exploration or pilot is appropriate.