Tuesday, September 30, 2008

Logical Framework Approach /ZOPP /OOPP



http://lgausa.com/logframe_approach.htm#Particip_anal

Logical Framework Approach, ZOPP, and OOPP - What and Why
The two terms Logical Framework (LF or Logframe) and the Logical Framework Approach (LFA) are sometimes confused. The LogFrame is a document, the Logical Framework Approach is a project design methodology.
Note: For most purposes the three terms; Logical Framework Approach, ZOPP and OOPP are terms for the same project design methodology or process. The terms OOPP and ZOPP mean respectively; Objectives Oriented Project Planning and in German Ziel Orientierte Projek Planung. All three terms refer to a structured meeting process which we will refer to as LFA.
The logical framework document is a 4 column by 4 row matrix. The cells of the matrix contain text that succinctly describes the most important features of a project. If the correct process (LFA) was used to develop the content of the logframe, the document will reveal the quality of the design and make flaws readily apparent. (Follow this link for a detailed explanation of the Logical Framework document - often referred to as the "Project Matrix")
Return to top of page
The LFA as a design methodology is described briefly on this page. The design methodology is a rigorous process, which if used as intended by the creators will impose a logical discipline on the project design team. If the process is used with integrity the result will be a high quality project design. The method is not without it's limitations, but most of these can be avoided with carefull use of ancilliary techniques. Many things can go wrong in the implementation phase of a project, but if the design is flawed, implementation starts with a severe handicap. The mind map diagram at the top of this page shows typical steps in the design process. The first few steps are:
situation analysis
stakeholder analysis
problems analysis
We might note that one common misuse of the logframe is to design the project first and attempt to "fill in" the logical framework matrix as an after thought. This defeats the whole purpose of the logical framework and the design methodology.
Return to top of page
Where's the logic?
There is a logical connection between the cells of the matrix. The logic that connects the cells in the left most column, is referred to as the vertical logic; the logic that connects the remaining three columns is referred to as the horizontal logic.
The vertical logic is the hierarchy of objectives of the project.
The horizontal logic is rather more involved. For a given level of objective (equivalent to a horizontal row of cells) the horizontal logic describes:
how the achievement of the objective will be measured or verified
how this information will be obtained
what are the external factors that could prevent the project manager and staff from achieving the next level objective.
Situation Analysis
This is a document that describes the situation surrounding the problem. The source could be a feasibility study, a pre-appraisal report, or be a compilation done specifically for the project design workshop. Typically the document describes the problem situation in detail, identifies the stakeholders and describes the effects of the problems on them.
Stakeholder or Participation Analysis
This stage is an analysis of the people, groups, or organizations who may influence or be influenced by the problem or a potential solution to the problem. This is the first step to understanding the problem. We might say, without people or interest groups there would be no problem. So to understand the problem, we must first understand the stakeholders. The objectives of this step are to reveal and discuss the interest and expectations of persons and groups that are important to the success of the project.
Return to top of page
Problem Analysis
If there is no agreement between participants on the statement of the problem, it is unlikely there will be agreement on the solution. This stage therefore seeks to get consensus on the detailed aspects of the problem.
The first procedure in problem analysis is brainstorming. All participants are invited to write their problem ideas on small cards. (approximately 8 in by 4 in.) The participants may write as many cards as they wish. The participants then group the cards or look for cause-effect relationship between the themes on the cards by arranging the cards to form a problem tree.
Objectives Analysis
In this step the problem statements are converted into objective statements and if possible into an objective tree. Just as the problem tree shows cause-effect relationships, the objective tree shows means-end relationships. The means-end relationships show the means by which the project can achieve the desired ends or future desirable conditions. Frequently there are many possible areas that could be the focus of an "intervention" or development project. The next step addresses those choices.
Alternatives Analysis
The objective tree usually shows the large number of possible strategies or means-end links that could contribute to a solution to the problem. Since there will be a limit to the resources that can be applied to the project, it is necessary for the participants to examine these alternatives and select the most promising strategy. After selection of the decision criteria, these are applied in order to select one or more means-end chains to become the set of objectives that will form the project strategy.
Return to top of page
Activities Planning
After defining the objectives, and specifying how they will be measured (OVIs) and where and how that information will be found (MOVs) we get to the detailed planning phase. We now determine what activities are required to achieve each objective.
Where to start?
This is a little like the chicken and the egg problem. It is tempting to say; always start at the situation analysis stage, and from there determine who are the stakeholders. Another argument is that the stakeholders define the problem so it is necessary to start with identifying the stakeholders. Each problem situation will require a different approach.
Where to go next?
The next step will be implementation planning and implementation.

Learning Expert Blog

Monday, September 29, 2008

Learn, Unlearn, and Relearn

The secret to learning new things is to be willing to unlearn--even if your behaviors previously brought success.

One summer in college I canvassed for a local non-profit. We went door to door telling people about the organization and asking them to sign various petitions. I recited my spiel a hundred times. "Hi, my name is Marcia and I'd like five minutes to tell you a little about..."

Halfway through the season my boss asked me to insert a slice of bologna in one shoe. I followed his request, but only after considering telling him where to stick the lunch meat.

At the first house we visited, I physically couldn't say my opening the same way. The bologna distracted me enough so that I needed to reflect on e-v-e-r-y word. The next day, without the bologna, my approach was still fresh, engaging, and more successful than it had been two days before. I had unlearned, and I had relearned.

Unlearning can be a one-shot (one-shoe?) deal or a daily practice. It can help you become open to new skills, experiences, behaviors, and knowledge. Although you can't physiologically unlearn anything--literally erase existing neural pathways--you can create the equivalent of a mental attic and put a sign on the door that reads, "Things I know no longer so." Then you can shift your focus to the edge of what you knew and transition from managing your knowledge to participating in the flow. Here's how.

Begin at the beginning. In order to pick up a new skill, even if it's similar to something you already can do, learn what makes it different. All of us repeat things that worked in the past, even when they don't apply to the now. Repeating isn't always a bad strategy, but when there is a significant difference, the old approach holds you back.

I'll never forget a husband-and-wife team who came to me to learn how to kayak. The guy was a canoeist and he just wouldn't set aside what he knew about canoeing in order to learn about kayaking. He spent his early lessons trying to compare the two types of boats and tried repeating canoe strokes he was certain would work. As a result, he continually found himself facing the bottom of the swimming pool where our class took place. What he knew already wasn't as useful as what he needed to learn fresh. Meanwhile, his wife, a complete novice, made significant progress from the first day.

Stay open. Unlearning doesn't require you to toss out all your accumulated experiences or presume previous know-how will keep you from success. Rather, it asks that you stay open to different ways of getting things done.

What happens when you begin a new job? You learn about the new organization and the department where you'll work while you unpeel the mindset and procedures of the groups you just left. Your refusal to unlearn old rules (for instance, comparing everything to the way it worked at the old company) leaves you out of the corporate culture and keeps you from getting a clear sense of the job. By thinking, "This is how we did it where I used to work," you miss learning opportunities and you avoid moving in. If you go in looking at how the new organization works, thereby replacing your old activities with new ones, you systematically begin to forget what's no longer useful and you begin to prepare for what's next.

Look for mirrors. Make it easy for your boss, coworkers, employees, family, and friends to give you guidance by asking for it. The more people you have in your life who help you reflect on your behaviors, the greater your chance to gain an accurate sense of how other people perceive you and which actions to unlearn.

