Select Page

Ui/Ux redesign of AtlaSense

I did an audit of the current site www.atlasense.com and pointed out some major issues to be improved on the landing page. Briefly, I am going to point out the reasons concerning my redesign:


Elaboration of a symbolic icon that defines the company. Distinguishable words by font weight. Makes it easier to read.


Earlier, this section appeared only in the footer.


Use of established icons that are immediately recognized and associated with particular actions. No need to label these. The web search functionality may be desirable as the company is specialized on data sorting.


Addition of the adjective “free”, to call for action.


Used in the header title as a highlight, for better readability than below the logo. Extensive use of complementary colors blue/orange for contrast/matching purposes.


Link to an intro video that explains briefly and clearly how the product works. Considering the complexity of the product, this is preferable than  the current animated gif sequence.


The movement of elements helps solidify the message. Scroll may start automatically or by clicking.


Show major active social networking profiles.


Use simple icons to accompany the text.

 


Take the opportunity to briefly explain and visually show a feature/benefit of the product together with the acknowledgement words of a satisfied client.


To improve trust and credibility, use when possible a personal photo and corporate logo of a prestigious client.

 

 

 


Study the possibility to use the graphic symbol without the company’s name to draw attention to it.


This is not shown in the header. Legal notes usually appear in the footer.


Displayed centered in the footer along with the copyright.

 

Flows & Navigation Ux

When navigating through the current Top Nav and link structure, a user may reach the same destination from different links. Therefore, a user may start reading the text on a particular topic and recognize he had already read it before on another web section. This repetition could become a bit confusing. Hence, when the user needs to read the explanation of a feature, it is preferable to show it to him fully in one step, rather than having him reading excerpts and clicking on numerous links. Briefly, I am going to point out the reasons concerning the restructure of the menu and links:


This section can be accessed and read in several ways from the homepage: a) from the button “See what AtlaSense can do for you”. b) from links inside the text: “eDiscovery, Contract Gathering or Records Management”. c) from the Menu: Product > Use cases.


This section can be accessed in several ways and read in different text versions: a) from the menu: Technology > Machine Learning (”Document, Topic”). b) from the menu: Products > Features > Machine Learning (”Document, Alerts, Topic”). c) from the menu: Technology > Machine Learning > button“Learn more”> Contract Gathering > Document Categorization > button“Learn more”.


This section can be accessed in several waysand read in different text versions: a) from the menu: Technology > Security (”Application, Data, Network, Audit, Two-factor, Certifications”). b) from the menu: Product > Benefits > Security (”Specialized Security”). c) from the menu: Product > Features > Security (”Application, Data & Network Security”).

 


This section can be accessed and read in 2 ways: a) from the menu: Technology > Machine Learning > button“Learn more”> Contract Gathering. b) from the menu: Product > Use Cases > Contract Gathering > button “Learn more”.


This section can be accessed and read in 2 ways: a) from the menu: Product > Benefits > Automation > Enterprise > button“Learn more”. b) from the menu: Product > Use Cases > Ediscovery > link “Enterprise”.


This section can be accessed and read in 2 ways: a) from the menu: Product > Benefits > Automation > Early Case Assessment > button“Learn more”. b) from the menu: Product > Use Cases > Ediscovery > link “Early Case Assessment”.


This section can be accessed and read in several ways: a) from the menu: Product > Use Cases > Contract Gathering > link “data sources”. b) from the menu: Product > Use Cases > Contract Gathering > Central Repository > button“Learn more”. c) from the menu: Product > Use Cases > Ediscovery > link “data sources”. d) from the menu: Product > Use Cases > Ediscovery > Features > Data Integrations > link “others”. e) from the menu: Product > Use Cases > Compliance > Central Repository > button “Learn more”. f) from the menu: Product > Use Cases > Records Management > Central Repository > button “Learn more”. g) from the menu: Product > Use Cases > Due Dilligence > Central Repository > button “Learn more”. h) from the menu: Product > Features > Data Integrations > button “Learn more”. i) from the menu: Product > Data Integrations.