Scaling Intelligence: A modular AI Assistant Layer

Architected a modular, cross-platform AI framework that unified disparate product experiences into a single, future-proof conversational layer.

Gradient 1 - Blue

Scaling Intelligence: A modular AI Assistant Layer

Architected a modular, cross-platform AI framework that unified disparate product experiences into a single, future-proof conversational layer.

Gradient 1 - Blue

Scaling Intelligence: A modular AI Assistant Layer

Architected a modular, cross-platform AI framework that unified disparate product experiences into a single, future-proof conversational layer.

Gradient 1 - Blue

Overview

As Senior Product Designer and Design Systems Lead, I led the creation of Ask Intel, the company’s first unified conversational AI platform.

Rather than launching another support widget, I architected an AI Assistant Layer that now serves as a scalable orchestration system across support, documentation and contact flows.

This was not a UI project. It was a systems redesign.

Role & Scope

I led the end-to-end design of Ask Intel, the company's first enterprise-wide conversational assistant. This meant defining the conversational model, building the chat UI and creating a scalable component system. This was a ground-up effort. No prior assistant, no existing framework, no shared model for conversational behavior. I established the foundation that Intel's conversational experiences continue to scale on.

Role
Senior Product Designer, Design Systems Lead for Digital Experiences at Intel
Platform
Web (responsive), integrated across Intel.com support ecosystem
Collaboration
Support teams, content owners, engineering, NLP teams

Challenge

Intel's legacy chat tools were:

Reactive
Siloed by business unit
Inaccessible in complex flows
Detached from structured content systems

Each group optimized locally. Users experienced fragmentation globally.

The mandate was clear: Move from “chat as add-on” to AI as a primary navigation and resolution layer.

Accessibility as Architecture

Conversational interfaces break differently than pages. I engineered:

aria-live="polite" regions for non-disruptive screen reader updates
Focus trap logic with controlled tabindex="-1" management
Transparent modal states (aria-modal, aria-expanded)
Failure state handling for AI uncertainty

Testing with keyboard-only and non-visual users surfaced logic gaps earlier than any prototype review.

I led a custom rebuild:

Key Insights

AI is not a UI feature.
It is a systems challenge involving data hygiene, governance and structured content.
By embedding conversational patterns into the Design System, we created a reusable foundation, not a one-off experiment.

Impact

KPI
Improvement
Metric Type
Support Deflection
22%
Operational Efficiency

A11y Speed
35% faster
Accessibility/CX Speed

Task Success
92%
User Proficiency

Compliance
100% WCAG 2.1 AA
Technical Standard

My Approach: Build the Foundation First

We aligned taxonomy, metadata and content governance before scaling. Before designing conversations, I focused on infrastructure.

1

The Assistant Layer

Conversational AI is systems design, not just UI. Success required aligning taxonomy, content quality, NLP capabilities, localization and user expectations. Not just building a chat window.

2

The Experience Layer

Enterprise users demand clarity and trust. Conversational design must be transparent, concise and predictable to work effectively in large organizations. Vague or uncertain responses erode confidence quickly.

3

The Explainer Layer

Machine-readable, modular content blocks designed for both internal logic and external LLM citation.

Detailed Results

80%+
Customer satisfaction with AI-assisted support interactions.
35%
Improvement in task completion compared to traditional documentation search.
Reduced support agent workload by handling routine, repetitive questions automatically.
Unified support entry point across business units, improving consistency.
Organic adoption growth because the experience felt easier than traditional search.
Scalable foundation for future AI-driven support experiences across Intel's ecosystem.

When systems break, teams slow down.

I work across UX, architecture and content to prevent fragmentation and help organizations move faster with confidence.

© Kevin Shalkowsky 2026 - All rights reserved

© Kevin Shalkowsky 2026 - All rights reserved

© Kevin Shalkowsky 2026 - All rights reserved

© Kevin Shalkowsky 2026 - All rights reserved

© Kevin Shalkowsky 2026 - All rights reserved

Overview

