<?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>Frankly, Green + Webb &#187; hints and tips</title>
	<atom:link href="http://www.franklygreenwebb.com/category/hints-and-tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.franklygreenwebb.com</link>
	<description>Helping organisations use mobile in smart ways to connect with their audiences</description>
	<lastBuildDate>Sun, 28 Apr 2013 20:38:54 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
		<item>
		<title>Mobile Interpretation and the importance of Stakeholders</title>
		<link>http://www.franklygreenwebb.com/2012/02/01/mobile-interpretation-and-the-importance-of-stakeholders/</link>
		<comments>http://www.franklygreenwebb.com/2012/02/01/mobile-interpretation-and-the-importance-of-stakeholders/#comments</comments>
		<pubDate>Wed, 01 Feb 2012 17:13:47 +0000</pubDate>
		<dc:creator>Lindsey</dc:creator>
				<category><![CDATA[hints and tips]]></category>
		<category><![CDATA[speaking]]></category>

		<guid isPermaLink="false">http://www.franklygreenwebb.com/?p=541</guid>
		<description><![CDATA[We’ve been lucky enough to have a workshop proposal accepted at Museums and the Web this year in San Diego. It’s a workshop we’ll be leading with Sandy Goldberg from sgscripts entitled “Bringing your Stakeholders Onboard: Delivering Vibrant Mobile Projects” We planned the workshop, after a few clients had talked to us about the challenges [...]]]></description>
			<content:encoded><![CDATA[<p>We’ve been lucky enough to have a workshop proposal accepted at <a href="http://www.museumsandtheweb.com/mw2012">Museums and the Web </a>this year in San Diego. It’s a workshop we’ll be leading with <a href="http://sgscripts.net/">Sandy Goldberg from sgscripts</a> entitled <a href="http://www.museumsandtheweb.com/mw2012/workshops/bringing_your_stakeholders_onboard_deliveri">“Bringing your Stakeholders Onboard: Delivering Vibrant Mobile Projects”</a></p>
<p><a href="http://www.flickr.com/photos/library_of_congress/2179067948/"><img class="aligncenter size-medium wp-image-542" title="2179067948_7fb98a30c1_o" src="http://www.franklygreenwebb.com/wp-content/uploads/2012/02/2179067948_7fb98a30c1_o-300x230.jpg" alt="" width="300" height="230" /></a></p>
<p>We planned the workshop, after a few clients had talked to us about the challenges they were facing pulling mobile projects together and facilitating the collaboration, which is so often needed. I’m pretty sure that most projects need some form of collaboration but it seems to be that in-gallery digital interpretation, and in particular mobile, needs input from a particularly wide group to ensure a successful roll out. We regularly work on projects that involve the input of as many as seven different departments and ensuring they all feel ownership of the project is a real challenge. And I’ve seen many a project that could have been transformed from poor to good or good to great with just a little more collaboration up front.</p>
<p>Getting the right people involved at the right time can often address those challenges faced at the beginning of a project:</p>
<ul>
<li>How do we make sure we have the right information in there without being overwhelming?</li>
<li>How do we create the content and keep it up-to-date when we have little budget?</li>
<li>How do you make sure the technical system does what it needs to do?</li>
</ul>
<p>Or, even more common, the questions that get asked once the system is up and running a while and the impact of decisions made at the development stage are playing out on the floor in the gallery:</p>
<ul>
<li>How do we stop this negatively impacting on visitor flow?</li>
<li>What happens if the visitor has a problem, how can they get help?</li>
<li>How do we get more people using the system?</li>
<li>Staff are reluctant to promote the system because they are worried it will reduce shop sales/attendance at live talks</li>
</ul>
<p>One of the toughest things in our experience is gauging when to bring people into the process and what level of involvement they should/could have.  We all enjoy the creative input of our colleagues but fear those huge brainstorming meetings where everyone goes around in circles o even worse, stakeholders holding up or derailing the whole project.</p>
<p>Here are a couple of ideas on how to work with your stakeholders. We hope you’ll join us in <a href="http://www.museumsandtheweb.com/mw2012/workshops/bringing_your_stakeholders_onboard_deliveri">San Diego</a> to hear more.</p>
<p><strong>Cast your net wide early on</strong></p>
<p>At this point you may well have identified the broad vision or goal for the project. What you need next is support and to identify the parameters you’ll be working within (refine vision, flush out challenges and boundaries, identify which teams we are talking about) Ensuring everyone is on-board with this focus/vision will make everything a lot easier later on. For example, ensuring that the audience is agreed on and any operational challenges of using mobile devices can help you to ensure that curators are giving you the right level of content when it comes to development.  Recently we worked with the Science Museum to develop a schools programme. Including the person who manned the phones and took the School bookings helped us to stay focussed on the needs of the teachers and how the project could be sold to them without putting them off with complicated talk of mobile technologies.</p>
<p><strong>Make sure they are comfortable with the technology</strong></p>
<p>We’d also suggest that everyone on the team is given access to a mobile device for a few weeks to see how they use it, what do they do on it, where they use it. The number of design meetings we have had where the leader of the group uses mobile ALL the time while the rest are unfamiliar and lack confidence is frightening.</p>
<p><strong>Testing the Idea</strong></p>
<p>Mobile experiences inside the museum succeed and fail more often on the practicality of operations than anything else and don’t be fooled, this is as much to do with the pace and location of content as it is to do with signage. Midway through the process you’ll want to start testing concept and – most importantly &#8211; asking the group you have involved to help you solve the problems using their expertise. This is where your visitor services and marketing teams will come into their own &#8212; ignore their advice at your peril!</p>
<p><strong>Everyone Involved</strong></p>
<p>Towards the end of the development process, involve as many people in testing as possible. Particularly volunteers and those who will come into contact with your visitors &#8211; the impact of engaging them and showing them how this mobile experience will benefit the visitors and fit into their daily lives will improve your take up rate more than any signs, websites or leaflets.</p>
<p>For more information about the workshop – have a look here: <a href="http://www.museumsandtheweb.com/mw2012/workshops/bringing_your_stakeholders_onboard_deliveri">Museums and the Web 2012 (MW2012): Workshops</a>
<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.franklygreenwebb.com%2F2012%2F02%2F01%2Fmobile-interpretation-and-the-importance-of-stakeholders%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.franklygreenwebb.com%2F2012%2F02%2F01%2Fmobile-interpretation-and-the-importance-of-stakeholders%2F&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
]]></content:encoded>
			<wfw:commentRss>http://www.franklygreenwebb.com/2012/02/01/mobile-interpretation-and-the-importance-of-stakeholders/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Designing Effective Content for Mobile in Museums</title>
		<link>http://www.franklygreenwebb.com/2011/03/23/designing-effective-content-for-mobile-in-museums/</link>
		<comments>http://www.franklygreenwebb.com/2011/03/23/designing-effective-content-for-mobile-in-museums/#comments</comments>
		<pubDate>Wed, 23 Mar 2011 08:00:19 +0000</pubDate>
		<dc:creator>Lindsey</dc:creator>
				<category><![CDATA[hints and tips]]></category>
		<category><![CDATA[speaking]]></category>

		<guid isPermaLink="false">http://www.franklygreenwebb.com/?p=444</guid>
		<description><![CDATA[We probably need to work on a snappier title, but this was the presentation Alyson made at Museums Association conference &#8216;Creating Digital Content&#8217; I&#8217;m currently digging her in the ribs to write a bit more here &#8211; but in the meantime, have a look see here . The version on Slideshare has the invaluable speaker [...]]]></description>
			<content:encoded><![CDATA[<p>We probably need to work on a snappier title, but this was the presentation Alyson made at Museums Association conference &#8216;Creating Digital Content&#8217; I&#8217;m currently digging her in the ribs to write a bit more here &#8211; but in the meantime, have a look see here . The <a href="http://www.slideshare.net/franklygreenwebb/designing-effective-content-for-mobile-in-museums">version on Slideshare</a> has the invaluable speaker notes too&#8230;</p>
<div id="__ss_7334070" style="width: 425px;"><object id="__sse7334070" classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="425" height="355" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowScriptAccess" value="always" /><param name="src" value="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=fgwmadigicontentv2-110321084640-phpapp02&amp;stripped_title=designing-effective-content-for-mobile-in-museums&amp;userName=franklygreenwebb" /><param name="name" value="__sse7334070" /><param name="allowfullscreen" value="true" /><embed id="__sse7334070" type="application/x-shockwave-flash" width="425" height="355" src="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=fgwmadigicontentv2-110321084640-phpapp02&amp;stripped_title=designing-effective-content-for-mobile-in-museums&amp;userName=franklygreenwebb" name="__sse7334070" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>
<div style="padding: 5px 0 12px;">View more presentations from <a href="http://www.slideshare.net/franklygreenwebb">Frankly, Green + Webb</a></div>
</div>
<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.franklygreenwebb.com%2F2011%2F03%2F23%2Fdesigning-effective-content-for-mobile-in-museums%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.franklygreenwebb.com%2F2011%2F03%2F23%2Fdesigning-effective-content-for-mobile-in-museums%2F&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
]]></content:encoded>
			<wfw:commentRss>http://www.franklygreenwebb.com/2011/03/23/designing-effective-content-for-mobile-in-museums/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How do you stop visitors staring at the tiny screen?</title>
		<link>http://www.franklygreenwebb.com/2011/02/04/how-do-you-stop-visitors-staring-at-the-tiny-screen/</link>
		<comments>http://www.franklygreenwebb.com/2011/02/04/how-do-you-stop-visitors-staring-at-the-tiny-screen/#comments</comments>
		<pubDate>Fri, 04 Feb 2011 15:37:23 +0000</pubDate>
		<dc:creator>Lindsey</dc:creator>
				<category><![CDATA[hints and tips]]></category>

		<guid isPermaLink="false">http://www.franklygreenwebb.com/?p=345</guid>
		<description><![CDATA[The iPhone is a beautiful, seductive but jealous mistress that craves your attention, and enslaves you to its jaw-dropping gorgeousness at the expense of the world around you. This quote comes from a  post on the Magical Nihilism blog (via this post by berg) discovered following a certain amount of &#8216;Friday afternoon noodling around&#8217; It [...]]]></description>
			<content:encoded><![CDATA[<blockquote><p>The iPhone is a beautiful, seductive but jealous mistress that craves your attention, and enslaves you to its jaw-dropping gorgeousness at the expense of the world around you.</p></blockquote>
<p>This quote comes from a  <a href="http://magicalnihilism.com/2007/11/15/lost-futures-unconscious-gestures/">post</a> on the Magical Nihilism blog (via this <a href="http://berglondon.com/blog/2011/01/14/asleep-and-awake/">post</a> by berg) discovered following a certain amount of &#8216;Friday afternoon noodling around&#8217;</p>
<p>It halted the noodling as it resonated with me so much, in particular <em>&#8216;<strong>At the expense of the world around you..</strong>.</em>&#8216; It occurred to me that we&#8217;re currently designing apps for devices that possibly &#8216;<strong>enslave</strong>&#8216;.  I&#8217;m not particularly sure we really want to &#8216;enslave&#8217; visitors to a tiny screen when they are making a special visit to a particular museum/gallery/historic site, possibly paying to enter, for a once in a lifetime visit. Personally, I want to look at the world around me, experience the space and the stories.</p>
<p>One of our key questions when  designing content and concepts for mobile in-gallery experiences (and one of the reasons that I enjoy so much about the work we do) is:</p>
<p><strong>How do we make sure that the visitor remains in the space and not transfixed by the tiny screen in front of them?</strong></p>
<p>For me, there&#8217;s something very magical about entering a space and having a tiny machine that helps you navigate, interact and understand that space. However, when that machine demands you give it maximum attention and you lose contact with that space &#8211; there is nothing worse. I haven&#8217;t come to your house just to be barked at by your dog.</p>
<p>When we work on multimedia tours or guides we work to a really simple, tried and tested rule &#8211; more audio than video. In fact, we use a ratio; maximum 30% screen time and 70% audio i.e. the visitor should only be looking at the screen for 30% of the time otherwise they feel dislocated from the experience they have come to enjoy.</p>
<p>This definitely works if you are providing content, particularly linear tour content with audio component. But, as Ed Rodley mentions <a href="http://exhibitdev.wordpress.com/2011/02/01/mobile-tours/">here</a>, museums are, and increasingly need to, move beyond the tour format when it comes to apps and explore more of the functionality available. The opportunities are endless but that key design principle of keeping visitors in the space makes it all super interesting.</p>
<p>I&#8217;m really looking forward to the next couple of years as these challenges and opportunities start to be addressed, as a new set of principles and ideas are tried and tested.
<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.franklygreenwebb.com%2F2011%2F02%2F04%2Fhow-do-you-stop-visitors-staring-at-the-tiny-screen%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.franklygreenwebb.com%2F2011%2F02%2F04%2Fhow-do-you-stop-visitors-staring-at-the-tiny-screen%2F&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
]]></content:encoded>
			<wfw:commentRss>http://www.franklygreenwebb.com/2011/02/04/how-do-you-stop-visitors-staring-at-the-tiny-screen/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Seven tips for moving past the &#8216;no phone&#8217; rule</title>
		<link>http://www.franklygreenwebb.com/2011/02/02/seven-tips-for-moving-past-the-no-phone-rule/</link>
		<comments>http://www.franklygreenwebb.com/2011/02/02/seven-tips-for-moving-past-the-no-phone-rule/#comments</comments>
		<pubDate>Wed, 02 Feb 2011 22:41:40 +0000</pubDate>
		<dc:creator>Lindsey</dc:creator>
				<category><![CDATA[hints and tips]]></category>

		<guid isPermaLink="false">http://www.franklygreenwebb.com/?p=273</guid>
		<description><![CDATA[We&#8217;ve had a few chats over the last couple of weeks with people who are nervous about launching a mobile in-gallery experience because their visitors aren&#8217;t currently able to use phones at all. In the past most museums operated a simple ‘no phone’ policy in their galleries. A simple rule, easily understood. But, as phones [...]]]></description>
			<content:encoded><![CDATA[<p>We&#8217;ve had a few chats over the last couple of weeks with people who are nervous about launching a mobile in-gallery experience because their visitors aren&#8217;t currently able to use phones at all.</p>
<p><a href="http://www.flickr.com/photos/jonlewisphotography/3706069312/"><img title="No" src="http://farm3.static.flickr.com/2487/3706069312_fbc5d8fdb9.jpg" alt="" width="500" height="375" /></a></p>
<p>In the past most museums operated a simple ‘no phone’ policy in their galleries. A simple rule, easily understood. But, as phones have morphed from simple devices for making voice calls to ones with cameras, access to the internet and a multitude of applications, things have got a little more complicated.</p>
<div id="_mcePaste">If your collection contains works from the recent past you may well have been wrestling with how to manage the combination of phone cameras, mobile phone tours and artworks that are still in copyright. Or perhaps, you’re a member of the operational or front of house team dealing with a confusing set of old rules that no longer work when faced with an audience who tweet, text, listen and play from their mobile device. If so, you have my sympathy &#8211; been there and have the scars to prove it.</div>
<div id="_mcePaste">Here are my top hints and tips culled from my experience:</div>
<h3>1. Identify who&#8217;s going to ‘own’ the policy.</h3>
<div id="_mcePaste">Often one of the biggest challenges in establishing a new policy in this area is the number of departments involved each with their own concerns and needs. Without someone taking the lead &#8211; and the risk of it not being quite right first time &#8211; nothing will change.  A confused or out of date policy will, inevitably, lead to conflict with visitors. This is not an issue you can ignore. The caveat is that everyone who is affected in the organisation needs to be consulted and their needs considered.</div>
<h3>2. Make sure the final policy is clear and straightforward.</h3>
<div id="_mcePaste">Everyone in the organisation needs to understand what the policy is and why and be able to communicate that, so no lengthy, complex technical explanations.</div>
<h3>3. Accentuate the positive.</h3>
<div id="_mcePaste">Write a policy that includes the type of behaviour you would like to encourage rather than focusing solely on what visitors can’t do. Framing your conversations with staff and visitors in terms of what is possible rather than what isn’t can transform everyone’s perception of the issue: “We’d love you to tweet about your experience today” beats a whole heap of negatives every time.</div>
<h3>4. Share the policy with everyone</h3>
<div id="_mcePaste">I learnt the hard way that creating a mobile phone policy is no use at all if the only people who know about it are the three who made it! Once you&#8217;ve shared it with the team who work directly with visitors, share it with the teams who may use mobile as part of their service (hint: that&#8217;s usually everyone!)</div>
<h3>5. Don’t just focus on the ‘what’, share the ‘why’.</h3>
<div id="_mcePaste">If everyone understands the policy and the reasoning behind it they should feel more confident in discussing the issues with visitors and able to avoid confrontations.  Help them identify welcome behaviours versus unwelcome, encourage them to try out and play with smartphones if they haven’t already, role play situations.</div>
<h3>6. Identify where you can best share the policy</h3>
<div id="_mcePaste">We all know that signage only works a very small amount of the time. You might want to consider adding the message to any content you are providing on mobile or asking staff at the entrance to mention it to visitors. But remember, keep it positive where you can &#8211; for example you might want to consider identifying any images where the visitor can take photos.</div>
<h3>7. Admit you won&#8217;t catch them all</h3>
<div id="_mcePaste">If someone is very determined to take a photo they will and there’s not a great deal you can do regardless of your policy. A phone may in fact be the best way for them to do this &#8211; the resulting image is unlikely to be of print quality!</div>
<div>Do you have any hints and tips on how to use mobile in cultural sites with copyright issues? Whose responsible for the mobile policy in your organisation? Have you seen a particular example of a mobile policy that worked?</div>
<div>Photo by <a href="http://www.flickr.com/photos/jonlewisphotography/">JonnyPhoto</a> &#8211; used under Creative Commons</div>
<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.franklygreenwebb.com%2F2011%2F02%2F02%2Fseven-tips-for-moving-past-the-no-phone-rule%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.franklygreenwebb.com%2F2011%2F02%2F02%2Fseven-tips-for-moving-past-the-no-phone-rule%2F&amp;style=compact&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
]]></content:encoded>
			<wfw:commentRss>http://www.franklygreenwebb.com/2011/02/02/seven-tips-for-moving-past-the-no-phone-rule/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
