IST 614: Management - Needs Statement

' IST 614: Management - Needs Statement

IST 614: MANAGEMENT OF LIBRARIES AND INFORMATION CENTERS

NEEDS STATEMENT

Need Statement for Proposal - Guidelines

To establish credibility, the proposal writer must show that he/she understands the problem, has investigated its effects, and that it is appropriate for the writer's organization to attempt to solve it -- at least partially.
To accomplish this task, the writeR must answer the following four questions:

Is the need or problem

Real?
Accurately reported?
Related to mission of organization?
A priority?

The proposal writer should assume that the funding source will closely scrutinize this section. Make every effort to insure that the need or problem is presented accurately and credibly. In the eyes of the reader, it must be believable.
The need also must be defined. It is not enough to say that a certain activity or service does not exist; a need must be shown.
The need should be specific and limited to an identifiable entity [use numbers if at all possible]. What is the present situation? How should it be changed? Why? The answers to these questions will help to articulate the need.
Documentation from authoritative sources will add strength.
The question often arises as to why the organization itself cannot finance the project or use regular operating funds for it; one should be prepared to address this issue. If requesting operating support, it should be shown that increases have occurred in services/costs or that previous funding has been reduced or withdrawn.
Successful past performance in the proposed activity should be emphasized. When appropriate, the project's impact on the community should be shown, e.g., higher employment, reduced numbers of homeless people, etc.
In summary, a proposal idea should be supported by a strong need/problem statement which should:

Clearly define need
Identify the target group
Limit the scope
Document the need
Cite project impact

Common Problems with Needs Statements (Taken from Miner & Griffith, p. 92)

Problems are more complex than proposal writer appears to realize.
Writer doesn't appear to be knowledgeable about pertinent literature.
Some significant efforts in the state (or elsewhere) are not mentioned in problem statement.
It is questionable whether new or useful information will result from the project.
The relationship of the problem rationale is not clearly connected to the local problem to be addressed by proposed project.
Emphasis in problem statement on institutional need rather than external need.
Demographic analysis is not developed;implications are not explored.

Objectives for Proposal -- Guidelines

The objectives should tell who will do what, whenit will be done, in what quantity (or to what degree) and how will the result be measured.
The objectives should flow logically from the statement of need and directly address how the problem will be solved.
The objectives should be stated in such a way that they can be evaluated.
Some tips for writing objectives from Miner & Griffith include:

List objectives in expected chronological order of achievement.

Don't confuse objectives (ends) with your methods (means). A good objective emphasizes what will be done and when it will be done, whereas a method will explain why or how it will be done.

Use action verbs -- nice list on pp. 97-98 of Miner & Griffith; textbooks on instructional design often also include lists of action verbs to use for objectives.

Common problems with objectives (taken from Miner & Griffith):

Project outcomes are of limited significance.

Project outcomes are nebulous, diffuse, or unclear.

Proposal writer proposes to undertake more than methods and/or budget will allow.

Objectives are not specific, measurable, achievable activities.