AI in Design Software
"Automate tedious data conditioning. Never automate professional judgment."
— Barbara Mirel, Interaction Design for Complex Problem Solving, 2004
The arrival of AI in creative software has been met with roughly equal parts enthusiasm and dread, and with good reason on both counts. Generative AI that produces images, music, or 3D assets from a text prompt is, depending on whom you ask, either a revolution or a threat. But this debate — fascinating as it is — obscures a far more useful question: what happens when you point AI at the friction around the creative work rather than at the creative work itself?
The answer, it turns out, is that professionals overwhelmingly welcome it, provided it stays out of the way of their judgment. The distinction that matters is between AI that performs the task and AI that supports the human's process. Automation research made this case long before generative AI existed: Lisanne Bainbridge's classic paper on the "ironies of automation" showed that handing a task entirely to a machine erodes the very skill and vigilance a person needs for the moments the machine gets it wrong.1 This maps precisely onto what we already know about complex software design: the goal is to reduce extraneous cognitive load, never to remove intrinsic load. The work is the point; the friction around it is not.
The Four Roles of AI in Creative Tools​
There are four distinct roles AI can play in professional creative software without stepping on the creative process. Each targets a different kind of friction, and each has different design implications.
1. Doing the Otherwise Impossible​
Some things are simply beyond practical human effort. Turning a 2D photograph into a spatial, navigable 3D scene. Reconstructing a complete environment from a handful of reference images. Generating plausible motion capture data from monocular video. These aren't tasks that artists used to do by hand and now don't have to — they're tasks that couldn't be done at all without AI, or required equipment so specialised that most studios couldn't justify the cost.
Neural Radiance Fields (NeRFs) are a good example. What once required expensive LIDAR rigs can now be approximated from commodity camera footage, opening up entirely new creative possibilities for independent artists and smaller studios.2 The AI here isn't replacing a workflow; it's creating one that didn't exist. This is the least contentious use of AI in creative tools, because there's nothing to feel replaced by.
The design implication is straightforward: when AI enables something genuinely new, the challenge is in making the output editable and composable within existing workflows. An AI-generated 3D reconstruction is only useful if it can be lit, textured, and rendered like any other scene element. The magic trick means nothing if it produces an opaque, untouchable result.
2. Eliminating Tedium​
Every creative discipline has its version of housekeeping — the work that's necessary but creatively unrewarding. Rotoscoping in VFX. Retopology and UV unwrapping in 3D. Naming and organising layers. Tagging assets. Conforming exports to delivery specifications. These are tasks where the artist's expertise is needed to verify the result, but the process of getting there is mechanical drudgery.
This is where AI can be transformative without being threatening. Nuke's CopyCat uses supervised machine learning to accelerate rotoscoping — a task that previously consumed days of artist time per shot.3 Auto-retopology tools generate clean mesh topology and UV maps from high-poly sculpts. Autodesk's AI assistant for Maya and 3ds Max is explicitly positioned as being "less about automation and more about removing friction when you're stuck."4
The critical design principle here is that AI should do the grunt work and then hand the result back for human review. The artist must remain the authority. An auto-generated roto mask that can't be adjusted by hand is useless; one that gets you 90% of the way there and then lets you refine the remaining 10% is worth its weight in gold. This maps directly to Mirel's distinction between easing burdens and simplifying work — you're easing the burden of mechanical execution without simplifying the professional judgment required to know when the result is correct.5
The same automation research offers a useful caution here: offloading effort tends to offload engagement along with it, whether or not the task in question actually warranted less scrutiny.1 The implication for design is clear — AI should handle tasks where reduced engagement is acceptable (naming layers, optimising geometry) and stay well away from tasks where it isn't (colour grading, composition, narrative editing).
3. Filling Functionality Gaps​
Professional workflows are idiosyncratic. No matter how comprehensive a DCC application is, there will always be moments where a user needs a specific tool or behaviour that simply doesn't exist. Historically, this meant writing a script, a plugin, or a workaround — or, more often, just living with the limitation.
AI can serve as a bridge here, generating bespoke tools or procedural operations on demand. Need a script that distributes objects along a spline with specific randomisation parameters? Need a shader that does something the material editor doesn't natively support? Need a batch operation that renames, resizes, and re-exports 400 assets according to a naming convention your studio invented last Tuesday? These are cases where AI acts less like a creative tool and more like a very capable technical assistant — one that understands the application's scripting API and can translate an artist's intent into executable code.
The design challenge is in making this capability discoverable and trustworthy. An AI that generates scripts needs to be transparent about what those scripts do, and the user needs a way to inspect, modify, and save the result. This is fundamentally about maintaining the user's sense of agency — they're still the one deciding what to build; the AI is just removing the barrier between the idea and the implementation.
4. Pre-Flight and Quality Assurance​
The fourth role is one that barely existed before AI made it practical: automated pre-flight checking. Designers aren't accessibility experts. Animators aren't performance engineers. Compositors aren't colour scientists (well, some are, but you take the point). There are entire categories of quality concern that fall outside a creative professional's core expertise but nonetheless affect the final output.
AI-powered pre-flight systems can check a design against accessibility standards (contrast ratios, colour blindness simulation, screen reader compatibility), audit a 3D scene for performance issues (excessive polygon counts, inefficient shader graphs, texture memory overruns), or verify that an animation meets broadcast delivery specifications — all without requiring the artist to become an expert in those domains.
This is AI as a safety net, not as a creative partner. The key design principle is that pre-flight results should be advisory, not blocking. Present the findings, explain the implications, offer to fix what can be fixed automatically, but never prevent the user from shipping if they've made a conscious decision to accept the trade-off. A warning is useful; a gate is patronising.
The Trouble with Prompts​
Whichever of the four roles AI plays, it needs an interface, and the default one — a blank text box — is usually a poor fit for professional work. A 2023 study of a Stable Diffusion forum collected 78,911 posts, read the highest-value 1,068 closely, and catalogued 25 recurring user behaviours across 8 user types.6 The pattern that stands out: serious users kept building their own tooling around the prompt box rather than living with it as supplied — tag autocomplete, prompt search, EXIF viewers to recover the prompt behind someone else's image, tag recommendation, tag-weight conversion. None of this exists because people enjoy building infrastructure in their spare time. It exists because a prompt is a leaky abstraction over the model's internals, and professionals will always route around a leaky abstraction if the capability underneath is worth having.
A prompt, in other words, is not a natural unit of professional intent. It is the model's API, handed to the user directly because building a proper interface on top of it is more work than not doing so. The fix follows the rest of this section: keep the model's input format out of the user's hands. Ask about the project, the constraints, the goal — structured questions, structured answers — and translate that into the prompt behind the scenes. The user should not need to know the word "prompt," let alone write one.
The Underlying Principle​
These four roles share a common thread, and it's one that aligns with everything else in this guide: AI should reduce extraneous cognitive load without touching intrinsic cognitive load. It should make the mechanical parts of creative work faster, make the impossible parts possible, fill gaps in expertise and tooling, and catch mistakes the user isn't equipped to catch — all while leaving the creative judgment, the aesthetic decisions, and the professional expertise firmly in human hands.
Or, to put it in terms of Larry Tesler's law of conservation of complexity7: AI can absorb complexity that the user shouldn't have to deal with, but it must never absorb the complexity that is the work.
A 2025 Dezeen survey found that 81% of designers felt AI "dulled creativity" — but critically, this correlated with AI being used for generative creative tasks, not for friction-reducing housekeeping.8 When AI stays in its lane — handling the tedious, the impossible, the peripheral, and the mechanical — professionals don't just tolerate it, they welcome it. When it reaches for the steering wheel, they resist, and rightly so.