intranet 2.0:

Intranet 2.0:

Nicole C. EngardNJLA Annual ConferenceMay 1, 2008

Fostering Communication & Collaboration

Jenkins Intranet Timeline• 2001

−Intranet 1.0 Completed• 2002

−Jenkins tries a message board• 2005

−Strategic plan finds communication lacking

• 2006 −Intranet 2.0!

Nicole C. Engard – NJLA Annual Conference – May 1, 2008

Problems to be Addressed• Communication between staff,

managers and staff, and between departments

• Too many places to look for information (email, Jenkins site, staff schedule, and room rentals)

• Organization: No navigation on Intranet & no logical way to find info

• Cluttered email inboxes communication was all via email and word of mouth


The Solution• A new communication &

collaboration friendly Intranet• Ability for all staff members to

create blogs without web team interference

• Ability for all staff members to edit and add pages on their own

• Easy access to shared calendars and documentation



Example of Projects at Jenkins

It's time to start a new project in your library - what

do you do?

• Set up a meeting with everyone involved?

• Start a list of tasks on your calendar?

• Create a document assigning specific people to tasks?


How do you go about doing those things?

• Pick up the phone?• Send out an email with your

documents attached?• In person?


At Jenkins we created a blog


Typical Project Procedures


Communication During a Project


Communication During a Project

And now,everyone knows little bits and pieces and no one knows everything.


How many of you can say that one year down the line you’ll be able to

find that email regarding policy changes?

Then there’s the issue of finding information years

down the road

…


Jenkins’ Solution - Blogs

• Web-based & full-text searchable• Archived & backed up• Visible to all staff – no one is left

out• Fewer emails in our inboxes• Conversational (email-like) format• Date and time stamps• Ability to link to relevant pages &

comments


What did the staff think?


Kathy Coon – Deputy Director

• It has cut down on some of the clutter in my inbox. Now that the important facts are on the project pages, I no longer save everything!

• It's great having everything related to a project in one place.

• When I worked on my annual report last year, it helped put the year in perspective.


Project’s Complete:Now What?


Once your project is done, what do you do with all of those

documents you were passing back & forth?

• Store them on a shared drive? • Add links to them to your intranet? • Store them in your email? • Print them out?


At Jenkins we’d use a wiki


Jenkins’ Solution - Wikis

• Web-based & full-text searchable• Archived & backed up• Visible to all staff – no one is left out• History of edits with date and time

stamps• Ability to link to relevant pages &

comments

• Sound familiar?


What did the staff think?


It's a darn nuisance, making documentation, but ya gotta or you won't remember what ya did last tuesday. These wiki thangs are better than tha old way.

- Ken Snyder, Network Admin


Let’s See It In Action!


Any Questions??

Nicole C. EngardOpen Source EvangelistLibLime – http://liblime.com [email protected] http://web2learning.net

Learn more: http://web2learning.net/learn-more

http://liblime.com/

mailto:[email protected]

http://web2learning.net/

http://web2learning.net/learn-more

intranet 2.0:

Documents

engard njla annual conference

annual report

staff members

staff schedule

information email

inboxesconversational

project pages

new project