Koperateur glossary

Precise terms for decisions that hold up

We use these terms to describe observable capabilities, choices and limits. Choose a path: each definition begins with a real situation and states what it commits us to.

Choose a path

01 · Five paths

Choose a path

Nineteen terms structure how we recognise a situation, clarify a choice, decide, retain control, then demonstrate and transfer.

Each path has a stable address, so it can be opened, shared and read independently.

02 · Operational definitions

Recognise

Begin with what exists, what people experience and what must be understood before proposing an answer.

01 / 04

Situation

Definition: The concrete state of a system and its environment when a decision becomes necessary.
Nuance: A situation also includes what works, the intended outcome and the unknowns; it is not limited to the visible problem.
Concrete situation: A service still works, but recurring incidents, a supplier deadline and conflicting priorities make the next decision risky.
Associated terms: Actual state, breakpoint, intended outcome, constraint.
Avoid: “Digital need” without facts or stakeholders; a diagnosis built from one symptom.

02 / 04

Listening

Definition: Receive and restate facts, expectations, constraints and unknowns before proposing a direction.
Nuance: Listening means neither agreeing automatically nor remaining passive; restatement checks that understanding is shared.
Concrete situation: Business, operations and leadership use the same word for three different expectations; questions make the gap visible.
Associated terms: Question, restatement, stakeholder, expectation, unknown.
Avoid: “We listen” without any restatement, criterion or resulting decision.

03 / 04

Context

Definition: The business, technical, human, legal, economic and time conditions that give a situation its meaning.
Nuance: Context is not background added to a diagnosis; it determines whether an answer is valid and sustainable.
Concrete situation: An architecture suited to an internal prototype may be a poor fit for a critical service operated around the clock.
Associated terms: Use, criticality, organisation, constraint, timing.
Avoid: Copying a solution because it works elsewhere; treating all environments as equivalent.

04 / 04

Understanding

Definition: A shared, usable representation of what exists, what interacts, what blocks progress and which options remain open.
Nuance: Collecting information is not enough; understanding requires connecting, explaining and being able to guide action.
Concrete situation: Mapping a flow shows that a failure blamed on the application comes from an access rule and an operational dependency.
Associated terms: Representation, causality, model, explanation, option.
Avoid: Confusing data volume with understanding; declaring a cause before connecting the facts.

Put the terms to work

A term matters only when it clarifies action

If your situation does not fit a ready-made definition, that is precisely where scoping begins.

Qualify your situation