Hi, I'm Amjad

Overview

Project Introduction

Project Goal:

Enhancing Ivanti Neurons Bots with an Adaptive Survey Feature

Project Goal:

To create an adaptive survey tool for business administrators that provides qualitative and quantitative user experience data. The aim is to empower these administrators to utilize the tool for various needs, such as HR checks or device preferences, and integrate it into the DEX (Digital Experience) score for a comprehensive view of the work environment.

Project Scope:

The Ivanti Neurons Bots project aims to introduce a flexible yet controlled survey feature that seamlessly integrates into the DEX (Digital Experience) score, ensuring meaningful and accurate insights. The key challenges are to strike a balance between providing too much control, which could overwhelm users, and implementing guardrails to maintain the integrity of the DEX score.

Project Phases:

1. End-user Experience: Designing the interaction between teams and survey bots, primarily focusing on the user experience.
2. DEX Score Integration: Merging survey feedback into the DEX score.
3. Analytics and Reporting: Creating a robust analytics dashboard to slice and dice results.

Resources:

Axure RP, Figma, Ivanti design system.

Discover

In the initial phase of our project to introduce an adaptive survey feature within Ivanti Neurons Bots, we adhered to a thorough empathize process to fully understand our users’ needs, pain points, and motivations. This phase was crucial in ensuring that our solutions would be user-centered and effectively address real-world challenges.

User Research

Stakeholder Interviews:

We began by conducting detailed stakeholder interviews with the project PM, focusing on two primary personas:

• Admin Persona: IT managers and administrators who are responsible for configuring and deploying surveys.
• End-user Persona (Surveyee): Employees within the organization who receive and respond to the surveys.

Goals:

• Understand the workflow and challenges faced by IT administrators in creating and managing surveys.
• Learn about employees' experiences with existing survey tools and their pain points regarding these processes.

Insights Uncovered:

From Admins:

1. Complexity and Overwhelm: While administrators appreciated having flexibility in survey design, they often found themselves overwhelmed by too many options, leading to decision paralysis and poorly constructed surveys.
2. Integration Concerns: Ensuring that the survey results were integrated correctly into the DEX score was a major concern. Admins needed a system that could prevent irrelevant or misaligned data from affecting the overall DEX metrics.
3. Usability and Efficiency: Admins desired a tool that was straightforward and efficient, allowing them to create and deploy surveys without a steep learning curve or excessive time investment.

From End-users:

1. Survey Fatigue: Employees expressed a sense of survey fatigue, often caused by frequent or poorly designed surveys, which led to lower engagement and completion rates.
2. Lack of Impact Transparency: Many employees were skeptical about the impact of their feedback, feeling that their responses did not lead to tangible changes or improvements in their work environment.
3. Usability Concerns: End-users preferred a survey interface that was simple, intuitive, and quick to complete. Features like the ability to postpone surveys were seen as highly beneficial.

Conclusion

The Discover phase was pivotal in laying a solid foundation for our project. By thoroughly understanding the needs, challenges, and motivations of both IT administrators and end-users, we gathered invaluable insights that will guide the development of a truly adaptive and user-centered survey feature within Ivanti Neurons Bots. This deep dive into user experiences has empowered us to move forward with a clear perspective, ensuring that our solutions are not only effective and efficient but also resonant with the real-world needs of our users.

Define

In the define phase of our project to introduce an adaptive survey feature within Ivanti Neurons Bots, we consolidated our findings from the empathize phase to articulate clear problem statements and objectives. This step was essential in setting a focused direction for our design and development efforts.

Problem Statement

After synthesizing insights from our stakeholder interviews and research, we formulated the following problem statement:

Administrators need a flexible yet controlled survey tool that can gather meaningful user feedback, integrate smoothly with the DEX (Digital Experience) score, and provide comprehensive analytics to enhance the digital work environment.

Key Challenges:

1. Balancing Flexibility and Control:
• Providing administrators with sufficient flexibility to design relevant surveys without overwhelming them with too many options.
• Ensuring clear and appropriate guardrails to prevent irrelevant data from skewing the DEX score.
2. Preventing Survey Fatigue and Irrelevant Data:
• Avoiding the overloading of employees with too many surveys, leading to reduced engagement and completion rates.
• Ensuring that only relevant, well-structured survey feedback influences the DEX score.
3. Usability for Admins and End-users:
• Creating an intuitive survey creation interface for administrators that simplifies the process and reduces the learning curve.
• Designing a user-friendly survey response interface for end-users that is quick to complete and minimally disruptive.
4. Transparency and Actionable Insights:
• Providing clear feedback to employees on how their survey responses impact the digital environment.
• Delivering robust analytics and reporting tools for administrators to derive actionable insights from survey data.

Objectives

Based on the defined problem statement, we established the following project objectives to guide our design and development process:

1. Survey Creation Tools:
• Develop a user-friendly interface for administrators to design and deploy surveys.
• Incorporate customizable templates that offer flexibility while maintaining control over the DEX score's integrity.
• Include various question types (e.g., star ratings, text feedback) to capture both qualitative and quantitative data.
2. Guardrails for DEX Score Integration:
• Implement mechanisms to ensure surveys contribute relevant data to the DEX score.
• Provide prescriptive guidelines and automated checks to prevent irrelevant survey topics from affecting the score.
3. End-user Engagement:
• Ensure a visually appealing and straightforward survey interface for end-users.
• Include features like multi-language support and the ability to postpone surveys to reduce fatigue and encourage participation.
• Clearly communicate the impact of their feedback on the digital environment.
4. Analytics and Reporting:
• Create a comprehensive analytics dashboard for administrators to track survey performance and derive actionable insights.
• Enable real-time data visualization and correlation with device performance and user experience metrics.

Key Findings and Personas

Admin Persona (IT Manager/Administrator):

• Needs: Simplified survey creation processes, effective template options, clear and relevant integration with DEX scores, and robust analytics for actionable insights.
• Pain Points: Decision paralysis due to too many options, concerns over skewed DEX scores, and complexity in survey tool interfaces.

End-user Persona (Employee/Surveyee):

• Needs: Intuitive and visually appealing survey interface, minimal disruption to daily tasks, clarity on feedback impact, multi-language support, and options to postpone survey completion.
• Pain Points: Survey fatigue, skepticism about feedback impact, and usability issues with current survey tools.

Conclusion

The empathize phase provided invaluable insights into the needs and pain points of our key personas. By deeply understanding the perspectives of both administrators and end-users, we were able to define clear problem statements and objectives for the project. This user-centered groundwork laid the foundation for developing a survey tool that not only meets administrative requirements but also enhances the end-user experience, ensuring meaningful and actionable feedback integration into the DEX score. Including use cases in the define phase allowed us to clearly articulate specific scenarios and requirements, ensuring that our solutions were tightly aligned with user needs. This provided a solid foundation for the subsequent ideate phase, where these detailed scenarios were translated into practical, user-centered design solutions.

Ideate

In the ideate phase, we leveraged the insights and problem statements identified in the earlier stages to brainstorm and conceptualize innovative solutions for the survey feature within Ivanti Neurons Bots. This phase involved generating and refining ideas to address the key challenges of balancing flexibility with control, preventing survey fatigue, and ensuring seamless integration with the DEX (Digital Experience) score.

Brainstorming Sessions

We conducted several brainstorming sessions with stakeholders, including project manager, Engineering, During these sessions, we focused on generating a wide range of ideas and potential solutions, which we then refined based on feasibility and user needs.

Admin Features:

1. Survey Builder:
• Drag-and-Drop Interface: Simplify the survey creation process by allowing administrators to easily add, remove, and rearrange questions using a drag-and-drop interface..
• Predefined Templates:Offer a variety of customizable survey templates tailored to common use cases, such as device satisfaction assessments or HR checks.
• Question Types: Include multiple question formats, such as star ratings, text feedback, and multiple-choice options, to gather both qualitative and quantitative data.
2. Scheduling and Notifications:
• Flexible Scheduling: Enable administrators to schedule surveys at optimal times to minimize disruption and avoid survey fatigue.
• Automated Reminders: Implement automated reminder notifications to prompt users to complete surveys without overwhelming them.
• Notification Customization: Allow admins to customize notification messages to make them more engaging and relevant to the end-users.
3. Guardrails for DEX Integration:
• Relevance Filters: Introduce filters to ensure that only relevant survey questions contribute to the DEX score, avoiding skewed data from irrelevant topics.
• Prescriptive Guidelines: Provide clear guidelines and recommendations to help administrators design surveys that align with the DEX score's criteria.
4. Analytics Dashboard:
• Real-time Data Visualization: Develop an analytics dashboard that displays real-time survey results with various filters (e.g., date range, campaign ID, user demographics).
• Actionable Insights: Offer detailed reports that correlate survey feedback with device performance and user experience metrics, helping administrators make informed decisions.

End-user Features:

1. Intuitive Survey Interface:
• Visually Engaging Design: Create a visually appealing survey interface that is easy to navigate and quick to complete.
• Mobile-Friendly:Ensure the survey interface is fully responsive and accessible on mobile devices to accommodate users on the go.
2. Multi-language Support:
• Language Options: Provide multi-language support to cater to a diverse workforce and ensure surveys are accessible to all employees.
3. Survey Fatigue Reduction:
• Postponement Feature: Allow users to postpone surveys to a more convenient time, reducing survey fatigue and increasing completion rates.
• Impact Transparency: Clearly communicate to users how their feedback will be used and its impact on the digital environment, fostering a sense of contribution and engagement.

Use Cases

Use Case 1: Monthly Device Experience Survey

• Persona: IT Admin
• Scenario: Admin wants to ask users about their device experience once per month.
• Flow:
• Admin creates a new bot:IT Admin
• Uses a predefined survey template.
• Adjusts settings like timeouts, user text, fields, and repetition frequency.
• End-user receives a survey notification:
• Opens the survey via MS Teams notification.
• Answers questions and submits responses.
• Admin receives and analyzes survey data:
• Data aggregated in the DEX dashboard.
• DEX score updated based on user feedback.

Use Case 2: Investigating High Memory Usage

• Persona: IT Admin
• Scenario: Admin wants to gather details from users experiencing high memory usage.
• Flow:
• Admin creates a high memory usage survey bot:
• Drag relevant survey stages.
• Configure settings for each stage.
• Bot scans devices and identifies high memory usage:
• Notifications sent to targeted users.
• End-user receives survey notification:
• Opens the survey via MS Teams notification.
• Answers questions and submits responses.
• Reminder for unanswered surveys:
• Reminder sent if survey not completed within the timeframe.
• Admin receives and analyzes survey data:
• Data aggregated in the DEX dashboard.
• Insights derived to reduce memory usage, potentially leading to further actions like creating additional bots.

User Flows

The brainstorming sessions and user flows enabled us to visualize the user journey and identify potential pain points or areas for improvement. We used techniques to map the user flows and refine the most promising ideas. These iterative discussions and stakeholder feedback ensured our solutions were both effective and user-centered.

Conclusion

The ideate phase allowed us to creatively explore and refine a variety of solutions to address the identified problems. By focusing on user-centered design principles and collaborative brainstorming, we developed a comprehensive set of features and functionalities that would enhance the survey experience for both administrators and end-users. These ideas laid the groundwork for the subsequent prototyping and testing phases, ensuring that our solutions were well-targeted and effective in meeting user needs and project goals.

Prototype

In the prototype phase, we transitioned from ideation to action, transforming our conceptual solutions into tangible, interactive representations. This phase was crucial for validating our designs and gathering early user feedback to iteratively refine the adaptive survey feature for Ivanti Neurons Bots. Using a combination of high-fidelity wireframes and interactive prototypes, we delivered a realistic simulation of our proposed solution to stakeholders and end-users for comprehensive evaluation.

Tools and Resources

To create our prototypes, we utilized a suite of design tools aligned with our project needs:

• Axure RP and Figma: For interactive prototyping and high-fidelity wireframes.
• Ivanti Design System:To ensure consistency and compliance with Ivanti's established UI/UX standards.

Focus Areas for Prototyping:

1. Survey Builder Interface for Admins
• Drag-and-Drop Interface:
• Objective: Ease the survey creation process by enabling administrators to add, remove, and rearrange questions effortlessly.
• Prototype Features: Interactive elements that mimic the drag-and-drop functionality.
• Question Types:
• Objective: Facilitate the collection of both qualitative and quantitative data through varied question formats (e.g., star ratings, text feedback, multiple-choice).
• Prototype Features: Interactive question-type options available through dropdown menus and selection.
2. Prototype

Test

Usability Test Neurons Survey Bot Prototype

Test Overview: The usability test aimed to evaluate the new "Survey Bots" feature's effectiveness and user-friendliness for IT Admins. Specific focus was on whether users could navigate the interface and complete various tasks, as well as gathering qualitative feedback to improve the overall user experience.

Participants:

• Chad - Infrastructure Manager.
• Jared - General Manager.
• Sara - Manager Enterprise Technology and Information.

Methodology:

This qualitative study involved observing users as they attempted to perform specific tasks using the Survey Bots prototype. Think-aloud protocols were used, and participants completed a questionnaire and a System Usability Scale (SUS) survey post-test.

• Axure RP and Figma: For interactive prototyping and high-fidelity wireframes.
• Ivanti Design System:To ensure consistency and compliance with Ivanti's established UI/UX standards.

Key Findings

1. Survey Builder Interface for Admins:
• Chad: Found most stages quickly but needed clarity on naming conventions and backend operations.
• Jared: Required assistance to find specific stages and was confused about bot locations.
• Sara: Managed to find most stages with minimal clicks but struggled with bot naming conventions.
2. Survey Configuration:
• Recurring Options: All users found the absence of a "Month" dropdown and other specific date settings confusing.
• Chad: Suggested more clarity on monthly settings.
• Jared & Sara: Proposed options for setting specific days of the month.
• Bot Naming: Users were generally confused by the bot naming conventions.
• Recommendation: Clearer guidance and tooltips are necessary for naming conventions and differentiating between stages.
3. New Concept Understanding:
• DEX Score: There was a notable lack of understanding regarding the DEX score.
• Chad: Needed more information on backend targeting mechanics.
• Jared & Sara: Needed help understanding DEX and its relevance.
• Recommendation: Provide introductory text or tool tips to explain DEX and its application within the settings.
4. User Interface (UI) Feedback:
• Users appreciated the live pre-view feature and found it helpful.
• Sara: Requested flexibility in positioning the preview panel.
• Integration: Sara suggested that the ITSM (ticketing system) UI be updated to match the modern look of the Bot UI.

Recommendations

1. Enhance UI and Navigation Clarity:
• Improve search functionalities and provide clearer categories and names for different bot stages. Introduce tooltips and in-app guides.
2. Expand Recurring Options:
• Offer options to set specific dates or days of the week/month within recurring settings to reduce confusion.
3. Educational Tooltips:
• Integrate brief tooltips or onboarding steps to explain new concepts like the DEX score within the settings.
4. UI Integration:
• Align the look and feel of older interfaces like ITSM with the modern UI design of the Bot interface to provide a coherent user experience.

Conclusion:

The usability test featuring Chad Dahlberg, Jared Carver, and Sara Holmes provided valuable insights into the user experience of the Neurons Survey Bots feature. While the core functionalities were well-received, addressing issues related to navigation, recurring options, and introducing educational aids for new concepts will significantly enhance overall user satisfaction and the effectiveness of the feature.

Overview

Highlights:

• Business Goals: Assist organizations in measuring user perception of various IT aspects.
• Feedback Collection: Enable capturing of both quantitative and qualitative feedback directly from end users.
• Business Intelligence: Extract insights at scale to identify key themes, issues, trends, and engagement.
• Measurement: Establish benchmarks to measure sentiment and evaluate the effectiveness of improvement initiatives and campaigns.

Personas:

• Primary personas are 'survey creator' (DEX admin or other LoB leaders like service desk managers or HR).
• IT leadership will use DEX score components at the organization level and require drilldown capabilities.

Admin Use Cases:

1. Top-Level View: See the number of responses in a given period without detailed exploration.
2. Overall Rating: View overall survey ratings based on individual rating questions.
3. Date Visibility: Easily see survey start and end dates for reporting.
4. Trend Analysis: Observe result trends compared to the previous period.
5. Completion Status: Monitor partial responses to assess question quality and need for revisions.
6. Response Rate: Understand engagement on a per-survey level.
7. Failure Insights: Identify survey failures without detailed examination.
8. Global Survey Frequency: Control survey frequency to manage fatigue and effectiveness.
9. Failure Trends: Compare trends based on failed submissions over time.
10. Change Over Time: Visualize per-question and overall result changes.
11. Median Scores: Compare median scores for specific periods.
12. Qualitative Responses: Understand qualitative responses in context.
13. Version Navigation: Navigate different survey versions.
14. DEX Score Influence: Opt-in specific surveys to influence DEX score.
15. AI Topic Generation: Get AI-generated topics from qualitative responses.
16. Survey Drilldown: Drill down from DEX score to individual survey scores.
17. AI Response Summary: Receive AI-generated summaries of survey responses for the selected period.

Scenarios

Scenarios for managing surveys can be divided into four key sections:

1. Survey Creation:
   • Testing to ensure functionality, resulting in invalid data which should not affect reports.
2. Survey Deployment:
   • Monitoring response rates and errors to gauge delivery success and identify necessary actions.
3. Results Analysis:
   • Interpreting data and comparing time periods to understand trends.
   • Drawing business conclusions primarily through monitoring the DEX score or detailed survey feature analysis.
4. Survey Decommission:
   • Managing expired surveys by purging or hiding them from the UI to ensure data relevance.

Prototype: Survey Bot Results

Survey Results User Testing

Participants:

• Jesse
• Jack
• Diane
• Julian

Overview:

The usability test aimed to evaluate the new "Survey Bots" feature's effectiveness and user-friendliness for IT Admins, focusing on task navigation and feature usability.

Purpose:

Assess IT Admins' ability to navigate and complete key tasks using the "Survey Bots" feature.

Product Team Goal:

Enable IT Admins to obtain qualitative and quantitative insights to form improved strategies.

Methodology:

• Five user test scenarios with a prototype.
• Freeform task approach with think-aloud method.
• Post-test questionnaire and System Usability Scale (SUS) survey.

Testing Environment:

Conducted virtually using Mac laptops, Microsoft Teams, Google Forms, and the Axure prototype.

Key Findings:

Conducted virtually using Mac laptops, Microsoft Teams, Google Forms, and the Axure prototype.

Jesse's Feedback:

• Found survey creation straightforward.
• Suggested clearer naming conventions and better explanations for settings.
• Appreciated the draft feature for iterative development.
• Preferred Interface A for comprehensive data display.
• Recommended improved visibility for survey result buttons and advanced filtering options.

Multiple Users' Feedback (Jack, Diane, Julian):

• Found survey bot creation user-friendly.
• Suggested intuitive tooltips and naming conventions.
• Emphasized the importance of advanced categorization.
• Preferred Interface A for presenting survey results.
• Highlighted the need for better multilingual support and interactive feedback.

Conclusion:

The testing sessions provided valuable insights into the strengths and areas for improvement of the "Survey Bots" feature. Key feedback includes the need for clearer guidance, more collaborative features, advanced filtering, and comprehensive data displays. These insights will guide future enhancements to make the tool more efficient and user-friendly.

Overview

Project Introduction

Project Overview:

The goal of this project is to integrate Ivanti's on-premises Environment Manager (EM) into the cloud-based Ivanti Neurons platform. By migrating EM to the cloud, we aim to enhance desktop personalization and policy management, enabling a subscription-based payment model that offers flexibility and cost-efficiency. The objective is to deliver personalized, consistent desktop environments and streamline desktop configuration and policy management for IT administrators. This integration is designed to support scalability, improve adaptability to business needs, increase user productivity, and optimize IT resources by reducing complexity and aligning costs with actual usage.

Executive Summary:

1. Goal: Migrate EM to the cloud for scalable, flexible desktop management.
2. Objectives: Deliver personalized desktops, simplify configurations, and enhance design with user feedback.
3. Impact: Transition to cloud-based, subscription-based payments, quick logons, and seamless roaming.
4. Scope: Integrate core EM functionalities, focusing on configuration policies.
5. Challenges: Address complexities, learning curve, harmonize nodes, and ease user adaptation.
6. Prototype Features: Intuitive UI with drag-and-drop, Neurons Bots UI.

Project Goal:

The goal of the project is to integrate Ivanti's on-premises Environment Manager (EM) into the cloud-based Ivanti Neurons platform. This integration aims to enhance desktop personalization and policy management by transitioning EM functionalities to the cloud. The key objectives are to provide users with personalized, consistent desktop environments and to simplify desktop configuration and policy management for IT administrators. The expected impacts are scalable and adaptable solutions, increased user productivity, and optimized IT resources with cost-efficiency through a subscription-based payment model.

Project Scope:

The project will focus on the integration of core Environment Manager functionalities into Ivanti Neurons. The primary features to be integrated include configuration policies and the minimal viable product (MVP) with basic EM functionalities. This scope will address the complexities of transitioning from on-premises to cloud, simplifying EM’s complexity, reducing the learning curve for users, and utilizing Ivanti Neurons bots framework. Key UI challenges, such as harmonizing nodes with the linear bot instructions and supporting multi-layered, nested, and parallel node execution, will also be addressed.

Project Phases:

• Phase 1: Design and implement working minimal viable product (MVP), Integration of core Environment Manager functionalities into Ivanti Neurons platform.
• Phase 2: Intorduce more advanced features from on-prem Environment Manager.

Resources:

Axure RP, Figma, Ivanti design system.

Discover

During the initial phase of our project to deliver a functional Minimum Viable Product (MVP) by integrating the core functionalities of Environment Manager into the Ivanti Neurons platform, we conducted a comprehensive empathy process. This approach allowed us to thoroughly understand our users’ needs, pain points, and motivations. This phase was essential in ensuring that our solutions were user-centric and effectively addressed real-world challenges.

User Research

In transitioning Ivanti's Environment Manager (EM) to the Ivanti Neurons platform, comprehensive user research is indispensable. Initially, the project faced significant challenges due to time constraints that led to insufficient user research. This resulted in relying on presumed requirements and hypothesis-driven development, rather than user-validated data. As a consequence, there was a mismatch in expectations, where EM could not seamlessly fit into the Bots framework envisioned, leading to user dissatisfaction. This highlights the crucial role of thorough user research in accurately gathering user requirements and ensuring the final product meets user expectations effectively.

User Research: Why It's Essential

User research is the cornerstone of the discover phase. Understanding the needs, pain points, and expectations of users is critical in ensuring that the integrated solution is user-centric and effective. Initial user requirements are to transition on-prem EM to Neurons, utilize the Neurons bots framework, and incorporate drag-and-drop instructions to build configurations. Users also expect an intuitive design where everything is visible on a canvas for easy access and troubleshooting. Initial User Interviews: Gather feedback from internal and external EM users across various roles and industries. Focus on understanding the advantages, pain points, and general comments from users.

Admin Persona:

IT managers and administrators who are responsible for configuring and deploying Environment Manager policies.

Research Goals:

Gain an in-depth understanding of the workflow and challenges encountered by IT administrators when creating, managing, and deploying Environment Manager policies. Additionally, examine users' experiences with the existing on-premises version of Environment Manager, identifying their pain points and difficulties associated with these processes.

Initial Challenges:

• Limited initial user research due to time constraints.
• Presumed user requirements were based on limited feedback and were hypothesis-driven, not validated by extensive user input.
• Mismatch in expectations when initial designs were tested, as EM could not fit seamlessly into the Bots framework (all-on-canvas approach).

User Interviews and Design Review - Environment Manager:

Conducting detailed user interviews with internal and external EM users from diverse roles and industries provided us with a wealth of valuable data. Participants were asked about their experiences, advantages, pain points, and general feedback regarding the current EM system.

Participants:

• Internal and external EM users from various roles and industries.

Data Collection Focus:

• Advantages of the current system (Ivanti Neurons Bots).
• Pain points and challenges faced (On-prem EM)
• General comments and suggestions for improvement.

Outcome & Key Takeaway:

• Mismatch in expectations highlighted the importance of thorough user research.
• Key takeaway: User research is critical for capturing accurate requirements and meeting user expectations.

Conclusion

The discover phase provided in-depth insights into user needs, pain points, and expectations. By engaging with a diverse group of users, we identified critical features and functionalities necessary for the successful integration of EM into Ivanti Neurons. The findings underscored the importance of a user-centric design, comprehensive configuration management tools, and a seamless transition from on-prem to cloud-based solutions. This phase lays a solid foundation for defining the project's goals, objectives, and scope in the subsequent phases of the design thinking process.

Define

In the define phase of our project to integrate the Environment Manager into the cloud-based Ivanti Neurons platform, we synthesized our findings from the empathy phase to articulate clear problem statements and set precise objectives. This step was critical in establishing a focused direction for our design and development efforts, ensuring that we address user needs and business requirements effectively.

Problem Statement

The current on-premises Ivanti Environment Manager (EM) is limited in its capacity to provide scalable, flexible, and user-friendly desktop management solutions. The complexity of managing multi-layered configurations, the steep learning curve for new users, and the reliance on multiple agents for endpoint management present significant challenges for IT administrators and end-users alike. Additionally, the static on-premises infrastructure does not offer the financial and operational flexibility that modern IT environments require.

Key Challenges:

1. Complexity in Configuration Management: Managing and deploying configurations in the current EM system is complex and time-consuming. The multi-layered, nested node structure with parallel execution presents significant difficulties in simplifying configurations and policy management.
2. Steep Learning Curve: New users face a substantial learning curve to understand and effectively use the existing EM platform, leading to inefficiencies and potential errors in configuration.
3. Lack of Unified Management: The need for separate management of on-premises and cloud resources creates inefficiencies and increases the workload for IT administrators, leading to fragmented management experiences.
4. Financial Inflexibility: The existing infrastructure demands significant upfront investment and ongoing maintenance costs, which are not aligned with modern, subscription-based, pay-as-you-go financial models preferred by many organizations.
5. Suboptimal User Experience: End-users experience inconsistent desktop environments, long logon times, and difficulty in maintaining personalized settings across different devices and locations.

Impact on Users and IT Administrators:

• Users: Inconsistent desktop experiences, long logon times, and difficulty maintaining personalized settings reduce user satisfaction and productivity.
• IT Administrators: Increased workload due to complex configuration management, fragmented resource management, and higher potential for configuration errors.

Business Implications:

• Cost Inefficiencies: High upfront costs and ongoing maintenance expenses impact the overall IT budget and limit financial flexibility.
• Operational Inefficiencies: IT teams spend excessive time on routine desktop management tasks, reducing their ability to focus on strategic initiatives and innovation.

Objectives for Solution:

The project aims to transition the on-premises EM to a cloud-based Ivanti Neurons platform, providing a scalable, flexible, and user-friendly desktop management solution that addresses the identified challenges. The solution will:

• Simplify configuration management with an intuitive UI and streamlined processes.
• Reduce the learning curve for new users through comprehensive training and support resources.
• Enhance scalability and adaptability by leveraging cloud infrastructure.
• Unify management of resources to provide a seamless experience for IT administrators.
• Align with modern financial models by enabling a subscription-based payment system.
• Improve user experience with personalized, consistent desktop environments and quick logon times.

Personas

Admin Persona (IT Manager/Administrator):

• Needs: Simplified survey creation processes, effective template options, clear and relevant integration with DEX scores, and robust analytics for actionable insights.
• Pain Points: Decision paralysis due to too many options, concerns over skewed DEX scores, and complexity in survey tool interfaces.

Conclusion

In the define phase, we set clear goals, objectives, and scope for integrating Environment Manager (EM) into the Ivanti Neurons platform. By addressing key challenges and adhering to user-centered design principles, we developed a strategy to deliver a user-friendly and efficient desktop management solution. This phase aligns the project with business objectives and user needs, providing a foundation for ideation, prototyping, and testing. Integrating Ivanti's on-premises EM into the cloud-based Neurons platform will address existing challenges, offering a scalable, flexible desktop management solution. This transition promises improved efficiency, reduced complexity, and enhanced user satisfaction, aligning IT resources with modern business needs and financial models.

Ideate

The ideate phase is dedicated to generating innovative ideas and solutions that address the key challenges, goals, and objectives identified during the define phase. This phase involves brainstorming, conceptualizing, and refining concepts to create a user-centered design that enhances desktop management within the Ivanti Neurons platform.

Brainstorming and Concept Development:

Based on insights gathered during the discovery and define phases, the ideation process focuses on the following key areas:

Simplified Configuration Management:

• Intuitive Interface: Design an intuitive, user-friendly interface with drag-and-drop functionality to streamline configuration management.
• Search: Incorporate search capabilities to help users quickly locate and troubleshoot configurations.

Utilize with Neurons Bots Framework:

• Harmonizing Nodes and Bots: Develop a cohesive interface that harmonizes multi-layered node structures of EM with the linear instruction sets of Neurons bots.
• Node Numbering:Implement an auto-adjust node numbering system to simplify node management.

Efficiency and Scalability::

• Unified Management: Propose a unified platform that allows seamless management of both on-premises and cloud resources.
• Flexible Configuration: Develop intuitive configuration management that is easy to uderstand and work with.

Key Features and Functionalities:

Phase 1 (MVP)

Configuraton managment:

• Allow user to Create, Edit and Delete EM policy similarly as Neurons bot.

Drag and drop:

• Allow user to drap and drop nodes to configure the EM policy similarly as Neurons bot.

Multiple Configurations:

• Enable support for multiple configurations within EM for Neurons to cater to varying organizational needs and scenarios.

Configuration Summaries:

• Provide summaries for large, inherited configurations, making them easier to understand and manage.

Phase 2 (Advance)

Exportable Configuration Reports:

• Allow users to export configuration reports in formats similar to flow diagrams for better visualization and documentation.

Draft-Saving Capability:

• Develop a feature that allows users to save drafts of their configurations, enabling progress tracking and iterative development.

Copy-Paste Functionality:

• Implement functionality that allows users to copy and paste nodes and actions, facilitating quick duplication and modification of configurations.

Profile Management Configurations::

• Incorporate configurations for profile management to support personalized user environments across different devices.

Concept Refinement and Prioritization:

User Feedback Integration:

• Continuously gather and integrate feedback from users during the ideation phase to refine and prioritize the most impactful features and functionalities.

Prototype Development Considerations:

• Align concepts with the defined goals and objectives, ensuring that the proposed features are feasible and deliver value to both users and IT administrators.

Prioritization Framework:

• Prioritize features based on user needs, project goals, and technical feasibility to ensure that the most critical functionalities are developed first.

Visualization and Storyboarding:

Mockups and Wireframes:

• Create detailed mockups and wireframes of the proposed features and functionalities to visualize the user interface and interaction flow.

User Scenarios:

• Develop storyboards and user scenarios that illustrate how users will interact with the new features, highlighting the benefits and improvements over the current system.

Userflow

Admin Persona (IT Manager/Administrator):

• Needs: Simplified survey creation processes, effective template options, clear and relevant integration with DEX scores, and robust analytics for actionable insights.
• Pain Points: Decision paralysis due to too many options, concerns over skewed DEX scores, and complexity in survey tool interfaces.

Conclusion:

The ideate phase has resulted in a wide range of innovative solutions and features that address the key challenges identified in the define phase. By focusing on user-centered design principles and continuous user feedback, we have conceptualized a detailed and prioritized plan for enhancing desktop management within Ivanti Neurons. These concepts will serve as the foundation for the subsequent prototyping and testing phases, ensuring that the final product is user-friendly, efficient, and aligned with both business goals and user needs.

