The job that doesn't have a name yet
A role is being built right now under other job titles, because the need showed up before the title did.
The claim
There's a job being done inside a growing number of companies right now that doesn't have a stable name, a standard job description, or an established career path. It's being done anyway, usually under some other title (UX, digital transformation, AI enablement, operations) because the need for it showed up before the title did.
What the work actually is
The work is choosing, organising and maintaining what an AI system needs to know to work consistently inside a company: what's already happened, the exceptions to the rules, the tone the output needs, and what has to be left out. It isn't prompt engineering, which is about how instructions are worded. It isn't documentation either, because documentation is written for people to read, not for a model to take in all at once. And it isn't UX as usually practised: wireframes and flow diagrams are made for people to look at, not for software to work from directly.
Why it doesn't have a name yet
Job titles usually arrive long after the need. UX was practised for years before it had its own department, title or hiring process. Growth and DevOps went the same way: people did the work under other titles until the industry settled on a name. This work is early in that same lag. In July 2026 the Nielsen Norman Group used the term "UX-context design", one of the first attempts to name part of it from the UX side. The naming has started; it hasn't finished. Context Design is this site's own attempt at a name, for the same reason.
Why naming it early matters
Work without a name tends to get missed when resources are handed out. It doesn't appear in job ads, budgets or org charts, so a company can lack the capability entirely without noticing: there's no box on the chart to show it's missing. Naming the discipline lets a company hire for it on purpose, instead of quietly relying on whoever has "AI" or "UX" in their title to do it on top of their actual job. It also helps the people already doing it see their work as a coherent discipline rather than a vague extra.
Where this leaves the work
This site starts from the premise that this is a real practice and will have a standard name before long. I'd rather do the work in public now than wait for the job description to exist. The role already works without a final name. It just needs someone doing it, which is what the work itself is there to show.
--- date: 2026-08-18 updated: 2026-10-03 title: The job that doesn't have a name yet slug: the-job-that-doesnt-have-a-name-yet summary: A role is being built right now under other job titles, because the need showed up before the title did. stat: July 2026 stat_label: when one of the first names for part of this work appeared ---
If this sounds like your business, the audit is the quickest way to find out what your AI is missing: one workflow, one 90-minute session, and a written brief on what to fix first.
Book the auditPrefer to talk first? Get in touch — no obligation.