Robert D Carlsen - Collected Quotes

"A systems analysis project is usually thought of as occurring in two separate phases [...]. The first phase involves both the study of the existing system and phase involves implementing the new or improved system. The second phase involves implementing the new or improved system. This means writing the detailed procedures and data processing programs, conducting various types of tests. and installing the new system." (Robert D Carlsen & James A Lewis, "The Systems Analysis Workbook: A complete guide to project implementation and control", 1973)

"A system is an operation or combination of operations performed by men and, possibly, machines to carry out a specific business activity. This might be a total system that considers all the factors in the entire operation of an enterprise, or it might be a subsystem of that total." (Robert D Carlsen & James A Lewis, "The Systems Analysis Workbook: A complete guide to project implementation and control", 1973)

"A systems analysis is a study of one of these systems or subsystems. The purpose is to evaluate the system in terms of one or more of the following factors ... efficiency, accuracy, timeliness, economy, and productivity ... and to design a new or improved system. The design should eliminate or minimize deficiencies and improve the overall operations. Basically, the systems analyst who performs the study is concerned with three things. First, he must consider what is currently being done. Second, he must develop a method for what should be done. Finally, he must plan for the new design's application and for implementation of the system. Systems analysis is the first step in the development of a successful automated computer system, but the results of a systems analysis do not necessarily have to result in an automated system." (Robert D Carlsen & James A Lewis, "The Systems Analysis Workbook: A complete guide to project implementation and control", 1973)

"Objectives recorded on the System Specification work sheet, even though preliminary in nature, should be specific. It is never sufficient to state an objective in terms of simply improving an existing system or of implementing a computerized system. The idea that a system or an 'automated' system is a better system has been a popular concept too long. An improved system, per se, is of no benefit to a business client; implementing a better system in order to increase profits or reduce costs is of great benefit." (Robert D Carlsen & James A Lewis, "The Systems Analysis Workbook: A complete guide to project implementation and control", 1973)

"Probably the most neglected area in systems analysis involves the planning and control of the project, especially those projects requiring automation. More than one disastrous project has been launched by 'computer people' who communicated their aims to the vexed manager using technical data processing jargon in lieu of specific lists of easily understood tasks, schedules, and costs. This problem applies equally to in-house projects or those requiring the services of outside consultants. Each project must first be planned in detail. Control is involved with comparing actual progress with the plan and taking corrective action when the two do not correspond. Without the plan, true control is not possible; the need for corrective action, its nature, extent, and urgency cannot be accurately determined." (Robert D Carlsen & James A Lewis, "The Systems Analysis Workbook: A complete guide to project implementation and control", 1973)

"Project management is the process by which it is assured that the objective is achieved and resources are not wasted. Planning is one of the two parts of project management. Control is the other." (Robert D Carlsen & James A Lewis, "The Systems Analysis Workbook: A complete guide to project implementation and control", 1973)

"The most important ingredient in any system analysis is the tody of fact on which it is based. This body of fact must be complete; it must fully descrite the system which is already in existence and the environment in which it operates. Although an essential part of it compries the forms and documents being used, these alone are not sufficient. The ultimate source of the critical facts is the people who are part of the system, the operators, the users, those who input the information, and the system mmagers. The only efficient way to obtain the required information is to ask these people; that is, to conduct a series of interviews." (Robert D Carlsen & James A Lewis, "The Systems Analysis Workbook: A complete guide to project implementation and control", 1973)

"There are basically two types of flowcharts. One is the program flowchart and the other the systems flowchart. The program flowchart. sometimes called 'logic diagram', graphically portrays the data precessing program logic. [...] Systems flowcharts display the flow of information throughout all parts of a system, including the manual portions. Systems flowcharts can be of two types. One type is task-oriented, describing the flow of data in terms of the work being performed. The other is forms-oriented, following the forms through the functional structure of the system." (Robert D Carlsen & James A Lewis, "The Systems Analysis Workbook: A complete guide to project implementation and control", 1973)

"There are several classes of flowcharts used in recording study data in the Workbook. The purpose of any chart; of course, is to clarify and to make the information more understandable. One of these types of charts is a Process Flow Chart. It concerns itself with the flow of physical materials, including documents, through a system, especially in terms of distance and time. It is most useful in analyzing some of the cost and benefit factors for existing and proposed systems. System flowcharts [...] have been called the analyst's 'shorthand'. They can be forms-oriented or task-oriented. These flowcharts are not only the primary way of recording data pertinent to the current system, but are used for developing and displaying the new system as well. Later, in the implementation phase, program flowcharts, a fundamental tool of programming, would be developed." (Robert D Carlsen & James A Lewis, "The Systems Analysis Workbook: A complete guide to project implementation and control", 1973)