During Friday lunch meetings with his team members, John Seely Brown (when he was still working at Xerox PARC) focused on what they did well, what they did wrong, and what they learned from it all. A primary objective was to help the team learn and unlearn. One day, team members remarked that whenever they saw John make a certain face in response to someone's idea, it was obvious that the idea didn't stand a chance. John had the next meeting videotaped. Sure enough, he saw for himself that he did sometimes wear a disapproving expression. From then on, whenever that feeling washed over him, he worked to change his facial expression and to listen more attentively to the other person's views.

Examine your beliefs. Your beliefs determine your behavior and it's difficult to act inconsistently with your beliefs for very long. When you believe you already know the right way to do things, everything else can seem wrong. Why then would you want to unlearn what you're currently doing, let alone replace it with something else?

A company I work with needed a way to ready the industry for their offerings and increase the firm's name recognition. Their research and publications team seemed suited for the task. Although widening the market and strengthening brand was far more lucrative than the sales the team brought in by selling papers, the group refused to give anything away. They believed what they were doing was right; that people wouldn't value the research as much if it was freely available, and that clients preferred paper copies to online versions. No matter how many times the CEO told them to blanket the marketplace with information, they continued to do what they'd always done. Then we sent them all to an industry event where they spent time asking questions and challenging their beliefs. Something almost magical happened. The people they met expressed their appreciation for the company's reports, asking if they could have the rights to reproduce and then distribute the research to their customers, too. Within a few days the team developed a new set of beliefs around their value to the industry. They began behaving like a team of market researchers and industry evangelists rather than a product group generating sales for one company.

So what are you going to unlearn first? Create a list of several approaches. Write it your journal or on a sticky note to post on the computer, the television, the dashboard, or your desk--then buy yourself a few slices of bologna.


Thursday, September 25, 2008

All Project Management

Wednesday, September 24, 2008

Accountability -
The obligation to report on one's actions.

Activity -
Any work performed on a project. May be synonymous with task but in some cases it may be a specific level in the WBS (e.g., a phase is broken down into a set of activities, activities into a set of tasks). An activity must have duration and will result in one or more deliverables. An activity will generally have cost and resource requirements. See Task.

Actuals -
The cost or effort incurred in the performance of tasks. Also, the dates tasks have been started or completed and the dates milestones have been reached.

Analogous Estimating -
Estimating using similar projects or activities as a basis for determining the effort, cost and/or duration of a current one. Usually used in Top-down Estimating.

Assumption -
Something taken as true without proof. In planning, assumptions regarding staffing, complexity, learning curves and many other factors are made to create plan scenarios. These provide the basis for estimating. Remember, assumptions are not facts. Make alternative assumptions to get a sense of what might happen in your project.

Authority -
The ability to get other people to act based on your decisions. Authority is generally based on the perception that a person has been officially empowered to issue binding orders. See Power.

Baseline -
A point of reference. The plan used as the comparison point for project control reporting. There are three baselines in a project—schedule baseline, cost baseline and product (scope) baseline. The combination of these is referred to as the performance measurement baseline.

Bottom-up Estimating -
Approximating the size (duration and cost) and risk of a project (or phase) by breaking it down into activities, tasks and sub-tasks, estimating the effort, duration and cost of each and rolling them up to determine the full estimate. Determining duration through a bottom-up approach requires sequencing and resource leveling to be done as part of the scheduling process.

Budget -
The amount allotted for the project that represents the estimate of planned expenditures and income. The budget may be expressed in terms of money or resource units (effort).

Business Case -
The information that describes the justification for the project. The project is justified if the expected benefits outweigh estimated costs and risks. The business case is often complex and may require financial analysis, technical analysis, organization impact analysis and a feasibility study.

Calendar Date -
A specific date shown on the calendar (e.g., July 3, 1942) as opposed to a relative date. See Relative Date.

Change -
Difference in an expected value or event. The most significant changes in project management are related to scope definition, availability of resources, schedule and budget.

Change Control -
The process of managing scope, schedule and budget changes to the plan. See Scope Change Control.

Change Request -
A documented request for a change in scope or other aspects of the plan.

Client -
The person or organization that is the principle beneficiary of the project. Generally the client has a significant authority regarding scope definition and whether the project should be initiated and/or continued.

Closing -
The process of gaining formal acceptance for the results of a project or phase and bringing it to an orderly end, including the archiving of project information and post-project review.

Consensus -
Unanimous agreement among the decision-makers that everyone can at least live with the decision (or solution). To live with the decision, one has to be convinced that the decision will adequately achieve objectives. As long as someone believes that the decision will not achieve the objectives, there is no consensus.

Constraint -
A restriction or limitation that influences the project plan. For example, a target date may be a constraint on scheduling. A schedule may be constrained by resource limitations.

Content Expert -

See Subject Matter Expert (SME).

Contingency Reserve -
A designated amount of time and/or budget to account for parts of the project that cannot be fully predicted. For example, it is relatively certain that there will be some rework, but the amount of rework and where it will occur in the project (or phase) are not known. These are sometimes called "known unknowns".
The purpose of the contingency reserve is to provide a more accurate sense of the expected completion date and cost of the project (or phase). Some PMs separate contingency reserves from management reserves while others combine the two into a single reserve. Reserves for changes and issues may be part of the contingency reserve or separate reserves.

Controlling -
The process of monitoring, measuring and reporting on progress and taking corrective action to ensure project objectives are met.

Critical Path -
The path(s) in a project network that has the longest duration. This represents the series of activities that determines the earliest completion of the project. There may be more than one critical path and the critical path(s) may change during the project.

Debate -
A discussion in which the participants exchange information for the purpose of supporting or refuting one anothers' positions. Debates are win-lose discussions, as opposed to dialogues, which are win-win discussions.

Deliverable -
Any item produced as the outcome of a project or any part of a project. The project deliverable is differentiated from interim deliverables that result from activities within the project. A deliverable must be tangible and verifiable. Every element of the WBS (activity or task) must have one or more deliverables.

Dependency -
A relationship between two or more tasks. A dependency may be logical (see Logical Relationship) or resource based (see Resource dependency). Also see Link.

Dialogue -
A discussion in which the participants share their thoughts and gain a better understanding of the subject and, possibly, reach consensus. This is contrasted with debate.

Duration -
The length of time required or planned for the execution of a project activity. Measured in calendar time units—days, weeks, months.

Early Start -
The earliest time a task can begin. The time at which all the tasks' predecessors have been completed and its resources are planned to be available.

Effort -
The amount of human resource time required to perform an activity. Measured in terms of person hours, person days, etc.

Estimate -
An assessment of the required duration, effort and/or cost to complete a task or project. Since estimates are not actuals, they should always be expressed with some indication of the degree of accuracy.

Estimate to Completion -
The expected effort, cost and/or duration to complete a project or any part of a project. It may be made at any point in the project's life.

Executing -
The process of coordinating the people and other resources in the performance of the project or the actual performance of the project.

Float -
The amount of time available for a task to slip before it results in a delay of the project end date. It is the difference between the task's early and late start dates.

Functional Manager -
A manager responsible for the activities of an organizational unit (department, work group, etc.), which provides some specialized products, services or staff to projects. For example, the manager of an engineering group, testing department or procedures development department. Also called a line manager.

Functional Group -
An organizational unit that performs a specialized business function (e.g., design, Human Resource management, etc.) and may provide staff, products or services to a project.

Gantt Chart -

A bar chart that depicts a schedule of activities and milestones. Generally activities (which may be projects, operational activities, project activities, tasks, etc.) are listed along the left side of the chart and the time line along the top or bottom. The activities are shown as horizontal bars of a length equivalent to the duration of the activity. Gantt Charts may be annotated with dependency relationships and other schedule-related information.

Goal -
A desired end result, often synonymous with objective. May be a high-level objective that has less-than-complete definition. See Objective.

