AI has moved beyond chat. Orchestration systems and agents now work as a central brain: they draw on almost all of humanity's recorded knowledge, and they are connected to the systems around them – they read their data and they control them. As an ERP consultant and solution architect, I work with such a system every day. Today I still hold the wheel. But the machine gets faster and more capable every month. I see AI development in three orders – in the sense of first-, second- and third-order effects. First-order work built the models. Second-order work turned them into agents and orchestration systems. Third-order work is ours – the people who now teach these systems to do real work. We see both in our own company: our technical lead builds the agents and implements them technically – that is second-order work. We consultants teach them how to behave in real work – that is third-order work. And this third-order work, I believe, is where it is decided what AI will actually do and how well. This session follows that journey in three parts. First, discovering the central brain: what changes when AI stops answering questions and starts doing real work across e-mail, Teams, documents, DevOps, ERP, HelpDesk (and hundreds of other systems in the future). Second, third-order work – how to talk to it and teach it using instructions, skills and plugins: why context, reasons, doubts and even emotions are data, not politeness – and why people who talk to AI "like a machine" get worse results. Including a side-by-side experiment: the same task, written two ways. And how one person's corrections become shared rules for the whole team – from features through user stories to code review. Third, the question none of us can avoid: we will most likely let go of the wheel voluntarily, for efficiency and comfort. What does that mean for our skills, our work and our society? No vendor pitch and no prompt templates – principles and real experience. Key takeaways: – The three orders of AI development – and why third-order work, people teaching AI to work, is decisive right now – Why context and the "why" matter more than prompt tricks – The principle of continuous improvement: mistake → correction with a reason → rule → shared with the team – Where will AI that can run everything at lightning speed take us – and why are the worlds of Skynet and I, Robot closer today than we think? (A philosophical reflection)
Dear DynamicsMinds team, I truly appreciate that DynamicsMinds goes beyond technology and leaves room for the philosophical and social side of what we do. That is why I am submitting this topic to the Fifth Track rather than to one of the product tracks. It is platform-independent and focused on people, communication and the impact on society. I am a returning speaker (DynamicsMinds 2023 and 2024). The session builds on my recent LinkedIn article "How long will we keep hold of the wheel?" (EN:
Originally, I graduated from a military university as a commander of chemical units. However, my career path took a turn, and I transitioned to working in a company specializing in the development, production, and supply of extensive radiation control systems, particularly for nuclear power plants. To effectively manage a substantial portfolio of ongoing projects, I took it upon myself to program a multi-project management system. This system proved to be highly successful and remained in use for nearly a decade. Seeking a deeper understanding of business processes, I furthered my education by earning a degree from the Faculty of Economics. Subsequently, I ventured into the realm of ERP systems, working as a consultant with hands-on experience in production, development, and project management. Over the years, I've had the opportunity to lead numerous substantial implementation projects as a solution architect. In this role, I've professionally overseen entire teams and collaborated closely with project managers to ensure successful outcomes.