"The types of graphics used in operating a business fall into three main categories: diagrams, maps, and charts. Diagrams, such as organization diagrams, flow diagrams, and networks, are usually intended to graphically portray how an activity should be, or is being, accomplished, and who is responsible for that accomplishment. Maps such as route maps, location maps, and density maps, illustrate where an activity is, or should be, taking place, and what exists there. [...] Charts such as line charts, column charts, and surface charts, are normally constructed to show the businessman how much and when. Charts have the ability to graphically display the past, present, and anticipated future of an activity. They can be plotted so as to indicate the current direction that is being followed in relationship to what should be followed. They can indicate problems and potential problems, hopefully in time for constructive corrective action to be taken." (Robert D Carlsen & Donald L Vest, "Encyclopedia of Business Charts", 1977)

Harold Kerzner - Collected Quotes

"The acceptance of project management has not been easy, however. Many executives are not willing to accept change and are inflexible when it comes to adapting to a different environment." (Harold Kerzner, "Project Management", 1979)

"There are always 'class or prestige' gaps between various levels of management. There are also functional gaps between working units of the organization. If we superimpose the management gaps on top of the functional gaps, we find that companies are made up of small operational islands that refuse to communicate with one another for fear that giving up information may strengthen their opponents. The project manager’s responsibility is to get these islands to communicate cross-functionally toward common goals and objectives." (Harold Kerzner, "Project Management: A systems approach to planning, scheduling, and controlling", 1979)

"There is no such thing as a good or bad organizational structure; there are only appropriate or inappropriate ones." (Harold Kerzner, "Project Management: A systems approach to planning, scheduling, and controlling", 1979)

"Project management is the planning, organizing, directing, and controlling of company resources for a relatively short-term objective that has been established to complete specific goals and objectives. Furthermore, project management utilises the systems approach to management by having functional personnel (the vertical hierarchy) assigned to a specific project (the horizontal hierarchy)." (Harold Kerzner, "Project Management for Executives", 1982)

"The acceptance of project management has not been easy, however. Many executives are not willing to accept change and are inflexible when it comes to adapting to a different environment." (Harold Kerzner, "Project Management for Executives", 1982)

"Project failures are not always the result of poor methodology; the problem may be poor implementation. Unrealistic objectives or poorly defined executive expectations are two common causes of poor implementation. Good methodologies do not guarantee success, but they do imply that the project will be managed correctly." (Harold Kerzner, "Strategic Planning for Project Management using a Project Management Maturity Model", 2001)

"Success or failure of a project depends upon the ability of key personnel to have sufficient data for decision-making. Project management is often considered to be both an art and a science. It is an art because of the strong need for interpersonal skills, and the project planning and control forms attempt to convert part of the 'art' into a science." (Harold Kerzner, "Strategic Planning for Project Management using a Project Management Maturity Model", 2001)

"Today, excellent companies realize that project failures have more to do with behavioral shortcomings - poor employee morale, negative human relations, low productivity, and lack of commitment." (Harold Kerzner, "In search of excellence in project management", 1998)

"Today, most project management practitioners focus on planning failure. If this aspect of the project can be compressed, or even eliminated, then the magnitude of the actual failure, should it occur, would be diminished. A good project management methodology helps to reduce planning failure. Today, we believe that planning failure, when it occurs, is due in large part to the project manager’s inability to perform effective risk management." (Harold Kerzner, "Strategic Planning for Project Management using a Project Management Maturity Model", 2001)

"When unmeetable expectations are formed, failure is virtually assured, since we have defined failure as unmet expectations. This is called a planning failure and is the difference between what was planned to be accomplished and what was, in fact, achievable. The second component of failure is poor performance or actual failure. This is the difference between what was achievable and what was actually accomplished." (Harold Kerzner, "Strategic Planning for Project Management using a Project Management Maturity Model", 2001)

"Project management is the art of creating the illusion that any outcome is the result of a series of predetermined, deliberate acts when, in fact, it was dumb luck." (Harold Kerzner, "Project Management: A Systems Approach to Planning, Scheduling, and Controlling", 2009)

Kevin Forsberg - Collected Quotes

"A model is a representation of the real thing used to depict a process, investigate an opportunity or a risk, or evaluate an attribute. Properly constructed models are valuable tools because they focus attention on critical issues while stripping away less important details that tend to obscure what is needed to understand and to manage. Because they idealize a complex situation, a variety of different models can be constructed to represent the same situation. A useful model will be simple, but it must retain the essence of the situation to be managed [...]" (Kevin Forsberg et al, "Visualizing Project Management: Models and frameworks for mastering complex systems" 3rd Ed., 2005)

"Being temporary, projects often bring together people unknown to each other. The newly formed group usually includes specialists motivated by the work itself and by their individual contributions. Teams of highly skilled technicians can make costly errors - even fatal ones - simply because the members fail to understand or internalize a systematic approach for applying best practices to project management. A major factor critical to project success is the availability of an effective and intuitive management process - one the group will quickly buy into and build their team upon." (Kevin Forsberg et al, "Visualizing Project Management: Models and frameworks for mastering complex systems" 3rd Ed., 2005)