Implementation -
May be a phase in the project life cycle in which a product is put into use. Also a term used as a synonym for development.

Incremental Delivery -
A project life cycle strategy used to reduce risk of project failure by dividing projects into more manageable pieces. The resulting sub-projects may deliver parts of the full product, or product versions. These will be enhanced to increase functionality or improve product quality in subsequent sub-projects.

In-house Projects -

Projects performed primarily by performers who are part of the same organization as the client. For example, a product developed by a manufacturing company's own Engineering Department is an in-house project. If an outside contractor developed the same product, the project would be externally sourced. Note that vendors might be used in in-house projects depending on the degree to which they are responsible.

Initiating (Project) -
The process of describing and deciding to begin a project (or phase) and authorizing the Project Manager to expend resources, effort and money for those that are initiated.

Kick-Off Meeting -
A meeting at the beginning of the project or at the beginning of a major phase of the project to align peoples' understanding of project objectives, procedures and plans, and to begin the team-building and bonding process.

Late Start -
The latest time a task can start before it causes a delay in the project end date.

Leveling -
See Resource Leveling.

Link -
A relationship between two or more tasks. See Logical Relationship.

Logical Relationship -
A dependency relationship between two or more tasks or between tasks and milestones, such that one cannot start or finish before another has started or finished.

Management Reserve -
A designated amount of time and/or budget to account for parts of the project that cannot be predicted. These are sometimes called "unknown unknowns." For example, major disruptions in the project caused by serious weather conditions, accidents, etc. Use of the management reserve generally requires a baseline change.
See Contingency Reserve.

Multi-Project Schedule -
A schedule of all the work (projects, operational activities, etc.) planned for an individual or organization unit. The purpose is to ensure that resources are not overburdened by inadvertently scheduling project or other work without regard to previously scheduled work. The Multi-Project Schedule is also used to determine the impact of slippage in one project on other projects assigned to the same resources.

Matrix Organization -
A business structure in which people are assigned to both a functional group (departments, disciplines, etc.) and to projects or processes which cut across the organization and require resources from multiple functional groups.

Metrics -
Metrics are quantitative measures such as the number of on time projects. They are used in improvement programs to determine if improvement has taken place or to determine if goals and objectives are met.

Milestone -
A point in time when a deliverable or set of deliverables is available. Generally used to denote a significant event such as the completion of a phase of the project or of a set of critical activities. A milestone is an event; it has no duration or effort. It must be preceded by one or more tasks (even the beginning of a project is preceded by a set of tasks, which may be implied).

Murphy's Laws -
A set of laws regarding the perverse nature of things. For example:

  1. Nothing is as easy as it looks. Everything takes longer than you think. Anything that can go wrong will go wrong. If there is a possibility of several things going wrong, the one that will cause the most damage will be the one to go wrong. Corollary: If there is a worse time for something to go wrong, it will happen then.
  2. If anything simply cannot go wrong, it will anyway.
Network Diagram -
A graphic tool for depicting the sequence and relationships between tasks in a project. PERT Diagram, Critical Path Diagram, Arrow Diagram, Precedence Diagram are all forms of network diagrams.

Objective -
An objective is something to be achieved. In project management, the objectives are the desired outcomes of the project or any part of the project, both in terms of concrete deliverables and behavioral outcomes (e.g., improved service, more money, etc.).

Parametric Estimating -
Estimating using an algorithm in which parameters that represent different attributes of the project are used to calculate project effort, cost, and/or duration. Parametric estimating is usually used in top-down Estimating.

PERT—Program Evaluation and Review Technique -
A scheduling technique that makes use of dependency analysis and critical path to determine the duration of a project and slack to determine priorities of tasks. In PERT, task durations are computed as (Optimistic + 4xMost likely + Pessimistic estimates) / 6).

PERT Diagram -
A type of network diagram deriving its name from the PERT technique. The term is often used as a synonym for network diagram.

Phase -
A grouping of activities in a project that are required to meet a major milestone by providing a significant deliverable, such as a requirements definition or product design document. A project is broken down into a set of phases for control purposes. The phase is usually the highest level of breakdown of a project in the WBS.

Planning -
The process of establishing and maintaining the definition of the scope of a project, the way the project will be performed (procedures and tasks), roles and responsibilities and the time and cost estimates.

Post-implementation Review -
See Post-Project Review.

Post-Project Review -
An activity to assess and evaluate the way a project was performed, so as to learn from the experience and continuously improve project performance.

Power -
Power is the ability to influence the actions of others. Power may come from formal delegation of authority, reference power, subject matter expertise, the ability to influence rewards and penalties, as well as other sources.

Predecessor Task -
A task (or activity) that must be started or finished before another task or milestone can be performed.

Process -
A series of steps or actions to accomplish something. A natural series of changes or occurrences.

Product -
The project's material outcome. It maybe a service, event or any material object (e.g., a machine, computer system, new drug, building, etc.). The product includes all necessary aspects of the deliverable (e.g., training, documentation, etc.).

Product Life Cycle -
The time from the delivery of a product, until the product is withdrawn from use or sale. There may be many projects during the product life cycle.

Program -
A suite of related projects and ongoing operational activities managed as a whole.

Project -
An effort to provide a product or service within finite time and cost constraints.

Project Charter -
A document that describes the project at a high level of detail and is used to authorize the Project Manager to begin work. It may also be called a "Project Brief," or any number of other synonyms.

Project Life Cycle -
The full set of activities from the beginning to the end of a project. Generally associated with a set of phases, which are determined based on the major parts of project performance (e.g., requirements definition, design, construction, deployment) and the need for control by the Client organization (checkpoints for Go/No go decision-making).

Project Management -
The process of managing a project which requires the application of planning, team-building, communicating, controlling, decision-making and closing skills, principles, tools and techniques.

Project Manager -
The person responsible and accountable for managing a project's planning and performance. The single point of accountability for a project.

Quality Assurance (QA) -
Making sure standards and procedures are effective and that they are complied with. Note, in some organizations QA is used to refer to the quality control function.

Quality Control (QC) -
Making sure deliverables comply with acceptance criteria. Includes testing and reviews.

Ramp Down -
Ramp down is the effort required to close or suspend a task. It may consist of filing away information, making notes, clean-up, etc. Ramp down can be significant, depending on the task. For tasks that are suspended the degree of ramp down (e.g., notes and filing away information) performed will reduce the ramp up effort. See Ramp Up.

Ramp Up -
Ramp up is the work required to get ready to do a task. It consists of assembling materials, learning about the task (including new tools and techniques) and the time required getting into an optimum work pace. Initial ramp up can be significant, depending on the task. Each time a task is interrupted there is an additional ramp up—getting back to that optimal work pace. See Ramp Down.

Relative Date -
A date expressed as a number of periods (e.g., days, weeks, or months) from a reference point. For example, two months after the project start date. See Calendar Date.

Request for Proposal (RFP) -
A document that describes a need for products and/or services and the conditions under which they are to be provided. The purpose of the RFP is to solicit bids or proposals from prospective suppliers. Also called a Request for Quote (RFQ).

Requirements -
The statement of detailed product objectives that describes the features and functions and performance constraints to be delivered in the product. The requirements provide the basis for accepting the product.

Resource -
Any tangible support such as, a person, tool, supply item or facility used in the performance of a project. Human resources are people.

Resource Dependency -
A dependency between tasks in which the tasks share the same resources and therefore cannot be worked on simultaneously. Resource dependent tasks can be scheduled at the same time but are limited by the availability of the shared resources.