As Senior Product Designer and Design Systems Lead, I led the creation of Ask Intel, the company’s first unified conversational AI platform.

Rather than launching another support widget, I architected an AI Assistant Layer that now serves as a scalable orchestration system across support, documentation and contact flows.

This was not a UI project. It was a systems redesign.

Reactive
Siloed by business unit
Inaccessible in complex flows
Detached from structured content systems

Challenge

Intel's legacy chat tools were:

Each group optimized locally. Users experienced fragmentation globally.

The mandate was clear: Move from “chat as add-on” to AI as a primary navigation and resolution layer.

aria-live="polite" regions for non-disruptive screen reader updates
Focus trap logic with controlled tabindex="-1" management
Transparent modal states (aria-modal, aria-expanded)
Failure state handling for AI uncertainty

Accessibility as Architecture

Conversational interfaces break differently than pages. I engineered:

Testing with keyboard-only and non-visual users surfaced logic gaps earlier than any prototype review.

I led a custom rebuild:

Impact

KPI
Improvement
Metric Type
Support Deflection
22%
Operational Efficiency

A11y Speed
35% faster
Accessibility/CX Speed

Task Success
92%
User Proficiency

Compliance
100% WCAG 2.1 AA
Technical Standard

My Approach: Build the Foundation First

We aligned taxonomy, metadata and content governance before scaling. Before designing conversations, I focused on infrastructure.

1

The Assistant Layer

Conversational AI is systems design, not just UI. Success required aligning taxonomy, content quality, NLP capabilities, localization and user expectations. Not just building a chat window.

2

The Experience Layer

Enterprise users demand clarity and trust. Conversational design must be transparent, concise and predictable to work effectively in large organizations. Vague or uncertain responses erode confidence quickly.

3

The Explainer Layer

Machine-readable, modular content blocks designed for both internal logic and external LLM citation.

Detailed Results

80%+
Customer satisfaction with AI-assisted support interactions.
35%
Improvement in task completion compared to traditional documentation search.
Reduced support agent workload by handling routine, repetitive questions automatically.
Unified support entry point across business units, improving consistency.
Organic adoption growth because the experience felt easier than traditional search.
Scalable foundation for future AI-driven support experiences across Intel's ecosystem.

Overview

As Senior Product Designer and Design Systems Lead, I led the creation of Ask Intel, the company’s first unified conversational AI platform.

Rather than launching another support widget, I architected an AI Assistant Layer that now serves as a scalable orchestration system across support, documentation and contact flows.

This was not a UI project. It was a systems redesign.

Reactive
Siloed by business unit
Inaccessible in complex flows
Detached from structured content systems

Challenge

Intel's legacy chat tools were:

Each group optimized locally. Users experienced fragmentation globally.

The mandate was clear: Move from “chat as add-on” to AI as a primary navigation and resolution layer.

aria-live="polite" regions for non-disruptive screen reader updates
Focus trap logic with controlled tabindex="-1" management
Transparent modal states (aria-modal, aria-expanded)
Failure state handling for AI uncertainty

Accessibility as Architecture

Conversational interfaces break differently than pages. I engineered:

Testing with keyboard-only and non-visual users surfaced logic gaps earlier than any prototype review.

I led a custom rebuild:

Impact

KPI
Improvement
Metric Type
Support Deflection
22%
Operational Efficiency

A11y Speed
35% faster
Accessibility/CX Speed

Task Success
92%
User Proficiency

Compliance
100% WCAG 2.1 AA
Technical Standard

My Approach: Build the Foundation First

We aligned taxonomy, metadata and content governance before scaling. Before designing conversations, I focused on infrastructure.

1

The Assistant Layer

Conversational AI is systems design, not just UI. Success required aligning taxonomy, content quality, NLP capabilities, localization and user expectations. Not just building a chat window.

2

The Experience Layer

Enterprise users demand clarity and trust. Conversational design must be transparent, concise and predictable to work effectively in large organizations. Vague or uncertain responses erode confidence quickly.

3

The Explainer Layer

Machine-readable, modular content blocks designed for both internal logic and external LLM citation.

