Contributing Frameworks

Add any frameworks that might have something to contribute to a usage data decision framework. See bottom for instructions about adding subjects or comments.

General comments?

Caryn Anderson - 3nov07

Feel free to post thoughts about usage data issues or to discuss your challenges or to respond to something someone else is saying here.

Data Evolution Continuum

---

Caryn Anderson - 3nov07

I use this four part framework when designing a new data-based project to be sure I think of everything so I can craft a system that will serve all the needs.

It lists issues to think about as data moves from being data (measurement and facts) to information (as context and meaning are added) to knowledge (something that is predictive and can help with decisions and spurs action).

Generation (Data) - types, source info, confidentiality, clean or dirty

Storage (Data) - space, formats, metadata, deposit/input, updates

Interaction (Information) - sharing, context, analysis, meaning, more data

Presentation (Knowledge) - summative, predictive, dynamic

THOUGHTS?

Technology 7 Framework

---

Caryn Anderson - 3nov07

I designed this framework when I first started teaching a core technology course. People only remember 7 things (plus or minus 2) and I thought this framework would help the students (most of whom did not want to be systems librarians) when they served on task forces trying to evaluate new technologies (ILS, RFID, wiki for library, facebook, etc.)

The seven areas must be considered within two other contexts: the organization's mission and a plan for evaluation:

MISSION

• Mission - What is the purpose of the institution, organization or department?
• Outcomes - What conditions will exist if the institution is successful in achieving its mission?
• Goals - What achievements are necessary to generate the desired outcomes?

EVALUATION

• Measures - What measures indicate that this technology has been successful (quantifiable, achievable, temporal)?
• Plan - What would be an effective plan for evaluating these measures? What obstacles might there be to executing the plan?
• Results - How should the evaluation results be used?

The main areas of the Technology 7 Framework are:

COMPONENTS

• Hardware - What hardware is necessary or involved in this technology? (or specifications for hardware)
• Operating System - What type of operating systems is necessary or involved? What adjustments to the operating system may be necessary?
• Application Software - What type of program(s) is/are necessary or involved in this technology? OTS? Custom?

AGENTS

• Data - What data are involved in this technology? Specific formats? Types of content? Size of units?
• Standards - What standards are required/involved? Existing? Need development?
• Actions - What types of actions are performed by/with/using this technology? Exchange? Storage? Transformation? Integration?

SECURITY

• Confidentiality - What are the methods for assuring only authorized access, disclosure and transformation rights?
• Integrity - What protection measures prevent corruption of data? What protocols are enforced to ensure reliability and authenticity?
• Availability - Are consistent and fully-functioning data/services available? How useful is feedback when data/services not available?

FILTERS

• Content - What controls exist governing data content (types available, date ranges, degree of specificity, etc.)?
• Organization - Is a certain type of organization of the system important to the functioning? Does organization of data affect utility?
• Presentation - How is the presentation of data affected? What are the options for how things look? (raw? with titles/headers? view only?)

PEOPLE

• Creators - Who is building the technology (or maintaining it)? What opportunities and limitations do they experience? Will they receive feedback or collaboration?
• End-Users - Who is using the technology (to access or to create with)? What are their skills and technology capacity?
• Beneficiaries - Who benefits from the technology? (from the output/results of the technology – but doesn’t actually use it) How will they want to view the knowledge?

COSTS

• Cash - What are the direct cash outlays necessary for this technology?
• Labor - What are the labor costs?
• Auxiliary - What hidden costs might there be?

IMPLEMENTATION

• Steps - What are the key stages of implementation?
• Challenges - What problems might be expected during implementation (and ways to avoid or overcome)?
• Maintenance - What problems might arise, or be overlooked, in regards to maintaining this technology?

7 Deadly Sins of Performance Measurement

---

Caryn Anderson - 3nov07

This comes from a Spring 2007 article by Michael Hammer in the MIT Sloan Management Review.

Vanity - Choosing measure that make self look good

• Provincialism - Not extending measurement beyond small units

Narcissism - Measuring self vs. measuring customer experience

Laziness - Measuring what is easy to measure

Pettiness - Only measuring things requiring small adjustments

Inanity - Compensating for improving metrics that are counter-productive

Frivolity** - Not being serious: finding excuses rather than root causes and solutions

4 Elements of Successful Measurement

---

Caryn Anderson - 3nov07

This comes from a Spring 2007 article by Michael Hammer in the MIT Sloan Management Review.

*Select the right things

*Measure in the right way

*Embed measurement in a disciplined process (treatment v. autopsy)

*Create an organizational culture of measurement

Add a topic/subject (by using a double exclamation point)

---

and/or add a horizontal line (by entering three dashes), put your name/date below and your comments/contributions below that.

PBwiki Help

• To edit the page you are on, just click "Edit Page" at the top. Add text wherever you like and click "Preview" to see how it looks. DON'T FORGET to click "Save" when you are happy with the Preview or all your edits will be lost.
• How do I...? - Wiki Style Guide