Your UX Team Is Set Up for the Wrong Job

This month we look at why most in-house UX teams are organized around work that no longer arrives in the way it used to. Product owners, developers, and marketers are all producing design with AI tools long before anyone thinks to raise a ticket, and telling them to stop has quietly stopped working. We talk about what to fund instead, how to measure a team that is no longer the bottleneck, and where Marcus thinks Paul has gone too far. We also cover a new tool that gives a freelancer something close to a staff team, a new free email course, and the unexpected link between bees, a man with a bin on his head, and the power of consistently turning up.

App of the Month: Grok Bot

Grok Bot launched in early beta on 11 August 2026 from SpaceXAI and Cursor, and it is the first AI tool in a while that has genuinely surprised Paul. Rather than a single chat window, you spin up a set of agents with their own roles, so there is a chief operating officer to talk to day to day, plus a finance person, a marketer, a salesperson, and a designer. Each one has its own computer, they brief each other, and they keep working after you shut the laptop.

What makes it interesting is the complete absence of setup. There are no API keys to find and no MCP servers to wire up. You tell it which service you use, it pops up a button, you log in as you normally would, and it handles the rest. If there is no connector, it falls back to a browser. Paul asked it about a client message sitting in Slack, and it read the thread, gave him advice, created a task for Monday, added a note to the relevant meeting, and then offered to write the Slack message telling the developers what was happening.

For freelancers who lose hours to the admin they are least confident about, this is the closest thing yet to having colleagues. Marcus raised the obvious concerns about privacy and about becoming too reliant on output nobody checks, which is fair. Paul's answer to the second one is a quality control agent whose only job is to check everyone else's work, with the caveat that both can still be wrong.

The catch is the price. It runs at $200 a month, although that does include Cursor.

How the team is set up for the wrong jobEverybody is designing now

Paul used to insist that only proper UX people should do UX, and he is honest that a good part of that was protecting the job description rather than protecting the user. That position has become much harder to defend. Product owners come back from an hour with an AI tool holding a prototype and a flow that mostly hangs together. Developers generate interface options before the ticket has even been refined. Marketers build and test their own landing pages. Some of it is good, some of it is plausible rubbish, and all of it turns up before anyone thinks to involve design.

The complaint Paul hears most often from in-house teams is some version of how do we stop people doing this. In our experience you cannot stop them, because going around you is faster than waiting three months for a slot. The consequences are real, they are just delayed. Somebody ships a prototype that looked fine, and six months later the accessibility has failed quietly, the conversion rate is poor, and the product looks like it was built by three different companies. By then everyone has moved on and the rework never gets attributed to the decision that caused it.

Cutting the team is the expensive response

Meanwhile the money is going the other way. Headcount that leaves is not replaced, and the seat at the table turns into being asked to comment on decisions that have already been made. Cutting the team is the expensive response, because the work does not disappear, it just gets done worse and later.

What to fund instead

The organizations getting this right have moved design upstream, away from producing every screen. Fund the team to set the conditions instead of being the only route to a wireframe:

• A design system with real usage guidance, so a developer at 4pm can make a decent decision, or brief an AI to make one, without booking time with a designer.
• Playbooks for the work that keeps repeating. Landing pages are the obvious one, because marketers are already building them and they are not conversion experts, copywriters, or developers.
• A research repository that anyone can query, so the findings get used in the meeting six months after the readout instead of dying in a slide deck.
• Office hours, audits, and coaching as the service, with the hard political work still firmly on the books.

How you measure the team

How the team is measured has to change with it. If people are still judged on screens produced and tickets closed, the queue rebuilds itself inside a month, because nobody can afford to spend a week writing guidance that tanks their own numbers. Measure whether other people shipped something decent without design touching the file. Measure whether last quarter's research got referenced again. A quieter team is a sign the setup is working, not evidence that they are underemployed.

Where Marcus disagrees

Marcus pushed back, and the disagreement is worth listening to in full. He is happy with the developer querying a design system, and he has argued for years that a salesperson or researcher should not be drawing wireframes, because a wireframe is a series of design decisions dressed up as a diagram. His worry is that Paul is conceding ground that should be defended, particularly where the design is new rather than an application of existing rules. Paul's split is between taste and rules. Branding and anything close to art still needs a human leading, but interface and information design runs on accessibility standards, hierarchy, grids, and type scales, and those are rules a well-trained AI can follow. The important word is trained. Briefed cold, these tools produce something plausible and shallow. Given a design system, real guidance, and quality checks, the output gets good, and a designer spending fifteen minutes critiquing it is a better use of talent than two days pushing pixels in Figma.

There is a caveat for agencies, which Marcus is right about. At Headscape every project starts from scratch with a new brand, so there is more taste involved and more reason to keep a designer in the driving seat. In a bigger in-house setting, you decide the level of human check based on risk. That might be every piece of work going past a designer, or spot checks weighted toward people who are new to the tools.

Two things neither of us could answer

Two worries neither of us could answer. Plenty of designers love the craft of moving things around, and asking them to write documentation instead is not the job they signed up for, so this has to be handled with a lot more care than most organizations are known for. The bigger one is where the next generation comes from. If non-designers now do the work junior designers used to learn on, and the design knowledge in the tools stops being refreshed, the whole thing stagnates.

Where to start on Monday

If you want somewhere to start on Monday, ask whoever runs design what people keep coming to them for week after week, fund turning one of those into something the rest of the business can use without them, and stop routing every request through the person who still says yes.

If that conversation is one you are having with your own team, the UX design leadership workshop covers the same ground in more depth.

Read of the Month

Paul has released a free 14-lesson email course, Become the UX practitioner your organization actually needs. It makes the same argument as this episode with the detail we could not fit into an hour, delivered as short emails every couple of days, plus the full workshop slide deck as a PDF.

The written version of this month's topic is also up as Your UX team is set up for the wrong job.

Marcus' Joke

I just got a new job making plastic Draculas. There's only two of us on the assembly line, so I have to make every second count!

Find The Latest Show Notes