<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:atom="http://www.w3.org/2005/Atom">

    <channel>
    <atom:link href="http://elusive84.com/rss" rel="self" type="application/rss+xml" />
    
    <title>Elusive84 - Journal</title>
    <link>http://elusive84.com</link>
    <description>Elusive84 RSS Journal Feed</description>
    <dc:language>en</dc:language>
    <dc:creator>artboy5884@yahoo.com</dc:creator>
    <dc:rights>Copyright 2012</dc:rights>
    <dc:date>2012-01-03T03:16:53+00:00</dc:date>
    <admin:generatorAgent rdf:resource="http://expressionengine.com/" />
    

    <item>
      <title>Sports Car Club of America</title>
      <link>http://elusive84.com/journal/sports_car_club_of_america/</link>
      <guid>http://elusive84.com/journal/sports_car_club_of_america/#When:03:16:53Z</guid>
      <description><![CDATA[<p class="lead-paragraph">As a member of the Sports Car Club of America (SCCA), I visit the SCCA Washington DC Region’s <a href="http://wdcr-scca.org/">website</a> routinely for the latest news and events.</p>

<p>It’s a great place to find information on different types of automotive sports offered in the DC metropolitan area. Some of these automotive sports include Club Racing, Solo (Autocross), Time Trials, Road Rally and Rallycross.&nbsp; </p>

<p>The Washington DC Region’s website is not bad, but could be improved with a stronger focus on information architecture and visual hierarchy. The navigation, particularly needs a cogent sense of organization. The visual design is also heavily dated and would benefit from an update. In this case study I will attempt to improve this website by addressing a few of these issues.&nbsp; </p>

<h3>The Issues</h3>
<p>One issue I’ve always had with this website was the navigation. Sometimes looking for information across this site can be an enigma. There are no indicators that a link might take a user offsite or reveal a sub navigation. Many of the links could be combined to reduce confusion. For example, <em>About the Region</em> and <em>Region History</em> do not necessarily need to be two separate pages. These pages could be placed under a larger category clearly labeled <em>About Us.</em> </p>

<p>In addition to combining links, the different automotive genres should be separated or at least have greater hierarchy. This is important as it helps define the purpose of this homepage which is essentially showing the automotive sports offered in the DC metropolitan area. </p>

<p>The welcome/introduction statement is nice, but it’s value doesn’t warrant the amount of real-estate it’s currently occupying. This section could possibly be removed or demoted to a lower area on the page. Moreover, the “2011 Season Schedule” and “Upcoming Events Calendar” sections should be combined. The 2011 Season Schedule adds additional functionality to the event calendar, but it’s disjointed and carries the user to another page. </p>

<h3>The Redesign</h3>
<p>For my proposed solution, I wanted to add excitement and impact to the site. To do this I used photos taken by automotive enthusiast in the DC metro area. Some of the <a href="http://www.flickr.com/photos/jfotogimage/sets/72157620394183108/with/3673090085/">photographs</a> are extremely good and it would be a crime not to use them for the site. Once selecting an image to establish a tone, I turned my attention to restructuring the navigation. </p>

<p><a href="http://elusive84.com/images/uploads/scca-redesign-concept.jpg"><img src="http://elusive84.com/images/uploads/blog_thumbs/scca-screen2.png" alt="SCCA Redesign"  /></a></p>

<p>The navigation is simplified and split into two groups. The first group contains the usual utility items while the second contains the different automotive sports. An icon is used to represent each sport and is accompanied with text to explain the genre. By setting these items apart, the design has a stronger focus on directing the user to a specific place. The Event Calendar has also been tweaked and now includes a filter to list events by category. Users will no longer have to dig into the subpages to filter the event calendar. </p>

<p>As usual these case studies are merely a personal exercise and to perform a real redesign would require extensive research and information from the client.</p>]]></description> 
      <dc:date>2012-01-03T03:16:53+00:00</dc:date>
    </item>

    <item>
      <title>The Shotgun Method</title>
      <link>http://elusive84.com/journal/the_shotgun_method/</link>
      <guid>http://elusive84.com/journal/the_shotgun_method/#When:16:53:03Z</guid>
      <description><![CDATA[<p class="lead-paragraph">When first beginning my career in Web Design, I thought it was common place, or <em>best practice</em> to show multiple design concepts to a client. However, this often left me feeling frustrated as the designs would be Frankenstein’d into one, yielding less than stellar results.</p>

<p>It left me with work of which I wasn’t proud. There was something wrong with this method, but yet this practice is followed without question. In certain cases an extra design is thrown in simply for a “backup” to show the client’s money is hard at work. It wasn’t until I watched an episode of Andy Rutledge’s <a href="http://www.youtube.com/user/theandyrutledge/featured">Design Pro Show </a>that it became quite clear. This approach to designing is simply flawed and rooted in the lack of understanding the needs of the client.</p>

<p>Showing the client three designs or more is equivalent to blasting a target with a shotgun. Sure it gets the job done, but it’s sloppy, wasteful and leaves holes everywhere. As design professionals we are paid to come up with the <b>best</b> solution to a problem. This doesn’t mean a designer shouldn’t explore different options or directions, but that the design you present to a client is the best and only solution based on your professional experience. When we fail at understanding the client’s problem we enter the shotgun method in hopes that one design will hit the nail on the head. While wishful thinking, this is hardly ever the case and results in a compromised design.</p>

<p>In addition, we invite design decisions from clients who are not design professionals. By presenting multiple concepts we are essentially telling the client, “We are not sure which design solves your problem, but look at these options and tell us what works best.” From here the client may suggests mixing parts from one design to another which can drive a designer nuts. This is not the clients fault, but the lack of understanding on the designers end. </p>

<p>So you maybe wondering how do we solve the issue of the Shotgun Method? Well, it’s very simple: an effective discovery process, much like the process advocated by Andy Rutledge. By spending time with the client to fully understand their issues and concerns we can create a design that hits the mark 99% of the time. Moreover, having a solid discovery process helps the client build confidence in the designer. This removes any second guessing and creates a positive and professional relationship. Understanding the problem removes the need to present multiple concepts. Why use a scattergun when you need the accuracy of a long range rifle? Remember, we are the design professionals not our clients.</p>]]></description> 
      <dc:date>2011-12-21T16:53:03+00:00</dc:date>
    </item>

    <item>
      <title>The Design Process</title>
      <link>http://elusive84.com/journal/the_design_process/</link>
      <guid>http://elusive84.com/journal/the_design_process/#When:17:07:10Z</guid>
      <description><![CDATA[<p class="lead-paragraph">There are many things the automotive industry has right when it comes to design, particularly their start to finish process of automotive building.</p>

<p>It’s amazing to view the industries concept sketches and how they progress into three-dimensional icons which for Americans, like myself, can represent personal expression and freedom.</p>

<p>As a spectator of this design process, it’s quite clear to the engineers and potential consumers that each step is merely a representation. There are no expectations that the <a href="http://www.autoblog.com/photos/subaru-brz-sti-concept-0/#photo-4614623/">concept sketches</a> have to appear as the showroom car. Furthermore to expect a two-dimensional representation of a car to operate like a three-dimensional automobile is ludicrous. While this concept of thinking is solidified in the automotive industry it doesn’t appear to be exactly understood in the web design field. </p>

<p>There seems to be a notion in the web design industry that each step is lockdown and is unchanging throughout its process. This can be particularly true for large design teams that have specialized groups. Wireframes are locked down with areas that can not be altered. Visual comps are designed around “lorem ipsum” instead of real content and style sheets are created for comps that have yet to be developed. All the while, the client approves each step and is not informed or expecting significant alterations.&nbsp; None of these steps by themselves are a website. Therefore each step is subject to change and radically changed based on providing the BEST solution for a functional interactive website.</p>

<p>It is important that both design teams and clients understand this aspect of building websites. This is not print design.</p>]]></description> 
      <dc:date>2011-11-20T17:07:10+00:00</dc:date>
    </item>

    </channel>
</rss>
