The starting point is always a specific question and a clear bottleneck.

Context, assumptions, and areas of tension are organized, relevant insights are filtered, and a viable logic is developed from them. Only then do concepts, prototypes, or decision-making frameworks emerge that are tested in realistic conditions. Only then do concepts, prototypes, or decision-making frameworks emerge that can be further developed and made transferable as a stepping stone.

Conceptual Design creates clarity about what should be developed – and what should not.
It makes options visible, reduces risk, and creates robust decision-making foundations before resources are committed. The outcomes are concrete, testable, and designed for further development. 

  This route makes sense when decisions are stuck, when measures contradict each other, or when a lot is being done without clarity emerging.
In such cases, the problem often lies not in implementation, but in a lack of orientation,

flawed assumptions, or an unclear decision-making framework. 

Stations along this route

Examples of such stations include concept modules, prototypes, service logics, and decision models. They are intentionally designed to be independently developed, transferred, or licensed. The system logic is transferred, while the specific implementation is always newly developed based on the objective, context, and organization.