Prototype

The prototype phase involves translating the innovative ideas generated during the ideate phase into tangible, interactive models that can be tested and refined. This phase is crucial for visualizing the proposed solutions, obtaining user feedback, and making iterative improvements to ensure the final product meets user expectations and business objectives.

Development of Prototypes

To create our prototypes, we utilized a suite of design tools aligned with our project needs:

• Use design tools such as Figma to create interactive mockups of the Environment Manager (EM) features integrated into the Ivanti Neurons platform.
• Develop multiple prototypes to explore different interface layouts, interactions, and workflows based on the features prioritized during the ideate phase.

• Drag-and-Drop Interface:
• Objective: Intuitive user interface, reduce complexty, easy to create configuration and troubleshoot, leverage Nurons bot framework.
• Prototype Features: Interactive elements that mimic the drag-and-drop functionality.
• Prototype

Conclusion

The prototype phase has resulted in the development of interactive models that visualize the innovative solutions and features conceptualized during the ideate phase. By conducting user testing and iterative refinements, we have created prototypes that effectively address user needs and business objectives. These validated prototypes provide a solid foundation for the subsequent testing phase, ensuring that the final product is user-friendly, efficient, and aligned with both the goals of the project and the expectations of its users

Test

Usability Test Environment Manager (EM)

The user test phase is critical for validating the prototypes developed during the prototype phase. This phase involves rigorous testing with real users to ensure that the solutions meet user needs, are user-friendly, and function correctly. Based on the test results, refinements will be made to optimize the final product.

Participants:

The user testing sessions involved various internal and external users, including system administrators, technical directors, and professional services managers. Feedback was gathered from clients in different industries to ensure diverse perspectives.

Methodology:

User interviews with Figma prototypes, Four different prototypes where presented to participants.

• Figma: For interactive prototyping and high-fidelity wireframes.

Key Findings

Advantages:

1. Intuitive User Interface:
• Participants appreciated the clean, focused interfaces and drag-and-drop functionality, which simplify configuration management.
• Quote: "I like this, it's clean and the focus is on what you're going into. The focus view is great and I'm a big fan."
2. Unified Management:
• The integration of EM functionalities into Neurons to reduce the number of endpoint agents was well-received.
• Quote: "Avanti's vision with Neurons is that it's one agent, reducing the number of agents on endpoints."
3. Search and Summaries:
• Users emphasized the need for real-time search within configurations and summaries for large inherited configs.
• Quote: "Finding something in a large config is hard, and a summary would help users understand the configuration better."
4. Multiple Configurations Support:
• Users were enthusiastic about the ability to support multiple configurations within EM for Neurons.
• Quote: "Allowing users to have multiple different configurations in EM in Neurons would be extremely beneficial."

Pain Points:

1. Complexity and Learning Curve:
• Users found the current EM system complex and challenging to navigate, especially when managing multi-layered node structures.
• Quote: "The learning curve of EM and package deployment is very complex."
2. Current Workflow Frustrations:
• The existing workflow for creating and editing configurations was not intuitive, causing frustration among users.
• Quote: "The workflow in Environment Manager isn't really intuitive, especially if you haven't used it for a while."
3. Node Management and Configuration:
• Users pointed out the difficulty in managing node numbering and the need for auto-adjustment to simplify configuration management.
• Quote: "Node numbering is essential, but manually renaming nodes with each change is extremely painful."

User Recommendations:

1. Comparison Features:
• Users suggested implementing a toggle switch to compare two configuration nodes side by side.
• Quote: "It would be great to be able to toggle between two nodes to compare them."
2. Reporting and Export Capabilities:
• Users requested the ability to export configuration reports similar to flow diagrams for better visualization and documentation.
• Quote: "Allow users to export a configuration report like a flow diagram from within the configuration."
3. Templates and Help Guides:
• Importance of providing configuration templates and help guides, especially for new users.
• Quote: "Provide some templates like those in bots to make it easier for new users to understand and configure."
4. Draft-Saving and Copy-Paste Functionality:
• Need for draft-saving capabilities and copy-paste functions for nodes and actions.
• Quote: "Allow users to save drafts and copy-paste functionality for nodes and actions."
5. Profile Management and Security Import:
• Users requested profile management configurations and the ability to import templates and base security settings.
• Quote: "Quote: "Is there any possibility to configure profile management and import security settings?"

Design Specific Feedback:

1. Design-1:
• Users liked the clean and intuitive interface but requested the ability to toggle between viewing the whole map and focused views.
• Quote: "The focus view is great, but I would like the ability to see the whole configuration at once."
2. Design-2 and Design-3:
• Positive feedback on the workflow style with suggestions for minor improvements in the UI layout.
• Quote: "I like the idea of not switching between screens constantly, but let's avoid clutter in the UI."

General Comments:

• Users emphasized the need for seamless integration between EM and Neurons to align with modern UI/UX principles.
• Quote: "Integrating EM functionalities into Neurons with modern UI would be extremely powerful and appealing."

Conclusion:

The user test phase provided extensive insights and validated the proposed solutions' effectiveness. Users generally appreciated the intuitive design and potential enhancements in EM integration with Neurons. Feedback highlighted key areas for refinement, such as reducing complexity, adding comprehensive search features, and ensuring a seamless user experience. These suggestions and identified pain points will guide iterative design adjustments to ensure the final product aligns with user needs and business goals..

Overview

Project Introduction

Project Overview:

Digital Employee Experience (DEX) refers to how employees use digital tools and systems at work, including hardware, software, and support. In today's remote and hybrid workplaces, DEX is vital for communication, collaboration, and efficiency. A positive DEX ensures smooth digital interactions, much like how companies strive to provide great experiences for their customers. Effective DEX management boosts productivity and satisfaction. Solutions like Ivanti Neurons for Digital Experience help organizations offer secure, tailored, and productive digital experiences for employees.

Project Goal:

The goal of the DEX Awaking project is to create an integrated management system that improves the digital experience for employees. By combining various tools and metrics into one system, the project aims to provide seamless, proactive, and contextual support. This will help IT teams effectively monitor and optimize employee digital interactions, leading to higher productivity, satisfaction, and operational excellence.

Project Scope:

The DEX Awaking project aims to build an integrated system to enhance Digital Employee Experience (DEX). This system will combine DEX scoring, ITSM systems, bots, analytics, and security tools into one platform. The project involves developing comprehensive metrics, using AI for proactive issue resolution, offering real-time support, and continuously monitoring security and compliance. It will also gather user feedback for ongoing improvements, ensuring seamless digital interactions and improved employee productivity and satisfaction.

Project Phases:

The DEX project enhances IT environment management through two key phases:

• Phase-1: Monitoring with DEX: Implement a monitoring system using DEX to evaluate device performance and user experience in real-time. This proactive approach helps IT teams identify and address issues quickly, maintaining operational efficiency.
• Phase-2: Recommendations and Remediation: Empower users with actionable recommendations to resolve device issues independently via a user-friendly interface. This decentralizes troubleshooting, reduces IT support dependency, and boosts productivity

Resources:

Figma, FigJam and Ivanti design system (IDS).

Discover

This discovery phase sets the foundation for enhancing Ivanti Neurons DEX system, focusing on creating a seamless, efficient, and secure digital experience for Ivanti Neurons users.

Objective:

The discovery phase aims to understand the current challenges and potential improvements for the Digital Employee Experience (DEX) within our organization. This phase focuses on gathering insights from users and analyzing existing systems.

Key Activities:

Stakeholder Interviews:

• Conducted internal interviews with PMs to understand user pain points and requirements.
• Gathered feedback on existing DEX systems and their limitations.

User Survey:

• Distributed a survey to Ivanti Neurons user (IT Aminds and IT manager etc.) to gauge their understanding and use of the DEX score.
• Collected data on how helpful Ivanti Neurons user find the current DEX system and their suggestions for improvement.