Resource Leveling -
Resource leveling is the part of the scheduling process in which the start and end dates of tasks are driven by resource limitations (e.g., limited availability of resources or difficult-to-manage resource levels). Among the scheduling objectives, is to ensure that resources are not overburdened (don’t schedule more resources for a period than are available) and that (as much as possible) there are not significant peaks and valleys in the resource schedule.

Resource Loading -
The process of assigning resources (people, facilities and equipment) to a project, usually activity by activity.

Responsibility -
The obligation to perform or take care of something, usually with the liability to be accountable for loss or failure. Responsibility may be delegated to others but the delegation does not eliminate the responsibility.

Responsibility Assignment Matrix (RAM) -
A tool used to relate each project activity in the WBS with a responsible organization unit or individual. Its purpose is to ensure that every activity is assigned to one or more individuals (only one with primary responsibility) and that the individuals are aware of their responsibilities.

Risk -
The likelihood of the occurrence of an event. Generally, the event is a negative one like project failure, but may also be a positive event, like the early completion of a task.

Risk Assessment -
Part of risk management in which planners identify potential risks and describe them, usually in terms of their symptoms, causes, probability of occurrence and potential impact.

Risk Response -
Action that can be taken to address the occurrence of a risk event. Contingency plans are collections of risk responses.

Risk Response Control -
Responding to risk event occurrences throughout the project life cycle. Taking corrective action is an aspect of risk response control.

Risk Response Development -
Part of risk management in which planners identify and define actions to be taken in case a risk (positive or negative) occurs.

Schedule -
The project timeline, identifying the dates (absolute or relative to a start date) that project tasks will be started and completed, resources will be required and upon which milestones will be reached.

Scope -
Scope is defined in terms of three dimensions—product, project and impact. Product scope is the full set of features and functions to be provided as a result of the project. Project scope is the work that has to be done to deliver the product. Impact scope is the depth and breadth of involvement by, and effect on, the performing and client organizations.

Scope Change -
Any change in the definition of the project scope. Scope change can result from changes in client needs, discovery of defects or omissions, regulatory changes, etc.

Scope Change Control -
Also called scope change management. The process of making sure that all changes to the project scope are consciously evaluated and their implications to the project plan are considered in making a decision to make the change, postpone it or reject it.

Scope Creep -
The unconscious growth of the project scope resulting from uncontrolled changes to requirements.

Scope Definition -
Breaking down the project's major deliverables into small, more manageable components to make verification, development and project control easier. This may be part of requirements definition and/or design.

Scope Planning -
Development of a statement of the principle deliverables of a project along with the project's justification (business case) and objectives. Part of requirements definition.

Scope Verification -
PMI's PMBOK Guide defines this as the process to ensure that all project deliverables have been completed satisfactorily. It is associated with acceptance of the product by clients and sponsors.

Sequencing Tasks -
A part of the scheduling process in which the tasks are positioned serially or parallel to one another based on dependencies between them. Sequencing results in a task network.

Slack -
See Float.

Specifications -
Detailed statements of project deliverables that result from requirements definition and design. Specifications generally describe the deliverables in terms of appearance, operational constraints and quality attributes. Specifications are the basis for acceptance criteria used in scope verification and quality control. In some organizations and industries, specifications may be qualified as requirements specifications and design specifications. See Requirements.

Spiral Development Approach -
A project life cycle strategy in which prototypes and models are used early in project life to define requirements and design the product. Commonly used when the product being developed is new (as in Research & Development and e-commerce) and the clients do not have a concrete understanding of their requirements and design attributes.

Stakeholder -
Anybody and everybody with a stake in the project - clients, sponsors, performers, the general public and even the family and friends of direct participants can be considered stakeholders. Not to be confused with the guy that holds the stake when the vampire slayer slays the vampire.

Statement of Work -
A description of the scope of a project centered on the major deliverables and constraints.

Straw man -
A tentative decision or solution put forth as a point of reference for detailed critical analysis.

Sub-contractor -

A group or individual providing products or services to the project. Commonly, sub-contractors are considered to be vendors. However there is a growing understanding that any internal group that provides products or services (e.g., an internal technical writing department) is a sub-contractor to the project manager. Of course in this broader usage, the agreement between the parties is not a legally binding contract but it is a contract nonetheless.

Subject Matter Expert (SME) -
An expert in some aspect of the project's content expected to provide input to the project team regarding business, scientific, engineering or other subjects. Input may be in the form of requirements, planning, resolutions to issues and/or review of project results.

Sub-task -
A breakdown of a task into the work elements that make it up. A task must be broken down into at least two sub-tasks for a meaningful decomposition.

Successor -
A task or milestone that is logically linked to one or more predecessor tasks.

Task -
A piece of work requiring effort, resources and having a concrete outcome (a deliverable). A task may be of any size (a project is a very large task). Sometimes the term is used to denote a piece of work at a particular level in a Work Breakdown Structure (WBS) hierarchy e.g., a phase is broken into a set of activities, and an activity into a set of tasks. Except for this hierarchical usage, activity is synonymous with task.

Task Dependency -
A relationship in which a task or milestone relies on other tasks to be performed (completely or partially) before it can be performed. Also referred to as a logical relationship.

Top-down Estimating -
Approximating the size (duration and cost) and risk of a project (or phase) by looking at the project as a whole and comparing it to previously performed similar projects. The comparison may be made directly using "analogous estimating," through an algorithm as in "parametric estimating", or from the memory of estimating experts.

Variance -
The difference between estimated cost, duration or effort and the actual result of performance. In addition, can be the difference between the initial or baseline product scope and the actual product delivered.

Vendor -
An organization or individuals providing products or services under contract to the client or to the project performance group. Also called outside contractors or sub-contractors.

Work Breakdown Structure (WBS) -
A hierarchical task list created by decomposing the project based on the breakdown of the product into components and the breakdown of the project process into increasingly detailed tasks. The WBS is depicted as a tree diagram (or hierarchy chart) or as a list in outline form with detailed items subordinated to higher-level items.

Work Package -
A task at a low level of the Work Breakdown Structure at which project accounting is performed. Usually a week or so in duration and performed by an individual or small work group.

Troubled Projects

September 2008, Issue 103, Judy Umlas and Frank P. Saladis, Co-Publishers

/ allPM Letters
Date: Sep 16, 2008 - 04:07 PM
From the Co-publisher's Desk - Frank P. Saladis, PMP

This month we focus our attention to a topic and a situation that many project managers attempt to avoid – managing troubled projects. The problem we seem to have is that regardless of all of the training that is available, all of the tools and techniques that have been developed, all of the best practices that are shared among project managers and the experiences and lessons learned from years of managing projects, many projects become “troubled.” Along with the troubled project there is usually a long list of troubled stakeholders. There are many reasons why projects develop problems. Any project manager can provide a long list of potential issues that can cause project problems or project failures. It is also well known that despite the efforts of a project manager to work with his or her team to develop clearly defined project objectives and detailed plans that include risk assessments, contingency plans, and other preventive measures, projects can develop trouble in an instant. A healthy project can breakdown at anytime and without much notice.

The intent of project management is to minimize project-related problems through the use of a defined methodology that includes significant interaction between the stakeholders and entities involved in the project. We emphasize the importance of communication between project team members and other stakeholders and the importance of strong leadership and commitment to the project. All of these will help to minimize the probability of experiencing project problems but I believe it is safe to say that every project will develop some type of problem or problems. Sometimes these problems can be managed expeditiously through a preplanned risk management process, an experienced project manager and project team. In some cases serious problems develop that require thoughtful review, patience, wisdom, and a little creativity.

Troubled projects, although undesirable, are a fact of life in the project management world and all project managers expect to deal with issues large and small throughout the project life cycle.

