Scheduler
Scheduler
Streamlining technical automation through an intuitive, data-driven orchestration system.
Streamlining technical automation through an intuitive, data-driven orchestration system.
Year :
Year :
2023
Industry :
Industry :
Telecom
Client :
Client :
Confidential
Project Duration :
Project Duration :
9 weeks


The Problem
The Problem
Telecom optimization engineers deal with a heavy operational workload driven by the constant need to monitor KPIs and network health. Currently, generating performance reports is a manual, repetitive process, consuming valuable hours that should be dedicated to strategic analysis and critical troubleshooting. The lack of centralized automation prevents these specialists from focusing on their core mission: ensuring network stability and quality.
Telecom optimization engineers deal with a heavy operational workload driven by the constant need to monitor KPIs and network health. Currently, generating performance reports is a manual, repetitive process, consuming valuable hours that should be dedicated to strategic analysis and critical troubleshooting. The lack of centralized automation prevents these specialists from focusing on their core mission: ensuring network stability and quality.




Impact & business metrics
Impact & business metrics
This inefficient workflow directly impacts Time-to-Action and increases the risk of operational errors. From a business perspective, this results in high labor costs for low-value tasks and potential degradation of network performance indicators (SLAs).
This inefficient workflow directly impacts Time-to-Action and increases the risk of operational errors. From a business perspective, this results in high labor costs for low-value tasks and potential degradation of network performance indicators (SLAs).
Objective
Objective
To design and test an end-to-end task scheduling experience, ensuring engineers can automate complex functions, define sharing rules, and monitor execution status in a single location
To design and test an end-to-end task scheduling experience, ensuring engineers can automate complex functions, define sharing rules, and monitor execution status in a single location
Research timeline
Research timeline
We implemented the Design Sprint to ensure:
Cross-functional Synergy: Aligning stakeholders to prevent rework by mapping constraints early.
Velocity & Testing: Validating complex scheduling flows with specialized engineers in record time.
Cultural Shift: Establishing a scalable, agile design process across the organization.
We implemented the Design Sprint to ensure:
Cross-functional Synergy: Aligning stakeholders to prevent rework by mapping constraints early.
Velocity & Testing: Validating complex scheduling flows with specialized engineers in record time.
Cultural Shift: Establishing a scalable, agile design process across the organization.


The challenge
The challenge
Our primary focus was on Telecom Optimization Engineers and Execution Failure Specialists, professionals responsible for the high-stakes orchestration of network tasks. These users operate in an environment where precision is non-negotiable, requiring them to schedule, edit, and monitor complex task frequencies and execution windows—often immediately after generating technical reports or when recurring execution issues are detected.
The core objective was to streamline the management of these tasks to ensure critical network data remains updated without compromising system stability. By focusing on rapid, straightforward scheduling updates, we aimed to eliminate manual friction and prevent unnecessary processing overloads, balancing operational agility with technical performance.
Our primary focus was on Telecom Optimization Engineers and Execution Failure Specialists, professionals responsible for the high-stakes orchestration of network tasks. These users operate in an environment where precision is non-negotiable, requiring them to schedule, edit, and monitor complex task frequencies and execution windows—often immediately after generating technical reports or when recurring execution issues are detected.
The core objective was to streamline the management of these tasks to ensure critical network data remains updated without compromising system stability. By focusing on rapid, straightforward scheduling updates, we aimed to eliminate manual friction and prevent unnecessary processing overloads, balancing operational agility with technical performance.
Initial Mapping & Continuous Iteration
Initial Mapping & Continuous Iteration
We developed an initial user flow to map the task journey. We treated this flow as a strategic hypothesis, designed to be continuously iterated and refined as we gathered deeper technical insights throughout the project.
We developed an initial user flow to map the task journey. We treated this flow as a strategic hypothesis, designed to be continuously iterated and refined as we gathered deeper technical insights throughout the project.


Skecthes
Skecthes
All team members contributed sketches that were presented and voted upon to select the one that would be developed into a prototype.
All team members contributed sketches that were presented and voted upon to select the one that would be developed into a prototype.




Click on any sketch to expand. Click anywhere outside to close.
Click on any sketch to expand. Click anywhere outside to close.
Usability test & iterations
Usability test & iterations
Before being implemented, the Scheduler module went through 2 rounds of sprints consisting of iterations and usability tests. Below are some behaviors and comments made by users during the tests.
Before being implemented, the Scheduler module went through 2 rounds of sprints consisting of iterations and usability tests. Below are some behaviors and comments made by users during the tests.
Iteration #1
Iteration #1
Solution
Solution
After identifying key user patterns and pain points, I implemented a series of refinements. By optimizing the microcopy and UI labels, we ensured each section was intuitive, significantly improving user confidence during the scheduling and management tasks
After identifying key user patterns and pain points, I implemented a series of refinements. By optimizing the microcopy and UI labels, we ensured each section was intuitive, significantly improving user confidence during the scheduling and management tasks


