MITRE · ENTERPRISE AI · EXPERIENCE INTELLIGENCE

Building enterprise experience intelligence.

Connecting AI, operational evidence, and human centered insight to understand employee experience across the enterprise.

ENTERPRISE AI & EXPERIENCE INTELLIGENCE CONSULTANT EXPERIENCE STRATEGY · EVIDENCE ARCHITECTURE · AGENTIC WORKFLOWS

EXECUTIVE SUMMARY

Connecting enterprise evidence to improve employee experience.

At MITRE, I helped shape an Enterprise Experience Intelligence capability that connects human centered design, AI, operational evidence, research, process intelligence, and enterprise systems. My work focused on developing the evidence strategy and experience model, mapping relevant enterprise sources, and exploring how AI can help teams connect signals and identify questions for further investigation.

The goal was to make existing evidence more useful by connecting it to where friction may occur, who may be affected, and what questions could guide further investigation.

01 · THE ENTERPRISE CHALLENGE

Understanding experience across systems and processes.

An employee may rely on several systems, policies, approval steps, support channels, and teams to complete one task. I framed the opportunity as connecting evidence across that journey so teams can better understand where friction may occur and what context warrants further investigation.

01

Evidence across sources

Evidence spans platforms, reports, documents, and teams.

02

Journeys across systems

A single task may involve multiple systems and processes.

03

Context for signals

Operational measures can show activity and point to questions about its causes.

04

Evidence synthesis

Reviewing evidence across formats calls for careful synthesis.

05

Decision support

Connected evidence can help leaders assess whether a pattern merits broader attention.

02 · THE TRANSFORMATION OPPORTUNITY

Connecting evidence to support enterprise decisions.

FROM System| →Report| →Individual analysis| →Decision
TO
Evidence sourcesCommon evidence modelAI analysisExperience intelligencePrioritizationAction

I developed a model for bringing evidence from existing sources into a shared view. It is intended to help teams examine patterns, identify questions for research, and consider where action may create value. The approach complements research, service management, analytics, and operational expertise by making their evidence easier to consider together.

03 · THE EXPERIENCE INTELLIGENCE MODEL

A shared model helps explain enterprise friction.

Enterprise Experience Intelligence
PeopleWho is affected?
JourneyWhat are they trying to do?
TechnologyWhich systems support it?
ProcessWhat procedures shape it?
EvidenceWhat signals reveal friction?
ImpactWhat does it affect?

Together, these dimensions offer a shared way to interpret experience evidence from multiple sources.

04 · MAPPING THE ECOSYSTEM

Understanding the evidence landscape before building intelligence.

I developed an approach to inventory and classify approximately 400 enterprise applications, extending the view beyond application names and owners.

For each potential source, I considered ownership, supported journeys, evidence type, existing reporting, access constraints, and its potential contribution to experience intelligence. This creates a basis for deciding which sources merit closer exploration.

BEHAVIORAL OPERATIONAL TRANSACTIONAL EXPERIENTIAL CONTEXTUAL

05 · EVIDENCE STRATEGY

Building on authoritative enterprise sources.

Service tickets Service demand, recurring issues, support interactions
Behavioral analytics Adoption, workflow completion, user behavior and drop-off
Application monitoring Application health, performance, reliability and technical signals
Enterprise reporting Governed analytics and existing enterprise reporting
Transactional systems Workflow and operational activity
SOPs, SLAs & documentation Context for intended service and process behavior

I mapped how existing sources such as ServiceNow, WalkMe, Azure Monitoring, Power BI, transactional systems, and process documentation could contribute evidence. The strategy is to connect relevant information while preserving the role of each source as its authoritative record.

06 · AI AS AN INTELLIGENCE LAYER

Exploring how AI can help connect enterprise evidence.

Use AI to examine evidence and explore journey patterns.

Explore recommendations alongside their evidence.

Use later evidence to understand what changed.

AI can help teams examine enterprise evidence, with people guiding interpretation and decisions.
Illustrative scenario. Sample evidence, not client data.

07 · DESIGNING FOR TRUST

Evidence supports human decision-making.

I incorporated evidence visibility and human review into the proposed approach. For each interpretation, teams should be able to inspect the evidence, its source and recency, what may support or challenge it, and what remains uncertain before deciding what it means or what to do.

EVENTSA single occurrence or multiple incidents dispersed over time or closely clustered.
EVIDENCEConnect each event to its supporting or conflicting evidence, and show the source, timestamp, relevance, and gaps.
HUMAN REVIEWCheck whether the evidence supports the interpretation. Add context, challenge assumptions, assess confidence and priority, and decide what happens next.

08 · BUILDING THE EVIDENCE PIPELINE

Prototyping a traceable evidence pipeline.

