Calendar
Calendar
Calendar

TL;DR

Goal: Help IT change managers automatically find the safest, conflict-free time slot for planned changes by using AI to analyze history, dependencies, and impacted services.

My Role: Lead UX Designer, responsible for workflow design, interaction model, and collaboration with AI, backend, and product teams.


Problem & User Story

Change managers were spending hours manually checking historical changes, maintenance windows, and service conflicts. It was slow, stressful, and easy to make mistakes.

🗣️ “Every time I schedule a change, I’m terrified of breaking something we didn’t notice.” — IT Change Manager

The existing calendar tool required users to do everything manually. We wanted to design an AI assistant that could handle the analysis and suggest the safest time automatically.


Where Complexity Lies

Thousands of interconnected configuration items made it difficult to detect and visualize conflicts. AI results were accurate but difficult to interpret, and users needed to trust them. The system had to balance automation with human control so users could review and confirm before applying changes.

💬 Our challenge was not only to automate scheduling but also to design for trust and clarity.

TL;DR

Goal: Help IT change managers automatically find the safest, conflict-free time slot for planned changes by using AI to analyze history, dependencies, and impacted services.

My Role: Lead UX Designer, responsible for workflow design, interaction model, and collaboration with AI, backend, and product teams.


Problem & User Story

Change managers were spending hours manually checking historical changes, maintenance windows, and service conflicts. It was slow, stressful, and easy to make mistakes.

🗣️ “Every time I schedule a change, I’m terrified of breaking something we didn’t notice.” — IT Change Manager

The existing calendar tool required users to do everything manually. We wanted to design an AI assistant that could handle the analysis and suggest the safest time automatically.


Where Complexity Lies

Thousands of interconnected configuration items made it difficult to detect and visualize conflicts. AI results were accurate but difficult to interpret, and users needed to trust them. The system had to balance automation with human control so users could review and confirm before applying changes.

💬 Our challenge was not only to automate scheduling but also to design for trust and clarity.

How I approached it

I worked closely with the product manager and engineers to break down the entire workflow step by step.
This included AI scanning, dependency analysis, conflict detection, time recommendation, and user confirmation.

During the design phase, we went through several rounds of prototyping and continuously aligned with the component team to ensure that the interaction patterns and system architecture worked seamlessly together.

We conducted concept testing with close partner customers including T-Mobile and GM to validate early design ideas. Their feedback helped us understand real enterprise workflows and improve trust and clarity in the AI assistant. We quickly iterated the prototype based on their input, refining how recommendations were explained and how users could adjust scheduling parameters.

Iterations
Minimalist Spa Setup
Minimalist Spa Setup
Minimalist Spa Setup
Modern Smart Speaker
Modern Smart Speaker
Modern Smart Speaker

Results

User validation time was reduced significantly (data pending), and scheduling-related errors decreased noticeably (data pending).


What I learned

I learned that successful AI design depends on clarity and trust as much as on automation. Users need to understand why the system makes a recommendation before they can rely on it.

If I were to improve this again, I would explore adaptive explanations that adjust the level of detail based on each user’s expertise.

Results

User validation time was reduced significantly (data pending), and scheduling-related errors decreased noticeably (data pending).


What I learned

I learned that successful AI design depends on clarity and trust as much as on automation. Users need to understand why the system makes a recommendation before they can rely on it.

If I were to improve this again, I would explore adaptive explanations that adjust the level of detail based on each user’s expertise.

AI Scheduling Assistant

Help IT change managers automatically find the safest, conflict-free time slot for planned changes, using AI to analyze history, dependencies, and impacted services.

Year

2024

Year

2024

Type

Saas

Type

Saas

Client

ServiceNow

Client

ServiceNow

Timeline

12 weeks

Timeline

12 weeks

AI Scheduling Assistant

Help IT change managers automatically find the safest, conflict-free time slot for planned changes, using AI to analyze history, dependencies, and impacted services.

Year

2024

Type

Saas

Client

ServiceNow

Timeline

12 weeks