Case Study 01
Case Study 01
Case Study 01
A significant upgrade to a workspace aimed at boosting efficiency through clearly defined processes and a visionary approach.
A significant upgrade to a workspace aimed at boosting efficiency through clearly defined processes and a visionary approach.
A significant upgrade to a workspace aimed at boosting efficiency through clearly defined processes and a visionary approach.
Industry
Industry
B2B (Supply Chain)
B2B (Supply Chain)
Company
Company
o9Solutions
o9Solutions
Timeline
Timeline
8 Weeks
8 Weeks
Highlights
My Deliverables
Designing for the web
Creative direction
Documentation UX testing
Designing for Accessibility
Creating icons
Tools Used
Figma, Sketch, Balsamiq, Docs, Sheets, Grain, Paper and pen
My Team
Shobhna: UX Designer I
Sarthak Panda: Product Manager
Vishnu Solanki: Sr. Software Engineer
Shashi Kumar: Software Engineer
Ayushi Saxena: Sr. QA Analyst
UX Team and rest of Team at o9!
o9Solutions
o9Solutions
o9Solutions is an unicorn supply chain software company with a valuation of over $2 billion. An AI-powered analytics and planning platform that seamlessly integrates revenue streams and decision-making processes, boosting efficiency and agility for businesses. Digitizing processes transforms businesses into an integrated business planning capability revolutionizes the process towards improved financial results and helping companies to reduce their carbon footprints with real-time data. It empowers transparency, reduces organizational silos, and forging a truly unified business planning system tailored for the digital era.
o9Solutions is an unicorn supply chain software company with a valuation of over $2 billion. An AI-powered analytics and planning platform that seamlessly integrates revenue streams and decision-making processes, boosting efficiency and agility for businesses. Digitizing processes transforms businesses into an integrated business planning capability revolutionizes the process towards improved financial results and helping companies to reduce their carbon footprints with real-time data. It empowers transparency, reduces organizational silos, and forging a truly unified business planning system tailored for the digital era.
Creative direction for the project
Creative direction for the project
Being with o9solutions for two years and four months has been a thrilling and insightful journey. My work revolved around, defining design scopes and timelines, mapping out the design process and high-fidelity mockups. I was managing the project’s creative direction. I diligently maintained documentation for the implementation of designs, ensuring transparency and coherence while collaborating or with the engineering team. I remained actively engaged with my team from the initial discussions to the testing phase, contributing proactively to the entire process.
Being with o9solutions for two years and four months has been a thrilling and insightful journey. My work revolved around, defining design scopes and timelines, mapping out the design process and high-fidelity mockups. I was managing the project’s creative direction. I diligently maintained documentation for the implementation of designs, ensuring transparency and coherence while collaborating or with the engineering team. I remained actively engaged with my team from the initial discussions to the testing phase, contributing proactively to the entire process.
Problem statement
Problem statement
Why the Config 2.0 version was needed?
Why the Config 2.0 version was needed?
Complex JSON Files Hinder Version Control
Complex JSON Files Hinder Version Control
The existing tenant configuration, version 1.0, uses a complex JSON file format that is difficult to manage with version control systems. This complexity creates challenges in tracking changes, collaborating on updates, and maintaining clear version histories, ultimately reducing efficiency and increasing the likelihood of errors.
The existing tenant configuration, version 1.0, uses a complex JSON file format that is difficult to manage with version control systems. This complexity creates challenges in tracking changes, collaborating on updates, and maintaining clear version histories, ultimately reducing efficiency and increasing the likelihood of errors.
Lack of Integrated Model Library for Package Sharing
Lack of Integrated Model Library for Package Sharing
Although the Model Library was intended to facilitate easy sharing of self-contained packages for customer implementations, this concept was not integrated into the original design of Config 1.0. This oversight makes it cumbersome to define and distribute these packages, limiting the usability and effectiveness of the Model Library for users.
Although the Model Library was intended to facilitate easy sharing of self-contained packages for customer implementations, this concept was not integrated into the original design of Config 1.0. This oversight makes it cumbersome to define and distribute these packages, limiting the usability and effectiveness of the Model Library for users.
Need for a More Robust and User-Friendly Config 2.0
Need for a More Robust and User-Friendly Config 2.0
To address a significantly enhanced platform with improved package creation flow and distribution within the Model Library. The new version will focus on aligning with user needs and expectations, enhancing compatibility, and providing a more flexible and user-friendly solution for managing tenant configurations. This will ensure a more seamless experience and better support for collaborative workflows.
To address a significantly enhanced platform with improved package creation flow and distribution within the Model Library. The new version will focus on aligning with user needs and expectations, enhancing compatibility, and providing a more flexible and user-friendly solution for managing tenant configurations. This will ensure a more seamless experience and better support for collaborative workflows.
Context
Context
Why the Config 2.0 version was needed?
Why the Config 2.0 version was needed?
How the o9 platform’s configuration is stored
How the reference products are built and released
The process by which customer implementations adopt and extend reference products
How users collaboratively work on the platform configuration and challenges they come across
The platform enhancements that constitute Config 2.0 can be grouped into two major categories
The concept of ‘modularisation’ here is the segregation of entities according to Project, Solutions and Config Blocks. This is going to help the users to make customised Solutions and later an option to update their ‘Config Blocks’ versions.
Git Integration with the o9 Platform
Modularisation of Platform Config
01
Paradigm shift incorporated these functionalities for Config 2.0
A Config Block
02
(A group of entities makes a config Block for example: IBP Foundation)
Dimensions
Rules
Reports
+More
Measures
Workspaces
03
Tenant
A Solution
Config 2.0
(A Collection of Config Block makes a Solution)
IBP Foundation
Demand Planning
Supply Planning
IBP Foundation
Workspaces
Workspaces
Who are the users ?
To proceed further, we needed to create personas that would give us a better understanding of our users and their needs, these personas are based on the interview notes shared by the previous project manager. To add depth to our knowledge, I have combined the functionality expectations to see how users might use Config 2.0 in different situations. The personas and scenarios together guide the design & development process by focusing on the real user’s needs, pain points & behaviors.
To proceed further, we needed to create personas that would give us a better understanding of our users and their needs, these personas are based on research notes shared by the project manager which the previous project manager documented.
To add depth to our understanding I have combined the functionality expectations to see how users might use Config 2.0 in different situations. The personas & scenarios together guide the design & development process by focusing on the real user’s needs, pain points and behaviors.
Personas are created based on insights are below;
User Research
User Research
Darrell Turner
Persona 01
Organisation
o9Solutions Inc.
Team
Demand Planning
Role
PMM DP team User
Needs
A secure and centralised repository for storing and managing platform configurations.
Version control mechanisms to track changes and revert to previous configurations if required.
Role-based access control to ensure only authorised users can modify or access configurations.
Pain points
Lack of centralized and easily accessible storage for platform configurations.
Difficulty in version control and tracking changes in the configuration.
Security concerns regarding the storage and access to sensitive configuration data.
Functionality
Expectations
Build
Release (R1)
Darrell Turner
Persona 01
Organisation
o9Solutions Inc.
Team
Demand Planning
Role
PMM DP team User
Needs
A secure and centralised repository for storing and managing platform configurations.
Version control mechanisms to track changes and revert to previous configurations if required.
Role-based access control to ensure only authorised users can modify or access configurations.
Pain points
Lack of centralized and easily accessible storage for platform configurations.
Difficulty in version control and tracking changes in the configuration.
Security concerns regarding the storage and access to sensitive configuration data.
Functionality
Expectations
Build
Release (R1)
Darrell Turner
Persona 01
Organisation
o9Solutions Inc.
Team
Demand Planning
Role
PMM DP team User
Needs
A secure and centralised repository for storing and managing platform configurations.
Version control mechanisms to track changes and revert to previous configurations if required.
Role-based access control to ensure only authorised users can modify or access configurations.
Pain points
Lack of centralized and easily accessible storage for platform configurations.
Difficulty in version control and tracking changes in the configuration.
Security concerns regarding the storage and access to sensitive configuration data.
Functionality
Expectations
Build
Release (R1)
Who are the users ?
To proceed further, we needed to create personas that would give us a better understanding of our users and their needs, these personas are based on research notes shared by the project manager which the previous project manager documented.
To add depth to our understanding I have combined the functionality expectations to see how users might use Config 2.0 in different situations. The personas & scenarios together guide the design & development process by focusing on the real user’s needs, pain points and behaviors.
Personas are created based on insights are below;
User Research
Darrell Turner
Persona 01
Organisation
o9Solutions Inc.
Team
Demand Planning
Role
PMM DP team User
Needs
A secure and centralised repository for storing and managing platform configurations.
Version control mechanisms to track changes and revert to previous configurations if required.
Role-based access control to ensure only authorised users can modify or access configurations.
Pain points
Lack of centralized and easily accessible storage for platform configurations.
Difficulty in version control and tracking changes in the configuration.
Security concerns regarding the storage and access to sensitive configuration data.
Functionality
Expectations
Build
Release (R1)
Gregory Whitman
Persona 01
Organisation
o9Solutions Inc.
Team
Master Planning
Role
PMM MP team User
Needs
Limited collaboration features lead to siloed work & communication gaps.
Challenges in real-time collaboration, especially for geographically dispersed teams.
Difficulty in tracking contributions and changes made by different users.
Pain points
Lack of collaborative and customizable capabilities for multiple users.
Communication tools are integrated into the platform for seamless collaboration.
User activity tracking and version history to identify contributors and changes.
Functionality
Expectations
Customise (R1)
Build
Release (R2)
Ava Lane
Persona 01
Organisation
o9Solutions Inc.
Team
Consultation
Role
Project Dev/ FT user
Needs
Automated workflows for building and testing reference products.
Continuous integration & deployment pipelines for streamlined releases.
Scalable infrastructure to handle increased production demands.
A more efficient and collaborative environment for users
Pain points
Inefficiencies in the reference product development process.
Lack of automation leads to manual errors and delays in releases.
Difficulty in scaling the production of reference products.
Transition plans to minimize disruptions and ensure a smooth migration.
Functionality
Expectations
Customize
Build
Run
Steven Carrington
Persona 01
Organisation
Acme Inc.
Team
Acme Inc.
Role
PMM team User
Needs
Education & communication about the advantages of the paradigm shift.
Clear documentation and training resources for customers.
Customization capabilities to easily adapt reference products to unique requirements.Help & support customers during the implementation phase and extension processes.
Pain points
Lack of centralized and easily accessible storage for platform configurations.
Difficulty in version control and tracking changes in the configuration.
Security concerns regarding the storage and access to sensitive configuration data.
Functionality
Expectations
Plan
User-flow
User-flow
This is a visual representation of how users navigate through Config 2.0. I created this user flow by closely working with the System Architect. To simplify the complex flow, I worked on user flow to optimize the existing design, identify pain points, facilitate collaboration & validate design decisions. Overall, this user flow ensured that we have thought holistically and are aligned with the user's needs in mind.
This is a visual representation of how users navigate through Config 2.0. I created this user flow by closely working with the System Architect. To simplify the complex flow, I worked on user flow to optimize the existing design, identify pain points, facilitate collaboration & validate design decisions. Overall, this user flow ensured that we have thought holistically and are aligned with the user's needs in mind.
Primary Flow/ Action
Secondary Flow/Action
Tertiary Flow
Task-flow
Task-flow
Since the user flow looks overwhelming by adding this step I thought to break down the complex flows into tasks. The task flows are a series of steps that users could follow to achieve the goal within the same interface. Generally, tasks could follow mutually exclusive sequences & goals or different sequences for the same goal.
Here, the task flows are divided into three tasks aiming for a similar goal of loading config blocks.
Since the user flow looks overwhelming by adding this step I thought to break down the complex flows into tasks. The task flows are a series of steps that users could follow to achieve the goal within the same interface. Generally, tasks could follow mutually exclusive sequences & goals or different sequences for the same goal.
Here, the task flows are divided into three tasks aiming for a similar goal of loading config blocks.
Designer
A project is selected. Now, user can create a solution or select a one from the list view.
Designer
Create a new Config Block.
Designer
A solution is selected & a new config block has to be created.
Designer
Once, the new details are saved the config block, it’ll be added to the list view. Blocks in the list are default selected to load.
Designer
Loading solution and config blocks in process.
Designer
All the solution & config blocks are loaded. User has primary action to publish this solution as a package following with secondary & tertiary actions.
Designer
Publish a package form
Designer
Successfully published the package, review the published details & close the form.
Designer
Back to the loaded config blocks. After publishing the package user are able to explore other actions like:
Reset the tenant
Manage module
Opening a config block to navigate to designer homepage
Other actions
Designer
Project list view
Designer
This is ‘Designer’ homepage page with active config block selection. User can create any number of dimensions, attributes & hierarchies here. This workspace is used for model design and model maintenance.
Designer
Adding config blocks from a project
Designer
Adding config blocks from a published package
Task 1
Publish a package by creating config blocks.
Task 2
Publish a package by adding config blocks from a project.
Task 3
Publish a package by adding config blocks from a published package.
Iterations & Final Designs
Iterations & Final Designs
Config 1.0 vs Config 2.0
Show Labels
Left Pane is used to just show loaded config blocks
Tab structure for organization modules and package used vs public packages
Additional action to create package on top
Accordion used for compress information
Previous Design
Overwhelming experience with multiple action flows at the same time at same time. The primary flow should be loading modules. Then you can create the package.
Information hierarchy missing from the pane. A lot is happening in the right pane increasing cognitive load for the user.
The left pane is not utilized until user loads some modules.
Step progress bar
Introducing the information hierarchy
Clear and precise context to CTA
Improvements
Simplifying the process as steps, focused on single flow outcome to able to load the config blocks (modules).
Structured information hierarchy in the steps making the concept of config blocks understandable.
Utilizing left pane with step instruction and context.
Video Loop
Add action icon for config block. Multiple options to create/ add the config block
Create config block
Add from project
Add from published package
Improvements
In the previous design, users could select config blocks (modules) only which are listed. In Config 2.0 users can create a new config block, add from other projects or add from published packages.
Users can create a new config block, add from other projects or add from published packages.
Accordion used for compress information
Arrange the order of added config blocks before loading.
Improvements
Once config blocks are added, the user can re-arrange the chronological sequence as required.
The pane is entirely for showing the loaded modules
Inconsistence information labels and repetition
Previous Design
Left pane being blank until the modules are loaded.
After modules are loaded, the right pane still stays there. It becomes quite packed when more loaded modules has to be displayed on left pane side.
The information on module blocks has inconsistent patterns and repeated information on the module tile.
The left pane is not utilized until user loads some modules.
Concept focus changed from Config blocks (modules) to solution
Organized & consistency information display
Reset all selection & redirect to start
Publish Package as primary CTA
Current tenant
Accordion used for compress information
Improvements
Revived the concept of the flow focusing on solution than config blocks. Structured information hierarchy in the steps making the concept of config blocks understandable.
The information on config blocks (modules) is organized, aligned and consistant.
Action bar placement changed to bottom with primary & secondary CTAs.
Reset flow redirect user to go back to start again allowing user to make correct selection.
Config 1.0 vs Config 2.0
Left Pane is used to just show loaded config blocks
Tab structure for organization modules and package used vs public packages
Additional action to create package on top
Accordion used to compress section
Previous Design
Overwhelming experience with multiple action flows at the same time at same time. The primary flow should be loading modules. Then you can create the package.
Information hierarchy missing from the pane. A lot is happening in the right pane increasing cognitive load for the user.
The left pane is not utilized until user loads some modules.
Step progress bar
Introducing the information hierarchy
Clear and precise context to CTA
Improvements
Simplifying the process as steps, focused on single flow outcome to able to load the config blocks (modules).
Structured information hierarchy in the steps making the concept of config blocks understandable.
Utilizing left pane with step instruction and context.
Video Loop
Add action icon for config block. Multiple options to create/ add the config block
Create config block
Add from project
Add from published package
Improvements
In the previous design, users could select config blocks (modules) only which are listed. In Config 2.0 users can create a new config block, add from other projects or add from published packages.
Users can create a new config block, add from other projects or add from published packages.
Accordion used for compress information
Arrange the order of added config blocks before loading.
Improvements
Once config blocks are added, the user can re-arrange the chronological sequence as required.
The pane is entirely for showing the loaded modules
Inconsistence information labels and repetition
Previous Design
Left pane being blank until the modules are loaded.
After modules are loaded, the right pane still stays there. It becomes quite packed when more loaded modules has to be displayed on left pane side.
The information on module blocks has inconsistent patterns and repeated information on the module tile.
The left pane is not utilized until user loads some modules.
Concept focus changed from Config blocks (modules) to solution
Organized & consistency information display
Reset all selection & redirect to start
Publish Package as primary CTA
Current tenant
Accordion used for compress information
Improvements
Revived the concept of the flow focusing on solution than config blocks. Structured information hierarchy in the steps making the concept of config blocks understandable.
The information on config blocks (modules) is organized, aligned and consistant.
Action bar placement changed to bottom with primary & secondary CTAs.
Reset flow redirect user to go back to start again allowing user to make correct selection.
Config 1.0 vs Config 2.0
Show Labels
Left Pane is used to just show loaded config blocks
Tab structure for organization modules and package used vs public packages
Additional action to create package on top
Accordion used to compress section
Previous Design
Overwhelming experience with multiple action flows at the same time at same time. The primary flow should be loading modules. Then you can create the package.
Information hierarchy missing from the pane. A lot is happening in the right pane increasing cognitive load for the user.
The left pane is not utilized until user loads some modules.
Step progress bar
Introducing the information hierarchy
Clear and precise context to CTA
Improvements
Simplifying the process as steps, focused on single flow outcome to able to load the config blocks (modules).
Structured information hierarchy in the steps making the concept of config blocks understandable.
Utilizing left pane with step instruction and context.
Video Loop
Add action icon for config block. Multiple options to create/ add the config block
Create config block
Add from project
Add from published package
Improvements
In the previous design, users could select config blocks (modules) only which are listed. In Config 2.0 users can create a new config block, add from other projects or add from published packages.
Users can create a new config block, add from other projects or add from published packages.
Accordion used for compress information
Arrange the order of added config blocks before loading.
Improvements
Once config blocks are added, the user can re-arrange the chronological sequence as required.
The pane is entirely for showing the loaded modules
Inconsistence information labels and repetition
Previous Design
Left pane being blank until the modules are loaded.
After modules are loaded, the right pane still stays there. It becomes quite packed when more loaded modules has to be displayed on left pane side.
The information on module blocks has inconsistent patterns and repeated information on the module tile.
The left pane is not utilized until user loads some modules.
Concept focus changed from Config blocks (modules) to solution
Organized & consistency information display
Reset all selection & redirect to start
Publish Package as primary CTA
Current tenant
Accordion used for compress information
Improvements
Revived the concept of the flow focusing on solution than config blocks. Structured information hierarchy in the steps making the concept of config blocks understandable.
The information on config blocks (modules) is organized, aligned and consistant.
Action bar placement changed to bottom with primary & secondary CTAs.
Reset flow redirect user to go back to start again allowing user to make correct selection.
More Projects