01 PractitionerArtifacts 02 SharePointMetadata 03 StructuredJSON 04 Bitbucketbranch 05 Evidence registryupdate 06 Pullrequest 07 Manualreview 04 Bitbucketbranch 05 Evidence registryupdate 06 Pullrequest 07 Manualreview 01 PractitionerArtifacts 02 SharePointMetadata 03 StructuredJSON 04 Bitbucketbranch 05 Evidence registryupdate 06 Pullrequest 07 Manualreview 04 Bitbucketbranch 05 Evidence registryupdate 06 Pullrequest 07 Manualreview

I prototyped an automated workflow in Power Automate to bring user generated artifacts, including journey maps, survey results, and synthesized workshop and interview reports, from enterprise sources into a structured intelligence environment. Each artifact is represented in a structured JSON file, with review, traceability, and governance built into the workflow.

09 · HUMAN-CENTERED INTELLIGENCE

AI can help identify patterns. Human centered design helps interpret them.

ObserveDetect signals
→
CorrelateConnect evidence
→
InvestigateUnderstand context
→
InterpretFrame the problem
→
PrioritizeAssess significance
→
ActImprove the system
→
MeasureLearn what changed

10 · EXPERIENCE INTELLIGENCE ARCHITECTURE

I designed a proposed architecture to connect distributed enterprise signals and support informed decisions.

01Enterprise sources

Applications, service platforms, monitoring, analytics, research, process documentation, employee feedback

→
02Evidence layer

Operational, behavioral, transactional, research, process, and service evidence

→
03Experience layer

Employee journeys, friction themes, experience patterns, hypotheses, research opportunities

→
04Intelligence layer

Classification, normalization, correlation, pattern detection, journey mapping, AI supported synthesis

→
05Decision layer

Prioritization, leadership insight, investment, product, process, and research direction

11 · GOVERNANCE BEFORE SCALE

I documented guardrails to support responsible ESI development.

Evidence quality

Documented expectations for assessing whether sources are relevant, current, and reliable enough to support analysis.

Fairness and coverage

Added guidance to identify gaps in whose experiences are represented and to avoid treating incomplete evidence as a complete picture.

Traceability and explanation

Outlined how findings should link back to their sources and make the supporting evidence and assumptions clear to reviewers.

Privacy and access

Documented guardrails for using employee information appropriately and limiting access to what is needed.

Human review

Included guidance for surfacing conflicting or uncertain signals and having people validate interpretations before they inform action.

I took a human centered approach to governance, translating trustworthy AI principles into practical guidance for the ESI Toolkit. I documented how the capability should handle evidence, interpret signals, protect sensitive information, and involve people in reviewing AI generated findings.

12 · MY ROLE

I translated leadership direction into a path toward experience intelligence.

I translated leadership direction into a scoped approach with immediate steps and a longer term path. I led discovery, modeling, and prototyping to define how an IT/ET CX capability could understand employee experience across the enterprise.

DEFINED Leadership direction & scope Canonical entities (Employee profiles, Journeys, & Friction categories)
CONNECTED Canonical entities Applications & services Stakeholder groups Enterprise signals Situations
ENABLED Experience data model JSON views Ingestion and automated workflows IT/ET CX capability & reporting
8 Primary employee profiles defined, initially modeled with synthetic users and later grounded through discovery sessions and workshops I led
5 Core journey categories covering the employee lifecycle: candidate, onboarding, employee obligations, mission and sponsor initiatives, and offboarding/alumni
18 Canonical entities defined to connect employee profiles, journeys, and friction
15 Stakeholder groups mapped around enterprise capabilities, rather than individual people or department names
36 Page toolkit covering the executive overview, profiles, journeys, friction definitions, governance, security and safety adherence standards, and SharePoint metadata—with a GPT skill to generate outputs
~400 Enterprise applications inventoried to identify and prioritize high-value sources for evidence-based reporting
What this established

A connected foundation linking employee profiles and journeys to friction, enterprise signals, applications and services, and potential resolution paths. I defined the supporting attributes and JSON-based views, prototyped an automated SharePoint-to-JSON ingestion workflow, and led workshops to shape the IT/ET CX capability and its reporting.

The Enterprise Situational Intelligence app brings together a current view of employee experience issues, affected employees, financial impact, and issue context for senior leaders. This information can help leaders assess significance and inform decisions about where to focus attention and investment.

Employee needs and financial impact Prioritized action Leadership decisions

THE TRANSFORMATION

The work extends experience design to the intelligence that can inform improvement.

Enterprise Experience Intelligence is a developing approach to connecting people, process, technology, data, research, AI, governance, and experience. The work defines a path for using connected evidence to support learning and inform future decisions.