Ever wonder why so many project tools are designed with lists of data and text? Today, we have more complex projects and more people joining projects, and few have the time and the patience to learn how to use these tools made for the previous era...
Living in the woods among the trees have made it easy for me to miss the logical design, which is just make the darn create button large and center! It took me a few years, but I get it now. In our new upcoming version, we will add the big plus where it's meant to be.
In our previous Part 1 version of this blog, I introduced the 3 reasons why there is a gap between the total number of software solutions and tools and the number of those that have been well adopted (used daily). 3 reasons for the adoption death gap:
Any product's success can be determined by user adoption. If they don't use it, it wasn't successful. Enterprise software faces this challenge every day. Millions are spent on the software and configuration only later to find that people don't use them.
We all know the story how the QWERTY keyboard became a standard. As a refresher, it stuck because we already had many people already accustomed to the QWERTY typewriters, which were designed to avoid the metal keys from bunching up. What about enterprise or project software user design?
Ever since Web 2.0 products like Flickr, Twitter, etc. and new design approaches from Apple shook up the market, there has been a lot of buzz around the user experience. Notice I didn't say "UI design" since too many people correlate that with "flashy and colorful, yet missing intuitiveness and functionality". User experience is really much more broad.