Some key factors to consider when managing troubled projects include:

  • All projects develop some problems. These are, in many cases, just inconveniences and “snags” that can be handled without extreme effort. Before declaring a project to be “troubled” and creating a potential managerial escalation domino effect, make sure there is evidence to support that claim.

  • Before escalating the problem, make sure you have gathered all the facts and are prepared to answer questions. Find out why the problem or problems developed. Obtain input from the project team members.

  • Ensure that tolerance levels for variances have been defined. Variances will show up during a review of results. Determine if the variances are actually outside of specified tolerance levels.

  • Determine the potential responses that can be used to resolve the problems and select the best option. Avoid “jumping to a solution.” There are many ways to solve problems. Although there may be severe time pressures involved, look for options, whenever possible.

  • When the root causes have been identified and problems have been resolved, take time to assess the issue. Lessons learned sessions about project issues are invaluable.
In this issue of allPM.com newsletter, we have gathered information from several subject matter experts who have offered to share their experience and their knowledge to assist project managers in developing action plans that will reduce the probability of having to deal with major project problems and to manage through problems if they actually develop. We know that projects can be unpredictable at times and allPM.com is your source for information that can help to smooth out even the roughest periods in your project’s life cycle. Consider allPM.com as your “project psychologist” for all of your project troubles. Just read an issue and email us in the morning.

Wednesday, August 20, 2008

Change Management

Thursday, July 31, 2008

4 Principles for breakthrough performance

Source: http://www.ssireview.org/articles/entry/achieving_breakthrough_performance/




Managers of nonprofit organizations should use the following four principles to help make the decisions that lead to breakthrough performance: 1) costs of serving should always decline; 2) market position determines your options; 3) clients and funding pools don’t stand still; and 4) simplicity gets results.

These four principles are derived from the recently published book The Breakthrough Imperative, written by two of this article’s three authors (Mark Gottfredson and Steve Schaubert). When the two of us began work on the book we wanted to uncover the secrets of companies, organizations, and governments that outperformed their peers. (See p. 38 for our methods.) We drew on our 50- plus combined years of consulting experience at Bain & Company and on the firm’s extensive research into corporate results. We also interviewed more than 40 leaders from industry and the nonprofit sector, including our co-author for this article, Elisabeth Babcock, CEO of the Crittenton Women’s Union, one of Boston’s oldest social service organizations.

In the course of our research we found both striking commonalities as well as one significant difference between for-profit and social sector managers. The commonality was the value of the four principles; the difference was that in the social sector these approaches are applied with two customers in mind— clients and funders—whereas in the for-profit sector attention is focused on just one customer—the one who buys the company’s product or service.

In this article we’ll explore these four principles of breakthrough performance and the ways that nonprofit managers can take advantage of them.

PRINCIPLE 1 Costs of Serving Should Always Decline

For-profit managers pay a great deal of attention to reducing costs because it is one of the main levers they have to increase profits. Nonprofit managers, on the other hand, often pay too little attention to reducing costs, even though doing so could enhance their organization’s impact. Nonprofit funders, for example, often push for what is new and different rather than what will reduce costs or increase outcomes. The specialized nature of many of the problems that nonprofits tackle is also an impediment, often resulting in organizations that are too small to achieve economies of scale.

In spite of these challenges, every organization—whether for-profit or nonprofit—that accumulates experience by making the same product, offering the same service, or deploying the same function should be able to reduce the cost per unit (in constant dollars) of its offering. Just as people progress along a learning curve for any given task, organizations follow the same sort of curve and become more efficient and cost-effective producers. The challenge, particularly for nonprofits, is to get the unit of experience just right, given that new approaches can often appear more costly. (See “More Bang for the Buck,” Stanford Social Innovation Review [spring 2008], for more on this subject.)

When tire manufacturers introduced radial tire technology, for example, the cost of making a tire rose. But because radial tires lasted longer and were more fuel efficient, the tire cost (in constant dollars) per mile traveled actually decreased. The right unit of experience for most nonprofits is the client outcome or benefit, not the cost of the service itself. For example, the cost of treating a particular disease may rise, but the number of patients cured per treatment may rise even faster, making the cost per positive patient outcome lower.

Boston-based Partners In Health, for example, lowered its cost per outcome by incorporating new practices based on what it had learned. “We are much better at starting treatment projects for tuberculosis or HIV/AIDS on the ground than we have ever been,” says Jim Yong Kim, a co-founder of Partners In Health. “Every time we do it, we’re more efficient and use resources much more effectively.” When Partners In Health began its first program attacking multidrug-resistant TB in Peru, the cost of the medicines ranged up to $32,000 per patient, with the average cost about $15,000. As Partners In Health gained experience, it learned to diagnose patients better and start treatment earlier, which reduced the cost of the treatment by shortening the drug regimens. By 2006 the organization, with the help of the World Health Organization and Doctors Without Borders, brought the per-patient cost of medicines down to as little as $2,500.

The cost per client successfully served not only should go down over time, it should decline predictably. And they do at nonprofits that are relatively large and repeat the delivery of a given service without major shifts in their funding, the populations they serve, the services demanded, or the geographies they cover. The Girl Scouts of the USA, called the best-managed organization in America by the late management guru Peter Drucker, is one nonprofit that has been able to do this.

The Girl Scouts of the USA procure millions of boxes of cookies on behalf of more than 200 Girl Scout Councils, which sell them as the organization’s annual fundraiser. One of the ways that the Girl Scouts save money is by licensing just two bakers to produce all of their cookies. Consolidated supply allows the organization to implement process improvements quickly. More efficient packaging, for example, has reduced the Girl Scouts’ costs of materials and transportation by allowing more boxes to be packed into each delivery truck1. The Girl Scouts also track sales by cookie type and troop location in order to recommend an optimal mix of products the following year, boosting sales and avoiding excess inventory.

Accumulating experience should not be confused with growing as large as the Girl Scouts. Some nonprofits should remain small and focused. Regardless of size, however, the best nonprofits have learned how to make use of the experience curve.

PRINCIPLE 2 Market Position Determines Your Options

In the for-profit world, garnering more market share is an important measure of success. Nonprofit managers, however, aren’t accustomed to thinking of their organizations’ relative position in the market.

A simple yet effective way to measure an organization’s market position is a gauge called relative market share (RMS), which in the nonprofit sector is usually defined as the percentage of potential clients an organization is serving. If an organization is the market leader, simply divide its share of the market for a given service by the share held by the closest alternative provider. (For example, 30 percent divided by 20 percent equals a RMS of 1.5.) If the organization is not the market leader, divide its share by the share of the market leader. (For example, 20 percent divided by 30 percent equals a 0.67 RMS.)

In the for-profit world the RMS metric is a powerful indicator of a company’s financial performance. A high RMS provides higher-than-average profits (technically, its return on assets) and increases the probability that the organization will achieve those profits. Nonprofits with a high RMS also benefit from some of the same advantages that for-profits garner, such as economies of scale.

“Organizations need to be larger in order to have any clout,” says Bill Walczak, director of the Codman Square Health Center in Boston’s Dorchester neighborhood. Late last year, Walczak and his colleagues were looking at the advantages and disadvantages of a merger between Codman Square and Dorchester House, a community health center of roughly the same size. The proposed merger would create a $40 million organization with 550 employees. The benefits would include increased visibility among donors and clients, sizable economies of scale in overhead costs and facilities, greater negotiating power, and greater ability to launch related services—all the advantages of a larger RMS.

