<?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>Tim&#039;s Blog &#187; opengov</title>
	<atom:link href="http://www.timdavies.org.uk/tags/opengov/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.timdavies.org.uk</link>
	<description>working for social change; thinking about the details</description>
	<lastBuildDate>Sun, 22 Jan 2012 17:47:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>OpenGov: One big challenge? Or a thousand small hurdles</title>
		<link>http://www.timdavies.org.uk/2009/04/22/opengov-one-big-challenge-or-a-thousand-small-hurdles/</link>
		<comments>http://www.timdavies.org.uk/2009/04/22/opengov-one-big-challenge-or-a-thousand-small-hurdles/#comments</comments>
		<pubDate>Wed, 22 Apr 2009 07:02:25 +0000</pubDate>
		<dc:creator>Tim</dc:creator>
				<category><![CDATA[E-Democracy]]></category>
		<category><![CDATA[digitalengagement]]></category>
		<category><![CDATA[interactivecharter]]></category>
		<category><![CDATA[opengov]]></category>
		<category><![CDATA[smallchallenges]]></category>

		<guid isPermaLink="false">http://www.timdavies.org.uk/?p=2382</guid>
		<description><![CDATA[Update &#8211; July 2009: This list of 50 Hurdles has evolved into the &#8216;Interactive Charter&#8216; (an attempt to create a clear statement of intent for open government) and &#8216;Social Strategy&#8216; (a toolkit of practical resources for sorting it out). Keep an eye on posts tagged &#8216;interactivecharter&#8216; on this blog for the latest updates. The original [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Update &#8211; July 2009: </strong>This list of 50 Hurdles has evolved into the &#8216;<a href="http://www.interactivecharter.org">Interactive Charter</a>&#8216; (an attempt to create a clear statement of intent for open government) and &#8216;<a href="http://www.practicalparticipation.co.uk/socialstrategy">Social Strategy</a>&#8216; (a toolkit of practical resources for sorting it out). Keep an eye on posts tagged <a href="http://www.timdavies.org.uk/tags/interactivecharter">&#8216;interactivecharter</a>&#8216; on this blog for the latest updates.</p>
<hr /><strong>The original post: </strong></p>
<p>What&#8217;s the big challenge to using new technology for mobilisation / communication around social issues, where government or large existing organisations are to be players in creating change?</p>
<p>Working with front-line professionals in local government over the last couple of months, I&#8217;ve been coming to see that:</p>
<ul>
<li>The big challenges are not about technology &#8211; they are about the content and the process of mobilisation and communication.</li>
<li>When it comes to technology we&#8217;ve not got one big challenge we&#8217;ve got 100s of small challenges &#8211; and we&#8217;ve got no systematic way of dealing with them.</li>
</ul>
<p>When all these small challenges stack up &#8211; the chance of staff members or teams in local or national government organisations and agencies being able to effectively engage with online-enabled policy making shrinks and shrinks.</p>
<p>Of course &#8211; as small challenges &#8211; I&#8217;m sure they can all be overcome. And one of the first steps to overcoming a challenge is knowing it is there &#8211; so below are 50 of the challenges I&#8217;ve encountered since the start of this year.</p>
<p><strong><span style="text-decoration: underline;">50 Small Hurdles to Online Engagement in Government</span></strong></p>
<p>(<strong>Update 4th May 2009:</strong> There is now <a href="http://www.practicalparticipation.co.uk/wiki/socialstrategy:start">a wiki set-up with all these hurdles listed, and space for you to read/add shared learning about overcoming them&#8230;</a>)</p>
<p>INTERNET ACCESS</p>
<ol>
<li>Access to Web 2.0 sites is blocked or filtered;</li>
<li>Requesting that a website is unblocked requires a form to be filled in and the request may not be actioned for 24 hours or more;</li>
<li>A site that has previously been unblocked is suddenly blocked again;</li>
<li>A site is only unblocked for the computer a staff member usually sits at &#8211; and they are unable to access Web 2.0 Sites from another part of the office, or another desk;</li>
<li>Web 2.0 Sites can only be accessed during lunch hours;</li>
<li>Managers see abuse of ICT resources as an ICT issue rather than a management issue;</li>
<li>ICT staff see access to Web 2.0 sites as an issue for ICT decision making, rather than for team leaders and managers;</li>
<li>There is no capacity to provide staff with internet-enabled mobile phones, even if a business case can be made;</li>
<li>Staff are not aware of the ICT, internet access and mobile phone/internet access resources they can legitimately ask for;</li>
<li>Permission to use Web 2.0 is granted ad-hoc but not enshrined in policy, so a change in ICT manager could make access more difficult;</li>
</ol>
<p>OFFICE TECHNOLOGY</p>
<ol>
<li>Computer only have out-of-date Internet Browsers (E.g. IE6);</li>
<li>Staff cannot change their browsers home-page;</li>
<li>Staff cannot install browser plug-ins or add-ons, and key plug-ins like Flash are out-of-date versions;</li>
<li>E-mail sign-up confirmations from Web 2.0 sites regularly get caught in spam filters;</li>
<li>Staff cannot install desktop widgets and utility software (e.g. Twitter clients, RSS readers etc.)</li>
<li>Office computers have no ability to play sound;</li>
<li>There is no easy way to get a photo onto an office computer. For example, a personal photo to use as a profile picture online;</li>
<li>Any customisations staff add to their computer log-in are regularly lost;</li>
<li>There is no WiFi in meeting rooms, and guests cannot get access to the internet in the building;</li>
<li>There is a one-size fits all IT policy;</li>
</ol>
<p>SYSTEMS &amp; PROCEDURES</p>
<ol>
<li>There are no finance procedures or company credit cards to pay for low-cost online subscription services;</li>
<li>There are no systems in place for backing up content from Web 2.0 tools;</li>
<li>There is no secure password vault that can be used to keep track of &#8216;corporate&#8217; memberships of Web 2.0 sites;</li>
<li>There is no agreed way of notifying other staff members of plans for using Web 2.0 tools;</li>
<li>There are no policies or procedures for responding to positive or negative online comments;</li>
<li>There is no processes for carrying out CRB or Independent Safeguarding Authority checks on staff or sub-contractors involved in the use of Social Media to engage with young people or vulnerable adults;</li>
</ol>
<p>POLICY &amp; GUIDANCE</p>
<ol>
<li>There are no policies on personal use of Social Networks and Social Media sites;</li>
<li>There is no accessible guidance available to staff on personal use of Social Networks and Social Media sites;</li>
<li>There is no policy on Safeguarding and Child Protection in digital environments;</li>
<li>There is no policy on Data Protection in digital environments &#8211; and no guidance on items of data which should not be shared in digital environments;</li>
<li>There are no policies on appropriate levels for official staff engagement with Web 2.0</li>
<li>Consent forms and model release forms make no mention of possibly sharing photos or videos from events and activities online;</li>
</ol>
<p>ORGANISATIONAL CULTURE</p>
<ol>
<li>Senior managers see Web 2.0 and the Social Web as something to be scared of;</li>
<li>Senior managers see Web 2.0 as a passing fad, or at best a persistent distraction and minority interest;</li>
<li>Staff see Web 2.0 as an extra burden to add to already busy and pressured days;</li>
<li>Ideas from outside the organisations are treated with suspicion;</li>
<li>The organisation wants to be in control of any discussions that take place about it online;</li>
<li>The organisation wants to moderate every discussion that it is any way responsible to convening or starting;</li>
<li>The organisation wants to put it&#8217;s brand front-and-centre in every online engagement;</li>
<li>Service-user engagement is not valued;</li>
</ol>
<p>BASIC TECHNICAL SKILLS</p>
<ol>
<li>Staff have never received basic training in how a web browser, web addresses and search engines work;</li>
<li>Staff are not aware of tabbed web-browsing;</li>
<li>Staff do not make use of search tools;</li>
<li>Staff find it difficult to adapt to and remember new ways of working digitally;</li>
<li>Staff are not able to download, edit and upload images in web formats;</li>
<li>Staff do not know how to install new utility software or browser plug-ins;</li>
<li>Staff have no opportunities to share skills and develop their understanding of digital environments;</li>
</ol>
<p>LEADERSHIP &amp; MANAGEMENT</p>
<ol>
<li>Managers do not support staff exploration and experimentation with Web 2.0;</li>
<li>Managers take no ownership over exploration and experimentation with Web 2.0 and provide no support to their staff;</li>
<li>Managers react to initial teething problems with Web 2.0 engagement by shutting it all down and banning further exploration of the potential;</li>
</ol>
<p><strong>Your Challenges &amp; Your Solutions?</strong><br />
I know that not only can all these challenges be overcome &#8211; but they have been. Somewhere.</p>
<p>If you&#8217;ve overcome one of the challenges here &#8211; could you write 50 words on how you did it? Add it as a comment here or your own blog post including the tag &#8216;smallchallenges&#8217;.</p>
<p>Or perhaps you can add to the challenges list? Naming the challenges is the first step to overcoming them!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.timdavies.org.uk/2009/04/22/opengov-one-big-challenge-or-a-thousand-small-hurdles/feed/</wfw:commentRss>
		<slash:comments>40</slash:comments>
		</item>
	</channel>
</rss>

