﻿<?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>Adrian Short &#187; Design theory</title>
	<atom:link href="http://adrianshort.co.uk/category/design-theory/feed/" rel="self" type="application/rss+xml" />
	<link>http://adrianshort.co.uk</link>
	<description>Design, citizenship and the city</description>
	<lastBuildDate>Thu, 08 Jul 2010 12:05:42 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Digital simulacra and the iPad human interface guidelines</title>
		<link>http://adrianshort.co.uk/2010/06/17/digital-simulacra-and-the-ipad-human-interface-guidelines/</link>
		<comments>http://adrianshort.co.uk/2010/06/17/digital-simulacra-and-the-ipad-human-interface-guidelines/#comments</comments>
		<pubDate>Thu, 17 Jun 2010 14:56:55 +0000</pubDate>
		<dc:creator>Adrian Short</dc:creator>
				<category><![CDATA[Design theory]]></category>
		<category><![CDATA[Product design]]></category>
		<category><![CDATA[Software design]]></category>
		<category><![CDATA[iPad]]></category>
		<category><![CDATA[Windows Phone 7]]></category>

		<guid isPermaLink="false">http://adrianshort.co.uk/?p=603</guid>
		<description><![CDATA[This was originally posted as a comment to an article in UX Magazine about the iPad human interface guidelines. I was reminded by it today by this blogpost by Ben.geek.nz about the forthcoming Windows Phone 7 UI design. While I haven&#8217;t seen a WP7 in the flesh it looks as if it may come closer [...]]]></description>
			<content:encoded><![CDATA[<p><em>This was originally posted as a comment to </em><a href="http://www.uxmag.com/design/ipad-user-experience-guidelines"><em>an article in UX Magazine</em></a><em> about the </em><a href="http://developer.apple.com/iphone/library/documentation/General/Conceptual/iPadHIG/Introduction/Introduction.html"><em>iPad human interface guidelines</em></a><em>. I was reminded by it today by <a href="http://www.ben.geek.nz/2010/06/why-youll-want-a-windows-phone/">this blogpost by Ben.geek.nz</a> about the forthcoming Windows Phone 7 UI design. While I haven&#8217;t seen a WP7 in the flesh it looks as if it may come closer to the spirit of innovative digital design I invoke below. It remains to be seen and as always, god is in the details.</em></p>
<p>This conversation would be funny if it weren&#8217;t so depressing.</p>
<p>So here we have what is supposedly one of the world&#8217;s leading technology companies launching what it calls a &#8220;magical and revolutionary&#8221; product. And what does it do? It goes and encourages developers to build twee simulacra of physical objects. How unmagical. How unrevolutionary. How dull. Apple have seriously employed top-flight designers and developers to build digital representations of address books and books and goodness knows what else that computers are designed to get rid of. And by &#8220;get rid of&#8221; I mean &#8220;eliminate as a concept&#8221; not &#8220;replace with a digital lookalike&#8221;. Now they want everyone else to do the same. No thanks. This is 2010 not 1910.</p>
<p>This approach is an enormous dead end that&#8217;s wrong on so many levels and plays itself out in various ways, some quite obvious, others more subtle and insidious. In a pragmatic sense, it just doesn&#8217;t work on its own terms. Digital metaphors of physical objects are full of leaky abstractions, being both capable of things that their physical counterparts are not and (surprise!) not capable of things their physical counterparts are. No-one seriously designs these metaphors to be perfect &#8212; it&#8217;s impossible. With computers being mainstream for at least twenty years I&#8217;m wondering why anyone&#8217;s still bothering at all. The desktop metaphor for graphical user interfaces was a smart-ish idea compared with the alternatives in 1984. With every year that passes it gets shot through with more and more holes. And the iPad is supposedly the device that moves on from all that. It certainly has the potential as a piece of hardware, as an OS, as a platform. So why try to limit designers&#8217; approaches to something so decidedly retrospective?</p>
<p>But the real problem is much worse than some of the cheesy UI elements like page curls, as excruciating as they may be. What&#8217;s wrong with this scenario?</p>
<p>I go to the (virtual) bookshop and browse through the (virtual) books. I find one I like and I pay real money for it. The (virtual) book gets transferred to me and placed on my (virtual) bookshelf alongside the other (virtual) books I&#8217;ve bought and that I now have to store and organise.</p>
<p>Hey! It&#8217;s just like the real world!</p>
<p>Quite. With most of its limitations, inefficiencies and exclusions comfortingly intact. Business as usual.</p>
<p>Page curl and page turning is a cartoon of something that&#8217;s an artifact of pagination which is a consequence of the former necessity for long-form texts to be printed and bound and distributed as such in the physical world. So are bookshops. So is the concept of owning a book. So are bookshelves and private collections of books. And yes, I notice that the age-old tradition of handing over real money for the non-exclusive opportunity to access a particular small and pre-defined chunk of content is still going strong.</p>
<p>Designers: You can think of better ways of doing it than this. Numerous better ways. You could get the genius lovechild of <a href="http://www.edwardtufte.com/tufte/">Edward Tufte</a> and <a href="http://www.johnpawson.com/">John Pawson</a> to redesign iBook&#8217;s UI and it&#8217;d still be a bad idea. We don&#8217;t need iBook any more than we need books. We still need ideas. We still need texts. But where they start and where they end and how we represent them and how we can explore them &#8212; that&#8217;s all up for grabs. Can we do this on the iPad? Probably. Should we try? Definitely. Does Apple want us to? Frankly, probably not.</p>
<p>Someone mentioned beauty. Supposedly there are 80% of people that like &#8220;functional&#8221; stuff and 20% that like &#8220;beautiful&#8221; stuff. That 20% are supposedly Apple&#8217;s customers. and the rest still use slide rules, telephone directories and Windows Mobile. I&#8217;m not going to pick apart how right or wrong that may be right now. But I&#8217;ll say this:</p>
<p>If beauty is making digital simulacra then we need a new aesthetic. If beauty is perpetuating not just the appearances but the cruel limitations of things past, it&#8217;s time to move on. We need a digital aesthetic that&#8217;s more than skin deep. One based on possibilities and power that continue to delight us as we use our new digital tools rather than briefly amusing us when we first encounter them. And yes, given that these are new things they should look like new things too. Get the message? If you&#8217;re not experiencing Google Search on an aesthetic level you&#8217;re not paying enough attention. I&#8217;m not talking about how it looks. I&#8217;m talking about what it can do for you. We need more of that. A whole lot more. In the short term, it&#8217;s about companies paying their bills, thriving, profiting. In the long run it&#8217;s about the entire field of computing progressing or stagnating, not the fortunes of any particular company. It&#8217;s about having an information society rather than an information technology society. You want to have something worthy of an upgrade in 2020? Step away from those horseless carriages. Don&#8217;t look back.</p>
<p>In short, if you love notebooks, buy a <a href="http://www.moleskine.co.uk/">Moleskine</a>. If you want to be a cartoonist, go and work for Pixar. If you&#8217;re confused about which way time&#8217;s running, go cyberpunk or trawl eBay for a <a href="http://en.wikipedia.org/wiki/Newton_(platform)">Newton</a>. And if you want to make a genuinely &#8220;magical and revolutionary&#8221; break with the past on the iPad platform &#8212; and I think you should &#8212; then forget about physicality and virtuality and retro computing and <strong>go and make something that not only doesn&#8217;t exist in the physical world but doesn&#8217;t exist in the digital one either</strong>. After two decades of mainstream computing we&#8217;re more than ready for something genuinely digitally native. We can stand the shock of the new. I hope that someone at Apple still understands that sometimes you&#8217;ve just got to break the rules &#8212; including your own.</p>
]]></content:encoded>
			<wfw:commentRss>http://adrianshort.co.uk/2010/06/17/digital-simulacra-and-the-ipad-human-interface-guidelines/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How ebooks will replace printed books</title>
		<link>http://adrianshort.co.uk/2010/02/03/how-ebooks-will-replace-printed-books/</link>
		<comments>http://adrianshort.co.uk/2010/02/03/how-ebooks-will-replace-printed-books/#comments</comments>
		<pubDate>Wed, 03 Feb 2010 20:52:21 +0000</pubDate>
		<dc:creator>Adrian Short</dc:creator>
				<category><![CDATA[Design theory]]></category>
		<category><![CDATA[books]]></category>
		<category><![CDATA[ebook readers]]></category>
		<category><![CDATA[ebooks]]></category>
		<category><![CDATA[iPad]]></category>
		<category><![CDATA[Kindle]]></category>

		<guid isPermaLink="false">http://adrianshort.co.uk/?p=508</guid>
		<description><![CDATA[Do you remember when film photography was ubiquitous and consumer digital cameras were just starting to come onto the market? (Worryingly, there will be readers of this blog that won&#8217;t.) At the time, there was any amount of commentary from the tech boosters who said that of course digital photography would supplant film soon enough. [...]]]></description>
			<content:encoded><![CDATA[<p>Do you remember when film photography was ubiquitous and consumer digital cameras were just starting to come onto the market? (Worryingly, there will be readers of this blog that won&#8217;t.)</p>
<p>At the time, there was any amount of commentary from the tech boosters who said that of course digital photography would supplant film soon enough. Meanwhile the naysayers trotted out a list of reasons why they wouldn&#8217;t be trading in their &#8220;real&#8221; cameras for these second-class substitutes and couldn&#8217;t see why anyone would.</p>
<p>I don&#8217;t need to tell you how that one worked out, but let&#8217;s look at the process by which this happened.</p>
<p><span id="more-508"></span></p>
<p>Mass-market consumer digital cameras started with the <a href="http://www.wherry.com/gadgets/qv10/">Casio QV-10</a> in 1995. With a resolution of a quarter of a megapixel (0.25MP) combined with pathetic image processing it was clearly a pale precursor to the intelligent and vivid cameras we enjoy fifteen years later. Yet it was essentially a modern digital camera: A (large) pocket-sized device producing colour pictures, with internal memory, a colour screen on the back and the ability to transfer pictures to a computer. The digital camera technology of today may be better but it isn&#8217;t fundamentally different.</p>
<p>In this first stage, the mass market and many pundits view the new technology as a loser. It&#8217;s both far more expensive and has far worse quality and usability than the thing it&#8217;s supposed to replace. <strong>This is the &#8220;birth&#8221; phase of a technology</strong>, where the early adopters spend a fortune to get something that&#8217;s massively compromised, yet shows promise and provides a fair amount of exclusivity.</p>
<p>I got my first digital camera in 2000, five years after the QV-10. It was a <a href="http://www.steves-digicams.com/mx1700.html">Fuji MX-1700</a>. Costing around £400, it produced 1.3 megapixel images and had a 3x zoom lens. There were cheaper cameras, but they had even lower resolutions, worse image processing and no zoom lens. On the upside, it was extremely pocketable and produced crisp, well-exposed pictures. On the downside, the pictures were still very low resolution and it was very slow to use, with a lag of what seemed like around a second between pressing the shutter release and the camera capturing and storing the image. Compared with most compact film cameras, it was incredibly expensive toy. Yet for these faults, it was a good replacement for much of my film photography. I could see my images immediately after they were shot and show them to other people. Having paid for the camera, each shot was effectively free. Best of all, I could transfer them to my computer and put them on my website, which was in the process of becoming a far more common way of sharing photos than making prints. For its time, and for the things I did, it was fantastic. But not everyone &#8220;got it&#8221;, or was prepared or able to spend that amount of money to replace the &#8220;perfectly good&#8221; film camera they were used to using.</p>
<p><strong>This is the &#8220;growing-up&#8221; phase of a technology</strong>, where products reach a wider audience who are prepared to make some compromises in respect of older devices in return for benefits in areas which they consider to be more important to them. Often these benefits are in cost and convenience rather than quality.</p>
<p>Now digital cameras are ubiquitous. When we talk of &#8220;cameras&#8221; we mean &#8220;digital cameras&#8221; and tend to specify &#8220;film cameras&#8221; if we mean otherwise. Film is the preserve of retro enthusiasts and a tiny minority of professionals. Businesses based around film technology have either died or revolutionised their operations towards digital. Any discussion of &#8220;will digital replace film?&#8221; now seems anachronistic and nonsensical.</p>
<p><strong>In this &#8220;mature&#8221; phase of the technology</strong>, the new technology is superior in almost every way to the old. Generally, it&#8217;s cheaper, quicker, more convenient, more flexible and has better quality. <em>Not </em>using it involves a large degree of compromise to get a niche benefit that the mass market simply doesn&#8217;t care about.</p>
<p>This is where I see ebooks and ebook readers going. Right now they&#8217;re in the &#8220;birth&#8221; stage. Often they&#8217;re more expensive, lower quality and more hassle than just buying a printed book. It&#8217;s easy to see why relatively few people bother &#8212; and why those that do are considered a little strange. To most people it makes little rational sense.</p>
<p>But before long &#8212; and I believe we&#8217;re just entering this phase with devices like the <a href="http://en.wikipedia.org/wiki/Amazon_Kindle">Kindle</a> and particularly the <a href="http://en.wikipedia.org/wiki/Ipad">iPad</a> &#8212; we&#8217;ll be in the &#8220;growing-up&#8221; phase. There will be definite pros and cons to ebooks and printed books, but not a clear-cut overall benefit either way. Which you choose will depend on what matters most to you. Cost, convenience (of carrying, purchasing and storing), display/reading quality, the ability to share and annotate, style and image. Some (richer) students will plump for an iPad over carrying a rucksack full of half a dozen fat textbooks. Other people will stick to the venerable printed book for a variety of reasons, including simple cost.</p>
<p>So how long before ebooks reach their &#8220;mature&#8221; phase? Five years? Ten? Almost certainly not any longer. Whatever device you&#8217;ll use to read them (phone, tablet, laptop, something else) you&#8217;ll have anyway, so no-one will think of that as a significant cost. The ebooks themselves will be much cheaper than their paper equivalents, where those even exist. Ebook reader quality will far exceed what&#8217;s possible on the printed page, in resolution, clarity and flexibility. Annotating ebooks and sharing those notes will be far easier and more powerful than on a paper page. You can&#8217;t search a printed book in any automated way at all, yet the ways we&#8217;ll be able to search, analyse and navigate ebooks in a few years will seem incredible compared to the best search technology we have today. And while some will wax nostalgic about the heft, the texture, the smell and the patina of the traditional printed book, in most cases they simply won&#8217;t be buying new ones. &#8220;Book&#8221; will mean &#8220;ebook&#8221; in common speech, and discussions about &#8220;ebooks vs. print&#8221; and will seem as quaint as the battles between digital and film photography advocates in the mid- to late-1990s.</p>
<p>I&#8217;ll miss printed books in some ways but I&#8217;ll be constantly reminded that the ebooks that have replaced them will have done so because they&#8217;re in every reasonable sense better. Rapid, incremental technological advancement will turn that potential into reality.</p>
<p>I just hope I’ll have the time to read more, but I won’t bet on that.</p>
]]></content:encoded>
			<wfw:commentRss>http://adrianshort.co.uk/2010/02/03/how-ebooks-will-replace-printed-books/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Why wouldn&#8217;t you want an Apple iPad on your coffee table?</title>
		<link>http://adrianshort.co.uk/2010/01/28/why-wouldnt-you-want-an-apple-ipad-on-your-coffee-table/</link>
		<comments>http://adrianshort.co.uk/2010/01/28/why-wouldnt-you-want-an-apple-ipad-on-your-coffee-table/#comments</comments>
		<pubDate>Thu, 28 Jan 2010 14:54:28 +0000</pubDate>
		<dc:creator>Adrian Short</dc:creator>
				<category><![CDATA[Design theory]]></category>
		<category><![CDATA[Product design]]></category>
		<category><![CDATA[Simplicity]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[iPad]]></category>
		<category><![CDATA[tablet computers]]></category>

		<guid isPermaLink="false">http://adrianshort.co.uk/?p=505</guid>
		<description><![CDATA[The Apple iPad isn't just the first credible device in a new category -- it's leading the way towards a world of elegant, specialised computers.]]></description>
			<content:encoded><![CDATA[<p><a title="Apple iPad by Adrian Short, on Flickr" href="http://www.flickr.com/photos/adrianshort/4310974617/"><img src="http://farm5.static.flickr.com/4001/4310974617_32ab446c7e.jpg" alt="Apple iPad" width="500" height="172" /></a><br />
The long-awaited and much-hyped <a href="http://www.apple.com/ipad/">Apple iPad</a> is out, receiving a fairly upbeat response in the media and a much cooler, going on hostile reaction among bloggers and commenters.</p>
<p>Spec-obsessed techies bemoan the lack of hardware features and the relatively modest screen resolution, processor power and storage space. But the iPad isn&#8217;t about any of those things. It&#8217;s about providing a great user experience for the things it does, not beating the competition on points.</p>
<p><span id="more-505"></span></p>
<p>What competition, anyway? Netbooks, the Kindle and other e-book readers, smartphones and even Windows 7-based tablet computers are all aimed at different uses and audiences. Assuming Apple wants to keep selling iPhones, MacBooks and iMacs, it clearly doesn&#8217;t believe the iPad is a replacement for your phone, laptop or desktop. The iPad is in a category of its own for now.</p>
<p>So cutting past the &#8220;I wanted two cameras, multi-tasking, Flash and a 500GB hard drive&#8221; crowd, let&#8217;s ask the real question: Why <em>wouldn&#8217;t </em>you want an iPad on your coffee table?</p>
<p>What would be so terrible about being able to pick up a hand-held device with a lovely big screen and browse the web?</p>
<p>Why would such a thing be so awful if you wanted to curl up in a chair &#8212; or in bed &#8212; and watch a film or some YouTube clips?</p>
<p>Could you really not enjoy reading a book on such a thing?</p>
<p>No-one is stopping you popping your (smart) phone in your pocket when you go out. And no-one is stopping you working on a fully-featured laptop or desktop computer with all its multi-tasking, power and disk space when you want to do some serious work. The iPad is for sitting back, browsing, watching, listening. Writing the occasional email, tweet or comment. The kind of thing you probably either squint at a smartphone to do, or struggle to do with a netbook or toasty laptop and its poorly-suited trackpad.</p>
<p>You don&#8217;t need a full, multi-tasking OS to do any of these things. You don&#8217;t need Flash. You don&#8217;t need USB ports. And you don&#8217;t need a lot of storage, although by many sensible standards, the top 64GB model <em>has </em>a lot of storage &#8212; but not if you&#8217;re the kind of chap that has a computer dedicated to running BitTorrent.</p>
<p>No-one needs an iPad. Even at what appears to be a modest price for what it is, it&#8217;s a luxury item. While I would definitely argue that most working people and students need a computer and that many would benefit from having a smartphone, this in-between category of slick media viewer is pure indulgence. It will stand or fall not so much on what it can do, and even less on what it can do that other gadgets can&#8217;t. The user experience will be everything.</p>
<p>The test of the user experience isn&#8217;t on the spec sheet or in the promo photos or videos. It&#8217;s in getting into your hands (and hopefully, living room) and having a go. I&#8217;ll reserve further judgement until I get a chance to do just that, but if it&#8217;s as much of a joy to use as the iPhone and iPod Touch then it&#8217;ll definitely be finding house room and earning its keep by pure pleasure alone.</p>
<p>We&#8217;ll be seeing a lot more of these kinds of devices in future, from Apple and many others. Not just tablets, but a myriad of things-that-compute-that-aren&#8217;t-computers. For all its versatility, the general purpose computer and operating system is lousy to use, still feebly perpetuating the same interface and interaction design of the first Macs (and <a href="http://en.wikipedia.org/wiki/Apple_Lisa">Lisas</a>) back in the early 1980s.</p>
<p>Smartphones show promise, but their small screens will always limit their uses for many applications, at least until we can wire them into our goggles or optic nerves. The future is computers that are smaller, more specialised and more numerous, each of which is limited to but hopefully beautifully suited to its task. With its screen, controls, software and storage, what is a digital camera if not an elegantly-specialised computer?</p>
<p>If you ran a big organisation, why wouldn&#8217;t you want half a dozen iPads in the waiting area at reception?</p>
]]></content:encoded>
			<wfw:commentRss>http://adrianshort.co.uk/2010/01/28/why-wouldnt-you-want-an-apple-ipad-on-your-coffee-table/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>What&#8217;s the point of a tweeting mobile library?</title>
		<link>http://adrianshort.co.uk/2009/12/17/whats-the-point-of-a-tweeting-mobile-library/</link>
		<comments>http://adrianshort.co.uk/2009/12/17/whats-the-point-of-a-tweeting-mobile-library/#comments</comments>
		<pubDate>Thu, 17 Dec 2009 18:46:41 +0000</pubDate>
		<dc:creator>Adrian Short</dc:creator>
				<category><![CDATA[Design theory]]></category>
		<category><![CDATA[Software design]]></category>
		<category><![CDATA[Sutton]]></category>
		<category><![CDATA[Urban design]]></category>
		<category><![CDATA[@SutMobLib]]></category>
		<category><![CDATA[libraries]]></category>
		<category><![CDATA[mobile libraries]]></category>
		<category><![CDATA[things that tweet]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://adrianshort.co.uk/?p=484</guid>
		<description><![CDATA[Last week I launched @SutMobLib, a Twitter account that tweets the location of Sutton&#8217;s mobile library in real time. No, I&#8217;m not sitting here all day sending messages. A program does that automatically. Every time the library gets to a new stop it posts up its location. The utility of such a thing isn&#8217;t immediately [...]]]></description>
			<content:encoded><![CDATA[<p><a title="@SutMobLib Twitter screenshot by Adrian Short, on Flickr" href="http://www.flickr.com/photos/adrianshort/4193374520/"><img src="http://farm3.static.flickr.com/2724/4193374520_34f35ca88d_o.jpg" alt="@SutMobLib Twitter screenshot" width="552" height="392" /></a></p>
<p>Last week I launched <a href="http://twitter.com/sutmoblib">@SutMobLib</a>, a Twitter account that tweets the location of <a href="http://www.sutton.gov.uk/index.aspx?articleid=915">Sutton&#8217;s mobile library</a> in real time. No, I&#8217;m not sitting here all day sending messages. A program does that automatically. Every time the library gets to a new stop it posts up its location.</p>
<p><span id="more-484"></span></p>
<div class="wp-caption alignnone" style="width: 513px"><a title="@SutMobLib Bing Maps Twitter search screenshot by Adrian Short, on Flickr" href="http://www.flickr.com/photos/adrianshort/4192613683/"><img src="http://farm3.static.flickr.com/2701/4192613683_90658e31b5_o.jpg" alt="@SutMobLib Bing Maps Twitter search screenshot" width="503" height="312" /></a><p class="wp-caption-text">@SutMobLib on Bing Maps Twitter Search</p></div>
<p>The utility of such a thing isn&#8217;t immediately obvious. While I don&#8217;t like to generalise or assume too much, I suspect that the vast majority of mobile library users don&#8217;t use Twitter. So far a grand total of nine  people have signed up to follow <a href="http://twitter.com/SutMobLib">@SutMobLib</a> and most of those are various <a href="http://en.wikipedia.org/wiki/Sockpuppet_(Internet)">sock puppets</a> of mine.</p>
<div class="wp-caption alignright" style="width: 330px"><a title="@SutMobLib Tweetie 2 screenshot by Adrian Short, on Flickr" href="http://www.flickr.com/photos/adrianshort/4193374714/"><img src="http://farm3.static.flickr.com/2798/4193374714_4ba375e7c8_o.jpg" alt="@SutMobLib Tweetie 2 screenshot" width="320" height="480" /></a><p class="wp-caption-text">@SutMobLib on Tweetie 2 &quot;nearby search&quot; for iPhone</p></div>
<p>Unlike most Twitter accounts that belong to real people, <a href="http://twitter.com/SutMobLib">@SutMobLib</a> isn&#8217;t great for conversation. It&#8217;s even less intelligent and interactive than it looks. Anyone that wants to be reminded when the library is visiting their neighbourhood would be better off just putting the relevant day in their calendar.</p>
<p><a href="http://twitter.com/SutMobLib">@SutMobLib</a> is useful because Twitter is now more than just a social network connecting people. It&#8217;s become a platform for realtime geospatial information, where things like the mobile library can post up what they&#8217;re doing and where they&#8217;re doing it, as they&#8217;re doing it.</p>
<p>Experienced Twitter users know that while half the power of Twitter is following people you&#8217;re interested in and conversing with them, the other half is reading <a href="http://search.twitter.com/search?q=dinner">realtime searches</a> for keywords, phrases and <a href="http://hashtags.org/">hashtags</a>. Recently, Twitter enhanced the power of its search by allowing members to post up their precise geographical location with each tweet, which other members can then discover by searching around an area rather than around a hashtag or topic.</p>
<p>So <strong>Twitter has become a radar</strong>. <a href="http://www.atebits.com/tweetie-iphone/">Tweetie 2</a>, a Twitter client for the iPhone, allows users to search &#8220;Nearby&#8221; based on the user&#8217;s current location and shows a map covered with plotted tweets. Web users can do something similar using <a href="http://www.bing.com/maps/explore/#5872/style=auto&amp;lat=51.36389&amp;lon=-0.174522&amp;z=13&amp;pid=5874/5003/0.40326=s:@SutMobLib&amp;o=&amp;a=0">Bing Maps&#8217; Twitter Search</a>. The popular client TweetDeck shows pop-up maps underneath geotweets.</p>
<p>Realtime geospatial search brings a new dimension to finding out about the world. For the first time we can pull up live information about a place, whether that&#8217;s people&#8217;s conversations and observations or the solipsistic self-reporting of things that tweet like Sutton&#8217;s mobile library. Various urban annotation and virtual graffiti projects have existed before now but Twitter brings this capability to a mass-market social network with tens of millions of members. Through reading conversations about coffee in Soho or chemo at the Royal Marsden Hospital, our awareness of the world around us just got a great deal broader.</p>
<div class="wp-caption alignright" style="width: 250px"><a title="@SutMobLib TweetDeck geotweet by Adrian Short, on Flickr" href="http://www.flickr.com/photos/adrianshort/4193374860/"><img src="http://farm3.static.flickr.com/2781/4193374860_aa6cd0bd35_o.jpg" alt="@SutMobLib TweetDeck geotweet" width="240" height="401" /></a><p class="wp-caption-text">@SutMobLib showing as a geotweet in TweetDeck</p></div>
<p>For some, that will mean discovering, spontaneously and without specifically searching for it, that a friend &#8212; or the mobile library &#8212; is around the corner and might be pleased to see us. The world around us is constantly shifting, with opportunities and hazards popping up and then disappearing again, often without leaving a trace. Now we can see those traces. Serendipity is the spice of life and it&#8217;s just got a very big helping hand. Fire up your radar.</p>
<p>&#8212;</p>
<p>Further reading on where ambient intelligence is taking us:</p>
<p>Peter Morville, <em><a href="http://www.amazon.co.uk/Ambient-Findability-What-Changes-Become/dp/0596007655/">Ambient Findability</a></em><br />
Malcolm McCullough, <a href="http://www.amazon.co.uk/Digital-Ground-Architecture-Pervasive-Environmental/dp/0262633272/"><em>Digital Ground</em></a><br />
Adam Greenfield, <a href="http://www.amazon.co.uk/Everyware-Dawning-Age-Ubiquitous-Computing/dp/0321384016/"><em>Everyware</em></a></p>
]]></content:encoded>
			<wfw:commentRss>http://adrianshort.co.uk/2009/12/17/whats-the-point-of-a-tweeting-mobile-library/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Parsimonious design (or not)</title>
		<link>http://adrianshort.co.uk/2008/09/17/parsimonious-design-or-not/</link>
		<comments>http://adrianshort.co.uk/2008/09/17/parsimonious-design-or-not/#comments</comments>
		<pubDate>Wed, 17 Sep 2008 22:18:53 +0000</pubDate>
		<dc:creator>Adrian Short</dc:creator>
				<category><![CDATA[Design theory]]></category>
		<category><![CDATA[Product design]]></category>
		<category><![CDATA[Amazon Kindle]]></category>
		<category><![CDATA[ebook readers]]></category>
		<category><![CDATA[ebooks]]></category>
		<category><![CDATA[parsimony]]></category>
		<category><![CDATA[Segway]]></category>
		<category><![CDATA[Sony Reader]]></category>

		<guid isPermaLink="false">http://adrianshort.co.uk/?p=68</guid>
		<description><![CDATA[In which we explore the parsimony principle in design with reference to two horribly over-engineered ideas: the Segway personal transporter and ebook readers.]]></description>
			<content:encoded><![CDATA[<p>Perhaps ironically, parsimonious design suffers from the lack of a clear definition. For some it&#8217;s practically synonymous with <em>simplicity.</em> For others it takes a narrower meaning that&#8217;s nearer to <em>frugal</em>.</p>
<p><strong>Parisimonious design is when you&#8217;ve got enough, but no more.</strong> It prefers simple solutions to complex ones and conserves scarce resources wisely. We might think of these resources in economic or environmental terms and design products that are both cheap and don&#8217;t consume an excess of material or energy. We might consider the user and reject designs that squander their time, attention, energy and space.</p>
<p>Many bad designs offend against the principle of parsimony by being too big, too wasteful, too expensive, too complex, too high maintenance. Such designs are the metaphorical sledgehammer to crack a nut. We find ourselves thinking, &#8220;Do we really need all <em>this</em> just to do <em>that?</em>&#8221;</p>
<p><span id="more-68"></span></p>
<p>Two relatively new products should provide cautionary tales.</p>
<p><img class="alignright size-full wp-image-73" title="Lembit Opik on his Segway" src="http://adrianshort.co.uk/wp-content/uploads/2008/09/opik-segway.jpg" alt="" width="200" height="412" /></p>
<p>The <a href="http://en.wikipedia.org/wiki/Segway">Segway PT</a> has been in the news lately as various parliamentarians including the peculiar Lembit Opik MP have put their slender weight behind <a href="http://www.legalisesegways.co.uk/">a campaign to legalise their use on Britain&#8217;s streets</a>. Clearly the fact that the Segway is currently illegal both on the roads and on pavements in this country must put a dampener on sales. Yet I suspect that even if some form of legalisation is eventually forthcoming, the Segway or anything much like it won&#8217;t become a significant mode of transport in urban areas.</p>
<p>The Segway does well in packing some seriously complex technology behind a relatively straightforward user interface, but my instinct is still that it&#8217;s overdesigned for the tasks it&#8217;s supposed to serve. Employing a £4000 electric vehicle just to be able to travel a little faster than walking or a little slower than cycling and in many cases with less range doesn&#8217;t offer enough marginal benefit to be worth the price, let alone the trouble of having to charge, insure and maintain it. As indefatigable campaigners <a href="http://www.livingstreets.org.uk/">Living Streets</a> keep reminding us, walking two or three miles for everyday journeys is often much quicker and more pleasant than we might imagine, particularly when compared with the alternatives. We&#8217;re just not in the habit of doing it. For those that want to travel further or more quickly, a £50 bicycle beats the pants off vertical milk float technology in almost every respect bar sloth.</p>
<p>So whenever I see Segways now I can&#8217;t help but be reminded of <a href="http://news.bbc.co.uk/1/hi/uk_politics/7605353.stm">simpering Mr Opik</a> proudly standing eight inches above a group of bored journalists selling the idea that his dorkmobile stands between us and ecogeddon as if his life &#8212; and ours &#8212; depended on it. Not parsimonious, I&#8217;m afraid. Move along.</p>
<p><img class="size-medium wp-image-70" title="Sony Reader PRS-505 &amp; Amazon Kindle" src="http://adrianshort.co.uk/wp-content/uploads/2008/09/sony_v_amzn_opener-400x266.jpg" alt="" width="400" height="266" /></p>
<p>This week sees the launch of Sony&#8217;s latest ebook reader, the imaginatively-titled <a href="http://en.wikipedia.org/wiki/Sony_Reader">Sony Reader</a> (PRS-505). The Sony competes with <a href="http://en.wikipedia.org/wiki/Amazon_Kindle">Amazon&#8217;s Kindle</a>, forthcoming wizardly wonders like the <a href="http://www.plasticlogic.com/">Plastic Logic Reader</a> and, well, books.</p>
<p>Despite &#8212; or perhaps because of &#8212; my love for good old fashioned dead tree books, I&#8217;m instinctively drawn to the idea of an ebook reader in almost equal measure to how I&#8217;m repelled by cumbersome personal transporters. Ebook readers promise to lighten our loads and <a href="http://unclutterer.com/category/books/">cut clutter</a> by replacing paper books with ethereal digital equivalents in much the same way that MP3 players have eliminated the need for CDs and vinyl for many. Is this parsimony?</p>
<p>The environmental credentials of ebook readers are hard to guess, but I&#8217;m sure they can be calculated. On the downside we have a (say) £200 device with complex electronics and a lifespan of five years, to be generous. On the upside, we have the lack of dozens or hundreds of paper books per device, their storage, transport and ultimate disposal. If the device really does provide an adequate substitute for paper books, I could be persuaded that it has environmental and space-saving benefits.</p>
<p>But there&#8217;s the rub. As the designers of the original <a href="http://en.wikipedia.org/wiki/Palm_Pilot">Palm Pilot</a> found, competing against the speed, flexibility and cheapness of paper is tough. <a href="http://www.moleskine.co.uk/">Moleskines</a> are the new <a href="http://en.wikipedia.org/wiki/Personal_digital_assistant">PDAs</a>. In <a href="http://mitpress.mit.edu/catalog/item/default.asp?ttype=2&amp;tid=8501"><em>The Myth of the Paperless Office</em></a>, Sellen and Harper offer a compelling explanation of the obvious: Digital technology has increased rather than decreased the amount of paper in use and this trend looks set to continue for the foreseeable future. The things that paper does well, computers do not. Further, computers have stimulated and expanded the various kinds of knowledge work in which paper is an essential tool.</p>
<p>So are ebook readers parsimonious? Could they be? At the current state of technology, ebook readers are adequate for linear reading but very little else. If you&#8217;re addicted to <a href="http://en.wikipedia.org/wiki/Airport_novel">airport novels</a> they could be right up your street. But the complex browsing, cross-referencing and annotation that is commonplace with professional and academic reading is way beyond current ebook readers&#8217; capabilities. Moreover, it&#8217;s usual for students and professionals to refer to several books and documents at once, implying that for this kind of use, the ebook reader is competing not just against one simultaneous book but several. It&#8217;s no consolation that your ebook reader may have the capacity to store 6000 copies of <em>War and Peace</em> when what you really want to do is to refer to all of Tolstoy&#8217;s works <em>at once</em>. If £200 for an ebook reader sounds reasonable, try budgeting for a dozen of them.</p>
<p>While ebook reader technology will presumably evolve to incorporate more of the characteristics of paper and thereby gain paper&#8217;s flexibility and affordability, right now the most parsimonious way to use large chunks of text is to print them on paper and bind them into attractive and durable covers. You can&#8217;t compete with tree.</p>
<p>The Segway and ebook readers condemn themselves to whimsical or niche uses by flagrantly ignoring the parsimony principle. Between two designs for the same purposes, the simpler one is the better one.</p>
]]></content:encoded>
			<wfw:commentRss>http://adrianshort.co.uk/2008/09/17/parsimonious-design-or-not/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The features you have vs. the features you use</title>
		<link>http://adrianshort.co.uk/2008/09/12/the-features-you-have-vs-the-features-you-use/</link>
		<comments>http://adrianshort.co.uk/2008/09/12/the-features-you-have-vs-the-features-you-use/#comments</comments>
		<pubDate>Fri, 12 Sep 2008 23:14:42 +0000</pubDate>
		<dc:creator>Adrian Short</dc:creator>
				<category><![CDATA[Design theory]]></category>
		<category><![CDATA[Product design]]></category>
		<category><![CDATA[Simplicity]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[iPhone]]></category>
		<category><![CDATA[mobile phones]]></category>
		<category><![CDATA[Nokia 1100]]></category>
		<category><![CDATA[phones]]></category>

		<guid isPermaLink="false">http://adrianshort.co.uk/?p=67</guid>
		<description><![CDATA[Of the 21 features on my phone, I use just five. Can't someone make a phone without all the rest?]]></description>
			<content:encoded><![CDATA[<p>As my own small contribution to the literature on <a href="http://en.wikipedia.org/wiki/Featuritis">featuritis</a>, here&#8217;s a personal illustration. My mobile phone isn&#8217;t anything fancy. It&#8217;s cheap and very basic by today&#8217;s standards. No internet, no camera, no MP3 player. I bought it because all I wanted to do was to make calls and send texts.</p>
<p>So here&#8217;s a list of what my &#8220;simple&#8221; <a href="http://www.nokia.co.uk/phones/1100">Nokia 1100</a> can do, and what I actually do with it.</p>
<p><span id="more-67"></span></p>
<p>Features that I have:</p>
<ol>
<li>telephone</li>
<li>SMS</li>
<li>contacts</li>
<li>call register</li>
<li>choice of ring tones</li>
<li>profiles (stored sets of settings)</li>
<li>headset jack</li>
<li>torch</li>
<li>welcome note (customisable message when you switch on)</li>
<li>call diversion</li>
<li>automatic redialling</li>
<li>speed dialling</li>
<li>clock</li>
<li>alarms</li>
<li>reminders</li>
<li>games</li>
<li>calculator</li>
<li>stopwatch</li>
<li>countdown timer</li>
<li>ringtone composer</li>
<li>screensaver</li>
</ol>
<div>Features that I use:</div>
<ol>
<li>telephone</li>
<li>SMS</li>
<li>contacts</li>
<li>call register</li>
<li>clock</li>
</ol>
<div>Reducing the phone to this very limited feature set, one could dispense with the menu entirely and have a simple toggle between phone and text modes. Even better, work out a way invoking these functions implicitly rather than explicitly.</div>
<div>In its favour, the phone lasts more days on a single battery charge than most fancy smartphones will last hours, as the <a href="http://www.janchipchase.com/blog/archives/2008/09/future_social_1.html">74% of Japanese iPhone users that carry it as a second phone</a> could probably testify.</div>
]]></content:encoded>
			<wfw:commentRss>http://adrianshort.co.uk/2008/09/12/the-features-you-have-vs-the-features-you-use/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Estimated date of birth &#8212; an interaction design pattern</title>
		<link>http://adrianshort.co.uk/2008/09/09/estimated-date-of-birth-an-interaction-design-pattern/</link>
		<comments>http://adrianshort.co.uk/2008/09/09/estimated-date-of-birth-an-interaction-design-pattern/#comments</comments>
		<pubDate>Tue, 09 Sep 2008 09:36:27 +0000</pubDate>
		<dc:creator>Adrian Short</dc:creator>
				<category><![CDATA[Design theory]]></category>
		<category><![CDATA[Software design]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[Web design]]></category>
		<category><![CDATA[ages]]></category>
		<category><![CDATA[birthdays]]></category>
		<category><![CDATA[database design]]></category>
		<category><![CDATA[dates of birth]]></category>
		<category><![CDATA[form design]]></category>
		<category><![CDATA[surveys]]></category>

		<guid isPermaLink="false">http://adrianshort.co.uk/?p=65</guid>
		<description><![CDATA[How to avoid asking people for their date of birth when you don't need it but still gain enough data to be able to produce meaningful age segmentations.]]></description>
			<content:encoded><![CDATA[<p><strong>Context</strong></p>
<p>You want to collect the dates of birth of a group of people so that you can analyse and segment the group by age, but asking for a date of birth isn&#8217;t necessary for any specific reason and many people in the group may balk at giving you this private information.</p>
<p><span id="more-65"></span></p>
<p><strong>Discussion</strong></p>
<p>It&#8217;s a common conceit among people designing forms and surveys that if you ask a question, you&#8217;ll get a useful answer, but when it comes to personal information the wise designer treads very carefully.</p>
<p>A general rule for form design is that every extra question reduces your response rate and diminishes the chances of the form being completed accurately. Every time you add something you take something away.</p>
<p>As people become more conscious of the real or imagined incidence of identity theft and the predations of overzealous marketers, they are increasingly reluctant to part with personal information even where they might otherwise be happy to provide information for a purpose with which they agree.</p>
<p>As consumers, we understand that there are times when our date of birth will be required for official purposes. We don&#8217;t expect to be able to open a bank account or obtain a passport without it. But when we&#8217;re completing a marketing survey or simply registering with an online shop it can often feel like too much information. I don&#8217;t get asked my date of birth when I shop on the high street &#8212; why would I need to disclose it just to use the online equivalent?</p>
<p>Having age information about a group of people is often useful or even necessary for researchers and marketers. They might want to produce an age breakdown of a group of people using their service or participating in their research, or validate that people in a group qualify to be there where there is an age restriction.</p>
<p>One solution to the problem is to ask respondents for their <em>age group</em> rather than their date of birth:</p>
<p><em>How old are you?</em></p>
<ul>
<li>under 18</li>
<li>18-25</li>
<li>26-39</li>
<li>40-49</li>
<li>50-64</li>
<li>65 and over</li>
</ul>
<p>This is less intrusive for respondents and more likely to gain a response than asking for a date of birth. It allows a report to be produced grouping the respondents by frequency under these headings.</p>
<p>Unfortunately, this approach is very inflexible. Once the respondents are placed into these groups you cannot produce a different age segmentation. In the above example, if there were a subsequent requirement to count all the people aged under 30, you couldn&#8217;t.</p>
<p>This approach also fails if the data are to be used over time. The age segmentations will be correct at the time of data collection but will rapidly obsolesce after that. It works for a one-time snapshot such as a survey but doesn&#8217;t work for a group who will be participating over time such as members of an organisation or customers of a business.</p>
<p><strong>Resolution</strong></p>
<p>These issues can often be better resolved by asking respondents for their <em>ages </em>and then calculating an <em>estimated date of birth</em> for them which is then stored. Ages are less specific than precise dates of birth and asking for them is more likely to gain an accurate response.</p>
<p><em>How old are you?</em> _____________ (write in your age; leave it blank if you&#8217;d rather not say)</p>
<p>If a person responds that they are 30 today, we cannot possibly know their birthday. It could be any day between today (they&#8217;ve just turned 30) up to a year&#8217;s time less a day.</p>
<p>So calulate the estimated date of birth to be:</p>
<p><em>today &#8211; respondent&#8217;s age in years &#8211; six months</em></p>
<p>While there is only a 1 in 365 (ish) chance of estimating the date of birth correctly for each individual, by assuming that each person is half way towards their next birthday you prevent skewing the overall age breakdown for the group either too low or too high.</p>
<p>Ensure that your database or spreadsheet column is called <em>estimated date of birth</em> to prevent subsequent users assuming that these DOBs are accurate.</p>
<p>Using these estimated dates of birth you can produce sufficiently accurate age segmentations at any time in the future regardless of how you define the segment boundaries.</p>
<p>As a caveat, be aware that while this technique allows you to estimate the <em>number </em>of people in the group, say, under 30, if there&#8217;s an absolutely specific reason to find the <em>actual members </em>that are under 30, you can&#8217;t. You&#8217;ll get a few false positives that you&#8217;re estimating to be under 30 even though they&#8217;ve already reached their 30th birthdays.</p>
]]></content:encoded>
			<wfw:commentRss>http://adrianshort.co.uk/2008/09/09/estimated-date-of-birth-an-interaction-design-pattern/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hack your world</title>
		<link>http://adrianshort.co.uk/2008/08/16/hack-your-world/</link>
		<comments>http://adrianshort.co.uk/2008/08/16/hack-your-world/#comments</comments>
		<pubDate>Sat, 16 Aug 2008 16:38:59 +0000</pubDate>
		<dc:creator>Adrian Short</dc:creator>
				<category><![CDATA[Design theory]]></category>
		<category><![CDATA[Product design]]></category>
		<category><![CDATA[Software design]]></category>
		<category><![CDATA[Urban design]]></category>
		<category><![CDATA[adaptive design]]></category>
		<category><![CDATA[hackability]]></category>
		<category><![CDATA[hackers]]></category>
		<category><![CDATA[hacking]]></category>

		<guid isPermaLink="false">http://adrianshort.co.uk/?p=58</guid>
		<description><![CDATA[On the web, in the streets and even in the municipal flowerbeds, people are taking design into their own hands.]]></description>
			<content:encoded><![CDATA[<p>First came the <a href="http://www.guerrillagardening.org/">guerilla gardeners</a>, sowing seeds and planting plants in public places without permission.</p>
<p>Then there were the <a href="http://www.spacehijackers.co.uk/html/projects/guerrillabench/guerrilla.html">guerilla benchers</a>, installing street seats where the local authority had been too poor or too mean to do it themselves.</p>
<p>On the web, a growing community of <a href="http://www.opendemocracy.net/debates/article-8-85-1025.jsp">civic hackers</a> has been building sites on top of public information to <a href="http://www.programmableweb.com/">mash it up</a> in new ways that the publishers hadn&#8217;t imagined or didn&#8217;t have the means or motive to build.</p>
<p><span id="more-58"></span></p>
<p>In digital and physical space, if something can be hacked it will be. People are no longer content to live with what designers give them. As Stewart Brand argues in <a href="http://en.wikipedia.org/wiki/How_Buildings_Learn"><em>How Buildings Learn</em></a>, the end of the formal, official design process isn&#8217;t the end of design, it&#8217;s just the start of the informal process where the users take over and adapt their spaces to their ever-changing needs.</p>
<p>Within the design profession, the practice of <a href="http://en.wikipedia.org/wiki/Co-Design">co-design</a> is acknowledging that products are better when the users aren&#8217;t just consulted but actually participate in the design process. But this is only half the story. Design is part observation and part clairvoyance, discerning likely future needs from current and past ones. When the scope is limited and familiar &#8212; <a href="http://www.whitehorsepress.com/images/products/large/cup.jpg">a container to hold liquid temporarily for drinking</a> &#8212; one has to try very hard to design badly. When the scope is broad and novel &#8212; <a href="http://ask.metafilter.com/65377/Can-an-Oyster-Card-be-hacked">a cashless and paperless ticketing system for a large urban transport system</a> &#8212; the risks of poor systems and rapid obsolescence increase.</p>
<p>This is where the hackers, or guerilla designers, come in. Hackers take a designed system or object and modify it for their own needs, sometimes by changing the thing itself, sometimes by combining it with other things to produce new possibilities. Unpaid and usually unrecognised, the hacker delights in the intellectual challenge and the satisfaction of making something for practical use. Sometimes the results are crude, sometimes elegant. The only true criterion for success is that they work.</p>
<p>Relatively few people have the inclination or opportunity to work as big-D professional designers, but as <a href="http://en.wikipedia.org/wiki/Brain">design tools</a> and the <a href="http://tom.acrewoods.net/research/hackerethic/dissertation">hacker ethic</a> become ever more embedded in the general population, the world is looking a lot more <a href="http://www.cityofsound.com/blog/2006/05/architecture_an.html">malleable</a> than it used to be.</p>
<p>Where do you want to hack today?</p>
<p><object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="100" height="100" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="id" value="VideoPlayback" /><param name="src" value="http://video.google.com/googleplayer.swf?docid=5088653796598486022&amp;hl=en&amp;fs=true" /><embed id="VideoPlayback" type="application/x-shockwave-flash" width="100" height="100" src="http://video.google.com/googleplayer.swf?docid=5088653796598486022&amp;hl=en&amp;fs=true"></embed></object></p>
]]></content:encoded>
			<wfw:commentRss>http://adrianshort.co.uk/2008/08/16/hack-your-world/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Getting to Less part 2: Critically refocus</title>
		<link>http://adrianshort.co.uk/2007/11/24/getting-to-less-part-2-critically-refocus/</link>
		<comments>http://adrianshort.co.uk/2007/11/24/getting-to-less-part-2-critically-refocus/#comments</comments>
		<pubDate>Sat, 24 Nov 2007 09:57:29 +0000</pubDate>
		<dc:creator>Adrian Short</dc:creator>
				<category><![CDATA[Design theory]]></category>
		<category><![CDATA[Simplicity]]></category>

		<guid isPermaLink="false">http://adrianshort.co.uk/?p=27</guid>
		<description><![CDATA[(Back to part 1) Getting to Less is all about helping designers decide what to keep and what to throw out of their designs. Whether you&#8217;re designing software, websites, products or cities, you need to choose what to include and what to omit. But how? Before we can even start to list the current and [...]]]></description>
			<content:encoded><![CDATA[<p>(<a href="/2007/11/21/23">Back to part 1</a>)</p>
<p><em>Getting to Less</em> is all about helping designers decide what to keep and what to throw out of their designs. Whether you&#8217;re designing software, websites, products or cities, you need to choose what to include and what to omit. But how?</p>
<p><span id="more-27"></span></p>
<p>Before we can even start to list the current and proposed features of our product so that we can evaluate them, we need to step back and look at the bigger picture. Even though we may have a specification or requirements document (though often we don&#8217;t!), we need to get back to the original problem or opportunity that is the reason for our product existing.</p>
<p>Flabby products come from forgetting what the product is designed to do and for whom. So let&#8217;s remind ourselves &#8211; and <em>write down</em>:</p>
<ul>
<li>who is this product for?</li>
<li>who is it not for?</li>
<li>what is the core function or purpose?</li>
<li>what problems does it solve?</li>
<li>what problems does it not attempt to solve?</li>
<li>what opportunities does this product exploit?</li>
</ul>
<p>This doesn&#8217;t have to be a long narrative document. A photo of a spread of Post-it notes on a whiteboard will be more than good enough, but make sure you keep it in the project folder so you can go back to it when your focus starts to drift.</p>
<p>This process is particularly necessary when revising a product. On the first iteration, the design objectives are often relatively clear. The original designers are the team. But once you come to the first revision, you could have a different team and different management. It&#8217;s easy to lose sight of the original vision.</p>
<p>So don&#8217;t even attempt to refine a product before you can clearly state what it&#8217;s for. Critically refocus the design team on its reason for existing and take it forward from there.</p>
<p>Part 3 of <em>Getting to Less</em> to follow soon. Stay tuned.</p>
]]></content:encoded>
			<wfw:commentRss>http://adrianshort.co.uk/2007/11/24/getting-to-less-part-2-critically-refocus/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Getting to Less part 1: How to keep what you need and chuck what you don&#8217;t</title>
		<link>http://adrianshort.co.uk/2007/11/21/getting-to-less-how-to-keep-what-you-need-and-chuck-what-you-dont-part-1/</link>
		<comments>http://adrianshort.co.uk/2007/11/21/getting-to-less-how-to-keep-what-you-need-and-chuck-what-you-dont-part-1/#comments</comments>
		<pubDate>Wed, 21 Nov 2007 13:59:07 +0000</pubDate>
		<dc:creator>Adrian Short</dc:creator>
				<category><![CDATA[Design theory]]></category>
		<category><![CDATA[Simplicity]]></category>

		<guid isPermaLink="false">http://adrianshort.co.uk/?p=23</guid>
		<description><![CDATA[Simplicity is becoming an increasingly important trend in design. As life becomes faster-paced and we&#8217;re deluged with more choices, more information and more stuff, users and consumers are demanding that designers do the heavy lifting of making things more focussed, easier to learn, more refined. The question for designers is &#8220;How?&#8221; How do we know [...]]]></description>
			<content:encoded><![CDATA[<p>Simplicity is becoming an increasingly important trend in design. As life becomes faster-paced and we&#8217;re deluged with <a href="http://www.blogger.com/www.ted.com/index.php/talks/view/id/93">more choices</a>, <a href="http://en.wikipedia.org/wiki/Information_overload">more information</a> and <a href="http://books.google.co.uk/books?id=F9E_k09HiG8C&amp;dq=clutter%27s+last+stand&amp;pg=PP1&amp;ots=wb-9tctyfz&amp;sig=YNPvAJ1ugeY9ZsqbBYVqlKXe9sA&amp;prev=http://www.google.co.uk/search%3Fq%3Dclutter%27s%2Blast%2Bstand%26ie%3Dutf-8%26oe%3Dutf-8%26aq%3Dt%26rls%3Dorg.mozilla:en-GB:official%26client%3Dfirefox-a&amp;sa=X&amp;oi=print&amp;ct=title&amp;cad=one-book-with-thumbnail#PPA90,M1">more stuff</a>, users and consumers are demanding that designers do the heavy lifting of making things more focussed, easier to learn, more refined.</p>
<p>The question for designers is &#8220;How?&#8221; How do we know when something is just right, and when it&#8217;s too much or not enough? How do we separate the essential from the peripheral? When do we stop?</p>
<p><span id="more-23"></span></p>
<p>It&#8217;s easy to coin meaningless slogans like &#8220;if in doubt, throw it out&#8221; but they give little help to the designer trying to refine their product to the point of optimal usefulness and usability without making it useless.</p>
<p><a href="http://plw.media.mit.edu/people/maeda/">John Maeda</a> approaches the subject in his book <a href="http://www.amazon.co.uk/Laws-Simplicity-Design-Technology-Business/dp/0262134721/ref=pd_bbs_1?ie=UTF8&amp;s=books&amp;qid=1195395671&amp;sr=8-1">The Laws of Simplicity</a>. His first law of simplicity is <font>Reduce</font>. He writes:</p>
<blockquote><p>The simplest way to achieve simplicity is through <font>thoughtful reduction</font>. When in doubt, just remove. But be careful of what you remove.</p></blockquote>
<p>Anyone then expecting a discussion of how we set out to thoughtfully reduce will be disappointed. The matter is sidestepped entirely and the rest of the chapter details strategies for minimising the impact of what remains.</p>
<p>This series of posts will give you a toolbox of strategies for thoughtful reduction, whether you&#8217;re designing software or websites, products, layouts or just decluttering your home.</p>
<p><strong><font>Strategies for Scope</font></strong></p>
<p>How many features should our product have? How long should our article be? How many books is it reasonable to own? The strategies for scope help us find the right <font>quantity</font><font> </font>of things to have.</p>
<p><strong><font>Strategies for Selection</font></strong></p>
<p>Which features should our product have? Which issues should our article address? Which books should we own? The strategies for selection help us to <font>discriminate </font>between the things worth including and those we can leave out.</p>
<p>This is a series in progress. I aim to complete it within the next two weeks, so please stay tuned.</p>
<p><a href="/2007/11/24/27">Part 2: Critically refocus</a></p>
]]></content:encoded>
			<wfw:commentRss>http://adrianshort.co.uk/2007/11/21/getting-to-less-how-to-keep-what-you-need-and-chuck-what-you-dont-part-1/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.895 seconds -->
