This is a guest post by Ray Slater Berry, a freelance writer for Chameleon with over nine years of content marketing and social media experience. He specializes in product tech, travel, SaaS and working one time as a CMO at Study Clerk. Ray is also a published fiction writer, with his first novel titled Golden Boy.

“Every dollar invested in ease of use returns $10 to $100.” – IBM, The ROI of UX

The above statement was made by the global business powerhouse, IBM. The company explains that it’s far more economical to consider user needs early in the design process than to try and solve them later. Based on the returns given in the above quote, we can calculate an ROI of 9,900%.

And considering the user needs early is exactly what a user experience (UX) map does, meaning creating an effective UX map has the potential to bridge the gap between business success and failure.

By understanding your user’s needs in the early stages of a design process, you’re more likely to consistently meet those needs, meaning a happy customer and reduced churn.

This is why we at Process Street have produced this article, your practical guide to user experience mapping.

Welcome and gather around the user experience campfire. Grab a marshmallow on a stick, a cup of something hot, and relax. Today you’ll learn the ins of outs of user experience maps and how you can create one in the leanest way possible.

Click on the relevant subheader below to jump to your section of choice. Alternatively, scroll down to read all we have to say regarding user experience mapping.

• What are user experience maps?
• The benefits of UX mapping
• How do you create a UX map?
• Examples of user experience maps

Once upon a time, in a land not so far from here…
Continue Reading

Jonathan Bond is a Process Street Staff Product Designer, Star Wars fan, and human problem solver. Reach him on Twitter @jrbond.

The path you actually take in life is often wildly different from the one you thought you’d take. I spent years undertaking a fine arts degree. However, after I graduated, I wanted to get my hands metaphorically dirty (and literally cleaner — goodbye, paint!) by going into graphic design.

Initially, I bounced between various agencies doing what you’d expect any freelance graphic designer to do: logos and websites. While it was interesting and paid the bills, there was a new buzzword on the block in 2010 that sounded even more exciting: UX.

“A user interface is like a joke.
If you have to explain it, it’s not that good.”
– Martin LeBlanc, CEO

User experience (UX) design is focused on the individual thoughts about a product or service a person might have. It takes into consideration qualitative data like the user’s emotions and attitudes towards a product, as well as the more practical elements like ease of use, efficiency, and so on.

The more I read about UX design, the more I liked what I read. I felt it fit my own design philosophy; I just connected with it. This was something I wanted to be involved in.

As luck would have it, a company that wanted someone to improve their app’s aesthetic hired me to be involved with that. I still didn’t have a clue what I was doing, but I kept reading and studying, and ten years later, I’m still doing that – now at Process Street.

This post will cover:

• Product design at Process Street
• The details make the (UX) design
• You are not your user

Let’s begin!
Continue Reading

If you’re looking to rapidly grow your user-base by optimizing your product, simply signing up to Trello and Asana will give you a masterclass.

These two apps are optimized for virality because they work best when teams collaborate around them. Here’s how it’s done.

The whole point of project management apps is to give teams a central place to collaborate, update project status and store information. Trello and Asana aren’t particularly useful for individuals, so their product teams put extra effort into getting users to propagate the apps within their own organizations. No marketing required.

Continue Reading

Staring at the tiny LCD progress bar of the vending machine in a lobby, I realize nothing pisses us off more than indefinite waiting times. Especially people waiting for their coffee, their cheap flight comparisons, or their computer to finish doing whatever it’s doing.

Since the creation of software, there has always been loading times. An early example comes from Bob Stahl’s way-ahead-of-its time article in February 1986’s Computerworld.

Continue Reading