Kollect
Kollect
UX Research & Design: simple user onboarding and content management
UX Research and Design - Neil Ranada
Project type - Concept for content management desktop application
Time - 3 months
Location - San Diego, CA
UX Research and Design - Neil Ranada
Project type - Concept for content management desktop application
Time - 3 months
Location - San Diego, CA
People like to collect notes, images, and links. And there are some great finds that people can't wait to share with family and friends.
But sometimes you struggle to remember where you saved things. Did you scribble it on a post-it? Jot it in your notebook? Save it in your phone? Save it in your laptop?! You may end up feeling like Batman.
Kollect is a web application design that lets you easily manage your notes, images, and links all in one place.
People have a difficult time remembering where they saved notes, images, and links.
A web application where people can save content all in one place and access it anywhere.
I started my research with a survey posted online to various social media platforms and public forums. I needed to get a feel for what problems may exist if any. I asked questions focused on people’s past behaviors for saving and organizing items.
Most people don't have a problem saving things with whatever tool they are using.
However, despite the ease of saving items, people complained that their files eventually become disorganized and difficult to find and sort later.
I needed to dig deeper and move beyond a feeler survey. I began with an assumption: people need a website that allows them to easily save, share, and collaborate with content from any device.
I identified three people to interview and used them as models to create the User Personas. I focused on learning about their past experiences with saving and organizing things that interest them most.
Open PDF file for User Personas in another tabopen_in_new
Stephen is the primary persona and the focus for the design. Out of the three personas, meeting his goals and addressing his frustrations would also address the needs for the secondary and tertiary personas.
The User Personas have different interests for managing content: fitness, photography, and business.
I used these three goals as the focus for my design decisions.
I needed to learn from the design patterns of more popular web applications. I identified three: Evernote, Google Keep, and Ember.
I created matrixes such as the one below to assess the strengths, weaknesses, opportunities, and threats of each web application (SWOT analysis).
View analysis matrixes for other apps in another tabopen_in_new
After conducting user research and defining the problem, I was ready to move forward and create design solutions.
I created a spreadsheet with a list of tasks to meet the goals of the user personas.
New User:
Returning User:
Open Google Sheets for User Stories in another tabopen_in_new
I created User Flows to visually depict how people completed each task set out in the User Stories.
I created low-fidelity wireframes through Balsamiq.com to focus on the functionality of the web app.
I describe how I tested wireframes to solve for some of the user stories under the Testing section.
To create a brand name and logo design, I looked to well-known brands that I admire, such as Uniqlo, for inspiration. The common pattern that I saw with popular brands is that they use carefully selected typography and simple logos. The logos also scale well to smaller sizes but are still recognizable.
I went through some ideas for a brand name and logo.
I eventually settled on the name Kollect. I needed to be straight forward in communicating what people can do with the web application, which is to collect things. I carried the collection theme into designing the logo. I grouped small triangles using gestalt-ism to form a simple, clean, modern box that scales well to smaller sizes.
I used PT Serif for the body text and complemented it with Karla, a san serif typeface similar in structure to PT Serif, but with a softer style meant to draw the eyes to headers and buttons.
Lastly, I worked on color to finalize the style guide. I chose a light blue to give the app a light, fresh feel. I used the Adobe's Color Wheel to build a monochromatic palette.
With the style guide, I used Sketch app to create high fidelity mockups to give the design a realistic look and feel. I also used color contrast to reinforce the visual hierarchy on each page.
I tested often during every stage of the design process from low-fidelity wireframes to high-fidelity mockups and prototype.
I conducted four usability tests using wireframes. I used a combination of in-person and remote testing with family, friends, and strangers to solve for the various user stories.
For example, using the dashboard wireframe, I asked testers to add a note, image, or link.
Based on these observations, I removed the vertical side bar because it was too distracting. I also relocated the navigation links to the top horizontal menu bar. It was also clear that I needed higher fidelity wireframes and mockups to give people more context.
As a result, the settings link was relocated to the top right corner of the main menu for more visibility.
Here are changes applied from the lessons learned above to a higher fidelity version of the dashboard:
I conducted three usability tests. I used a high-fidelity prototype created with Sketch and InVision. I then posted it on UserTesting.com.
"Imagine you are looking for a new app to organize your notes, images, and links."
Press play above or watch video in another tabopen_in_new
Press play above or watch video in another tabopen_in_new
Press play above or watch video in another tabopen_in_new
Open Prototype and try out the usability tasks in the section above.open_in_new
I used InVision to create a prototype with mockups imported from Sketch app. You can open it in another tab and try the scenario and tasks found in the Usability Testing section above.
I was able to design a web application where people can easily sign up and add content.
It was pleasing to see how people during usability tests clicked outside of the modals to exit them. Unfortunately, they returned to the blank dashboard which is a limitation of the overlay feature in InVision. The "Back" button would have led them to the filled dashboard, but none of the testers used this option.
If I were to test that interaction pattern again, I would create mockups mimicking a modal overlay and set up touch zones around the box so that testers can transition to the filled version of the dashboard.
If given more time, I would have liked the opportunity to collaborate with other people that specialize in business, design, and development. Although I created a simple design that works, there are many perspectives from other areas of expertise that should be incorporated to build more value into Kollect.
Designing Kollect was enjoyable, and I hope to build more things that people find useful in the future.