<?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>Rattle &#187; design</title>
	<atom:link href="http://www.rattlecentral.com/blog/tag/design/feed" rel="self" type="application/rss+xml" />
	<link>http://www.rattlecentral.com</link>
	<description></description>
	<lastBuildDate>Fri, 30 Jul 2010 15:12:50 +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>Design Monday #2 &#8211; Lunch&#8230;</title>
		<link>http://www.rattlecentral.com/blog/2008/10/design-monday-2-lunch</link>
		<comments>http://www.rattlecentral.com/blog/2008/10/design-monday-2-lunch#comments</comments>
		<pubDate>Wed, 15 Oct 2008 22:10:13 +0000</pubDate>
		<dc:creator>Frankie Roberto</dc:creator>
				<category><![CDATA[design monday]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[lunch]]></category>

		<guid isPermaLink="false">http://www.rattlecentral.com/?p=44</guid>
		<description><![CDATA[This is the second of our new Design Mondays feature. This is where we take a look at an interesting design challenge that&#8217;s outside of usual web sphere. Last time we looked at central heating, this time the topic is &#8216;lunch&#8217;. As before, you can see a video presentation as well or instead of the [...]]]></description>
			<content:encoded><![CDATA[<p>This is the second of our new Design Mondays feature. This is where we take a look at an interesting design challenge that&#8217;s outside of usual web sphere. Last time we looked at <a href="http://www.rattlecentral.com/archives/2008/09/design-monday-1---central-heat.html">central heating</a>, this time the topic is &#8216;lunch&#8217;.</p>
<p>As before, you can see a video presentation as well or instead of the blog post below.</p>
<p><object width="400" height="300" data="http://vimeo.com/moogaloop.swf?clip_id=1972408&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=0&amp;color=&amp;fullscreen=1" type="application/x-shockwave-flash"><param name="allowfullscreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://vimeo.com/moogaloop.swf?clip_id=1972408&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=0&amp;color=&amp;fullscreen=1" /></object><br />
<a href="http://vimeo.com/1972408?pg=embed&amp;sec=1972408">Design Monday #2 &#8211; Lunch!</a> from <a href="http://vimeo.com/frankieroberto?pg=embed&amp;sec=1972408">frankieroberto</a> on <a href="http://vimeo.com/?pg=embed&amp;sec=1972408">Vimeo</a>.</p>
<p><strong>Lunch</strong> is something that is taken for granted, embedded in daily routines. This week&#8217;s Design Monday session was about lunch and how it can be improved. Not the foodstuff but the &#8216;event&#8217;, the planning and organising and managing of lunch. Why? Well it&#8217;s something that is undertaken everyday, is highly social and yet is fraught with &#8216;issues&#8217; (we took on the subject after a spate of tweets saying what people were doing for lunch, what they were eating, who they were meeting etc.). It seemed ripe for a makeover.</p>
<p>The &#8216;problem&#8217; with lunch covers a few things: who to have lunch with, where to have lunch, what to eat. We take a lot of this for granted.  Spontaneous &#8216;coming togethers&#8217; around lunch do happen, but invariably there is some planning involved &#8211; the who, what, where, when, how and why. Some of this is routine &#8211; you go to the same sandwich shop because it&#8217;s nearby and get one of a few different sandwiches (which you&#8217;ve trialled), at a certain time (when your contract allows and when the shop is presumably not to busy) and eat at your desk. We did some quick persona work and cam up with Jenny, 33, a single administrator in a big office of 50 people in central London. She treats herself three times a week for lunch &#8216;out&#8217;. Because she doesn&#8217;t go every day she has to <em>negotiate</em> who to go with, where to go and what to eat.</p>
<p>Jenny is subject to diet &#8216;fads&#8217;. Food is both a passion and a curse. Choosing what to eat is not a simple task.  She&#8217;ll have in mind foods that are healthy, or non-fatty but won&#8217;t be able to make a decision on what to eat until she knows where she is eating and what they have on the menu.  Planning ahead is hard, because her lunch will depend on what she ate the previous night and also had for lunch yesterday. &#8216;Guilt&#8217; for perceived weakness at following an &#8216;ideal&#8217; is a strong emotional factor. Other decision making factors about where to eat and with whom, might include who you &#8216;like&#8217; and who is going out to lunch, time taken to get to the shop and waiting time at the shop and the menu at the shop (items and cost).</p>
<p>Let&#8217;s tackle each of these problems in turn.</p>
<p>Who you like and if they are going for lunch. Having collectively worked in lots of offices, this is a major topic of conversation before lunch.  Knowing what other people are doing is really important, especially to Jenny, for whom lunch is a &#8216;treat&#8217; and who wants to spend her time well.  But have you noticed that broaching who is going for lunch is a difficult thing in a large office.  You don&#8217;t want to invite Sally openly because she sits next to Pete and you don&#8217;t like Pete and you don&#8217;t want to spend lunch with him.  And Claire always brings Amanda, her best friend and they&#8217;re a pain when they&#8217;re together.  The problem is one of <strong>social &#8216;awkwardness&#8217;</strong>, you&#8217;re not able to ask people because you&#8217;re not always sure the response is one you&#8217;ll want and because you don&#8217;t want to be seen to be &#8216;needing&#8217; to have someone to go with.  It&#8217;s a faff.</p>
<p><strong>Solution</strong>: Creating a reason to invite people to lunch &#8211; giving people an excuse.  That would help.  Then <em>you&#8217;re</em> not asking them, merely letting them know of a good reason to do something. This might sound minor but a lot of so-called social software totally fails to understand the &#8216;soft&#8217; side of the social in design work.</p>
<p>The Menu. Menu items change, specials are offered and ingredients run out.  Point-of-sale (POS) is where most people decide what to eat.  People don&#8217;t choose their lunch online and then collect it.  This is mainly because choosing the venue is a collective decision embarked on as lunch starts but also because the &#8216;choosing&#8217; is <em>good</em>.  People like to buy and they make decisions that hinge on what their friends are eating. Cumulative advantage prevails amongst food as well as <a href="http://www.nytimes.com/2007/04/15/magazine/15wwlnidealab.t.html">music</a> and people&#8217;s buying decisions are informed by what their friends buy and eat.  So, the guilt that Jenny could have about having a perceived unhealthy meal is offset if her friends also choose to eat &#8216;unhealthily&#8217;.  And that sort of decision making is negotiated by seeing how people behave, talking about it and agreeing collectively. It&#8217;s not simple.</p>
<p><strong>Solution 1:</strong> You can start to segment the audience. Some people will be more price sensitive than others.  Allowing people to &#8216;book&#8217; their lunch in advance provides two benefits. Firstly, it allows them to create &#8216;groups&#8217; around lunch. Invite friends to participate in choosing their lunch, see what your friends are thinking of buying and potentially help them by tying this into diet menus (Atkins, Weightwatchers, whatever&#8230;).  Opening people up to trialling new menu items could be a possibility here, as you then have an implicit recommendation engine as people see what their colleagues are trying.  Secondly, it allows people to save money and budget their lunch over a period (week, month etc.).  Weekly email prompts could be supported by daily text messages as an option if your advance booking is due. Sure, this a web based solution and that &#8216;feels&#8217; like using a sledgehammer to crack a nut.  It&#8217;s a big office solution.</p>
<p><strong>Solution 2:</strong> Provide better labelling and slicing of the menu.  Slice them up by popularity (wouldn&#8217;t that be good to know &#8211; you could see their &#8216;special&#8217; as chosen by the people), calories, user rating / feedback.  Having a simple board to rate menu items (with a sticker system) would be fun and interactive. Moreover, you could take suggestions from your customers, where people opt for it to be on next weeks menu.  These are simple &#8220;web sensibilities&#8221; that people are beginning to expect in the offline world, so why not at lunch, in a cafe?</p>
<p>Waiting times. These can generally be guessed at and understood. 12:30 &#8211; 1:30 is going to be busy. That&#8217;s &#8216;lunch time&#8217;.  However, lunch &#8216;shops&#8217; are often very bad at providing tell tale signs of waiting times.</p>
<p><strong>Solution </strong>: Leisure/theme parks inform people of waiting times for rides really well.  They tell you waiting times, physically, by embedding it in the queue!</p>
<p><a href="http://www.flickr.com/photos/dan4th/2553127409/"><img class="mt-image-center" style="margin: 0pt auto 20px; text-align: center; display: block;" src="http://www.rattlecentral.com/waittime.jpg" alt="waittime.jpg" width="500" height="375" /></a></p>
<p>Lunch shops don&#8217;t do<br />
this because I guess some things take longer to process than other<br />
things. You can&#8217;t measure waiting times well enough.  Although <a href="http://www.subway.co.uk">Subway</a><br />
have got their sandwich processing down to a fine art (and a lengthy<br />
training programme).  They can do it.   So others should be able to<br />
to.  People would then be able to make better informed decisions about<br />
whether to get their lunch there.  You could then have two &#8216;streams&#8217; -<br />
one for custom orders and one for ready made &#8216;standard&#8217; orders.</p>
<p>It&#8217;d be good to have your feedback on this.  Have you seen other solutions, internet sensibilities being catered for&#8230; Where you go for lunch, and how do you manage communal office lunching?</p>
<p><strong>Update:</strong> We&#8217;ve just come across <a href="http://www.nike.com/playmaker/">Nike Playmaker</a>, a web service that helps you to organise football matches by sending out invites to friends, selecting a pitch, and tracking responses. Seems pretty similar to what we were suggesting for a lunch-organising service.</p>
<p>Playmaker also supports text message reminders and post-match &#8216;banter&#8217;. Pretty nice. Services like this help to make organising social events that bit easier. They might also remove some of the stigma of &#8216;being the officious person who does all the organising&#8217;, as the website becomes the entity that nags people with reminders, rather than you.</p>
<p>This video does a good job of explaining the Playmaker service:</p>
<p><object width="425" height="344" data="http://www.youtube.com/v/V1sI7V208sA&amp;hl=en&amp;fs=1" type="application/x-shockwave-flash"><param name="allowFullScreen" value="true" /><param name="src" value="http://www.youtube.com/v/V1sI7V208sA&amp;hl=en&amp;fs=1" /><param name="allowfullscreen" value="true" /></object></p>
]]></content:encoded>
			<wfw:commentRss>http://www.rattlecentral.com/blog/2008/10/design-monday-2-lunch/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Talk [with just text and images]</title>
		<link>http://www.rattlecentral.com/blog/2007/09/talk-with-just-text-and-images</link>
		<comments>http://www.rattlecentral.com/blog/2007/09/talk-with-just-text-and-images#comments</comments>
		<pubDate>Mon, 24 Sep 2007 17:29:15 +0000</pubDate>
		<dc:creator>James Boardwell</dc:creator>
				<category><![CDATA[conferences]]></category>
		<category><![CDATA[consumption]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[NMSI]]></category>
		<category><![CDATA[science museum]]></category>
		<category><![CDATA[talk]]></category>

		<guid isPermaLink="false">http://www.rattlecentral.com/?p=23</guid>
		<description><![CDATA[I gave a talk at the science museum a week or so ago. I think I left the audience behind because I assumed a greater level of knowledge than I perhaps should have and because I tried to cover too much ground. Anyway, it was an interesting couple of days with talks from a range [...]]]></description>
			<content:encoded><![CDATA[<p><a href="/images/oldblog/slide_blog.jpg"><img alt="slide_blog.jpg" src="/images/oldblog/slide_blog-thumb.jpg" width="480" height="324" /></a><br />
I gave a talk at the science museum a week or so ago.  I think I left the audience behind because I assumed a greater level of knowledge than I perhaps should have and because I tried to cover too much ground.  Anyway, it was an interesting couple of days with talks from a range of people including <a href="http://www.mysteryexperience.com/">Bryan Kennedy </a>from the Museum of Minnesota, who was excellent.  Thanks to Dave &#038; Jane for the invite.<br />
<a href="http://www.slideshare.net/technogoggles/social-networks-and-experience-design-117258/download">Download the slideshare file [11mb PDF]</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rattlecentral.com/blog/2007/09/talk-with-just-text-and-images/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>UI</title>
		<link>http://www.rattlecentral.com/blog/2007/03/ui</link>
		<comments>http://www.rattlecentral.com/blog/2007/03/ui#comments</comments>
		<pubDate>Thu, 01 Mar 2007 16:32:51 +0000</pubDate>
		<dc:creator>James Boardwell</dc:creator>
				<category><![CDATA[design]]></category>
		<category><![CDATA[cafe]]></category>
		<category><![CDATA[UID]]></category>

		<guid isPermaLink="false">http://www.rattlecentral.com/?p=41</guid>
		<description><![CDATA[You can strip away the layers of organisational structure in UID work to create a nice functional flow. But sometimes it&#8217;s good to keep it there. Sometimes that history is good, it adds to the experience This is Forge Dam cafe in Sheffield. It makes good tea.]]></description>
			<content:encoded><![CDATA[<p>You can strip away the layers of organisational structure in UID work to create a nice functional flow.  But sometimes it&#8217;s good to keep it there.  Sometimes that history is good, it adds to the experience <img src='http://www.rattlecentral.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
<img alt="forge_dam_cafe.gif" src="/images/oldblog/forge_dam_cafe.gif" width="500" height="375" /><br />
This is Forge Dam cafe in Sheffield.  It makes good tea.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.rattlecentral.com/blog/2007/03/ui/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
