{"id":14061,"date":"2016-06-09T06:00:44","date_gmt":"2016-06-09T13:00:44","guid":{"rendered":"https:\/\/www.uxpin.com\/studio\/?p=14061"},"modified":"2024-06-12T03:30:11","modified_gmt":"2024-06-12T10:30:11","slug":"the-redesigned-uxpin-is-here","status":"publish","type":"post","link":"https:\/\/www.uxpin.com\/studio\/uxpin\/the-redesigned-uxpin-is-here\/","title":{"rendered":"The Redesigned UXPin is Here"},"content":{"rendered":"

Today as we celebrate the release of our new version<\/a>, we want to take you behind the scenes and show you the lessons we learned while building it.<\/p>\n

The first thing we learned when embarking on a redesign was that it isn\u2019t enough that you use your product. You can\u2019t just eat your own dog food and leave it at that.<\/p>\n

As pointed out in <\/span>this Forbes article<\/span><\/a>, no one uses your product as much as you do, and not everyone is a power user as much as you. You can only know so much by using your product yourself. But if you only do that, you can become myopic in your approach. You have to seek outside perspective from your users.<\/span><\/p>\n

You have to talk to them and learn from them, while still eating your own dog food.<\/p>\n

That\u2019s precisely what we did with the UXPin redesign. We used UXPin to redesign UXPin, while at the same time spending hundreds of hours talking to our users.<\/p>\n

<\/div>\n

Before and after of the <\/span><\/i>UXPin<\/span><\/i><\/a> design editor. <\/span><\/i><\/p>\n

Learning From Previous User Experience <\/span><\/h2>\n

We didn\u2019t embark on our redesign on a lark. After all, the decision to do one should be based on data and feedback from users.<\/p>\n

As we said in the free e-book <\/span>The Guide to UX Design Process and Documentation<\/span><\/a>, you always need to know why you\u2019re building something. You have to do a bit of legwork and research, analyzing users. We won\u2019t get into creating user personas. If you\u2019re embarking on a redesign, you probably already know a lot about users\u2019 motivations, fears, mentality, and, of course, behavior.<\/span><\/p>\n

But it\u2019s the last bit that\u2019s going to be really useful to you. How do users behave in your application? What works for them? What doesn\u2019t? More importantly, do they have workarounds to accomplish what your product actually promises?<\/p>\n

For us, past usability tests and user feedback via customer service, as well as various \u201cengagement metrics\u201d were strongly suggesting that the learning curve is too steep for a design collaboration solution.<\/p>\n

Having the lowest learning curve is important to us because we\u2019re not only a tool for designers.<\/p>\n

\"image08\"<\/p>\n

A close up of the redesigned <\/span><\/i>UXPin<\/span><\/i><\/a> editor. <\/span><\/i><\/p>\n

For instance, Ingrid Brummer, a product manager at e-commerce site CHECK24, uses UXPin with her team because it allows her to fully articulate her ideas. As she told us, \u201cI really appreciate that with UXPin I, as a non-designer, am able to produce really exact designs.\u201d<\/p>\n

Since non-designers are also involved in the design process, we needed to lower the barrier to entry.<\/p>\n

With that knowledge, we dove back into our app, taking inventory of how we can create a better user experience across UXPin. OK, here\u2019s where things get a little meta. As we said before, we actually used UXPin to redesign UXPin. <\/span><\/p>\n

Why a Redesign? <\/span><\/h2>\n

Let us repeat again:<\/strong> a redesign isn\u2019t a lark.<\/span><\/p>\n

Learning from previous experience is the first part of that. Next, you have to decide why a redesign and set goals. <\/span><\/p>\n

A redesign starts very much by asking the same questions you would before embarking on any other design project, such as \u201cwhat is the purpose of this?\u201d \u201cWhat are our goals?\u201d \u201cHow does this affect our users?\u201d<\/span><\/p>\n

Certainly, users were at the heart of our decision to redesign. We wanted to create a smoother experience for them all around, making it easier to use UXPin and increase the speed of our platform. But to get to specifics, these were the factors that went into our decision: <\/span><\/p>\n