Insights Uncovered:

Findings:

1. Fragmented Systems: Current tools and metrics are isolated, leading to nefficiencies in monitoring and troubleshooting.
2. Inadequate Measurement: Lack of comprehensive metrics to evaluate digital experiences across devices and applications.
3. Reactive Support: Predominantly reactive troubleshooting, causing delayed resolutions and lower employee satisfaction.
4. Data Silos: Isolated data sets hinder effective root cause analysis.
5. Security Gaps: Challenges in continuous security and compliance monitoring.

User Feedback:

1. Need for customizable dashboards and clear DEX score calculations.
2. Desire for real-time, proactive issue resolution.
3. Importance of metrics like device performance, network performance, and security compliance.

Next Steps:

1. Develop an integrated, data-driven DEX management system.
2. Create robust metrics and use AI for proactive issue resolution.
3. Incorporate continuous monitoring and user feedback for ongoing improvements.

Conclusion

The discovery phase identified major issues with our current DEX system, such as fragmented tools, inadequate metrics, reactive support, and data silos. User feedback emphasized the need for customizable dashboards and real-time issue resolution. These insights will guide us in developing an integrated, efficient, and user-friendly DEX management system, focused on enhancing security and employee satisfaction. This foundation prepares us for the next steps in improving our digital employee experience.

Define

The define phase clarifies the project's objectives and provides a roadmap for developing an effective DEX management system that meets user needs and addresses key challenges identified during the discovery phase.

Objective:

The define phase uses insights from the discovery phase to set clear goals, scope, and requirements for the DEX Awaking project. This phase is crucial for understanding what the project aims to achieve and how it will address the identified challenges.

Key Activities:

1. Setting Goals:
• Primary Goal:Create an integrated system that improves the Digital Employee Experience (DEX) with seamless, proactive, and contextual support.
2. Defining Scope:
• System Integration: Combine DEX scoring, ITSM, bots, analytics, and security tools into one platform.
• Metrics: Develop strong metrics and use AI for proactive issue detection and resolution.
• Real-Time Support: Provide real-time, contextual support and continuous monitoring of security and compliance.
• User Feedback: Use user feedback to guide ongoing system improvements.
3. Specifying Requirements:
• Unified Experience: Design a smooth troubleshooting and diagnostics workflow.
• Customization: Ensure the system is flexible and can be tailored to individual user needs.
• Scoring and Analytics: Create a comprehensive and detailed scoring system with deep insights.
• Data Visualization: Build dynamic dashboards that highlight key issues and actionable insights.
• Problem Resolution: Incorporate tools for detailed diagnostics and root cause analysis.
• User Interaction: Design intuitive and easy-to-navigate interfaces.
• Integration: Ensure the DEX works well with other Neuron products.
4. Expected Outcomes:
• Higher employee productivity and satisfaction.
• More efficient and strategic IT support.
• Remediation with Integration of Neurons bots.
• DEX hub dashboard that offers monitoring and remediation.
• Better security and compliance oversight.
• Continuous system improvement through feedback.

Key Findings and Personas

Mark: IT Administrator:

Mark is the IT Administrator at a mid-sized company, responsible for maintaining the organization's IT infrastructure. His daily tasks include monitoring system performance, managing updates, and troubleshooting technical issues to ensure seamless digital operations for employees.

Sarah: Security Administrator:

Sarah is the Security Administrator focused on protecting the company's digital assets. She ensures robust security protocols, monitors for threats, and addresses security incidents, especially in a remote and hybrid work environment.

Lisa: Service Desk Manager:

Lisa is the Service Desk Manager who leads a team dedicated to resolving employees' technical issues promptly. She values tools that streamline support workflows, provide actionable insights, and enhance the digital experience, minimizing downtime and boosting productivity.

User Stories

IT Administrator - Mark

1. User Story: Segmentation of Digital Experience Information

As an IT Administrator, I want to view digital experience information segmented by buildings, departments, and job titles so that I can understand the relative health and challenges within different parts of the organization.

Acceptance Criteria: The dashboard must display DEX information segmented by these categories, with customizable filters and drill-down functionality.

2. User Story: Trends and Anomalies in DEX Scores

As an IT Administrator, I want to see trends and anomalies affecting DEX scores so that I can identify and address issues proactively.

Acceptance Criteria: The dashboard should include trend graphs, highlight anomalies, and suggest potential resolutions based on analytics.

3. User Story: Effective Root Cause Analysis

As an IT Administrator, I want an effective root cause analysis process so that I can understand the issues impacting experience, productivity, and manageability.

Acceptance Criteria: The dashboard must enable RCA with drill-down capabilities, integrating the process within the workflow.

Security Administrator - Sarah

1. User Story: Impact of Security Policies

As a Security Administrator, I want visibility of the impact of security policies on users and devices so that I can tune those policies for better adoption and success.

Acceptance Criteria: The dashboard must display policy impact on productivity and performance, offer tuning recommendations, track adoption rates, and provide real-time and historical data.

2. User Story: Security-Centric View for Defense Strategies

As a Security Administrator, I want a security-centric view of the tools supporting a defense-in-depth strategy so that I can understand the impact of security changes on user experience and compliance levels.

Acceptance Criteria: The dashboard should monitor and analyze security changes, track compliance levels, provide insights on user experience shifts, and display historical compliance data.

Service Desk Manager - Lisa

1. User Story: Comprehensive View of Issues

As a Service Desk Manager, I want to understand the bigger picture by viewing issues beyond just the reported tickets, so that I can address the larger set of users experiencing the same issues.

Acceptance Criteria: The dashboard must display both reported and unreported issues, allow for segmentation and analysis, highlight patterns, and enable proactive measures with comprehensive report generation.

2. User Story: Retrospective Ticket Analysis for Automation

As a Service Desk Manager, I want to retrospectively analyze ticket history to identify automatable issues so that I can optimize resource allocation and improve efficiency.

Acceptance Criteria: The dashboard must provide analytics to identify automatable issues, measure their impact, and offer automation recommendations with historical insights on potential savings.

3. User Story: Prioritization of Issues by Impact and Cost

As a Service Desk Manager, I want to view issues through different lenses, such as the impact on end users and the cost to the support desk, so that I can prioritize and address the most critical and costly problems.

Acceptance Criteria: The dashboard must segment issues by impact and cost, enabling prioritization and effective resource allocation.

Conclusion

The define phase set a clear roadmap for enhancing Digital Employee Experience (DEX). By integrating DEX scoring, ITSM systems, bots, analytics, and security tools into a unified platform, we aim to boost productivity and satisfaction.
We outlined key requirements: a unified user experience, customizable settings, comprehensive analytics, intuitive interfaces, and strong security. Focus on proactive issue resolution and real-time support ensures the system will be effective and user-friendly. This phase provides clear direction for the next stages, aligning our solutions with user needs and organizational goals, thus setting the stage for a robust and continuously improving DEX management system.

Ideate

The ideate phase focuses on generating a wide range of ideas and potential solutions to tackle the challenges identified in the discovery and define phases. This creative process encourages brainstorming and collaboration to develop innovative concepts for enhancing the Digital Employee Experience (DEX).

Key Activities:

1. Brainstorming Sessions:
• Conduct collaborative brainstorming sessions with PMs and user survey to gather diverse perspectives.
• Encourage participants to think freely and suggest innovative solutions without constraints.
2. Idea Generation:
• Generate a broad array of ideas aimed at resolving the fragmented systems, improving measurement metrics, enabling proactive support, and breaking down data silos.
• Focus on integrating various tools and metrics into a unified platform that enhances troubleshooting, analytics, and the overall digital experience..
3. Concept Development:
• Develop initial concepts for the unified DEX management system incorporating DEX scoring, bots, analytics, and security metrics.
• Explore features for predictive analytics and automated issue resolution.
4. User-Centric Solutions:
• Ideate on user-friendly interfaces and dashboards that provide real-time, contextual and actionable insights.
• Consider customizable features to cater to different user needs and preferences.
5. Prototypes and Mockups:
• Create low-fidelity prototypes and mockups of the proposed solutions, including dynamic dashboards, scoring systems, and integrated tools.
• Visualize features such as drill-down capabilities, root cause analysis tools, and context-driven troubleshooting suggestions.