Other organizations have already gained the benefits of merging. In Boston, Crittenton and the Women’s Union were both well-established nonprofits serving low-income women. Crittenton, which began in 1824 as a program to house and care for single mothers, had developed a strong program of service delivery for homeless and at-risk women, but lacked a diversified funding base. The Women’s Union, founded in 1877 to provide education and skills training for poor women, had an illustrious history of research, advocacy, and services, along with cash in the bank (the result of the 2004 sale of its headquarters building), but it lacked strategic focus.

Both organizations also needed a succession plan, as their leaders were retiring. Thanks to a timely encounter between board members, the two organizations found one in the same person: our co-author Elisabeth Babcock, former director of the Lynn Community Health Center, who signed on expressly to lead the merger.

The newly merged Crittenton Women’s Union (CWU) has focused its research, advocacy, and direct-service programs on helping low-income women and their families achieve economic self-sufficiency. Following the merger, CWU has raised its visibility in the community and among potential donors, and lowered its service delivery costs—turning an operating loss of more than $500,000 into an operating surplus of more than $200,000.

RMS is an important metric, but it is not always synonymous with size. Some nonprofits might have a 100 percent market share yet remain small. Examples of this are nonprofits operating in a fixed geography where no other organization will serve (such as remote development zones in Afghanistan) or nonprofits tackling a narrow, though significant, social problem (such as fighting for research into diseases that have very low occurrence).

PRINCIPLE 3 Clients and Funding Pools Don’t Stand Still

For-profit and nonprofit markets undergo regular changes, largely because customers’ needs change. The organizations that meet customers’ needs also evolve by providing new and innovative offerings to retain and attract customers. One of the outcomes of these shifts is that the point on the value chain where the bulk of the profits are made, or in the case of nonprofits where the bulk of the funding takes place, can also change. (The entire pool of profits or funding in a given market is called the profit pool or the funding pool.)

In the coffee industry, for example, the profit pool includes the entire spectrum of companies, from those growing and roasting the beans to those distributing and brewing the coffee. Before the advent of Starbucks, the coffee industry made most of its profits in roasting and relatively little in retailing. But when Starbucks introduced its innovative retail model based on the Italian-style coffee bar, customers began flocking to the experience and profits shifted dramatically from roasting to retailing.

In the nonprofit sector there are two sets of customers. The first is the people who use the services, such as recipients of social services. The second is the donors and payers whose funding makes these services possible. Nonprofits operate best when they meet the needs of both sets of customers. In the nonprofit sector, customers’ demands also change: clients’ needs change and funders’ priorities evolve. These shifts may, in turn, cause changes in the funding pool.

Take HIV/AIDS prevention and treatment, for example. In the late 1980s more funding was available for hospices because few remedies existed and patients needed inpatient, palliative care. Today, with the advent of drug cocktails to keep symptoms in check, the funding pool has shifted to outpatient care, including clinics and community health agencies.

The HIV/AIDS care funding pool has shifted in other ways as well. In the early years foundations focused most of their attention on the United States and Western Europe. Today, foundations focus much more attention on Africa and the developing world, where the disease continues to spread at a more rapid pace than in the developed world.

Lynn Community Health Center provides another example of how changing customer needs can affect nonprofits. During a 10-year period large numbers of immigrants arrived in Lynn, Mass., first from Central America, then from Southeast Asia, and finally from the former Soviet Union. To meet the needs of these new immigrants Lynn Community Health Center had to provide services in three and sometimes four additional languages.

At the same time, the health center needed to educate its funders about these changes so that the funders’ priorities would stay in sync with clients’ needs. Experienced nonprofit managers monitor these shifts closely so that they aren’t caught unaware when one source of funds dries up. Great nonprofit managers anticipate both client and funding-pool shifts and plan their strategies and tactics accordingly.

PRINCIPLE 4 Simplicity Gets Results

As customer needs and profit and funding pools change, organizations often change with them, offering new products and services to new groups of customers or in new geographies. When organizations make these changes they increase the likelihood that they will drift away from their mission or become too complex—potentially costly mistakes for nonprofits and for-profits alike. To avoid this problem, organizations should find ways to simplify their operations and focus.

To understand the benefits of simplicity, consider an example from the automotive industry. Hal Sperlich is an automotive legend. He led product teams that created the Ford Mustang and the industry’s first minivan for Chrysler. Both were runaway hits, generating billions of dollars in profit for their makers. Sperlich was successful because he realized cars had to stand out on only three dimensions and could simply be competitive on all other dimensions. He got this insight by observing customers, who when asked why they bought a particular vehicle could seldom remember more than three reasons, even immediately after buying the car.

Sperlich’s insight also applies to strategies, processes, and organizations themselves. Human beings can’t effectively focus on more than three or four things at once. A nonprofit with too many disparate services usually drives up costs and confuses its donors. An organization with too many layers of management is probably unable to take quick action, even when the need for action is obvious.

When David Cicilline was elected mayor of Providence, R.I., in November 2002, the city’s situation was bleak. The previous mayor had been convicted and jailed for corruption, the city faced a $59 million budget gap, its crime rate was increasing, and it had the third highest rate of child poverty in the nation. To make matters worse, Cicilline inherited a city workforce that lacked skills because jobs had often been awarded as patronage instead of on merit.

Cicilline decided to begin addressing the myriad problems by focusing on just five priorities: government integrity, strong neighborhoods, safe streets, great schools, and a dynamic economy. Each priority encompassed a variety of short-term initiatives. For example, as part of his effort to clean up graft, Cicilline refused campaign contributions from city employees and suppliers. He also abolished lists of preferred vendors that had been based on campaign donations.

To upgrade Providence’s workforce, he persuaded some city employees to retire early and replaced them with new talent. To combat crime and revitalize neighborhoods, he brought community policing to the neighborhoods, put police officers back on walking beats, cleaned up graffiti, improved garbage collection, and tackled a backlog of municipal trees that needed cutting or trimming.

Cicilline’s decision to concentrate on five priorities gave his administration a focus that other reformers have often lacked. By the end of his first term, Cicilline had achieved impressive results: boosting the city’s credit rating, creating a budget surplus, reducing crime to its lowest level in 29 years, and growing the city’s tax and job base. Cicilline’s focus for his second term is likewise clear: He will plow the city’s budget surplus into upgrading its public schools and after-school programs. “Those are the things that make cities great places to live in,” said Cicilline in an April 2006 speech to the Bridgespan Group. “A relentless focus on the quality of life in a city will do more than anything else.”

Putting the Principles Into Action

Nonprofit managers can create breakthrough performance by using all four principles together. An example of an organization that has done this is the United Way of Massachusetts Bay and Merrimack Valley (UWMBMV), one of 1,300 United Ways in the United States. Three years ago UWMBMV decided that it should narrow its efforts to increase its impact. “In the old United Way, we did anything and everything, depending on who gave us funding for what,” says Jeff Hayward, senior vice president of community impact. To create a new United Way, Hayward and his colleagues first had to decide what issues to concentrate on. To do this they surveyed community leaders, agency clients, and policymakers—“a process of 1,000 voices” as Hayward describes it—and identified a handful of issues where they could achieve the greatest results in the community and the highest returns for the donors who contributed to its $35 million annual budget.

UWMBMV used three criteria to select which areas the organization would concentrate on: The issue should take advantage of the organization’s accumulated experience; the issue should be one in which impact could be achieved with investments of several million dollars and where the organization could achieve some degree of market leadership; and the issue should be one where donors and policymakers—the voices of the customers—were clamoring for change. “It came down to: Was it called for? Did we have the expertise? And could we make a difference?” says Hayward.

