Crystal+

Support Sales & Marketing teams identifying client patterns and insights to enable prospect identification, recommendations and development of value propositions.

Role
UI/UX Designer & Frontend Developer
Problem

First version of Crystal+ features a search engine for Companies, companies' key people and IBM products. Although the application was very useful for Sales & Marketing IBMers, the traditional keyword search & browsing approach to navigate through the huge amounts of data was usually tedious, and sometimes the obtained data was difficult to understand.

Previous version navigation approach was usually tedious, and the obtained data was difficult to understand.

Solution

The second version of Crystal+ proposes a new experience using NLQ (typing or using voice) to allow the user ask more complex question and in that way reduce the number of results obtained. Beside of improving the search experience, the overall design of the application was re-done having the Material paradigm as inspiration.

Responsabilities

In a dynamic team of 5-8 people, I was responsible for User Research, Prototyping & Designing and UI Development, working close and constantly aligning with the other Backend Engineers and Researchers.

Design Methodology

Although this application is a research prototype and not a final product, we were able to run some interviews with real users of the existing application to understand how it was helping them and what we could improve. The results of this interviews made us realize of some issues and confirm that our own goals where also interesting to tackle.

User Pain points
  • Understand data Sometimes the data is presented in a way difficult to understand, specially charts.
  • Specific results Search results UIs are cluttered up with a lot of data, some of it needless
  • Poor search experience Search engine is very limited User should be able to make specific questions and return very precise results.
Product Goals
  • Better information architecture presenting the data in the most understandable and meaningful way
  • Introduce Natural language to be able to ask very specific questions and get narrowed relevant results
  • Revamp the UI with a more modern and flat design
  • Component based UI to easily adapt and scale it when necessary
Technical Side

My goal for this project was to create a UI that was Component-based (to allow future scalability) and minimize framework dependency. The Polymer project was the perfect choice: although it is not very extended, it aims to be a Standard. Compared to the most famous frameworks at the moment (React and Angular), Polymer is more a library that allows developers to work easier with Web Components (nowadays supported by almost all browsers) by giving us some sugar functions to make our lives easier.

URL Technologies
HTML, CSS, Sass, JavaScript, Polymer, Web Components, Sketch, inVision, REST, ElasticSearch, Docker, Jenkins
Company Years
2016 - 2019