Creative v Machine Interaction Gap

A few months ago I wrote a paper about the way in which AI fails the creative industries, as a lot of AI products still do not really consider how different people naturally communicate. Some of us think visually, some verbally, some through sound, movement, examples or comparison. Yet most AI tools still begin with the dreaded prompt box, asking everyone to translate what is in their head into written instructions before the machine can do anything useful. We have used prompt boxes in our product, of course, but they need to be balanced with other types of input and used at times as a last resort, especially when we are trying to bridge the gap between the human and creative and the mechanical and logical.

A designer may know what feels wrong before they can explain why. A musician may communicate through sound. A creative director might work through references, mood, colour, association and comparison rather than a precise written brief. Asking them to convert all of that into text is not necessarily making the technology easier to use. It may simply be forcing people to communicate in the way the machine prefers.

There is a quiet inversion at work here. Prompt-based systems end up rewarding the people who can describe creativity well over those who actually practise it, giving an advantage to the prompt-writer rather than the practitioner.

Generative AI is now very good at producing text, images, video, audio and code, but the way we give it information has not developed at the same pace. A richer interface might let someone combine references, sketches, examples, taxonomy, emotional language, images, previous work and simple choices rather than trying to describe an entire creative vision in a paragraph. The point is not to remove language, but to recognise that natural language is much broader than words.

There is a cultural bias built into this too. Prompt systems privilege certain norms of expression, making some forms of communication easier for the AI to recognise than others, which is its own quiet kind of exclusion.

This becomes even more important when AI sits inside real business workflows. Different stakeholders often hold different parts of the knowledge: a designer understands the visual intention, a technical team understands what can be built, a commercial team understands the customer and someone else may understand compliance or production. If AI is going to sit between those people, it needs to help capture and hand off that knowledge without flattening it, misinterpreting it or quietly throwing away the parts that cannot easily be put into words. Human-in-the-loop oversight has a real role to play, but it should be there for judgment and compliance, not as a fallback for an interface that is hard to use. If people keep stepping out of the system just to make themselves understood, the model has failed, not the user.

For product developers, this means thinking beyond the model itself. Domain knowledge still matters, but so does understanding how the people in that domain actually think, communicate and make decisions. The best AI products may be the ones that learn how to meet users in those existing behaviours rather than training everyone to become better prompt writers.

The next step in AI interaction may therefore be less about teaching humans how to communicate with machines, and more about designing machines that can understand the different ways humans already communicate with each other.