Scheduler
Scheduler
Streamlining technical automation through an intuitive, data-driven orchestration system.
Streamlining technical automation through an intuitive, data-driven orchestration system.
Year :
Year :
2023
Industry :
Industry :
Telecom
Client :
Client :
Confidential
Project Duration :
Project Duration :
9 weeks


The Problem
The Problem
Telecom optimization engineers deal with a heavy operational workload driven by the constant need to monitor KPIs and network health. Currently, generating performance reports is a manual, repetitive process, consuming valuable hours that should be dedicated to strategic analysis and critical troubleshooting. The lack of centralized automation prevents these specialists from focusing on their core mission: ensuring network stability and quality.
Telecom optimization engineers deal with a heavy operational workload driven by the constant need to monitor KPIs and network health. Currently, generating performance reports is a manual, repetitive process, consuming valuable hours that should be dedicated to strategic analysis and critical troubleshooting. The lack of centralized automation prevents these specialists from focusing on their core mission: ensuring network stability and quality.




Impact & business metrics
Impact & business metrics
This inefficient workflow directly impacts Time-to-Action and increases the risk of operational errors. From a business perspective, this results in high labor costs for low-value tasks and potential degradation of network performance indicators (SLAs).
This inefficient workflow directly impacts Time-to-Action and increases the risk of operational errors. From a business perspective, this results in high labor costs for low-value tasks and potential degradation of network performance indicators (SLAs).
Objective
Objective
To design and test an end-to-end task scheduling experience, ensuring engineers can automate complex functions, define sharing rules, and monitor execution status in a single location
To design and test an end-to-end task scheduling experience, ensuring engineers can automate complex functions, define sharing rules, and monitor execution status in a single location
Research timeline
Research timeline
We implemented the Design Sprint to ensure:
Cross-functional Synergy: Aligning stakeholders to prevent rework by mapping constraints early.
Velocity & Testing: Validating complex scheduling flows with specialized engineers in record time.
Cultural Shift: Establishing a scalable, agile design process across the organization.
We implemented the Design Sprint to ensure:
Cross-functional Synergy: Aligning stakeholders to prevent rework by mapping constraints early.
Velocity & Testing: Validating complex scheduling flows with specialized engineers in record time.
Cultural Shift: Establishing a scalable, agile design process across the organization.


The challenge
The challenge
Our primary focus was on Telecom Optimization Engineers and Execution Failure Specialists, professionals responsible for the high-stakes orchestration of network tasks. These users operate in an environment where precision is non-negotiable, requiring them to schedule, edit, and monitor complex task frequencies and execution windows—often immediately after generating technical reports or when recurring execution issues are detected.
The core objective was to streamline the management of these tasks to ensure critical network data remains updated without compromising system stability. By focusing on rapid, straightforward scheduling updates, we aimed to eliminate manual friction and prevent unnecessary processing overloads, balancing operational agility with technical performance.
Our primary focus was on Telecom Optimization Engineers and Execution Failure Specialists, professionals responsible for the high-stakes orchestration of network tasks. These users operate in an environment where precision is non-negotiable, requiring them to schedule, edit, and monitor complex task frequencies and execution windows—often immediately after generating technical reports or when recurring execution issues are detected.
The core objective was to streamline the management of these tasks to ensure critical network data remains updated without compromising system stability. By focusing on rapid, straightforward scheduling updates, we aimed to eliminate manual friction and prevent unnecessary processing overloads, balancing operational agility with technical performance.
Initial Mapping & Continuous Iteration
Initial Mapping & Continuous Iteration
We developed an initial user flow to map the task journey. We treated this flow as a strategic hypothesis, designed to be continuously iterated and refined as we gathered deeper technical insights throughout the project.
We developed an initial user flow to map the task journey. We treated this flow as a strategic hypothesis, designed to be continuously iterated and refined as we gathered deeper technical insights throughout the project.


Skecthes
Skecthes
All team members contributed sketches that were presented and voted upon to select the one that would be developed into a prototype.
All team members contributed sketches that were presented and voted upon to select the one that would be developed into a prototype.




Click on any sketch to expand. Click anywhere outside to close.
Click on any sketch to expand. Click anywhere outside to close.
Usability test & iterations
Usability test & iterations
Before being implemented, the Scheduler module went through 2 rounds of sprints consisting of iterations and usability tests. Below are some behaviors and comments made by users during the tests.
Before being implemented, the Scheduler module went through 2 rounds of sprints consisting of iterations and usability tests. Below are some behaviors and comments made by users during the tests.
Iteration #1
Iteration #1
Solution
Solution
After identifying key user patterns and pain points, I implemented a series of refinements. By optimizing the microcopy and UI labels, we ensured each section was intuitive, significantly improving user confidence during the scheduling and management tasks
After identifying key user patterns and pain points, I implemented a series of refinements. By optimizing the microcopy and UI labels, we ensured each section was intuitive, significantly improving user confidence during the scheduling and management tasks