Detailed Results

80%+
Customer satisfaction with AI-assisted support interactions.
35%
Improvement in task completion compared to traditional documentation search.
Reduced support agent workload by handling routine, repetitive questions automatically.
Unified support entry point across business units, improving consistency.
Organic adoption growth because the experience felt easier than traditional search.
Scalable foundation for future AI-driven support experiences across Intel's ecosystem.

Overview

As Senior Product Designer and Design Systems Lead, I led the creation of Ask Intel, the company’s first unified conversational AI platform.

Rather than launching another support widget, I architected an AI Assistant Layer that now serves as a scalable orchestration system across support, documentation and contact flows.

This was not a UI project. It was a systems redesign.

Reactive
Siloed by business unit
Inaccessible in complex flows
Detached from structured content systems

Challenge

Intel's legacy chat tools were:

Each group optimized locally. Users experienced fragmentation globally.

The mandate was clear: Move from “chat as add-on” to AI as a primary navigation and resolution layer.

aria-live="polite" regions for non-disruptive screen reader updates
Focus trap logic with controlled tabindex="-1" management
Transparent modal states (aria-modal, aria-expanded)
Failure state handling for AI uncertainty

Accessibility as Architecture

Conversational interfaces break differently than pages. I engineered:

Testing with keyboard-only and non-visual users surfaced logic gaps earlier than any prototype review.

I led a custom rebuild:

Impact

KPI

Support Deflection

Improvement

22%

Metric Type

Operational Efficiency

KPI

A11y Speed

Improvement

35% faster

Metric Type

Accessibility/CX Speed

KPI

Task Success

Improvement

92%

Metric Type

User Proficiency

KPI

Compliance

Improvement

100% WCAG 2.1 AA

Metric Type

Technical Standard

My Approach: Build the Foundation First

We aligned taxonomy, metadata and content governance before scaling. Before designing conversations, I focused on infrastructure.

1

The Assistant Layer

Conversational AI is systems design, not just UI. Success required aligning taxonomy, content quality, NLP capabilities, localization and user expectations. Not just building a chat window.

2

The Experience Layer

Enterprise users demand clarity and trust. Conversational design must be transparent, concise and predictable to work effectively in large organizations. Vague or uncertain responses erode confidence quickly.

3

The Explainer Layer

Machine-readable, modular content blocks designed for both internal logic and external LLM citation.

Detailed Results

80%+
Customer satisfaction with AI-assisted support interactions.
35%
Improvement in task completion compared to traditional documentation search.
Reduced support agent workload by handling routine, repetitive questions automatically.
Unified support entry point across business units, improving consistency.
Organic adoption growth because the experience felt easier than traditional search.
Scalable foundation for future AI-driven support experiences across Intel's ecosystem.

Overview

As Senior Product Designer and Design Systems Lead, I led the creation of Ask Intel, the company’s first unified conversational AI platform.

Rather than launching another support widget, I architected an AI Assistant Layer that now serves as a scalable orchestration system across support, documentation and contact flows.

This was not a UI project. It was a systems redesign.

Reactive
Siloed by business unit
Inaccessible in complex flows
Detached from structured content systems

Challenge

Intel's legacy chat tools were:

Each group optimized locally. Users experienced fragmentation globally.

The mandate was clear: Move from “chat as add-on” to AI as a primary navigation and resolution layer.

aria-live="polite" regions for non-disruptive screen reader updates
Focus trap logic with controlled tabindex="-1" management
Transparent modal states (aria-modal, aria-expanded)
Failure state handling for AI uncertainty

Accessibility as Architecture

Conversational interfaces break differently than pages. I engineered:

Testing with keyboard-only and non-visual users surfaced logic gaps earlier than any prototype review.

I led a custom rebuild:

Impact

KPI

Support Deflection

Improvement

22%

Metric Type

Operational Efficiency

KPI

A11y Speed

Improvement

35% faster

Metric Type

Accessibility/CX Speed

KPI

Task Success

Improvement

92%

Metric Type

User Proficiency