Proposed Ideas:

1. Unified Platform:
• Integrate DEX scoring, bots, analytics, and security metrics into a single, seamless platform.
• Ensure the platform provides a cohesive troubleshooting and diagnostic workflow.
2. Comprehensive Scoring System:
• Develop a robust DEX scoring system that aggregates data from multiple sources.
• Include time-based comparisons and ensure scores are related to baselines for better context.
3. Proactive Optimization:
• Utilize predictive analytics to identify and resolve potential issues before they impact user experience.
• Implement tools for automated diagnostics and remediation actions.
4. Dynamic Dashboards:
• Design interactive dashboards that display live data, key focus areas, and problems.
• Use various lenses to examine data, such as ITSM load, end-user impact, and automatable issues.
5. Detailed Diagnostics:
• Enable detailed drill-down capabilities to explore deeper insights, long-term views, and patterns of issues.
• Integrate root cause analysis tools and methods for quick identification and resolution of problems.
6. Intuitive User Interfaces:
• Create interfaces that guide users through troubleshooting scenarios and provide contextual suggestions.
• Ensure ease of navigation based on symptoms leading to potential causes and solutions.

Expected Outcomes:

• A cohesive and integrated DEX management system that addresses the current challenges.
• Enhanced productivity and satisfaction for employees through improved digital interactions.
• Proactive and effective support reducing downtime and IT dependency.
• Continuous monitoring and compliance.
• Ongoing system improvements driven by user feedback and analytics.

Conclusion

The ideate phase generated innovative solutions to enhance the Digital Employee Experience (DEX), including integrating DEX scoring, ITSM systems, bots, analytics, and security tools into a unified platform. We focused on creating customizable scoring systems with real-time insights and trend analysis, using AI for proactive issue detection and resolution. Additionally, we designed user-friendly dashboards with detailed analysis and root cause identification, along with intuitive interfaces for guided troubleshooting and contextual support. These ideas provide a solid foundation for prototyping and testing, aiming to develop a robust DEX management system that boosts employee productivity and satisfaction.

Prototype

In the prototyping phase of the DEX project, we will create functional prototypes of our integrated DEX management system. These will combine DEX scoring, ITSM systems, bots, analytics, and security tools into a unified platform. Prototypes will feature customizable scoring with real-time insights, AI-driven issue detection, and user-friendly dashboards for detailed analysis. This phase aims to validate concepts, gather feedback, and refine solutions to enhance Digital Employee Experience (DEX), ultimately improving productivity and satisfaction for employees.

Tools and Resources

To create our prototypes, we utilized a suite of design tools aligned with our project needs:

• Figma: For interactive prototyping and high-fidelity wireframes.
• FigJam: For UX activities.
• Ivanti Design System:To ensure consistency and compliance with Ivanti's established UI/UX standards.

Prototype

Test

Neurons DEX Usability Test

The user testing phase for the DEX project is scheduled to take place in 2025. During this phase, we will conduct comprehensive usability tests to evaluate the functionality, efficiency, and overall user experience of our integrated DEX management system.

Our goal is to gather valuable feedback from IT Administrators, Security Administrators, and Service Desk Managers using detailed test scenarios that reflect real-world tasks. Participants will interact with the system's customizable scoring, AI-driven issue detection, user-friendly dashboards, and intuitive interfaces to complete typical workflows and troubleshooting processes.

The insights gained from these tests will be crucial in identifying any usability issues, areas for improvement, and validating that the system meets the needs of its users. Based on the feedback, we will make iterative enhancements to ensure the final product delivers a seamless, productive, and satisfying Digital Employee Experience (DEX). This user-centered approach will help us achieve a robust and effective DEX management system aligned with user expectations and organizational

Overview

Problem

Axxerion's users using the mobile device's camera in the web browser want to upload multiple images to attach with a request to report an incident/anomaly or to a property inspection questionnaire. The mobile device's camera usage in Axxerion's AUI (Adaptive User Interface) a web-based interface is a highly demanded feature request.

Intro to Axerrion

Axxerion is a completely cloud-based information system for Facility and Property Management, next-generation smart IWMS. Axxerion is a product brand of Prop-Tech solutions, software, and advisory firm Spacewell. for more visit: www.spacewell.com

About the Project

This project was part of an epic project to introduce the missing features in AUI (Adaptive User Interface) Axxerion's web-based interface to deprecate "Axxerion Mobile" a legacy mobile app to have a single code base and a single entry point to the cloud-base application.

My role and responsibilities

• UX/UI Designer
• Research
• Wireframing
• Prototyping
• Interaction Design
• Visual Design
• Testing

Tools: Adobe XD, Adobe Photoshop, Adobe Illustrator, Trello, App.Mural and Axxerion

Timeline: 8 weeks.

Team and collaboration

• Product Owner
• Team Lead
• Software Architect
• Full-stack Developers

The Goal

Allow user to take or upload images in Axxerion's AUI (Adaptive User Interface) using a web browser, User should be able to add multiple images to a single document object.
Also, the user should be able to:

• Upload multiple images with drag and drop (desktop)
• Upload images from mobile device and desktop
• Delete single or multiple images
• Edit the image e.g., create a circle around an area in the image
• View full image, fit to full screen
• View multiple images in the Gallery view, Grid view, and Strip view 
• Scroll left and right and swipe the images in full screen and in Strip view

Overview

Problem

Axxerion's old UI OUI (original user interface) and new AUI are two entry points to the system, the aim is to eventually completely deprecate old UI but the issue is the portals uses OUI, It is the major blockade to deprecate the old user interface, before OUI is deprecated the portals must be migrated to Axxerion's AUI (adaptive user interface) which also require a complete redesign of portals to align with AUI.

Intro to Axerrion and Portals

Axxerion: Axxerion offers powerful, highly configurable CMMS and IWMS software that is completely role-based. This means it is specially customized for each type of user, whether it be a maintenance manager, a tenant, or a vendor. This allows for the optimization and personalization of the user experience, which means its client organizations can get the most out of this software. Axxerion is part of the Spacewell family. for more visit: www.spacewell.com

Portals: Portals are use as intranet for companies internal use and also as web portal for their exteral client, Axxerion provides both out-of-the-box and customized portals with features that are configured to the needs of the users in client organization.

• Embedded Portals for Client Websites: Embedded directly into a company website so that tenants/clients can easily submit service requests.
• Vendor & Contractor Portal: This portal enables third-party service providers to log into the system with limited access.
• Tenant Portal: Tenants can review and sign leases; make and track rental payments; submit and track service requests; easily communicate with property management.
• Manager Portal: Axxerion’s manager portal offers maintenance managers and system administrators full access to all modules, applications and sites.
• Employee Portals: Employees who are not fully involved in facilities and property management but may need to use the system with Limited Access.

About the Project

This project was an epic project to "Migrate portals to AUI (adaptive user interface)" to have a single entry point to the system, which require complete redesigning of portal UI to align with AUI and introduce new features in new portal UI.​

Use cases

Portals replaced by adaptive user interface, Possible a specific mode of the AUI.

Facilicom internal multi-client use case:
Facilicom applies regions as a concept to seperate internal clients. Each client can have its own portal although not directly tight to the region, they have their own custom menu that is related to the region. The custom menu enables seperate stylesheets to allow the branding per internal client. Facilicom engineers use the regions and the portals to 'go' to an internal client 'environment'.

Samsung Usecase (Samsung is a new customer so not a real migration case).:

• Samsung corporate identity/Branding is must.
• Generic for all users News/Notification/Announcement feed (Through Axxerion Wiki or Introduce RSS Feed?).
• Samsung portal will be used by Samsung employees internal use in BE and NL.
• Main area of portal usage are Requests, Reserving rooms and Registering visitors.

As these usecases define by Team lead:

• ad-hoc and infrequent usage of Axxerion:
  Some customers have portals because the users don't use Axxerion frequently and use it for mundane activities. Such as issuing a request or reserving a room and registering a visitor. The user should not need much knowledge about the system and it should be self-explanatory how to perform these activities. In most cases access to the system is limited. Links to underlying objects are hidden and when necessary special single-purpose pages are configured that are only visible from the portal.
• Access point for suppliers:
  Some customers have portals because they want to provide access to parts of Axxerion for external suppliers and similar affiliated organisations. Also here is the need to limit the access to the system. Single purpose pages are offered.
  

Business case

Portals use old user interface, It is the major blockade to deprecate the old user interface, Migrate portals to adaptive user interface

Scenario

The new functionality is expected to work as follows: A portal can not just be replaced with the adaptive user interface as is. It requires a special mode where the user is focused on a limited set of offered use cases. This portal mode makes sure the user stays within boundaries of the a particular use case and does not stray off to other areas. The consultant should be able to setup the 'portal' that it can offer this focused use cases. Clients are used to the portal to mimic there corporate identity or are branded for the particular usage the client intended.

Aims and Objectives

• Current portals are part of Axxerion OUI
• The old UI will be replaced by new UI AUI(on going process)
• Existing portals require migration to New UI
• Modernize Axxerion Portal UI – aim is gradually move to Material Design​
• Current portals require re-design to align with Axxerion New AUI​
• Client Samsung's portal use as an example use case​
• Architectural changes are require in Axxerion's AUI for portals (Back-End e.g. user related settings – user-profile)​
• New features will be introduced in Portal UI (sub-projects inside portal migration)​

Portals migration and Re-designing of new portal UI

• Analysis phase (100 clients portals were analysed during research)
• Portals migration to new UI (large scale project)
• Re-designing of Portal UI to align with AUI (look & feel, design phase) .
• Introduction of new features in new Portal UI (Sub Projects)​
• Testing phase​

My role and responsibilities

• UX/UI Designer
• Interaction Design
• Visual Design
• Research
• Prototyping
• Testing

Timeline: 14 weeks.

Tools: Adobe XD, Adobe Illustrator, Adobe Photoshop, Trello and Axxerion

Team and collaboration

• Product Owner
• Team Lead
• Software Architect
• Full-stack Developers

Overview

Problem

Axxerion's users using the mobile device's web browser want to get signature from their clients when work is done or have contract signed.

Intro to Axerrion

Axxerion is a completely cloud-based information system for Facility and Property Management, next-generation smart IWMS. Axxerion is a product brand of Prop-Tech solutions, software, and advisory firm Spacewell. for more visit: www.spacewell.com

Use case

Axxerion's users want to more control on the way a signature is exported in a document so that the exported document looks professional and not wrongly generated which would reflect badly on user and client company.

Business case

Provide a signature feature that works, and looks the part it, so Axxerion's customers can rely on it to work as expected and looks professional. The feature is part of the interaction of Axxerion's customers and business partners.

About the Project

This project was part of an epic project to introduce the missing features in AUI (Adaptive User Interface) Axxerion's web-based interface to deprecate "Axxerion Mobile" a legacy mobile app to have a single code base and a single entry point to the cloud-base application.

My role and responsibilities

• UX/UI Designer
• Research
• Wireframing
• Prototyping
• Interaction Design
• Visual Design
• Testing

Tools: Adobe XD, Adobe Illustrator, Trello, and Axxerion

Timeline: 8 weeks.

Team and collaboration

• Product Owner
• Team Lead
• Software Architect
• Full-stack Developers

The Goal

Allow users to sign a property inspection or to get singature from their clients in Axxerion's AUI (Adaptive User Interface) using a web browser, Also, the user should be able to:

• Upload the signature as an image
• Delete the signature
• View the signature details

Overview

Problem

Design agency ask me to redesign Doula App with modern look and feel and add new features.

Intro to Doula

A pregnancy app to help you through contractions, Doula is pregnant women personal labor coach that will help pregnant women breath through labor, ease contractions, will provide with psychological comfort and calm.

Brief

(Brief from design Agency) Download the Doula Labor Coach app from the App Store or the Google Play Store and study the app carefully. We ask you to redesign the app and make a complete workflow of the app based on your new design.

All functionalities that are currently available in the app should be included in the new workflow:

• We want a smarter, better, and cooler interface.
• Upgrade it to a more fresh and modern ‘2018’ feeling.
• We are not just looking for an upgrade in color or fonts though, but also a redesign on a UI/UX- and interaction design level.

Add a minimum of 1 and a maximum of 3 new functionalities to the app:

• The focus of these new functionalities should be to improve the current user experience.
• Think about the target user group and what they need.
• Feel free to be creative and think out-of-the box!.

Project discription

In this app, expert midwife coaches pregnant women during labor contractions. User just have to listen to the audio coaching to relax. The statistics and history of labor times are automatically displayed in a clear table. Make photo albums, Save appointments. The app is available in several languages: English, Dutch, German, Spanish, Russian, French, Turkish and Moroccan.

About the Project

The purpose of this project was to upgrade the existing app to a more fresh and modern look and feel with addition of extra useful features.

Two new features were added:

• Make photo albums to keep track of pregnancy and baby growth.
• keep record of appointments and set reminders.

User Consultation:

• Female 28 years.
• Mother of 2 year old.
• Pregnancy related apps user.

Overview

Brief

(Brief from design Agency) Briefing Starbucks would like to provide payment convenience and speed via an app, and also generate customer loyalty and repeat-purchases through a loyalty system.

Provide payment convenience and speed for customers, to generate extra revenue:

• Pre-Order and pay coffee and pastry for the location, date, and time you selected.
• Send the user a notification when the order is ready for pickup.
• Focus on a smart interface and be sure the most important modules are accessible through the home screen.
• Additional options in the order / payment-flow are welcomed.

Binding customers, and generating repeat-purchases, through a loyalty system:

• A straight-forward, honest and clear loyalty module.
• Rewarded loyalty points are dependent on the quantity of orders or prices of purchases.
• Overview on the user’s saved points.
• Extra features for this app solution are not needed, unless the checklist or any evaluation criteria require these.

Project discription

The Starbucks pre-order app is a convenient way to order ahead for pickup, and pay online and customize your favorites. Rewards are built right in, so you'll earn Stars towards free drinks and food on your purchases. Rewards points encourages the customer to repeat-purchases through a loyalty system. Customize and place your order, then pick up from a nearby participating store without waiting in line.

Aims and Objectives

The purpose of this project is to demonstrate UX/UI design skills.

About the Project

Design agency ask me to design Starbucks Pre-Order App with modern look and feel.

Resources:

Pixabay, Pixeden, Freepik, Flaticon, Svgrepo.

Overview

Project discription

Indus Food is a fictional food delivery service. for those who are always busy and don't have time to cook. they can use this service and order their meal online. This is single page responsive website.

About the Project

The purpose of this project is merely to demonstrate web development technologies including HTML, CSS and Jquery skills.

Tools and Technologies

HTML, CSS and Jquery, Photoshop and VS Code.

Resources:

Pixabay, Pixeden, Freepik, Flaticon, Google Fonts.

Overview

Project discription

Visit Pakistan is a fictional tour Pakistan service. user can booking tours in groups small or large, This is single page responsive website.

About the Project

The purpose of this project is merely to demonstrate web development technologies including HTML and CSS.

Tools and Technologies

HTML, CSS, SASS, Photoshop and Visual Studio Code.

Resources:

Responsive Grid System, Codepen, Pixabay, FontIcons, Google Fonts, BDEX.

Overview

Project discription

Indus Bakers is a fictional bakery service website. provide Bakery products for all events and arrange vast variety of events at Indus hall or at customers venue for all kind of events, thanks to indus webshop, bakery items can be purchased online, This is responsive website.

About the Project

The purpose of this project is to demonstrate UX/UI design skills. In UI section you will find desktop, tablet and mobile version of Indus Bakers.

Resources:

Pixabay, Pixeden, freepik, flaticon.