Enterprise Generative Search — Azure and Open Source · View 05 of 41 · People and journeys
The people who ask Knowledge Worker 9,000 daily, 26 queries a week Goal — Give me an answer I can paste into a client mail without opening three documents to check it first. Core journeys Ask and act on one answer 180k queries a month Follow up in the same thread Open the source that convinced me Research Analyst 400 seats, regulated work Goal — Show me every place we said something about this, including the places that disagree, and let me cite it. Core journeys Answer a multi-hop question 9k a month Compare positions across sources Export an evidence pack Field Engineer 1,200 mobile, low bandwidth Goal — Let me photograph the panel in front of me and get the right procedure for that exact revision. Core journeys Search from a photo Ask by voice, hands busy Pin a procedure offline The people who keep it honest Knowledge Steward 85 content owners Goal — Tell me why my document is not being found, in terms I can act on without raising a ticket. Core journeys Diagnose a document that never surfaces the trust journey Retire and supersede content Read my domain coverage report Search Platform Engineer 6 engineers, on call Goal — When an answer is wrong, tell me in one trace whether it was retrieval, ranking, context or the model. Core journeys Triage a bad answer from its trace Ship a retrieval change behind a gate Rebuild an index without downtime Security and Compliance Officer 2 named owners Goal — Prove to an auditor that no answer ever contained a passage its reader could not have opened. Core journeys Replay an answer for an audit Attest the entitlement path Review injection and safety events Machines that act without being asked Source Connectors 6 sources, delta-driven Goal — Notice every change in my source within its freshness class and never lose one silently. Core journeys Pull a delta and enqueue it Reconcile a missed change Entitlement Sync 60-second target Goal — Make a permission change true in the index before the person it affects asks their next question. Core journeys Apply an ACL delta Invalidate affected cache keys Nightly Evaluation Run 1,400 golden queries Goal — Fail the build before a regression reaches a person who is going to trust the answer. Core journeys Score retrieval and generation Block a release on a gate Re-embed and Compact model-version driven Goal — Move the corpus to a new embedding model without a day where the index answers from two. Core journeys Shadow-build a new index Cut over by alias Systems that consume answers CRM Assistant on-behalf-of the seller Goal — Ask on my user's behalf and inherit exactly what they may see, with no access model of my own. Core journeys Ask with a delegated token Render citations inline Intranet Answer Widget read-only embed Goal — Answer the six questions people ask the intranet every day without a second content pipeline. Core journeys Serve a cached common answer Fall back to a result list Actors and Their Core Journeys Person or role Journey / task Security / platform External / third party Every actor here has a goal in their own words. Three of these journeys are mapped in views 06 to 08; the rest are served by views later in the set. v 1.0 · owner Data and AI Global Practice
Why the machines have cards
The connectors, the entitlement sync, the nightly evaluation and the re-embedding job each have a goal, a target and a failure path. The entitlement sync in particular has a 60-second goal that is a security control, not a performance one.
The CRM assistant is listed as a consuming system with no entitlements of its own. That single line is the whole security argument for the downstream integration in view 37.
The journeys that got their own map
Ask and act on one answer — the highest volume and the journey a sponsor judges the platform by.
Answer a multi-hop question that has to survive review — where correctness, not speed, is the failure mode.
Diagnose a document that never surfaces — the journey that decides whether stewards trust the platform or blame it.
Deliberately not mapped
The field engineer, the platform engineer and the compliance officer have named journeys but no map. Each is answered by a view later in the set — 28, 34 and 40 respectively — and none surfaced a distinct structural requirement that those views do not already carry.
