Judgment · A recurring failure, and what it taught me
The toolset nobody could use
Across four studios I've watched the same tool project fail the same way. The rooms had engineering authority and domain authority. What they never had was design authority.
The pattern
A small engineering team builds a new toolset for a department. One artist is embedded. Everyone else is invited to give input, and every piece of that input is treated as sacred.
What comes out is technically capable and close to unusable. An enormous plumbing burden, an interface nobody can navigate, and a handful of people who ever really learn it. Worse, the genuinely important ideas get sorted into the hard-to-build pile and shelved, while low-hanging features nobody needed ship on time and the project wraps.
The diagnosis
It isn't a skills gap. Those rooms have engineering authority, and they have domain authority. What they don't have is design authority — anyone whose job is to take the wish list, reject most of it in service of something coherent, and own that call.
Raw input isn't design input. Most of the artists giving notes had never used a comparable system anywhere else. They had no reference for what good looked like, so they described their current pain rather than a better tool. That isn't their failing; it's what happens when you ask people to specify something they've never seen.
Why it matters more now
Until recently, building tools was gated behind engineering, and that gate did some accidental quality control. The gate is gone.
Engineers now ship more, faster, and the tools stay technical — someone who doesn't live inside the work can't feel where the interface is wrong. Artists build their first tools ever, and they build small, single-purpose buttons that do something clever and solve nothing structural. Both groups are producing more than they ever have. Neither has interface design literacy, and because neither has it, nobody notices it's missing.