Several issues fell off the table during the selection process. Two of these were health care and public education—issues where government and the private sector were already spending billions of dollars. Another was elder care, where UWMBMV had less expertise. Four issues emerged as having high potential: healthy child development and youth opportunities, where UWMBMV had a long and strong track record; and sustainable employment and affordable housing, which are prerequisites for healthy and stable families.

UWMBMV helped the agencies it funded adopt programs to reach specific goals with agreed upon measures of success. To create affordable housing the goal was eradication of homelessness, with two measures: the number of families prevented from entering homelessness and the number of homeless families moved to permanent homes. The financial rationale behind these measures was indisputable: It cost an average of $2,000 to prevent a family from falling into homelessness (covering a medical expense or back rent), compared to about $19,000 to shelter a homeless family for a year.

The new measures that UWMBMV and its grantees adopted realigned incentives. Homeless shelters, for example, now received flexible funding to empty their beds and provide support services to transitioning families. Some of the direct subsidies to the homeless were also changed. In the past, all homeless people received a housing voucher worth the same amount of money. Under the new system the value of vouchers was tiered on the basis of an individual’s true barriers to keeping his or her housing. Implementing the new strategy required healthy partnerships between policymakers, shelters, and other parts of the community.

The results of this new approach to ending homelessness have been dramatic. Homelessness in Quincy, Mass., where the program was implemented, plummeted 55 percent after two years. In Denver, which implemented a similar program, homelessness dropped more than 36 percent. Adopting clear priorities has also helped improve UWMBMV’s relations with its donors. “The focus has made it easier now to communicate with donors and manage those relationships,” says Hayward. “The program focus has brought expertise to the team. We’ve become more efficient at judging where to spend a dollar.”

UWMBMV is not the only nonprofit that has benefited from using these four principles. In our interviews with numerous nonprofit leaders, nearly every case of breakthrough performance that we encountered reflected a manager’s deep knowledge and implementation of these principles. By the same token, most of the instances where nonprofits underperformed could be traced to a manager’s failure to understand one or more of the principles, or to apply the principles accurately and aggressively.

1 Bradley Jacobson, “Buying More Means Less Packaging,” Waste Age, April 1, 2000.

Research Methods This article is based on years of extensive research on corporate performance that we and our partners at Bain & Company have conducted. One set of studies was originally conducted by Chris Zook, a Bain partner and author of three books about understanding a company’s core business, titled Profit From the Core, Beyond the Core, and Unstoppable. Zook compiled a database tracking the performance of 1,804 public companies over 10 years. We used the latest version of Zook’s database to better understand the role that individual managers have in improving a company’s performance. First, we took the 202 companies in the database that maintained profitable growth of at least 5.5 percent a year over the 10-year period ending in 2005. Next, we examined the tenure of the 413 CEOs leading these companies during this period, and we compared the stock performance under each leader with a broader stock index.

Our research found that for the first six months of a CEO’s tenure, these companies’ average stock performance tracked the relevant index almost exactly: the ratio was about 1.1-to-1. Performance then crept up steadily, but not until nearly six years after the CEO took office was the company outperforming the index by an average of 2-to-1. After nine years of the CEO’s tenure these companies outperformed the index by 3-to-1.

From these studies we knew that a manager could make a big difference over time. But how did these managers get better results more quickly? What specific practices made some more successful in just two or three years than peers with equally stellar track records and leadership attributes?

To answer these questions we turned from study to experience. We interviewed more than 40 successful managers, most of whom had held multiple general manager positions en route to their CEO role. Many were people whom we or our colleagues had come to know in the course of our work. Many others came from our search for successful managers. We spoke with leaders from companies as diverse as Northrop Grumman Ship Systems, Burger King, and the Australian telephone company Telstra. We also interviewed leaders of nonprofits and governments, including Teach for America’s CEO and founder Wendy Kopp, Partners In Health co-founder Jim Yong Kim, and Providence, R.I., Mayor David Cicilline, who has done much to turn around that city’s government in a short period of time.

Our research revealed a striking commonality in successful general managers’ approach to their task—whether they headed for-profit businesses, nonprofit organizations, or city governments. Like engineers designing a mission to Mars, they all understand and apply four basic principles that govern what they do. Using those principles, they map out where they are starting from, where they are going, and how they plan to get there. And then they actually do it. –M.G. & S.S.

Thursday, May 11, 2006

Tools and Tips for Bosses

Tools and Tips for Bosses
By James Manktelow, CEO, MindTools.com

Last month, we surveyed Mind Tools’ readers to recommend their top “mind tools”, including the one they would most like to recommend to their boss. The response was amazing and very insightful. In reading some of your many comments, I recognized some of my own quirks (okay, bad habits), so I’ve promised the team here at Mind Tools that I’ll be making even greater day-to-day use of our “mind tools” from now on!

Now the interesting thing we learned from our survey is that bosses are pretty much like everyone else. When it comes to managing time, clarifying priorities, setting goals and so on, bosses can benefit as much as, if not more than, everyone else from tools and techniques at Mind Tools. So read on, for tools and tips that are good for the boss are great for the rest of the team too!

Five themes stood out as the most important in our survey:

  • Prioritize, prioritize, prioritize
  • Be clear and stay focused
  • Manage meetings
  • Hear the facts!
  • Motivate, motivate, motivate

See what readers have to say and learn about some of the tools and techniques that can help in the sections below.

Prioritize, prioritize, prioritize
If there’s one thing that causes frustration among our readers, it’s unclear priorities: Sometimes priorities change without people being informed, and sometimes priorities have simply never been communicated at all. Only when team priorities are clear can team members’ set their own priorities clearly too.

There was such a huge emphasis on the benefits of prioritization that we’ve written a full article bringing together many of the tools and techniques that help with it. You'll find this prioritization toolkit at http://www.mindtools.com/pages/article/newHTE_92.htm. Enjoy it!

And a final tip on prioritization from readers: Remember the importance of two-way communication! If you’re the boss, clearly people need to know your priorities and work within them. As a team member, it’s important to validate your own priorities with your boss: This helps avoid the misunderstandings and false assumptions that cost time and effort further down the line.

Be clear and stay focused
Does everyone in your team know the teams goals and objectives? Just as people are frustrated by prioritization issues, so people get frustrated when goals and objectives are unclear or constantly changing. Many readers mentioned goal-setting as the tool they would most recommend for their boss.

And I’d add that goal-setting also makes a great team tool: What better way to ensure the team’s goals are clear than to involve team members in refining these and breaking them down into sub-goals? More on goal-setting at http://www.mindtools.com/page6.html.

Manage meetings
It’s no surprise to hear that everyone gets frustrated by meetings that run over, or that achieve very little or that keep getting re-scheduled. And guess what? Everyone blames the one who organized the meeting – often the boss.

Now my personal view is that everyone who attends a meeting shares in making it a success. If you don’t know why you are there and what the aim is, ask the organizer! But of course as a meeting organizer, you can try to make sure no one ever needs to ask those questions! Our “mind tool” on effective meetings helps you do this. Read this (even if only for a refresher) by visiting http://www.mindtools.com/CommSkll/RunningMeetings.htm.

Hear the facts!
Can you imagine: A boss who jumps to conclusions without considering all the facts? Well apparently there are a few of them about!

Maybe it’s because they feel they should know the answers, or maybe it’s because they are under such enormous time pressure each day. Whatever the reasons, Mind Tools Readers say “Stop, hear the facts”! (And they get especially frustrated if they are the ones presenting the facts that are being ignored!)

If you consider that certain facts are not relevant, or you have some other basis for your conclusions, it can be helpful to share these with your people. This helps them learn the appropriate level of detail, and refine their own decision making for the future.