Scheduler
Scheduler
Streamlining technical automation through an intuitive, data-driven orchestration system.
Streamlining technical automation through an intuitive, data-driven orchestration system.
Year :
Year :
2023
Industry :
Industry :
Telecom
Client :
Client :
Confidential
Project Duration :
Project Duration :
9 weeks


The Problem
The Problem
Telecom optimization engineers deal with a heavy operational workload driven by the constant need to monitor KPIs and network health. Currently, generating performance reports is a manual, repetitive process, consuming valuable hours that should be dedicated to strategic analysis and critical troubleshooting. The lack of centralized automation prevents these specialists from focusing on their core mission: ensuring network stability and quality.
Telecom optimization engineers deal with a heavy operational workload driven by the constant need to monitor KPIs and network health. Currently, generating performance reports is a manual, repetitive process, consuming valuable hours that should be dedicated to strategic analysis and critical troubleshooting. The lack of centralized automation prevents these specialists from focusing on their core mission: ensuring network stability and quality.




Impact & business metrics
Impact & business metrics
This inefficient workflow directly impacts Time-to-Action and increases the risk of operational errors. From a business perspective, this results in high labor costs for low-value tasks and potential degradation of network performance indicators (SLAs).
This inefficient workflow directly impacts Time-to-Action and increases the risk of operational errors. From a business perspective, this results in high labor costs for low-value tasks and potential degradation of network performance indicators (SLAs).
Objective
Objective
To design and test an end-to-end task scheduling experience, ensuring engineers can automate complex functions, define sharing rules, and monitor execution status in a single location
To design and test an end-to-end task scheduling experience, ensuring engineers can automate complex functions, define sharing rules, and monitor execution status in a single location
Research timeline
Research timeline
We implemented the Design Sprint to ensure:
Cross-functional Synergy: Aligning stakeholders to prevent rework by mapping constraints early.
Velocity & Testing: Validating complex scheduling flows with specialized engineers in record time.
Cultural Shift: Establishing a scalable, agile design process across the organization.
We implemented the Design Sprint to ensure:
Cross-functional Synergy: Aligning stakeholders to prevent rework by mapping constraints early.
Velocity & Testing: Validating complex scheduling flows with specialized engineers in record time.
Cultural Shift: Establishing a scalable, agile design process across the organization.


The challenge
The challenge
Our primary focus was on Telecom Optimization Engineers and Execution Failure Specialists, professionals responsible for the high-stakes orchestration of network tasks. These users operate in an environment where precision is non-negotiable, requiring them to schedule, edit, and monitor complex task frequencies and execution windows—often immediately after generating technical reports or when recurring execution issues are detected.
The core objective was to streamline the management of these tasks to ensure critical network data remains updated without compromising system stability. By focusing on rapid, straightforward scheduling updates, we aimed to eliminate manual friction and prevent unnecessary processing overloads, balancing operational agility with technical performance.
Our primary focus was on Telecom Optimization Engineers and Execution Failure Specialists, professionals responsible for the high-stakes orchestration of network tasks. These users operate in an environment where precision is non-negotiable, requiring them to schedule, edit, and monitor complex task frequencies and execution windows—often immediately after generating technical reports or when recurring execution issues are detected.
The core objective was to streamline the management of these tasks to ensure critical network data remains updated without compromising system stability. By focusing on rapid, straightforward scheduling updates, we aimed to eliminate manual friction and prevent unnecessary processing overloads, balancing operational agility with technical performance.
Initial Mapping & Continuous Iteration
Initial Mapping & Continuous Iteration
We developed an initial user flow to map the task journey. We treated this flow as a strategic hypothesis, designed to be continuously iterated and refined as we gathered deeper technical insights throughout the project.
We developed an initial user flow to map the task journey. We treated this flow as a strategic hypothesis, designed to be continuously iterated and refined as we gathered deeper technical insights throughout the project.


Skecthes
Skecthes
All team members contributed sketches that were presented and voted upon to select the one that would be developed into a prototype.
All team members contributed sketches that were presented and voted upon to select the one that would be developed into a prototype.




Click on any sketch to expand. Click anywhere outside to close.
Click on any sketch to expand. Click anywhere outside to close.
Usability test & iterations
Usability test & iterations
Before being implemented, the Scheduler module went through 2 rounds of sprints consisting of iterations and usability tests. Below are some behaviors and comments made by users during the tests.
Before being implemented, the Scheduler module went through 2 rounds of sprints consisting of iterations and usability tests. Below are some behaviors and comments made by users during the tests.
Iteration #1
Iteration #1
Solution
Solution
After identifying key user patterns and pain points, I implemented a series of refinements. By optimizing the microcopy and UI labels, we ensured each section was intuitive, significantly improving user confidence during the scheduling and management tasks
After identifying key user patterns and pain points, I implemented a series of refinements. By optimizing the microcopy and UI labels, we ensured each section was intuitive, significantly improving user confidence during the scheduling and management tasks