"Developers often focus on what is possible technically regardless of the constraints of cost, a limiting schedule, or what the customer requires." (Kevin Forsberg et al, "Visualizing Project Management: Models and frameworks for mastering complex systems" 3rd Ed., 2005)

"Failure usually results from a lack of a common approach to accomplish the work as a team. Inadequate leadership fails to create the environment in which teams can flourish. Furthermore, potential team members are seldom trained in how to share their efforts to accomplish team goals. The team may also assume they know more about teamwork than they actually do. So we need to be able to differentiate between superficial teamwork and the real thing." (Kevin Forsberg et al, "Visualizing Project Management: Models and frameworks for mastering complex systems" 3rd Ed., 2005)

"In project management there are two levels of opportunities and risks. Because a project is the pursuit of an opportunity, the first category, the macro opportunity, is the project opportunity itself. The approach to achieving the project opportunity and the mitigation of associated project-level risks are structured into the strategy and tactics of the project cycle, the selected decision gates, the teaming arrangements, key personnel selected, and so on. The second level encompasses the tactical opportunities and risks within the project that become apparent at lower levels of decomposition and as project cycle phases are planned and executed. This can include emerging, unproven technology; incremental and evolutionary methods that promise high returns; and the temptation to circumvent proven practices in order to deliver better, faster, and cheaper." (Kevin Forsberg et al, "Visualizing Project Management: Models and frameworks for mastering complex systems" 3rd Ed., 2005)

"Opportunities and risks are endemic to the project environment. However well planned a project may be, there will always be residual project risk." (Kevin Forsberg et al, "Visualizing Project Management: Models and frameworks for mastering complex systems" 3rd Ed., 2005)

"Project failures can frequently be traced to unrealistic technical, cost, or schedule targets. Such targets may be entirely arbitrary or based on bad assumptions - setting team members up for failure. Furthermore, the goals that motivate one team member may not motivate another member. All tasks don’t have to be inherently motivating - that’s not sensible. But there have to be motivating factors, if by nothing more than participating in goal determination. This also helps ensure adequate opportunity and risk identification, analysis, and management." (Kevin Forsberg et al, "Visualizing Project Management: Models and frameworks for mastering complex systems" 3rd Ed., 2005)

"The appropriate models help avoid costly errors that can lead to failure. One of the major sources of project failure is f lawed requirements and scope management. Models of the project environment, therefore, need to address the development and management of project requirements. Continuing to work on the project solution with an insufficient understanding of stakeholder requirements and a deficient requirements development process often leads to expensive time delays and redesigns. This doesn’t have to be the case. A strong requirements development and management process model can provide that ounce of prevention." (Kevin Forsberg et al, "Visualizing Project Management: Models and frameworks for mastering complex systems" 3rd Ed., 2005)

"When we pursue opportunity, we normally incur risk. The opportunity to experience the thrill of an exciting sport like hang gliding or scuba diving brings with it the attendant risks. Many people instinctively make the trade that the thrill is worth the risks. Others decline." (Kevin Forsberg et al, "Visualizing Project Management: Models and frameworks for mastering complex systems" 3rd Ed., 2005)

"When we fail to grasp the systemic source of problems, we are left to treat symptoms rather than eliminate underlying causes. Without systemic thinking, the best we can ever do is adapt or react. Systems thinking, powered by visual models, stimulates creative - rather than adaptive - behavior. [...] To benefit from systems thinking, the project team needs to extend that viewpoint upward to the bigger picture of the project’s overall environment."(Kevin Forsberg et al, "Visualizing Project Management: Models and frameworks for mastering complex systems" 3rd Ed., 2005)

Daniel Kahneman - Collected Quotes

"[Executives] make decisions based on delusional optimism rather than on a rational weighting of gains, losses, and probabilities. They overestimate benefits and underestimate costs. They spin scenarios of success while overlooking the potential for mistakes and miscalculations. As a result, they pursue initiatives that are unlikely to come in on budget or on time or to deliver the expected returns - ​​​​​​or even to be completed." (Daniel Kahneman, "Thinking, Fast and Slow", 2011)

"It is the consistency of the information that matters for a good story, not its completeness. Indeed, you will often find that knowing little makes it easier to fit everything you know into a coherent pattern." (Daniel Kahneman, "Thinking, Fast and Slow", 2011)

"The illusion that we understand the past fosters overconfidence in our ability to predict the future." (Daniel Kahneman, "Thinking, Fast and Slow", 2011)

"This is the essence of intuitive heuristics: when faced with a difficult question, we often answer an easier one instead, usually without noticing the substitution." (Daniel Kahneman, "Thinking, Fast and Slow", 2011)

