<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
><channel><title>AJ McClary &#187; design</title> <atom:link href="http://www.ajmcclary.com/tags/design/feed" rel="self" type="application/rss+xml" /><link>http://www.ajmcclary.com</link> <description>Located in Washington DC/Northern Virginia</description> <lastBuildDate>Fri, 13 Jan 2012 01:12:27 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>WHY don’t people get it? It IS all about design!</title><link>http://www.ajmcclary.com/why-don%e2%80%99t-people-get-it-it-is-all-about-design.html</link> <comments>http://www.ajmcclary.com/why-don%e2%80%99t-people-get-it-it-is-all-about-design.html#comments</comments> <pubDate>Tue, 25 Oct 2011 15:30:43 +0000</pubDate> <dc:creator>A.J. McClary</dc:creator> <category><![CDATA[Web Design]]></category> <category><![CDATA[design]]></category><guid
isPermaLink="false">http://www.ajmcclary.com/?p=1286</guid> <description><![CDATA[Time and time again, I ask myself “why don&#8217;t people get it?” It really is all about design after all. So why doesn&#8217;t our industry reflect that. It has become abundantly clear, design rules. Design has become the determining factor on whether someone chooses to use a system or not. We all know that that [...]]]></description> <content:encoded><![CDATA[<p><a
href="http://cdn.ajmcclary.com/wp-content/uploads/2011/10/shutterstock_53306749.jpg"><img
class="alignright size-medium wp-image-1289" title="shutterstock_53306749" src="http://cdn.ajmcclary.com/wp-content/uploads/2011/10/shutterstock_53306749-300x210.jpg" alt="" width="300" height="210" /></a>Time and time again, I ask myself “why don&#8217;t people get it?”</p><p>It really is all about design after all. So why doesn&#8217;t our industry reflect that. It has become abundantly clear, <strong>design rules</strong>. Design has become the determining factor on whether someone chooses to use a system or not. We all know that that bad design is the number one factor for usability, user acceptance, and overall adoption.</p><p><strong>I know this firsthand:</strong> users are willing to except slow performance and system architecture issues because much of this they cannot see. While performance can be devastating to the over arching user experience of a website, the data indicates that if other factors are favorable, users are more than willing to wait-especially when there is a gratuitous payoff.</p><p>I&#8217;m not saying performance is not a usability issue-and I&#8217;m certainly not saying it&#8217;s not a huge user experience culprit-but system architects and engineers have a tendency to prioritize architectural issues over design issues.</p><p>I certainly believe we all have a place in system development. What I will not accept, however, is the omission of a great design feature that greatly improves the user experience, because the feature is not congruent with the established architecture. It&#8217;s almost 2012 people, we can do just about anything we put our mind to.</p><p>It&#8217;s time to begin to prioritize design with equal attention to architecture and engineering. The truth is we all have a place in the design of the system-but I know for a fact, and I know like I know like I know that: design rules nowadays.</p><p>Many people may argue that design is already prioritized in most development projects. If this is true, why is it that user experience designers are not the highest paid employees at companies-or at least the highest-paid contractors on development projects? In my experience user experience designers usually make less than six figures. Even worse, why is it the visual designers and web designers often make below $50K a year—when their responsible for an integral part of the customer experience? System architects, DBAs, and high-level system engineers can make significantly more than that. I&#8217;ve seen architects that make a quarter of $1 million a year and sometimes more.</p><p><strong>Can anyone give me a definitive answer on why designers don&#8217;t make as much as engineers?</strong> I would really like to know. In the fashion industry, for example, designers are the top paid employees. Just look at the greats like Tom Ford, Ralph Lauren, Tommy Hilfiger, and Versace.<strong> What can we do in the software industry to be more design progressive?</strong></p> ]]></content:encoded> <wfw:commentRss>http://www.ajmcclary.com/why-don%e2%80%99t-people-get-it-it-is-all-about-design.html/feed</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Armedia.com Blog: Software design is in crisis</title><link>http://www.ajmcclary.com/armedia-com-blog-software-design-is-in-crisis.html</link> <comments>http://www.ajmcclary.com/armedia-com-blog-software-design-is-in-crisis.html#comments</comments> <pubDate>Fri, 16 Jul 2010 00:51:11 +0000</pubDate> <dc:creator>A.J. McClary</dc:creator> <category><![CDATA[User Experience]]></category> <category><![CDATA[design]]></category> <category><![CDATA[software development]]></category><guid
isPermaLink="false">http://www.ajmcclary.com/?p=775</guid> <description><![CDATA[In the 90’s, when ECM solutions were rare, we could get away with designing solely toward requirements, but there is too much at stake nowadays. A recent study sampling various IT projects reported that: 62% percent of projects fail to meet their schedules 49% are over budget 47% have higher than expected maintenance costs And [...]]]></description> <content:encoded><![CDATA[<p>In the 90’s, when ECM solutions were rare, we could get away with designing solely toward requirements, but there is too much at stake nowadays. A recent study sampling various IT projects reported that:</p><ul><li>62%      percent of projects fail to meet their schedules</li><li>49% are      over budget</li><li>47% have      higher than expected maintenance costs</li><li>And      get this—<strong>25% are canceled</strong> before they are ever deployed!</li></ul><p>If you’ve been in the software industry long enough, you’ve probably seen all of these things happen. The funny thing is, it doesn’t really come down schedule, cost, or requirements—it comes from bad design. When software companies think design, they’re thinking about contractual obligations and meeting commitments with their stakeholders.</p><p><a
href="http://www.armedia.com/blog/2010/07/software-design-is-in-crisis/" target="_blank">Click HERE</a> to read the rest of the entry over at Armedia.com</p> ]]></content:encoded> <wfw:commentRss>http://www.ajmcclary.com/armedia-com-blog-software-design-is-in-crisis.html/feed</wfw:commentRss> <slash:comments>2</slash:comments> </item> </channel> </rss>
<!-- Served from: www.ajmcclary.com @ 2012-02-07 06:43:24 by W3 Total Cache -->