KPI

Compliance

Improvement

100% WCAG 2.1 AA

Metric Type

Technical Standard

My Approach: Build the Foundation First

We aligned taxonomy, metadata and content governance before scaling. Before designing conversations, I focused on infrastructure.

1

The Assistant Layer

Conversational AI is systems design, not just UI. Success required aligning taxonomy, content quality, NLP capabilities, localization and user expectations. Not just building a chat window.

2

The Experience Layer

Enterprise users demand clarity and trust. Conversational design must be transparent, concise and predictable to work effectively in large organizations. Vague or uncertain responses erode confidence quickly.

3

The Explainer Layer

Machine-readable, modular content blocks designed for both internal logic and external LLM citation.

Detailed Results

80%+
Customer satisfaction with AI-assisted support interactions.
35%
Improvement in task completion compared to traditional documentation search.
Reduced support agent workload by handling routine, repetitive questions automatically.
Unified support entry point across business units, improving consistency.
Organic adoption growth because the experience felt easier than traditional search.
Scalable foundation for future AI-driven support experiences across Intel's ecosystem.

Role & Scope

Role
Senior Product Designer, Design Systems Lead for Digital Experiences at Intel
Platform
Web (responsive), integrated across Intel.com support ecosystem
Collaboration
Support teams, content owners, engineering, NLP teams

I led the end-to-end design of Ask Intel, the company's first enterprise-wide conversational assistant. This meant defining the conversational model, building the chat UI and creating a scalable component system. This was a ground-up effort. No prior assistant, no existing framework, no shared model for conversational behavior. I established the foundation that Intel's conversational experiences continue to scale on.

Role & Scope

Role
Senior Product Designer, Design Systems Lead for Digital Experiences at Intel
Platform
Web (responsive), integrated across Intel.com support ecosystem
Collaboration
Support teams, content owners, engineering, NLP teams

I led the end-to-end design of Ask Intel, the company's first enterprise-wide conversational assistant. This meant defining the conversational model, building the chat UI and creating a scalable component system. This was a ground-up effort. No prior assistant, no existing framework, no shared model for conversational behavior. I established the foundation that Intel's conversational experiences continue to scale on.

Role & Scope

Role
Senior Product Designer, Design Systems Lead for Digital Experiences at Intel
Platform
Web (responsive), integrated across Intel.com support ecosystem
Collaboration
Support teams, content owners, engineering, NLP teams

I led the end-to-end design of Ask Intel, the company's first enterprise-wide conversational assistant. This meant defining the conversational model, building the chat UI and creating a scalable component system. This was a ground-up effort. No prior assistant, no existing framework, no shared model for conversational behavior. I established the foundation that Intel's conversational experiences continue to scale on.

Role & Scope

Role
Senior Product Designer, Design Systems Lead for Digital Experiences at Intel
Platform
Web (responsive), integrated across Intel.com support ecosystem
Collaboration
Support teams, content owners, engineering, NLP teams

I led the end-to-end design of Ask Intel, the company's first enterprise-wide conversational assistant. This meant defining the conversational model, building the chat UI and creating a scalable component system. This was a ground-up effort. No prior assistant, no existing framework, no shared model for conversational behavior. I established the foundation that Intel's conversational experiences continue to scale on.

Key Insights

AI is not a UI feature.
It is a systems challenge involving data hygiene, governance and structured content.
By embedding conversational patterns into the Design System, we created a reusable foundation, not a one-off experiment.

Key Insights

AI is not a UI feature.
It is a systems challenge involving data hygiene, governance and structured content.
By embedding conversational patterns into the Design System, we created a reusable foundation, not a one-off experiment.

Key Insights

AI is not a UI feature.
It is a systems challenge involving data hygiene, governance and structured content.
By embedding conversational patterns into the Design System, we created a reusable foundation, not a one-off experiment.

Key Insights

AI is not a UI feature.
It is a systems challenge involving data hygiene, governance and structured content.
By embedding conversational patterns into the Design System, we created a reusable foundation, not a one-off experiment.