<?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>Library &#38; Information Services &#187; user services goals</title>
	<atom:link href="http://sites.middlebury.edu/lis/tag/user-services-goals/feed/" rel="self" type="application/rss+xml" />
	<link>http://sites.middlebury.edu/lis</link>
	<description>We Bring Knowledge to You</description>
	<lastBuildDate>Wed, 22 May 2013 12:09:41 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>User Services Goal: Centralized Student Employment</title>
		<link>http://sites.middlebury.edu/lis/2010/01/28/us-goal-centralized-student-employment/</link>
		<comments>http://sites.middlebury.edu/lis/2010/01/28/us-goal-centralized-student-employment/#comments</comments>
		<pubDate>Thu, 28 Jan 2010 20:01:56 +0000</pubDate>
		<dc:creator>Nathan Burt</dc:creator>
				<category><![CDATA[Areas and Workgroups]]></category>
		<category><![CDATA[goal]]></category>
		<category><![CDATA[goals]]></category>
		<category><![CDATA[User Services]]></category>
		<category><![CDATA[user services goals]]></category>

		<guid isPermaLink="false">http://sites.middlebury.edu/lis/?p=20971</guid>
		<description><![CDATA[Goal Statement: Centralize student employment/ management/ training/ scheduling or some subset of that.  Shared training is for tasks already commonly shared across work areas – while cross-training might be an eventual outcome, this is not part of this goal. Consolidation &#8230; <a href="http://sites.middlebury.edu/lis/2010/01/28/us-goal-centralized-student-employment/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p><strong>Goal Statement: </strong>Centralize student employment/ management/ training/ scheduling or <span id="more-20971"></span> some subset of that.  Shared training is for tasks already commonly shared across work areas – while cross-training might be an eventual outcome, this is not part of this goal.</p>
<p>Consolidation of repetitive tasks related to student employment.  This provides uniform policies and procedures, and reduces staff hours allocated to these tasks.</p>
<p><strong>Deliverable:</strong></p>
<ul>
<li>User services student supervisors work as team to find commonalities in the process</li>
<li>Document timelines (numbers needed, when, hiring process, training)</li>
<li>Agree upon common payroll policy, scheduling tools, advertising, hiring, &amp; training</li>
<li>Identify areas of difference between work groups – and document these as well</li>
</ul>
<p><strong>Outcome:</strong></p>
<ul>
<li>Stress reduction by providing redundancy &amp; supporting one another</li>
<li>Anticipate consolidation of service points</li>
<li>Standardize process</li>
<li>Resource sharing</li>
</ul>
<p><strong>Delivery:</strong></p>
<p>Complete &#8211; Fall 2010</p>
<p>Milestones:</p>
<ul>
<li>Ongoing: Continuing customer service training</li>
<li>February 2010:<br />
Spring hires – team consulting with one another during job posting, interview, hiring, paperwork process</li>
<li>Summer 2010:<br />
Create a secondary training for overlaps in job descriptions</li>
</ul>
<p><strong>Resources:</strong></p>
<ol>
<li>Who is involved:<br />
Student supervisors for Library Circulation, branches, reserves, helpdesk, media services.<br />
Currently – Elin, Todd, Dan, Kellam, Shawn, &amp; Stewart.</li>
<li>Time:<br />
mostly the same as in the past, but allow for initial organizational meetings, and a bit more time when advertising, interviewing &amp; hiring.  Time required determined by team allocation of tasks to members.  Little if any additional money or materials – depending on team choices.<br />
Team approach will allow sharing of responsibilities with common resources – avoiding current challenges when staff are not available for these tasks.</li>
</ol>
<p><strong>Viability: </strong></p>
<ul>
<li>We have already demonstrated part of this goal with the current shared customer service training.  The rest is an extension of the same concept.</li>
<li>Challenges: buy-in of supervisors, finding shared time to work together</li>
<li>Opportunity: use of common tools (e.g. scheduling)</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://sites.middlebury.edu/lis/2010/01/28/us-goal-centralized-student-employment/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>User Services Goal &#8211; Establish SLAs with User Services/LIS</title>
		<link>http://sites.middlebury.edu/lis/2009/12/22/user-services-goal-establish-slas-with-user-serviceslis/</link>
		<comments>http://sites.middlebury.edu/lis/2009/12/22/user-services-goal-establish-slas-with-user-serviceslis/#comments</comments>
		<pubDate>Tue, 22 Dec 2009 19:31:38 +0000</pubDate>
		<dc:creator>Doreen Bernier</dc:creator>
				<category><![CDATA[LIS Staff Interest]]></category>
		<category><![CDATA[User Services]]></category>
		<category><![CDATA[user services goals]]></category>

		<guid isPermaLink="false">http://sites.middlebury.edu/lis/?p=19281</guid>
		<description><![CDATA[Goal:  Establish and publish Service Level Agreements (SLA) with every service point within User Services. The scope of this effort may extend beyond User Services in specific cases. Service Level Agreements (SLAs) do not currently exist in an official capacity within &#8230; <a href="http://sites.middlebury.edu/lis/2009/12/22/user-services-goal-establish-slas-with-user-serviceslis/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p style="text-align: left"><strong>Goal:</strong>  Establish and publish Service Level Agreements (SLA) with every service point within User Services. The scope of this effort may extend beyond User Services in specific cases.</p>
<p style="text-align: left">Service Level Agreements (SLAs) do not currently exist in an official capacity within User Services between our service points.  In addition this particular goal spans beyond User Services and spills over into an overall LIS scope.  Establishing SLAs between Workgroups will promote understanding, create efficiencies, and improve cross-teaming with Workgroups and within LIS.</p>
<p style="text-align: left"><strong>Deliverable:</strong>  </p>
<ul>
<li>
<div style="text-align: left">Establish agreements between identified Workgroups.</div>
</li>
<li>
<div style="text-align: left">Two party negotiations toward agreement(s)</div>
</li>
<li>
<div style="text-align: left">Rules established</div>
</li>
<li>
<div style="text-align: left"> Each party will self-regulate their commitments</div>
</li>
<li>
<div style="text-align: left"> Map-out key deliverables:</div>
</li>
</ul>
<p style="text-align: left"> Service provided:</p>
<ol style="text-align: left">
<li>Establish conditions and rules</li>
<li>Establish escalation paths</li>
<li>Establish responsibilities of both parties</li>
<li>Cost versus service trade-offs</li>
<li>How will service effectiveness be tracked/measured?</li>
<li>How will problems be resolved?</li>
<li>How will parties review and adjust SLAs</li>
</ol>
<p style="text-align: left">Implementation</p>
<ul>
<li>
<div style="text-align: left">Open-up communication channels</div>
</li>
<li>
<div style="text-align: left">Conflict prevention between groups and service points</div>
</li>
<li>
<div style="text-align: left">Living document(s) to be reviewed periodically and adjusted as needed</div>
</li>
<li>
<div style="text-align: left">Objective tool to determine service effectiveness</div>
</li>
<li>Establish the framework to be used: May 15, 2010</li>
<li>Identify parties to participate in this effort: June 15, 2010.</li>
<li> Outreach to our partners to be completed by: August 15, 2010</li>
<li> SLA drafts reviewed and accepted by participating groups: September 15, 2010</li>
<li> SLAs published and communicated to organization:  October 15, 2010</li>
</ul>
<p> <span><strong>Outcome:</strong>  </span></p>
<ul>
<li>
<div style="text-align: left"><span><span style="font-size: 10.5pt"><span style="font-family: Times New Roman">Open-up communication channels</span></span></span></div>
</li>
<li>
<div class="MsoNormal" style="text-align: left;margin: 0pt"><span style="font-size: 10.5pt"><span style="font-family: Times New Roman">Conflict prevention between groups and service points</span></span></div>
</li>
<li>
<div class="MsoNormal" style="text-align: left;margin: 0pt"><span style="font-size: 10.5pt"><span style="font-family: Times New Roman">Living document(s) to be reviewed periodically and adjusted as needed</span></span></div>
</li>
<li>
<div class="MsoNormal" style="text-align: left;margin: 0pt"><span>Objective tool to determine service effectiveness</span></div>
</li>
</ul>
<p style="text-align: left"><span><strong>Delivery:</strong>  <span> </span></span></p>
<ul>
<li>
<div class="MsoNormal" style="margin: 0pt"><span style="font-size: 10.5pt">Establish the framework to be used: May 15, 2010</span></div>
</li>
<li>
<div class="MsoNormal" style="text-align: justify;margin: 0pt 0pt 0pt -0.9pt"><span style="font-size: 10.5pt">Identify parties to participate in this effort: </span><span style="font-size: 10.5pt">June 15, 2010.</span></div>
</li>
<li>
<div class="MsoNormal" style="text-align: justify;margin: 0pt 0pt 0pt -0.9pt"><span style="font-size: 10.5pt">Outreach to our partners to be completed by: August 15, 2010</span></div>
</li>
<li>
<div class="MsoNormal" style="margin: 0pt"><span style="font-size: 10.5pt">SLA</span><span style="font-size: 10.5pt"> drafts reviewed and accepted by participating groups: September 15, 2010</span></div>
</li>
<li>
<div class="MsoNormal" style="margin: 0pt"><span style="font-size: 10.5pt">SLAs published and communicated to organization: </span><span style="font-size: 10.5pt">October 15, 2010</span></div>
</li>
</ul>
<p><strong>Resources:</strong>  </p>
<ul>
<li><span style="font-size: 10.5pt">Each group must be identified and engaged<span>  </span>to participate in this effort</span></li>
<li><span style="font-size: 10.5pt">Sponsorship from Area Directors and Dean should be present before effort begins</span></li>
<li>
<div class="MsoNormal" style="text-align: left;margin: 0pt"><span style="font-size: 10.5pt">Assigned representation from each group identified</span></div>
</li>
<li>
<div class="MsoNormal" style="text-align: left;margin: 0pt"><span style="font-size: 10.5pt">SLA</span><span style="font-size: 10.5pt"> process owner established (PM)</span></div>
</li>
</ul>
<p class="MsoNormal" style="text-align: left;margin: 0pt"><span style="font-size: 10.5pt"><strong>Viability:</strong>   </span></p>
<ul>
<li>
<div class="MsoNormal" style="text-align: left;margin: 0pt"><span style="font-size: 10.5pt">Goal is achievable </span></div>
</li>
<li>
<div class="MsoNormal" style="text-align: left;margin: 0pt"><span style="font-size: 10.5pt">Organization must establish proper agreements between groups to create needed efficiencies and promote better cooperation.</span></div>
</li>
<li>
<div class="MsoNormal" style="text-align: left;margin: 0pt"><span style="font-size: 10.5pt">Goal consists of working across groups and departments; within sub groups in User Services first.</span></div>
</li>
<li>
<div class="MsoNormal" style="text-align: left;margin: 0pt"><span style="font-size: 10.5pt">Establishing SLA between two parties is time consuming; effort will take time.</span></div>
</li>
<li>
<div class="MsoNormal" style="text-align: left;margin: 0pt"><span>Barriers are centered around buy-in and clear direction/sponsorship from leadership.</span></div>
</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://sites.middlebury.edu/lis/2009/12/22/user-services-goal-establish-slas-with-user-serviceslis/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>US Goal &#8211; Baseline Knowledge and Skills</title>
		<link>http://sites.middlebury.edu/lis/2009/12/17/us-goal-baseline-knowledge-and-skills/</link>
		<comments>http://sites.middlebury.edu/lis/2009/12/17/us-goal-baseline-knowledge-and-skills/#comments</comments>
		<pubDate>Thu, 17 Dec 2009 19:01:59 +0000</pubDate>
		<dc:creator>Elin Waagen</dc:creator>
				<category><![CDATA[Areas and Workgroups]]></category>
		<category><![CDATA[goal]]></category>
		<category><![CDATA[goals]]></category>
		<category><![CDATA[learning]]></category>
		<category><![CDATA[strategic choices]]></category>
		<category><![CDATA[strategic directions]]></category>
		<category><![CDATA[User Services]]></category>
		<category><![CDATA[user services goals]]></category>

		<guid isPermaLink="false">http://sites.middlebury.edu/lis/?p=18961</guid>
		<description><![CDATA[Goal Statement Establish a “User Services Literacy” standard for baseline knowledge and skills every member of User Service should have. Supports Strategic Choices #1 – move to cloud computing and next gen tools; emerging technology #2 – new models for &#8230; <a href="http://sites.middlebury.edu/lis/2009/12/17/us-goal-baseline-knowledge-and-skills/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p><img src="http://sites.middlebury.edu/lis/files/2009/12/learning.jpg" alt="learning" width="129" height="127" class="alignleft size-full wp-image-18971" /><br />
<strong>Goal Statement</strong><br />
Establish a “User Services Literacy” standard for baseline knowledge and skills every member of User Service should have.<br />
<span id="more-18961"></span><br />
Supports Strategic Choices<br />
#1 – move to cloud computing and next gen tools; emerging technology<br />
#2 – new models for service delivery; new org structures<br />
#4 – staff development as part of performance process<br />
Supports Main Things<br />
-Change<br />
-People<br />
-Teach<br />
-Innovate</p>
<p><strong>Deliverable</strong><br />
-Develop an ongoing program to learn “FIVE  NEW THINGS” in TEN WEEK time chunks<br />
-Menu of FIVE THINGS” that evolves to match new tech trends and directions<br />
-Self-paced; self-scheduled menu of learning platform choices to suit schedules and work demands &#8211; web-based; workshops; 1:1 and small group tutorials<br />
-Menu of modules to choose from – with Liberal Arts model of distribution areas, requirements and electives; with a focus on tangible tools and practical, applicable know-how<br />
-System to track accomplishments and incorporate into performance process </p>
<p>Possible menu of competency modules:<br />
-Blogging – read, comment, publish; rss; tagging<br />
-Wiki – add a page; edit a page; be able to seach  and find documentation; tagging<br />
-Library Resources -how to search Library data-bases and catalog<br />
-Print/copy &#8211; troubleshooting<br />
-Smart classroom – troubleshooting; how-to<br />
-Personal  computing<br />
-Photo and image – search, edit, resources<br />
-Web bookmarking tools<br />
-Web-based/cloud applications and computing<br />
-Podcasts, video, streaming, music<br />
-Personal web pages -iGoogle; Drupal profiles ; College Directory<br />
-Real-time trends – twitter etc.<br />
-Geo and location<br />
-Mobile computing<br />
-Social Gaming<br />
-Personal privacy issues<br />
-Social web</p>
<p><strong>Outcome</strong><br />
-Stay current with trends in library and information services<br />
-Develop a “Change ready” attitute<br />
-Gain confidence in ability to learn new tools<br />
-Bridge LIS work areas<br />
-Decrease fear of learning new things<br />
-Open minds to new ideas<br />
-Encourage discovery and innovation in the workplace<br />
-Encourage staff to explore new tech with an eye to integrating into daily work<br />
-Engage in activities to inspire imagination, curiosity<br />
-Learning as its own reward<br />
-Have fun<br />
-Collaboration across User Services and LIS<br />
-Foster team ethic<br />
-Share knowledge – learn and teach<br />
-Create an environment and have expectations for staff to work together<br />
-Develop generalist knowledge of LIS resources and tools; and emerging technologies</p>
<p><strong>Delivery</strong><br />
-Inventory skills; identify experts – May ‘10<br />
-Develop the list of competency modules – July ‘10<br />
-Create a system of MY FIVE THINGS to track individual and group progress  &#8211; July &#8217;10<br />
-Every staff member in User Services contracts to accomplish at least 5 modules from menu &#8211; Sept ‘10<br />
-Celebrate the  accomplishments – Sept ‘10<br />
-Evaluate and assess program  &#8211; what worked/did not? Re-evaluate effectiveness of program, system, platform – go/no go of program &#8211; Nov ‘10<br />
-If go –develop new menu offerings  &#8211; Jan ‘11</p>
<p><strong>Resources</strong><br />
-Align with newly formed Training Team to support leaning opportunities<br />
-Partner with Web Team to learn about WordPress and Media wiki<br />
-Curriciular Technology Team as a resource for identifying new technology learning meeds<br />
-Internal “experts” identified to direct learning modules<br />
-Collaborate with LIS Liaison program</p>
<p><strong>Viability</strong><br />
-Minimum outcome &#8211; all US staff exposed to 5 new skills<br />
-Maximum outcome – 50% US staff exceed goal – and go beyond the 5 new things<br />
-Low cost – potential to tap into existing low cost/free resources and tools<br />
-Flexible<br />
-Partnering across User Services<br />
-Non-threatening, self-paced, self-scheduled learning<br />
-Realistic – 5 small steps at a time<br />
-Allows participation by all<br />
-Fun and productive; self-motivating<br />
Possible barriers:<br />
-Changing LIS org structure<br />
-Time<br />
-Pressing demands of day-to-day work<br />
-Fewer staff resources</p>
]]></content:encoded>
			<wfw:commentRss>http://sites.middlebury.edu/lis/2009/12/17/us-goal-baseline-knowledge-and-skills/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
