We’re coming across more and more artifacts created with the help of AI. In every field. Whether in our personal lives, at work, or\u2014as in my\/our case\u2014as a professional or expert… <\/p>\n\n
And in doing so, we\u2019ve noticed that the skill set required to inspect such artifacts has shifted significantly. The inspection process has become much more time-consuming because you can no longer tell anything about these items just by looking at them \u201cat first glance.\u201d Everything looks great\u2014it\u2019s all shiny and flashy. And to find any potential problem areas, you have to look very closely and dig very deep. <\/p>\n\n
It\u2019s helpful to know the associated prompts\u2014that is, to understand how AI was used to generate specific artifacts. This makes it clear where things might have been omitted (because they weren\u2019t included in the prompt to begin with) or, conversely, in what context and with what input data the artifacts were generated. <\/p>\n\n
Without the corresponding prompts, conducting a high-quality review is very tedious, difficult, and time-consuming, because errors and problems can, in principle, be hidden behind every single phrase. (Yes, I know that was the case in the past as well, but back then, the effort required to generate such artifacts was much greater.) <\/p>\n\n
Today, for example, I can say, \u201cWrite a 50-page bachelor\u2019s thesis on the topic of XY according to Mr. Wagenpfeil\u2019s guidelines.\u201d Right away. Boom. Done. Takes 15 minutes. <\/p>\n\n
As a professor, though, I still have to take a deep dive into this topic. The problem is\u2014the paper is probably really good, or at least pretty solid. But the knowledge contained in it has nothing to do with the student\u2019s own knowledge. Therefore\u2014an oral exam, and have the student defend the topic. It works reasonably well at the university, especially since we still require AI-generated papers. <\/p>\n\n
But in a project context? Or perhaps even when it comes to disputes? <\/p>\n\n
In that case, too, I can say, \u201cWrite a 500-page operational concept for Project XYZ that sounds just right.\u201d Right away. In a flash. Done. It only takes 15 minutes. <\/p>\n\n
As an expert, though, you still have to read through all that nonsense and review it. And even if, after 10 pages, you strongly suspect that the document doesn\u2019t quite fit the topic, you have to back that up. But unlike at the university, I often don\u2019t have anyone here to ask. That means analyzing cross-references in detail, comparing them with reality, conducting tests, and much more. <\/p>\n\n
In a way, this is the perfect guide to keeping people \u201cbusy.\u201d And we must not let that happen. We therefore need a new skills profile that clearly defines what AI can (and cannot) do, how AI is typically used, what we need to look for, and at what point we need to break out of this employment cycle. <\/p>\n\n
In AI-powered software processes, for example, I would always look at the prompts first and only then check the artifacts… <\/p>\n","protected":false},"excerpt":{"rendered":"