<?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>Rick Monro &#124; Designing the Middle</title>
	<atom:link href="http://blog.rickmonro.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.rickmonro.com</link>
	<description>A UI design journal. Mostly.</description>
	<lastBuildDate>Tue, 10 Apr 2012 21:57:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>A sense of completion</title>
		<link>http://blog.rickmonro.com/design/a-sense-of-completion/</link>
		<comments>http://blog.rickmonro.com/design/a-sense-of-completion/#comments</comments>
		<pubDate>Tue, 10 Apr 2012 21:51:24 +0000</pubDate>
		<dc:creator>Rick Monro</dc:creator>
				<category><![CDATA[An Imperfect Process]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[UX]]></category>

		<guid isPermaLink="false">http://blog.rickmonro.com/?p=543</guid>
		<description><![CDATA[Throughout a career primarily as a visual designer, I&#8217;ve always struggled with the judgement of when a piece of work is &#8220;done&#8221;. In graphic design, the urge to continue adding, embellishing is almost overwhelming. Maturity and of course experience influence better decision-making, but inevitably you find yourself mentally revisiting each project many times in the [...]]]></description>
			<content:encoded><![CDATA[<p>Throughout a career primarily as a visual designer, I&#8217;ve always struggled with the judgement of when a piece of work is &#8220;done&#8221;. In graphic design, the urge to continue adding, embellishing is almost overwhelming. Maturity and  of course experience influence better decision-making, but inevitably you find yourself mentally revisiting each project many times in the months after it&#8217;s supposedly &#8216;finished&#8217;, thinking of better choices you could have made, better directions you could have taken, better refinements you could have insisted on.</p>
<h4>The craftsman&#8217;s eye</h4>
<p>I often find myself looking at things that my dad made during his life, his joiner&#8217;s skills manifesting themselves in seemingly flawless dovetail joints and perfect angles, and outputs consistently fit for purpose.</p>
<h4>The end is not nigh</h4>
<p>Producing work that is deployed in a digital context brings with it a frustration, a yearning for a sense of completion where you know that something is simply <em>done</em>. This is something that has dogged me throughout my working life to date, whether I realised it or not. The quest for completion led me to acquire technical skills I never believed I would want or need, in what I now believe was the hope that they would bring me a clearer understanding of &#8220;finished&#8221;. </p>
<h4>In short: I&#8217;m older now</h4>
<p>What this drive for completion has meant for me is a quest for metrics, for data &#8211; measurable factors. In joinery, a glance through seasoned eyes can likely offer all the reassurance required to know it&#8217;s a job well done. Call it a search for meaning if you will, but moving deeper into UX thinking has brought me closer to the answer; knowing the right questions were asked, the right conclusions were reached and the right recommendations were made is as close as I believe I&#8217;m going to get. That sense of satisfaction is what drives me now &#8211; a far cry from the &#8220;cool&#8221; factor that motivated the younger me, an empty quest to mimic the latest ego-centric design trends.</p>
<h4>So…</h4>
<p>And yet, no matter what nostalgic gloss I might put on it, I am sure Dad would have been able to see in his work where improvements could have been made. It is both the blessing and the curse of the craftsman &#8211; the belief that the next project will be closer to elusive perfection that never comes.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.rickmonro.com/design/a-sense-of-completion/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Putting the spotlight on &#8216;delight&#8217;</title>
		<link>http://blog.rickmonro.com/design/putting-the-spotlight-on-delight/</link>
		<comments>http://blog.rickmonro.com/design/putting-the-spotlight-on-delight/#comments</comments>
		<pubDate>Sat, 17 Mar 2012 22:25:32 +0000</pubDate>
		<dc:creator>Rick Monro</dc:creator>
				<category><![CDATA[Community]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Process]]></category>

		<guid isPermaLink="false">http://blog.rickmonro.com/?p=540</guid>
		<description><![CDATA[Disclaimer: I tend to react adversely to industry buzzword memes. A new word has been gradually creeping into the design industry lexicon. Designers should now, apparently, design for &#8220;delight&#8221; &#8211; and once again a word has been introduced without context into the forefront of design debate. I&#8217;ve avoided &#8216;cool&#8217; for most of my professional career. [...]]]></description>
			<content:encoded><![CDATA[<p>Disclaimer: I tend to react adversely to industry buzzword memes.</p>
<p>A new word has been gradually creeping into the design industry lexicon. Designers should now, apparently, design for &#8220;delight&#8221; &#8211; and once again a word has been introduced without context into the forefront of design debate.</p>
<p>I&#8217;ve avoided &#8216;cool&#8217; for most of my professional career. I don&#8217;t do &#8216;awesome&#8217;. I don&#8217;t trust it. I don&#8217;t strive for it. But I like &#8216;effective&#8217;. <em>Effective</em> I can work with.</p>
<p>The most rational, level-headed thoughts on this come from CX Partners&#8217; Giles Colborne. <a href="http://www.slideshare.net/cxpartners/designing-for-delight-giles-colborne">The points Colborne makes</a> illustrate that we don&#8217;t really know what we&#8217;re saying. It&#8217;s all too easy to drop these phrases into discourse, but it&#8217;s quite another to try and measure or define it. And yet invariably a section of the design community, certainly within web design, will regurgitate this type of commentary and broadcast it without questioning what it actually means. </p>
<p>I don&#8217;t disagree with the sentiment; I agree fully that &#8216;delight&#8217; would be a.. um, delightful reaction for users of our work to have. But to impose this on an industry that strives for effective results appears to be imposing very shallow measures on a complex profession. If we&#8217;re going to propagate something meaningful, what about &#8220;design for success&#8221; &#8211; how&#8217;s that?</p>
<p>&#8220;Delight&#8221; is a meme and a millstone. It&#8217;s another way of saying that we should design something <em>cool</em>. But <em>cool</em> is not a commercial imperative, and it&#8217;s place in the process is undefinable. So, at what point should &#8216;delight&#8217; appear? Until definitions and metrics emerge I will continue to hold such opinion at arm&#8217;s length.</p>
<p>There is no magic ingredient for a successfully designed product. There is only process and effort. As with cool, &#8216;delight&#8217; will be a by-product of an effective outcome. </p>
<p>&#8216;Delight&#8217; happens, just as &#8216;cool&#8217; happens, most often through rigorous attention to detail and a rock solid understanding of user requirements.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.rickmonro.com/design/putting-the-spotlight-on-delight/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Reflections on Refresh</title>
		<link>http://blog.rickmonro.com/design/process/reflections-on-refresh/</link>
		<comments>http://blog.rickmonro.com/design/process/reflections-on-refresh/#comments</comments>
		<pubDate>Mon, 27 Feb 2012 08:20:22 +0000</pubDate>
		<dc:creator>Rick Monro</dc:creator>
				<category><![CDATA[Community]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[Responsive]]></category>
		<category><![CDATA[UI]]></category>

		<guid isPermaLink="false">http://blog.rickmonro.com/?p=525</guid>
		<description><![CDATA[…or how I learned to stop worrying and love the Responsive Summit. Apart from work itself, two industry events dominated last week for me. I was directly involved in one, but watched the other from afar with many others. As it transpired the two were not unrelated. On Monday evening I was fortunate enough to [...]]]></description>
			<content:encoded><![CDATA[<p><strong><em>…or how I learned to stop worrying and love the Responsive Summit.</em></strong></p>
<p>Apart from work itself, two industry events dominated last week for me. I was directly involved in one, but watched the other from afar with many others. As it transpired the two were not unrelated.</p>
<p>On Monday evening I was fortunate enough to co-host a session of <a href="http://www.refreshbelfast.org">RefreshBelfast</a> with none other than <a href="http://www.acejet170.com">Richard Weston</a> under the title &#8220;There&#8217;s more than one way to design a cat&#8221;. </p>
<p>We managed to shoehorn all manner of issues under that banner, the central theme being that the middle ground of the design industry is a pretty vibrant and rewarding place to practice. We sang the praises of teams and organisations (versus the notion of the rockstar individual designer), and addressed the idea that vehement opinions put forward on the web as truisms are nothing more than that: opinions.</p>
<p>It was an enjoyable evening and one that we hope lived up to the standards set by previous speakers, including <a href="http://adactio.com">Jeremy Keith</a>, <a href="http://www.thecreativityhub.com/">The Creativity Hub</a> and <a href="http://www.designbyfront.com/">Design by Front</a>.</p>
<p>Another key point Richard and I made was that no single point of view on techniques and processes is any more true than others simply because of how strongly the point is made, and  attempts to dictate best practice to the wider industry is wrong. Unfortunately, that was the perception of many of an event in London later in the week.</p>
<p>The <a href="http://responsivesummit.com/">Responsive Summit</a> &#8211; a tongue-in-cheek, self-aware moniker &#8211; riled a number of people on Twitter and beyond, apparently by bringing together a select group (&#8216;select&#8217; only in the sense that it was organised within a matter of days) to discuss the current hot topic of responsive design.</p>
<p>It is now almost two years since <a href="http://www.alistapart.com/articles/responsive-web-design/">Ethan&#8217;s original post</a>, yet RWD remains a grey area and continues to be difficult to implement on larger commercial projects. The idea behind Responsive Summit was nothing more sinister than trying to aggregate opinion on the challenges at hand and at least begin to plot a way forward. Knowing a couple of the personalities involved, I am confident that the aims of the session were true and will produce not diktats or imperatives, but something of practical benefit to our industry.</p>
<p>We need more honest and open discussion in this area. Early support for RWD was a touch <a href="http://blog.rickmonro.com/design/responsive-design-dont-stifle-debate-with-dogma/">absolutist in its fervour</a> and more honest documentation of the difficulties in implementing RWD as a solution on large scale commercial projects is required. I believe this pragmatic viewpoint was reflected in the discussions during the day.</p>
<p>It may be that this one event will inspire many others either directly, or as a reaction against an unfortunate perception of &#8216;elitism&#8217; surrounding it. Either way, this is what we need and positives will flow from it.</p>
<p>I am grateful for both of last week&#8217;s events, in different ways. Thank you to everyone involved.</p>
<p>&#8212;&#8211;</p>
<p><em>For more information on the background to Responsive Summit, see <a href="http://storify.com/Armstrong/how-responsive-summit-was-concieved">Chris Armstrong&#8217;s candid summary</a> of the build up to the event on Storify.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.rickmonro.com/design/process/reflections-on-refresh/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Rockstars, preachers or craftsmen. Time to choose.</title>
		<link>http://blog.rickmonro.com/design/rockstars-preachers-craftsmen/</link>
		<comments>http://blog.rickmonro.com/design/rockstars-preachers-craftsmen/#comments</comments>
		<pubDate>Mon, 26 Sep 2011 20:36:21 +0000</pubDate>
		<dc:creator>Rick Monro</dc:creator>
				<category><![CDATA[Community]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[UI]]></category>
		<category><![CDATA[UX]]></category>

		<guid isPermaLink="false">http://blog.rickmonro.com/?p=505</guid>
		<description><![CDATA[My father was a joiner, serving his apprenticeship in the Harland &#38; Wolff shipyard in Belfast. He took a simple pride in his work, going on to develop his skills in a number of construction firms across the city. I don&#8217;t believe he would have labelled himself a &#8220;craftsman&#8221; and I am confident that, while [...]]]></description>
			<content:encoded><![CDATA[<p>My father was a joiner, serving his apprenticeship in the Harland &amp; Wolff shipyard in Belfast. He took a simple pride in his work, going on to develop his skills in a number of construction firms across the city. I don&#8217;t believe he would have labelled himself a &#8220;craftsman&#8221; and I am confident that, while knowing no project he worked on would be complete without his contribution, he had a balanced sense of where that contribution sat in the greater scheme of things. We are fortunate to still have a couple of pieces of furniture that Dad made over the years as labours-of-love. They are simple, usable items.</p>
<h4>Intense introspective</h4>
<p>When I first read <a href="http://jontangerine.com/log/2011/09/we-who-are-web-designers">this recent blog post by Jon Tan</a> it resonated hugely. His thoughtful appreciation of our industry is a heartening summary of how quickly things have changed and improved. On reflection though, should we subject ourselves to so much soul-searching based on moments of awkwardness in social situations? Should it matter what others&#8217; perception of us is?</p>
<p>The drive towards a craft-based approach to design for the web continues to gain momentum, something worth fostering. Craft implies care, thoroughness. If we are to be craftsmen, we also need to accept that dedicated craftsmanship is often carried out in relative anonymity. Our contributions, if they are effective, will go unnoticed by most. Intuitive usability implies a lack of conscious effort on the part of the end user which, in turn, suggests a lack of acknowledgement on the part of the user.</p>
<p>My Dad ended his working life as a Clerk of Works. You may not be familiar with that role. I don&#8217;t believe Dad would have minded and would quite happily have explained his job to anyone. As our profession matures and we struggle with perceptions and interpretations of what we do, we should prepare for nothing but a muted response from those outside the industry or elsewhere in the design community.</p>
<p>We do great things, but they are not made any greater or lesser by how others perceive them.</p>
<h4>You&#8217;re either with us or you&#8217;re against us</h4>
<p>Elsewhere on the web, others appear keen to let us know exactly what defines us.</p>
<p>During his years in trade, Dad came into contact with engineers, architects and tradesmen of all kinds. He took an interest in them and how they contributed to projects. It informed his own work. To the best of my knowledge he never took it upon himself to accuse others of not being genuine joiners. As in all professions, he knew there are two types of practitioners: those who are effective, and those who are not.</p>
<p>I have written before of being proud to work in a profession that places effective practice over showboating. However there has been a trend of late for showy pronouncements suggesting what designers are or are not, depending on their approach. For example:</p>
<p><a href="http://forabeautifulweb.com/blog/about/i_dont_care_about_responsive_web_design">&#8220;…you&#8217;re not a web designer, you&#8217;re something else.&#8221;</a></p>
<p><a href="http://whitneyhess.com/blog/2011/04/23/youre-not-a-user-experience-designer-if/">&#8220;You’re not a user experience designer if…&#8221;</a></p>
<p><a href="http://andyrutledge.com/web-design-is-product-design.php">&#8220;A designer who does not write markup and css is not designing for the web, but drawing pictures.&#8221;</a></p>
<p>The defense for statements of this nature tends to be that they are intended to &#8220;provoke debate&#8221; or similar. I really wonder. Because sometimes, just sometimes, the intention appears to be to create divisions in our field where there are none; to create a &#8216;them and us&#8217; based on approach and technique, rather than effectiveness of output.</p>
<p>A situation where a relatively small number of (I should state &#8211; exceptional) professionals, with the biggest platforms, who shout loudest feel empowered to define what we should or should not be is one that I&#8217;ll call unhelpful. Producing great work sets the best possible example to others in the profession. Sharing of the process gives something back to the community. Does proselytising really add any more value?</p>
<h4>Future proof</h4>
<p>We want to attract the best possible calibre of people into our industry. A clear sense of ourselves and what we contribute as UI and UX designers is crucial to that effort. Promotion of best practice, which is always changing, is a positive. There are suitable ways and means to do this. I suggest that haranguing those with a different perspective is not one of them.</p>
<p>Reading much of our internal debate of late, I cannot help but hear Dad&#8217;s voice and what he said to me in so many situations over the years:</p>
<p><em>&#8220;Just get on with it, son&#8221;.</em></p>
<p>I commend this sentiment to the industry.</p>
<p>&#8212;&#8212;</p>
<p><em>Update: Following some particularly gracious feedback from Jon Tan, whose <a href="http://jontangerine.com/log/2011/09/we-who-are-web-designers">blog post</a> is referenced here, I have edited the text of this piece to more accurately establish sources and targets for a number of points made. Thanks to Jon for his input. <a title="Original post" href="http://wp.me/p1KV6f-7Q/">The original post has been retained for reference.</a></em></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.rickmonro.com/design/rockstars-preachers-craftsmen/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Words fail us.</title>
		<link>http://blog.rickmonro.com/design/words-fail-us/</link>
		<comments>http://blog.rickmonro.com/design/words-fail-us/#comments</comments>
		<pubDate>Tue, 13 Sep 2011 20:36:02 +0000</pubDate>
		<dc:creator>Rick Monro</dc:creator>
				<category><![CDATA[Community]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Writing]]></category>

		<guid isPermaLink="false">http://blog.rickmonro.com/?p=208</guid>
		<description><![CDATA[A recent exchange on Twitter, started by this tweet from Andy McMillan, brought attention to the use of self-deprecating terms by designers that may contribute to an overall lack of respect for &#8211; or awareness of &#8211; the discipline of web design. Andy also questioned what the responsibility of the design community should be in overcoming misconceptions. [...]]]></description>
			<content:encoded><![CDATA[<p>A recent exchange on Twitter, started by this tweet from <a title="goodonpaper" href="http://twitter.com/goodonpaper">Andy McMillan</a>, brought attention to the use of self-deprecating terms by designers that may contribute to an overall lack of respect for &#8211; or awareness of &#8211; the discipline of web design. Andy also questioned what the responsibility of the design community should be in overcoming misconceptions.</p>
<p>I believe our industry dialogue has shortcomings that go beyond self insulting slang. How we choose to discuss our work amongst ourselves and how we communicate outwardly is directly linked to the fundamental credibility of our industry. And yet modern design discourse cannot manage to get much past &#8220;cool!&#8221; or &#8220;awesome!&#8221;.</p>
<p>Reading a blog post by a practitioner of say, the legal industry which began &#8220;Being a solicitor totally kicks butt!!&#8221; might reasonably lead you to think that something so crass reflects badly on the writer and, if it was a widely read site or journal, on the profession itself. But a recent design-related blog post I came across began precisely that way (substitute &#8220;designer&#8221; for &#8220;solicitor&#8221;). Names withheld to protect the innocent.</p>
<p>Our deficiency in apposite language is not always so overt. We have all seen design agency homepages that proudly pronounce something along the lines of: &#8220;We design cool web stuff for awesome clients&#8221;. Reading this you simply have to wonder &#8211; who is the target audience Vocabulary in the design world has become a series of memes. Phrases like &#8220;We&#8217;re passionate about creating awesome online experiences&#8221; suggest everything and nothing.</p>
<p>Try Googling the phrase &#8220;We&#8217;re passionate about design&#8221; and look at the number of results returned, or <a href="http://tinyurl.com/6f2376l">let me do it for you</a>. Apologies if you find yourself in there. I don&#8217;t doubt for a second that each of those companies and individuals truly believe in what they are saying. However, if they also believed that making this statement created some kind of differentiator in the marketplace, they were clearly and painfully wrong.</p>
<p>Professional design bodies around the world, such as the very vibrant <a href="http://www.gdc.net/">GDC</a> in Canada or <a href="http://www.aiga.org/">AIGA</a> in the US, work extremely hard to bring credibility to the design profession by lobbying business and industry on the benefits of design supplied by accredited, licensed professionals. We rail against the idea of organisations producing substandard design work in-house, or roll our eyes when we hear that the boss&#8217;s nephew produced the company&#8217;s website because he had a copy of Dreamweaver.</p>
<p>And yet too many designers and design agencies insist on prioritising credibility with their peers over professional communication by adopting a witless &#8220;aren&#8217;t we cool?&#8221; approach to how they discuss and present their work. Do we really believe that clients are attracted to us by lambasting them with how &#8220;cool&#8221; or &#8220;awesome&#8221; we are?</p>
<p>The arrival of <a href="http://www.alwaysreadthemanual.com/">The Manual</a> may represent a watershed, and the publication has <a title="kickstarter" href="http://www.kickstarter.com/projects/goodonpaper/the-manual">very clearly set out its stall</a> in terms of what it hopes to achieve. Similarly, <a title="naconf" href="http://www.newadventuresconf.com/">New Adventures in Web Design</a> has fired up debate of a nature that simply had not existed before. We should applaud these earnest efforts to usher in a new era of industry communication and hope they bear fruit. Further to that, the rest of us should make a contribution and start introducing maturity to the &#8211; at times &#8211; adolescent lexicon of design discourse, be it in our industry publications, on our blogs… even on Twitter. Or is that asking too much?</p>
<p>When we can communicate as accomplished and eloquent professionals, between ourselves as well as beyond our industry, then perhaps the boss&#8217;s nephew won&#8217;t get so much work.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.rickmonro.com/design/words-fail-us/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>In other news, perfection remains elusive</title>
		<link>http://blog.rickmonro.com/design/elusive-perfection/</link>
		<comments>http://blog.rickmonro.com/design/elusive-perfection/#comments</comments>
		<pubDate>Sun, 04 Sep 2011 22:03:45 +0000</pubDate>
		<dc:creator>Rick Monro</dc:creator>
				<category><![CDATA[An Imperfect Process]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://blog.rickmonro.com/?p=470</guid>
		<description><![CDATA[Here is a hypothetical scenario which may or may not sound familiar to you: A project has progressed to the visual design stage. The process you followed fell somewhat short of textbook. Deadlines are imminent. The first iteration of a rendered design has gone to a client with various caveats:- that feedback is welcomed, that [...]]]></description>
			<content:encoded><![CDATA[<p>Here is a hypothetical scenario which may or may not sound familiar to you: A project has progressed to the visual design stage. The process you followed fell somewhat short of textbook. Deadlines are imminent. The first iteration of a rendered design has gone to a client with various caveats:- that feedback is welcomed, that various aspects need to be reviewed, that the design can be progressed based on further discussion, etc. Then the word comes back:</p>
<p><strong>&#8220;Looks fine. We&#8217;ll go with that&#8221;.</strong></p>
<p>The question is: have you failed or succeeded?</p>
<h4>Blind vision</h4>
<p>As a professional you are almost certainly torn. You want to work towards the best possible result, ensuring the project is effective and represents something both you and the client can be proud for years to come. The craftsman in you wants to hone and improve. You had anticipated further debate, leading to the next iteration. Instead what you appear to have is approval. And the commercial imperative suggests that the time for iteration is past; the client has accepted your work and the process must move on.</p>
<h4>The long wait</h4>
<p>I suspect these are familiar dilemmas for design professionals. We hear much about the &#8216;perfect process&#8217; in our industry writing and conferences. Professionalism calls for improvement; often arduous, incremental, glacial improvement that may only be measured in years rather than months. But it is a truism that perfection never arrives.</p>
<h4>Reality slap</h4>
<p>To remain commercially viable, relentless quests for perfection may have to be set aside for another day. Not, let&#8217;s be clear, abandoned completely: defeatism is the path to template-driven mundanity. Without question we should all aspire to better. However the harsh truth is &#8211; and you may want to brace yourself &#8211; compromise is a fact, in life and in business. Another element of professionalism is the maturity to accept that fact, while knowing that you are still a credible member of the design community <em>despite</em> falling short of perfection.</p>
<h4>Conclusion</h4>
<p>The lesson from a scenario such as this is almost certainly that we should not present anything to a client that we are not prepared to stand by 100%, or indeed go live with. It can be all too easy to sleepwalk your way to a design that doesn&#8217;t represent you or the client particularly well. #speakingfromexperience</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.rickmonro.com/design/elusive-perfection/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Small viewports&#8230; and the death of the fold</title>
		<link>http://blog.rickmonro.com/web/death-of-the-fold/</link>
		<comments>http://blog.rickmonro.com/web/death-of-the-fold/#comments</comments>
		<pubDate>Thu, 11 Aug 2011 07:13:13 +0000</pubDate>
		<dc:creator>Rick Monro</dc:creator>
				<category><![CDATA[Process]]></category>
		<category><![CDATA[Responsive]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://blog.rickmonro.com/?p=454</guid>
		<description><![CDATA[Like all the best/worst B-movies, the bad guy you thought was dead and gone has summoned up his last ounce of strength for one last attack. The Fold is back. With a twist. A short debate The debate about whether a &#8216;fold&#8217; exists on the web begins and ends with the following assertions: yes, content [...]]]></description>
			<content:encoded><![CDATA[<p>Like all the best/worst B-movies, the bad guy you thought was dead and gone has summoned up his last ounce of strength for one last attack. The Fold is back. With a twist.</p>
<h4>A short debate</h4>
<p>The debate about whether a &#8216;fold&#8217; exists on the web begins and ends with the following assertions: <strong><em>yes</em></strong>, content goes off-screen in the majority of websites and <strong>yes</strong><em></em>, users are willing to scroll to read it. Period. Note that the second point doesn&#8217;t dispense with the need for clients and designers to assign priorities within content and for the designer to create a visual hierarchy based on these priorities. These are crucial conversations in any project. And this is the very area where things are going to get interesting.</p>
<h4>Top of the (content) pops</h4>
<p>The current mobilisation towards responsive design is laudable, and a great many people are currently wrestling the theory towards best practice. Despite what may be pronounced from various sources across the web, it is not a one-size-fits-all solution for myriad viewport sizes. What we will likely emerge with is a toolbox of approaches for use in a variety of contexts, of which responsive design will be just one. But what &#8216;responsive&#8217; highlights very effectively, in a way that designing for desktop does not, is the relative priority of content as the viewport shrinks.</p>
<h4>Top=good, bottom=bad</h4>
<p>Laying out web content for a desktop PC or laptop provides plenty of screen real estate to play with. We can cheat the hierarchy by placing something somewhere else in a vast 960 x [whatever] pixel canvas and create visual priorities through the use of colour, space etc. We can design within grids and columns that allow pretty much everything to get a look in. Whatever sits further down the page is somewhat <em>less</em> important and everything that sits towards the top of the page is <em>more</em> important. But this is far from the absolute scale that we are going to need.</p>
<h4>Extreme content. Dude.</h4>
<p>For a responsive approach we need to decide on <strong>absolute</strong> priority, not a vague, general hierarchy. A glance at any of the new breed of responsive sites on a mobile device tells you one thing: the content has a no-nonsense, top-to-bottom hierarchy. This kind of <em>extreme</em> prioritisation is going to form part of the new normal in designing for the web. The conversations right at the outset of the design process will need to address this. &#8220;<em>If the user could only see one part of the site, what would it be?</em>&#8221; is as basic a question as can be asked but it has tremendous resonance now.</p>
<h4>All change</h4>
<p>Further, if we are now giving something lowest priority and it will require a significant amount of swiping or scrolling to get to… is it really required at all? And if that element is removed, what about the content which is <em>now</em> at the bottom? These issues have massive potential to skew how we assess content and it is barely credible that the now &#8216;traditional&#8217; website we have grown so accustomed to will not be affected by these shifts.</p>
<h4>It&#8217;s what thumbs are for</h4>
<p>And what of the fold? The old arguments used to go that if the fold existed, everything needed to be forced into the area above it for fear of users missing it. By the same logic, on a 320 x 480 viewport the user is going to miss&#8230; pretty much <em>everything</em>. The same logic would also suggest that those users won&#8217;t know to swipe to see more. Except we know that they will.</p>
<h4>Web origami</h4>
<p>The fact is there is no longer even a single fold. On a small device there are multiple folds, multiple screens to scroll through. But bizarrely the more folds exist the less they matter. Users now <em>expect</em> to swipe and to scroll. So sleep easy and let it be known: the fold is dead.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.rickmonro.com/web/death-of-the-fold/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Design like an expert. Don&#8217;t communicate like one.</title>
		<link>http://blog.rickmonro.com/design/expert-communication/</link>
		<comments>http://blog.rickmonro.com/design/expert-communication/#comments</comments>
		<pubDate>Tue, 02 Aug 2011 20:47:21 +0000</pubDate>
		<dc:creator>Rick Monro</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Simplicity]]></category>
		<category><![CDATA[UI]]></category>
		<category><![CDATA[Writing]]></category>

		<guid isPermaLink="false">http://blog.rickmonro.com/?p=427</guid>
		<description><![CDATA[Networking between designers is not the rarity it used to be. The web, and more specifically Web 2.0, has brought the design community together through conferences, unconventions and good old informal meet-ups. By and large though our professional communications take place with two other main groups: clients and end users. So it&#8217;s worth considering how [...]]]></description>
			<content:encoded><![CDATA[<p>Networking between designers is not the rarity it used to be. The web, and more specifically Web 2.0, has brought the design community together through conferences, unconventions and good old informal meet-ups. By and large though our professional communications take place with two other main groups: clients and end users. So it&#8217;s worth considering how we handle those conversations. Hold that thought.</p>
<h4>Culverts? Cool.</h4>
<p>The July selection for UX Bookclub Belfast was &#8216;How to Use Your Eyes&#8217; by academic James Elkins. Each chapter delivers a brief but compelling insight into the expertise of others. By deconstructing amongst other things a culvert, an oil painting and the Periodic Table, the book reveals hidden mechanics and meanings, inspiring admiration for those whose contributions you might not otherwise consider.</p>
<h4>Designers are experts too!</h4>
<p>Had there been a chapter devoted to the makeup of a graphic user interface or how a web browser renders HTML no doubt most of us could have produced something that would draw similar admiring gasps from readers. But before we descend into a round of &#8220;woohoo!&#8221;s, &#8220;awright!&#8221;s and high fives, let&#8217;s remember that expertise is (or should be) the minimum price of entry to the Service Industry Club. The question to consider is: how do we communicate our knowledge?</p>
<h4>It just works</h4>
<p>Throughout the day almost everything we interact with or consume is the product of others&#8217; technical mastery and this input is largely invisible, allowing us to go about our day without giving a second thought to theory, systems or manufacturing processes. Similarly when we consult with experts outside of work, be it a doctor or a car mechanic, we appreciate it when they frame any potential problems in simple terms.</p>
<h4>Dumbing up</h4>
<p>In UI design, and I&#8217;d suggest every other design discipline, expertise should manifest itself in simplicity. Certainly the science we incorporate into what we produce should be invisible to a non-expert. Further to this, we should be able to communicate our expertise and remain easily understood. Too often we are tripping over ourselves to <em>prove</em> our competence rather than communicate it effectively. Our ability blinds us. We should not berate the client for, as designers are so fond of saying, &#8220;not getting it&#8221;. Others do not see as we do.</p>
<h4>Conclusion</h4>
<p>So perhaps the truest test of our expertise is how simply it can be shared. When we discuss a project&#8217;s challenges with the client and more importantly what the solutions are, keep it simple. And sound like a true expert.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.rickmonro.com/design/expert-communication/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Late nights, passion and the creativity myth</title>
		<link>http://blog.rickmonro.com/design/late-night-passion/</link>
		<comments>http://blog.rickmonro.com/design/late-night-passion/#comments</comments>
		<pubDate>Mon, 18 Jul 2011 06:30:33 +0000</pubDate>
		<dc:creator>Rick Monro</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[Process]]></category>

		<guid isPermaLink="false">http://blog.rickmonro.com/?p=371</guid>
		<description><![CDATA[My first professional job was in a small advertising agency. Despite knowing many fine people there who have gone on to great careers elsewhere, for a graduate designer it was, put simply, a sweatshop. Working there taught me two important things: 1) I had to get out of advertising as soon as I could 2) [...]]]></description>
			<content:encoded><![CDATA[<p>My first professional job was in a small advertising agency. Despite knowing many fine people there who have gone on to great careers elsewhere, for a graduate designer it was, put simply, a sweatshop.</p>
<p>Working there taught me two important things:</p>
<p>1) I had to get out of advertising as soon as I could<br />
2) Routinely working long hours reduces quality, productivity and creativity</p>
<p>During my time there I was involved in numerous pitches for advertising accounts that were poorly planned and executed, more often than not resulting in failure. Each had another common characteristic: a reliance on working late into the night.</p>
<p>Time would invariably be wasted on various approaches with no structure or purpose until with little time left, the Creative Director would pipe up dramatically &#8220;I&#8217;ve got it!&#8221;. We&#8217;d then throw the kitchen sink at it, working excessively late or over the weekend as though it were proof of creativity and commitment. It wasn&#8217;t. It was proof of poor planning and a lack of creativity.</p>
<p>I don&#8217;t mean to generalise; of course like all aspects of design, well practiced advertising has its best practice processes and systems. Similarly working late to finish a project based on agreed milestones and deadlines goes with the territory.</p>
<p>However when company culture relies on sapping the energies of junior staff members in the name of creativity then there is a problem. The agency I cut my teeth with was all about the creativity myth. The myth that says if you work late enough and throw enough time at it, great creativity will simply happen.</p>
<p>An over-reliance on &#8220;passion&#8221; in the marketing lexicon of design agencies further fuels the fallacy. Regardless of the intent, what something like &#8220;we&#8217;re passionate about design&#8221; says at best is that &#8220;we will work long into the night for you&#8221;. As a client I don&#8217;t think I would care how much of a flurry you whip up due to your passion, or how many all-nighters you are prepared to pull. It&#8217;s results that count. To <a href="http://cognition.happycog.com/article/whats-the-roi-on-cool">paraphrase Joe Rinaldo</a>, what&#8217;s the ROI on passion?</p>
<p>Time and again it has been proved that effective results come from careful planning, iteration and craft. Otherwise known as professionalism. Yes, you can work round the clock on a labour of love. We all do it. Can you do it on a number of projects in a row? Yes, you can. Can you sustain that pace and a reliance on late hours over a number of years, over a career? You can if you are prepared to have nothing else of value in your life.</p>
<p>Waiting for the creative director&#8217;s faux inspiration wasn&#8217;t for me. Despite being completely new to the workplace, I could see that it was an ineffective way of working. Although I didn&#8217;t know it at the time I was crying out for process, order and sanity.</p>
<p>Happily UI design provides just that, and I am proud to be working now in a discipline that increasingly values a systematic process over flamboyant showboating.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.rickmonro.com/design/late-night-passion/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>I&#8217;m a designer. What do I know?</title>
		<link>http://blog.rickmonro.com/design/im-a-designer-what-do-i-know/</link>
		<comments>http://blog.rickmonro.com/design/im-a-designer-what-do-i-know/#comments</comments>
		<pubDate>Tue, 05 Jul 2011 09:45:57 +0000</pubDate>
		<dc:creator>Rick Monro</dc:creator>
				<category><![CDATA[Books]]></category>
		<category><![CDATA[Design]]></category>

		<guid isPermaLink="false">http://blog.rickmonro.com/?p=343</guid>
		<description><![CDATA[From time to time something comes along to give you a gentle nudge, prompting you to reassess your knowledge as a professional. Such an occasion came last month in the form of the ever-enjoyable UX Bookclub Belfast. People are liars (apparently) The book being discussed was &#8220;100 Things Designers Should Know About People&#8221; by Susan [...]]]></description>
			<content:encoded><![CDATA[<p>From time to time something comes along to give you a gentle nudge, prompting you to reassess your knowledge as a professional. Such an occasion came last month in the form of the ever-enjoyable <a href="http://uxbelfast.tumblr.com/">UX Bookclub Belfast</a>.</p>
<h4>People are liars (apparently)</h4>
<p>The book being discussed was &#8220;<a href="http://www.amazon.co.uk/Things-Every-Designer-Needs-People/dp/0321767535/">100 Things Designers Should Know About People</a>&#8221; by Susan Weinschenk. Compiled from a series of <a href="http://www.whatmakesthemclick.net/blog/">blog posts</a>, &#8220;100 Things&#8230;&#8221; features some eyebrow-raising revelations on the apparent true needs of users, versus what people <em>say</em> they want. The book prompted a number of comments along the lines of &#8220;I&#8217;m a designer. I knew a lot of this stuff already&#8230; but I&#8217;m not sure how.&#8221;</p>
<h4>Is there a designer in the house?</h4>
<p>Professional practice in any number of design disciplines, graphic and UI among them, is not <em>absolute</em>, differentiating them from law, medicine or accounting for example. However design should not be subjective. The weakest possible position a designer can adopt in communicating with a client is a &#8220;just trust me, I know best&#8221; stance. Any sense of the designer-as-artist can result in needless, subjective discussions. In other words, either have a good reason for deploying a particular colour or prepare for a discussion over who&#8217;s favourite colour is best.</p>
<h4>The appliance of science</h4>
<p>One of the many positive developments to have occurred during my time as a professional is the proliferation of scientific thinking in the industry. The influence and contributions of thought leaders such as <a href="http://www.jnd.org/">Donald Norman</a>, <a href="http://en.wikipedia.org/wiki/Alan_Cooper">Alan Cooper</a> and others cannot be overstated; what they have brought to the table is a shift in rationale from the old, instinctive design sensibility to a more effective, quasi-scientific approach. So we have gone from arguing that a button with rounded corners simply &#8220;looks right&#8221; (instinctive) to stating that it has <a href="http://en.wikipedia.org/wiki/Affordance">affordance</a> and benefits from the <a href="http://www.jnd.org/dn.mss/emotion_design_attractive_things_work_better.html">Aesthetic-Usability Effect</a> (scientific). What&#8217;s more, data supports the fact that <a href="http://www.alistapart.com/articles/indefenseofeyecandy/">attractive things work better</a>.</p>
<h4>That&#8217;s&#8230; logical, captain</h4>
<p>Without question this type of approach demands more from the designer: craft, study, insight. It can also supply some much-needed constraints within which creativity can flourish, rather than relying on the artist&#8217;s muse. Arguing a point based on data and evidence is less likely to result in needless exchanges with a client over the amount of [insert client's favourite colour here]. That&#8217;s not to say it will never happen, but our position as professionals is strengthened when we can actively demonstrate a thorough knowledge of the rules of the game.</p>
<h4>Reboot</h4>
<p>We might assume to &#8220;know&#8221; so much gained from experience or absorbed from years of industry-related reading but regular reassessment of what we assume to be firm knowledge can only be healthy. Plus it is much more conducive to a sustained and successful career in design. Taking the opportunity has never been easier, with the web as a central hub for debates and discussions that lead to shifts in our industry and each of us with a front row seat.</p>
<h4>Cliché, okay</h4>
<p>Hackneyed it may be, but designers cannot afford to stop learning about the components of professional practice, particularly those of us who have had extended tenures in the field. Old thinking needs to be identified and regularly weeded out. We need to challenge accepted truths time and again, reassess our own subjective views and progress our work and contribution.</p>
<h4>Gratuitous Star Wars quote</h4>
<p>To paraphrase Yoda, <a href="http://mnmal.org/post/1029963881/you-must-unlearn-what-you-have-learned-yoda">we need to unlearn what we have learned</a> &#8211; and then relearn it, sometimes daily.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.rickmonro.com/design/im-a-designer-what-do-i-know/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

