IT folks carry the stigma of being particularly non-collaborative, but the stereotype of the loner programmer barricaded in a cubicle is not necessarily accurate. The growing number of collaborative projects between library public services and IT departments make it necessary to examine relationships and create excellent communications for resulting success. This program will discuss proven management and collaborative techniques for building relationships, through self-assessment and teambuilding techniques, and will offer a glimpse into how strong relationships between IT and public services libraries can lead to award-winning and innovative projects.
7. Traditionally:
ď§ Service and work oriented
ď§ Loyal
ď§ Respect authority/tend to accept others'
opinions as their own
ď§ Provide stable/standardized service
ď§ Constantly changing rules causes stress
8. But seeing more:
ď§ Helping others be the best they can be
ď§ Assume responsibility in times of conflict
ď§ Outstanding group leader/Self-confident
ď§ Decision makers/Independent
ď§ Need for accuracy can lead to inflexibility
ď§ Can be demanding and difficult
ď§ Can easily become tired, stressed and fatigued
10. But also:
⪠Non-conformist and innovative
⪠Use imagination and innovation to deal with problems
⪠Can tend to nit-pick and overdo simple issues
⪠Can easily become tired, stressed and fatigued
11. And can be:
⪠Impulsive, fearless, crave excitement
⪠Value privacy and tend to keep important issues to
themselves
12. RACI is a project management tool that clearly
lays out roles and responsibilities for any activity
or group of activities
A RACI Chart is used to identify activities or
decisions and the individuals or groups involved
in answering:
The RACI Model
14. Responsibility - The person or position responsible for
doing the activity (the work)
Accountability - The person or position accountable
to ensure the activity happens
Consulted - The person or position who should be
consulted prior to decision or action
Informed - The person or position that needs to be
informed of the decision or action after it is made
15.
16. When to use Raci:
ď§For employees to get a clear understanding of the
role and responsibilities around the work process
ď§To improve the understanding of function
between departments and responsibilities within
one's department
ď§To clearly define the roles and responsibilities of
team members who are working on a project
17. How to use Raci:
ď§Hold meetings to introduce the concept/model
and get buy-in
ď§Define functional roles and activities
ď§Conduct workshops to assign values to the chart
ď§Revise/revisit as necessary
18. It is often a political process which
confronts three elements of roles and
responsibilities:
19. Role Conception: What people think their jobs are
and how they have been trained to perform them
Role Expectation: What others in the organization
think another person's job is and how it should be
carried out
Role Behavior: What people actually do in carrying
out their job
21. ď§ Clearly understood individual expectations
ď§ Reduced redundancy in tasks
ď§ Clearer communication (what is really
necessary)
ď§ Reduced levels of approvals in process
ď§ Greater focus on the value add of a process
step
22. ď§ Assists teams in charting roles and
responsibilities in a consistent manner
ď§ Clarifies individual and organizational roles
and responsibilities
ď§ Identifies accountabilities
ď§ Eliminates misunderstandings
23. ď§ RACI is a useful and effective decision making tool
that helps to define roles and responsibilities. This is
used to identify inefficiencies of organizational roles
ď§ It helps to resolve any functional issues that arise
within departments or between individuals
ď§ The main objective of RACI chart tool is to eliminate
role confusions and to able to deliver the product or
service successfully to the customer and contribute to
the long term organizational objectives
24.
25.
26. Preparing for the day-to-day
⢠Terminology/Lingo
⢠Hallway Conversations
⢠SLAâs
⢠Tickets