Comments on: Surviving a Design: What to Consider When Launching Your Website http://blog.brazencareerist.com/2013/03/04/surviving-a-design-what-to-consider-when-launching-your-website/?utm_source=rss&utm_medium=rss&utm_campaign=surviving-a-design-what-to-consider-when-launching-your-website Personal development meets professional aspiration Tue, 05 Aug 2014 10:13:00 +0000 hourly 1 http://wordpress.org/?v=3.9.1 By: Karen J http://blog.brazencareerist.com/2013/03/04/surviving-a-design-what-to-consider-when-launching-your-website/comment-page-1/#comment-33751 Fri, 26 Apr 2013 14:42:00 +0000 http://blog.brazencareerist.com/?p=11544#comment-33751 “More likely than not, a majority of the functionality issues you notice
won’t be recognized by users simply because of your intimate
relationship with the process.”

- On the other side of the coin, there may be major functionality or UX issues that you *and your designer* don’t recognize, for the same reason – the intimate relationship with your goals, tech and process!

Always do a thorough beta-test with people who *don’t* have the latest technology and aren’t the most-informed about “what you do” and “how or why you do it” – the Buddhist concept of “beginner mind”. Remember that your “ideal user” is probably NOT your “average user” – and there are a lot more people in the average range than at the ideal end of the spectrum. Don’t forget the Assistants in your quest for the Executives.

]]> By: Brian Hildman http://blog.brazencareerist.com/2013/03/04/surviving-a-design-what-to-consider-when-launching-your-website/comment-page-1/#comment-32989 Wed, 13 Mar 2013 04:57:00 +0000 http://blog.brazencareerist.com/?p=11544#comment-32989 Something critical that wasn’t exactly pointed out was that the client is more likely than not, NOT the target user. So if you don’t like the website, it doesn’t mean your team is wrong, though it does mean there should be a conversation about why the decisions the designer made will ultimately be the best decisions for your shiny new product. User Experience > Your Experience (this goes for your design team as well, their opinion is not necessarily the opinion of your users!)

]]>