"We are prone to overestimate how much we understand about the world and to underestimate the role of chance in events." (Daniel Kahneman, "Thinking, Fast and Slow", 2011)

"When people believe a conclusion is true, they are also very likely to believe arguments that appear to support it, even when these arguments are unsound." (Daniel Kahneman, "Thinking, Fast and Slow", 2011)

"​​​​​​The illusion of control deludes leaders into banking on a single outcome in situations that are highly risk dependent."  (D​​aniel Kahneman) 

 

James P Lewis - Collected Quotes

"A lot of people want to be managers, but many of them don’t want to manage." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"A methodology should be as simple as possible to get the job done. If you make the requirements a burden, rather than a help, then people will resist following them. You want to achieve a consistent, workable approach to managing projects, not hang a noose around the manager’s neck." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"A problem is defined as a gap between where you are and where you want to be that is confronted with obstacles that make closing the gap difficult. It is actually the obstacles that make the gap a problem." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"A project methodology must unambiguously specify what a manager must do to document, execute, and control a project. It must also specify what approvals are needed for various actions, such as procurement, changes to plan, budget variances, risks, and so on. It should tell who is responsible for various aspects of the project, and should spell out the limits of each stakeholder’s authority, responsibility, and accountability." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"[…] all activities are probabilistic, not deterministic! There is a probability that a task can be completed in a certain time, given a fixed level of effort. If you want to guarantee that the task is finished in a fixed time period, then you must vary effort, reduce scope, or sacrifice quality. You can’t have it all. Therefore, an exact estimate is an oxymoron." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"As a rule, it is best to separate discovery from development." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"Choosing a proper project strategy can mean the difference between success and failure." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"Control cannot be achieved through micromanaging." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"Control is exercised by comparing progress against planned performance, and taking steps to correct for any deviations from the proper course." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"Ensuring that you have a shared understanding of the mission, vision, and problem is the most important action you can take as a project manager." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"Getting project management to work in an organization requires a change in culture." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"If you have no plan, you cannot have control, by definition, because it is your plan that tells where you are supposed to be in the first place. Further, if you don’t know where you are, you can’t have control. This comes from your information system. Most organizations have difficulties with both of these." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"If you treat people as though they are responsible, they tend to behave that way." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"In any system of humans or machines, the element in the system that has the greatest variability in its behavior will control the system." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"In general, two or three small projects are all one person should manage." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"Management is proactive, not reactive" (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"No project can succeed when the team members have no commitment to the plan, so the first rule of project planning is that the people who must do the work should help plan that part of the project. You will not only gain their commitment to the plan, but also most likely cover all of the important issues that you may individually have forgotten."(James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"Note that a project always begins as a concept, and a concept is usually a bit fuzzy. Our job as a team is to clarify the concept, to turn it into a shared understanding that the entire team will accept. It is failure to do this that causes many project failures." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"Projects often fail at the beginning, not the end." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"Projects seldom fail because of tools. They fail because of people!" (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"So the first stage in a project is to make sure you have correctly defined the problem being solved, that you have developed a vision for what the end result will be, and that you have stated your mission." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The big fallacy in our assumptions is that the world will stand still while we execute our project plan." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The difference between risks and threats is that a risk is something that can simply happen - an accident, act of nature, or missed deadline - whereas a threat is something that may be done by another entity." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The difference between strategy and tactics is that tactics get you down to the 'nitty-gritty' details of exactly how you are going to do the work." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The entire reason for managing a project is to make sure you get the results desired by the organization. This is commonly called being in control, and it is what is expected of a project manager." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The only time you ever get 80 percent availability from people is when they are tied to their work station, and the only people for whom this is true are factory workers. You may get close to 80 percent availability from them, but for knowledge workers - who aren’t tied to their work stations - you never get such a high level. It is more likely to be around 50 or 60 percent." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The only truly successful project is the one that delivers what it is supposed to, gets results, and meets stakeholder expectations." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The primary objective for a manager is to meet the needs of the organization while helping the followers meet their own needs in the process. To do this, you must help individuals find meaning in their work." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The self-fulfilling prophecy is one of the most important principles from psychology, at least for leaders. The principle is that you tend to get what you expect from others. Thus, if you expect poor performance from a person, you will tend to get it, and conversely." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The way a problem is defined determines how we attempt to solve it. […] If the definition is wrong, you will develop the right solution to the wrong problem." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The word culture designates the sum total of the values, attitudes, traditions, and behaviors that exist in an organization." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"The word means a belief, or model of reality. A paradigm is what we believe to be true about any given situation, thing, or event. It is usually a deeply held conviction about how things actually are." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)

"You can’t delegate responsibility without giving a person authority commensurate with it." (James P Lewis, "Project Planning, Scheduling, and Control" 3rd Ed., 2001)