Autodev Studio is a tool that developers use in tandem with Docker© to manage software containers. Their launch date was set for 4 weeks prior to contacting me and all they had produced was the code for the backend as well as a rudimentary UI.
To have their software ready for the public they needed to:
· Design a brand identity
· Layout UI for pages
· Define primary user flows for the software.
To understand the foundational qualities that define their brand, I held a brand workshop that consisted of a card sorting exercise that the entire company participated in. On one side was a category of “What is Our Brand” and on the other was “What Our Brand is Not”. Through many iterations of descriptive adjectives they boiled it down to keywords like Bold, Exciting, Momentum, Unique, Connecting. This helped inspire the first round of logo design.
Based on what I learned during the brand workshop, I began sketching out a series of 15 low-fi logo ideas on paper. From this list, a company-wide vote was conducted from which the top 4 logos were selected. A higher fidelity rendition was made to these 4 choices and a final variation was eventually selected as their official logo.
Knowing that we had little time to complete the scope of this project, I created three UI theme variations to spark conversations concerning the use of color, texture, line, and buttons, navigation strategy, UI interaction and more. I then held a focus group with executives and developers where we picked apart and iterated upon the elements in each UI and finally decided on an official version.
The official UI variation set the stage for how UI’s in the system would be constructed overall.
· Consulting with the development team, I identified 5 unique user flows in the system.
· Step-by-step flows were detected and designed using breadcrumbs to give the user a more intimate understanding of the process and where they were currently in it.
· Analyses of the major flows were conducted and simplified, decreasing extraneous steps and pages.
· Simple and constructive language was added to make the system more intuitive and accessible to a wider audience.
· A/B Testing was done and 100% of the 20 users agreed that these changes made the experience easier and more enjoyable.
Autodev Studio is a tool that developers use in tandem with Docker© to manage software containers. Their launch date was set for 4 weeks prior to contacting me and all they had produced was the code for the backend as well as a rudimentary UI.
To have their software ready for the public they needed to:
· Design a brand identity
· Layout UI for pages
· Define primary user flows for the software.
To understand the foundational qualities that define their brand, I held a brand workshop that consisted of a card sorting exercise that the entire company participated in. On one side was a category of “What is Our Brand” and on the other was “What Our Brand is Not”. Through many iterations of descriptive adjectives they boiled it down to keywords like Bold, Exciting, Momentum, Unique, Connecting. This helped inspire the first round of logo design.
Based on what I learned during the brand workshop, I began sketching out a series of 15 low-fi logo ideas on paper. From this list, a company-wide vote was conducted from which the top 4 logos were selected. A higher fidelity rendition was made to these 4 choices and a final variation was eventually selected as their official logo.
Knowing that we had little time to complete the scope of this project, I created three UI theme variations to spark conversations concerning the use of color, texture, line, and buttons, navigation strategy, UI interaction and more. I then held a focus group with executives and developers where we picked apart and iterated upon the elements in each UI and finally decided on an official version.
The official UI variation set the stage for how UI’s in the system would be constructed overall.
· Consulting with the development team, I identified 5 unique user flows in the system.
· Step-by-step flows were detected and designed using breadcrumbs to give the user a more intimate understanding of the process and where they were currently in it.
· Analyses of the major flows were conducted and simplified, decreasing extraneous steps and pages.
· Simple and constructive language was added to make the system more intuitive and accessible to a wider audience.
· A/B Testing was done and 100% of the 20 users agreed that these changes made the experience easier and more enjoyable.
Autodev Studio is a tool that developers use in tandem with Docker© to manage software containers. Their launch date was set for 4 weeks prior to contacting me and all they had produced was the code for the backend as well as a rudimentary UI.
To have their software ready for the public they needed to:
· Design a brand identity
· Layout UI for pages
· Define primary user flows for the software.
To understand the foundational qualities that define their brand, I held a brand workshop that consisted of a card sorting exercise that the entire company participated in. On one side was a category of “What is Our Brand” and on the other was “What Our Brand is Not”. Through many iterations of descriptive adjectives they boiled it down to keywords like Bold, Exciting, Momentum, Unique, Connecting. This helped inspire the first round of logo design.
Based on what I learned during the brand workshop, I began sketching out a series of 15 low-fi logo ideas on paper. From this list, a company-wide vote was conducted from which the top 4 logos were selected. A higher fidelity rendition was made to these 4 choices and a final variation was eventually selected as their official logo.
Knowing that we had little time to complete the scope of this project, I created three UI theme variations to spark conversations concerning the use of color, texture, line, and buttons, navigation strategy, UI interaction and more. I then held a focus group with executives and developers where we picked apart and iterated upon the elements in each UI and finally decided on an official version.
The official UI variation set the stage for how UI’s in the system would be constructed overall.
· Consulting with the development team, I identified 5 unique user flows in the system.
· Step-by-step flows were detected and designed using breadcrumbs to give the user a more intimate understanding of the process and where they were currently in it.
· Analyses of the major flows were conducted and simplified, decreasing extraneous steps and pages.
· Simple and constructive language was added to make the system more intuitive and accessible to a wider audience.
· A/B Testing was done and 100% of the 20 users agreed that these changes made the experience easier and more enjoyable.
Autodev Studio is a tool that developers use in tandem with Docker© to manage software containers. Their launch date was set for 4 weeks prior to contacting me and all they had produced was the code for the backend as well as a rudimentary UI.
To have their software ready for the public they needed to:
· Design a brand identity
· Layout UI for pages
· Define primary user flows for the software.
To understand the foundational qualities that define their brand, I held a brand workshop that consisted of a card sorting exercise that the entire company participated in. On one side was a category of “What is Our Brand” and on the other was “What Our Brand is Not”. Through many iterations of descriptive adjectives they boiled it down to keywords like Bold, Exciting, Momentum, Unique, Connecting. This helped inspire the first round of logo design.
Based on what I learned during the brand workshop, I began sketching out a series of 15 low-fi logo ideas on paper. From this list, a company-wide vote was conducted from which the top 4 logos were selected. A higher fidelity rendition was made to these 4 choices and a final variation was eventually selected as their official logo.
Knowing that we had little time to complete the scope of this project, I created three UI theme variations to spark conversations concerning the use of color, texture, line, and buttons, navigation strategy, UI interaction and more. I then held a focus group with executives and developers where we picked apart and iterated upon the elements in each UI and finally decided on an official version.
The official UI variation set the stage for how UI’s in the system would be constructed overall.
· Consulting with the development team, I identified 5 unique user flows in the system.
· Step-by-step flows were detected and designed using breadcrumbs to give the user a more intimate understanding of the process and where they were currently in it.
· Analyses of the major flows were conducted and simplified, decreasing extraneous steps and pages.
· Simple and constructive language was added to make the system more intuitive and accessible to a wider audience.
· A/B Testing was done and 100% of the 20 users agreed that these changes made the experience easier and more enjoyable.