For a successful enrolment of modern E-Learning-based education, it is inevitable to apply a holistic quality-concept across the entirety of processes around planning, development, implementation, exploitation, and dissemination. The aim of a related quality strategy is ensuring that all stakeholders in the supply chain fully understand all processes, conditions, and responsibilities. For this purpose, proper descriptions of the processes are required. What makes a proper and homogenous description of processes on a general level very complicated, is the fact that stakeholders from different fields need to fully understand them. In our experience, if project partners do not feel familiar with a certain type of process-representation method, it is most likely that they either stay ignorant regarding the details or generally reject the processes in lack of understanding. In smaller TEL-related projects (up to 15 partners) face-to-face discussions at the round table can reveal and cope with lacks of understanding. But what happens when face-to-face discussions are not an option because of the project's size? In such contexts how can still be ensured that all partners in the project fully understand their own responsibilities and also dependencies between different project parts? A compromise between formal, semi-formal and informal description models is required without losing information but aiming interdisciplinary comprehensibility. Particularly for such cases, we developed a project description model type, which provides benefits of several existing process description models and languages and eventually produces outcomes easy enough to understand for any kind of (academic) education. With 51 project partners from several fields, we tested the modelling technique in both directions, confronting the project partners with a variety of already described project-related processes as well as asking them to describe their own planned processes. The tool we are going to introduce alongside the methodology bases on MS PowerPoint. We decided to use this particular application because we found it most commonly used the employees of all of our project partners' organizations/institutions.
