Enterprise UX in the Age of AI, Part 4: One Ecosystem, No Manual
Part four of a series on designing the tools behind the business. This time: Total Ecosystem Coherence and Smart Onboarding.
Part three was about trust in the numbers. This pair is about the spaces between: the gaps between tools, and the gap between a new starter and competence. Both are where enterprises quietly lose the most time.
Principle 7: Total Ecosystem Coherence
Nobody uses one tool. A support agent might touch six systems before lunch: the ticketing tool, the CRM, the knowledge base, the billing system, the chat platform, the phone software. Each context switch costs a little attention, and every inconsistency between tools costs a little more.
When the same action is called “close” in one system and “resolve” in another, when the search box sits top-left here and top-right there, when one tool’s “save” is another’s “submit”, each difference is tiny. Multiplied by every switch, every user, every day, they become a tax the organisation pays forever.
Coherence is the answer: a shared design system, shared terminology, single sign-on, and navigation that behaves the same way everywhere. The unit of design is no longer the app. It’s the ecosystem, because that’s what your users actually experience.
The AI twist
Agents are the ultimate ecosystem users. The tasks worth delegating are precisely the ones that cross tools: pull the ticket, check the account, update the record, notify the customer. A human absorbs inconsistency with a sigh. An agent turns it into an error.
If “close” means archive in one system and delete in another, a person learns the difference once. An agent acting across both at speed will eventually pick wrong, and it won’t feel suspicious afterwards. Semantic consistency, the same word meaning the same thing everywhere, used to be polish. It’s becoming a safety requirement.
This gives design systems a new job. Beyond shared components, they need shared meanings: consistent states, actions and permissions that both people and agents can rely on. The design system is quietly becoming the contract between your organisation and its automation.
Principle 8: Smart Onboarding
Enterprise tools have steep learning curves, and the traditional answer is training: a course, a manual, a video recorded three reorganisations ago. By the time the knowledge is needed, it’s gone.
Help has to live where the work lives. Tooltips at the point of decision, walkthroughs for the first attempt, guidance that appears when a user hesitates and gets out of the way when they don’t. The aim is learning in the flow of work, so the tool teaches itself and the training budget shrinks.
The AI twist
Every tool can now ship with an expert colleague inside it.
“How do I process a refund for a closed account?” used to mean searching a knowledge base, or interrupting whoever sits nearby and knows. Now the answer can arrive in context, grounded in your organisation’s actual policy, with the relevant screen one click away. For new starters this collapses weeks of awkwardness into a conversation.
Two cautions. First, onboarding help that hallucinates policy is worse than no help, because a new starter has no way to smell the error. Ground the assistant in verified documentation and link every answer to its source. The provenance rule from part three applies to guidance as much as to data.
Second, notice the symmetry: agents need onboarding too. An agent arriving in your ecosystem needs the same things a person does, context, examples, boundaries, and someone checking its early work. If part two’s job description was the hiring paperwork, this is the induction week. The organisations doing this well are writing onboarding material for software.
Where This Series Goes Next
Part five takes the unglamorous pair, Invisible Compliance and Mistake Recovery: how you audit an action nobody typed, and why undo is becoming the most important button in agentic software.
The thread here: the gaps between tools and between people are where AI helps most, and where it breaks most. Design the connective tissue on purpose.
Patrick Mooney is a senior design leader based in Ireland, with more than 25 years’ experience in UX, product and enterprise software, and the founder of Dublin UX. He writes at patrickmooney.me..