A recent favorite tool here is the Ladder of Inference, which you can read about at http://www.mindtools.com/pages/article/newTMC_91.htm. We'll also remind you about our "Mind Tools on Active Listening" guide, which you can share with your team - you can download this from http://www.mindtools.com/CommSkll/Mind%20Tools%20Listening.pdf.

Motivate, motivate, motivate
Last but not least on the list of readers recommendations for bosses is motivation. Bosses need to motivate their teams – no surprise there!
But the message for bosses is not “Go learn to motivate us!”, it’s “Be motivated yourself – it rubs off on the team!” The flip side is that a demotivated boss can easily and seriously infect his or her team with their negativity.

Recent newsletter subscribers will have received the mini e-book "Mind Tools on Motivation". If you haven’t received this and you interested to read more on motivation, you can download "Mind Tools on Motivation" from http://www.mindtools.com/courses/lbs0356vrx/DownloadCenter.htm up to 16 May. Again, enjoy it!

Finally, thank you again to all the readers who participated in our survey, and who helped us compile this list of tools and tips for bosses (and their teams) everywhere!

Managing Interruptions

Managing Interruptions
Maintain focus. Keep control of your time.

This recent article was the number one tool recommended by readers for their bosses in our survey. We "reprint" it as a refresher!

Everyday interruptions at work can be a key barrier to managing your time effectively and, ultimately, a barrier to your success.

Think back to your workday yesterday and consider for a minute the many interruptions that occurred. They may have been phone calls, emails, hallway conversations, colleagues stopping by your office, or anything else that unexpectedly demanded your attention and, in doing so, distracted you from the task at-hand.

Because your day only has so many hours in it, a handful of even the smallest interruptions can rob you of the time you need to achieve your goals and be successful in your work and life.

More than this, they can break your focus, meaning that you have to spend time re-engaging with the thought processes needed to successfully complete complex work.

The key to managing interruptions is to know what they are and whether they are necessary, and to plan for them in your daily schedule when they truly need your attention. The tips that follow will help you do that and so prevent interruptions from frustrating you and jeopardizing your success.

Using The Tool

Use the following tips to understand and manage interruptions:

(a) 1. Keep An Interrupters Log

If interruptions consistently rob you of time and energy, or if they frequently push you off schedule and cause delays, it’s time to keep an Interrupters Log. This is a simple record of the interruptions you experience in the course of a day.

Click here to download our free Interrupters Log Worksheet (you'll need to have Adobe Acrobat installed on your PC to open this - click here to go to Adobe for this.) And figure 1 shows an example of it.

Figure 1: The Interrupters Log

Person Date and Time Description of Interruption Valid? Urgent?

Keep your Interrupters Log with you every day for at least a week, recording every interruption you experience, and marking down the person interrupting you; the date and time it occurs; what the interruption is; whether it was valid; and whether it was urgent (or whether someone could have waited until a better time.)

This allows you to more accurately identify the interruptions that are causing you to fall behind or to experience time crunches and delays.

Once you have recorded the interruptions for a week, sit down with your log and analyze the information.

Which interruptions are valid and which are not?

You need to deal with the valid interruptions. We'll show you below how you can schedule them into your day so that they get the attention they need, while you still have the time you need to adequately address these and complete your daily work.

As for the interruptions that are not valid, you must find a way to block these out in the future or the productivity that will suffer is your own!

2. Analyze and Conquer Interruptions

To analyze and conquer the interruptions you find in your Interrupters Log, firstly look at whether the interruption is valid or not.

Could someone have avoided interrupting you by waited for a routine meeting? Or was it something they should have asked you about at all?

If not, deal with this politely but assertively.

Next, look at how urgent the interruptions were, and whether they could have been pre-empted. You can pre-empt many interruptions by holding routine meetings with people: If they're confident that they'll have access to you at a defined point in the near future, they'll learn to save up non-urgent issues until this meeting.

However, some interruptions are both urgent and valid. You need to be interrupted, and you need to deal with the situation.

From your Interrupters Log, you'll see how much time is taken up by these urgent, valid interruptions. Block this time into your schedule as "contingency time", and only take on as much other work as you can fit into the remaining time. You'll have to juggle this other work around the interruptions, but at least you won't be overloaded and stressed by the things that you haven't done because they've been displaced by emergencies.

(b) Put Your Phone to Work for You (…Not Against You)

A little bit of planning can go a long way in working to control telephone interruptions, which most people experience all day long. If you are on a deadline or your focus needs to be intense (and not interrupted), use your voice mail to screen calls or have an assistant deal with messages for you. This way, you can deal with calls by priority at times that suit you. In fact, this telephone time can be planned into your schedule, and so become a normal part of your working pattern.

(c) Catch Your Breath

When interrupted, it’s easy to get caught up in the “rush” of the person who is interrupting, for they undoubtedly feel their request is urgent. In reality, however, most interruptions are not a crisis and it can serve everyone best to take a little time before taking action.

Take a few minutes to consider the situation. Catch your breath and clear your head. A small delay, even one of just a few minutes, goes a long way in assessing the situation accurately and reacting appropriately.

(d) Learn to Say “No”

It’s often acceptable to say “no” to requests or tasks if you are busy when someone else can handle it, if it is not an important task, or if it can be done later.

When this is the case, saying “no” in a courteous and sincere way, followed by a short explanation is the best course of action to take: “I am working against a very tight deadline on an important project right now so, I am sorry, but I can not jump in and help”.

(e) “Available” and “Unavailable” Time

Simple yet effective: Let people know when you are available… and when you are not. Make sure that people know that during your "unavailable time", they should only interrupt you if they have to.

You and your co-workers can also agree on a signal that everyone in the office can use when tied up and unavailable, like turning the nameplate on the door around, or simply closing the door. This alleviates interruptions and can avoid hurt feelings.

Tip:
Be careful here. If you're a manager, an important part of your job is to be available to people, to handle urgent issues which arise, and to coach your team so that people are as effective as possible.

If you put up barriers that are too high, you won't be able to do these jobs. By all means, use "unavailable time", but don't over-use it, and make sure people know they can interrupt you if there is a genuine crisis.


(f) “Invitation Only” Time

Schedule regular check-in times for the individuals you talk to most often. Ask these people to keep a running list of things that they need to discuss, so you can cover all the points at one time. And, force yourself to do the same.

An open-door policy is good, but you should limit the number of people you invite to your work area. For instance, if you're scheduling a meeting, offer to meet your co-worker in his or her office or a conference room. This way, you can excuse yourself after you accomplish your purpose. Additionally, it's much easier to get up and leave than it is to get people to leave your office once seated and comfortable there.

(h) Uncontrollable Interruptions

There are interruptions that, no matter how hard you try, you simply cannot control.

Most people are happy to schedule a more convenient time, but when this does not work, quickly set the parameters by saying something like, “I only have five minutes to talk about this right now,” and stick to it.

Do not ask the interrupter to sit down and do not engage in small talk. Encourage the interrupter to get right to the point and if a solution cannot be reached before the allotted time runs out, set a time for getting back to them and, again, stick to it.

The Interrupters Log is just one of 39 essential personal effectiveness tools in ‘Make Time for Success!’, our self-study time management course. To take control of your time, and so focus on the things that really matter, click here to find out more.


A Final Note From James

Whether you’re the boss, or whether you’re keen to give your boss a few gentle tips and hints, there has been something for everyone in this issue. Thanks again to readers for all the great insights and tips!

Next issue is a very special one, as Mind Tools celebrates an important milestone. I'll say no more than that until then!

We’ll also have some great new tools, and we announce a special challenge…

Until then, have a great couple of weeks!

James & Kellie