Embedded Files
Planning
Needs Assessment - Mission - Goals - Objectives - Tasks
(1) NEEDS ASSESSMENT / PROBLEM STATEMENT
(1A) Understand and clearly define the problem the program plans to address in as few words as possible.
(1B) Focus on the conditions the program wants to improve/enhance and on specific benefits that will be produced.
(1C) Provide evidence drawn from experience, from statistics provided by authoritative sources, and from testimony of persons or organizations known to be knowledgeable/credible. Also, show an understanding of related programs and issues.
(1D) Do not make assumptions, use jargon, or use circular reasoning by saying the problem is the lack of the method suggested.
(2) MISSION
A brief easily understood statement of the program's reason for existence. It proposes a solution to the problem statement (needs assessment) including the geographic area served, target population, and underlying philosophy or perspectives.
(3) GOALS
Goals are broad statements which spell out all the things needed to be accomplished in order to achieve the above Mission.
(4) OBJECTIVES
Statements of precise and measurable results for each GOAL the program intends to achieve during a specific period. Each should be stated in terms of an output or outcome which will establish the program's criteria for success. An objective states the "ends", but not does not state the "means" or activities used for achievement. Each objective should:
(4A) identify a single desired end result;
(4B) state a specific time period for the desired result to occur;
(4C) be realistically obtainable; and
(4D) define the minimum acceptable level of measurable accomplishment required to determine success
Phrases: increase, decrease, reduce, expand by X percentage or amount (not "task" words - create/implement)
Questions: "who" is doing "what" to whom "when" -- "How" much is being done -- "How" it will be measured.
(5) TASKS/ACTIVITIES/METHODS/PROCEDURES
A sequence of steps taken to accomplish a particular OBJECTIVE. Each step will identify specific input resources required (time/information/materials/expenditures), and state specific planned outputs (reports/meetings/$). Human involvement is typically measured in units of FTE (full time equivalency based on 40 hours/week). Standards for outcomes should be established and task output should be directly linked to Objective outcomes. Special skills and tools required should also be identified.
Phrases: provide, establish, create, implement, build, prepare, etc...
Questions: how long will each step take, in what order should steps be implemented, what resources are required per step
Clarify: understand reason for selecting specific steps instead of others (show awareness/logic of alternatives)
MeetingsThere is no greater time-waster than poorly planned, poorly managed meetings. If you are in a position to call meetings, keep that in mind. Ask yourself: is this meeting a substitute for action? Can I make the decision myself without involving others? Then, why not do so?If you do have to involved others, consider doing it by telephone, perhaps by conference call. Don't meet unless you need to, because every minute wasted is multiplied by the number of people in attendance.But, assume the meeting is needed. First, invite people in writing, being specific about what you hope to decide, not just listing subjects you want to consider.For example, if you invite several people to your office to "discuss" product lines, you are, in effect, asking them to come and chat. Consider, instead, the effect of a memo like this.....subject, date, start time, end time, specific items to decide on...Those receiving such a memo will come to the meeting knowing exactly what information is expected and are likely to have done some thinking and some homework.Start your meeting on time, stick with the agenda, and try to reach some kind of decision on each item, or assign responsibility for further action. Don't let the meeting drag on beyond the scheduled time.But probably the most important point to remember is to restate, at the end of the meeting, the decisions reached and the assignments made. Too many meetings end with people unsure of exactly what was decided and who is supposed to do what by what date.After the meeting, the same day if possible, send a memo to the participants confirming what was decided, what responsibilities were assigned, and what deadlines were set for further action. Never omit this step. It clinches the assignments and establishes responsibility. And the mere act of writing such a memo will make you face up to the question of whether or not you accomplished your objectives.So much for meetings you call. What about the meetings where someone else, such as your boss, is in charge and is wasting everyone's time by violating the suggestions outlined previously?Well, don't just sit there and let your time be wasted without trying to do something about it. If your boss doesn't prepare agendas before a meeting, suggest that this might be a good idea, "in order to keep us from getting off the track." If meetings drag on forever, suggest privately that they be scheduled for 11:30 or 4:30 "to keep the more talkative people from getting carried away." If your boss won't crystallize a decision on one subject before moving to another, volunteer to keep minutes of the meeting. This gives you a reason to interrupt and say, "Just a minute - before we go on to another subject I want to make sure my notes are accurate: what have we decided to do about the item we've been talking about?"The reason you were invited to the meeting was because you supposedly could contribute something. Frequently the greatest contribution you can make is to help a weak chairperson keep the meeting on track. So don't just sit there. Speak up!Reference (pages 88-91): ISBN 0-553-24426-4 ... "Getting Things Done" ... Edwin Bliss
Page updated
Google Sites
Report abuse