Pre-mortem

Last updated

A pre-mortem, or premortem, is a managerial strategy in which a project team imagines that a project or organization has failed, and then works backward to determine what potentially could lead to the failure of the project or organization. [1] [2]

The technique breaks possible groupthinking by facilitating a positive discussion on threats, increasing the likelihood the main threats are identified. Management can then reduce the chances of failure due to heuristics and biases such as overconfidence and planning fallacy by analyzing the magnitude and likelihood of each threat, and take preventive actions to protect the project or organization from suffering an untimely "death". It formalizes and expands on the acknowledgedly much older concept of prospective hindsight (Mitchell, Russo, and Pennington 1989) in which participants "look back from the future" to identify problems before they occur.

According to a Harvard Business Review article from 2007, "unlike a typical critiquing session, in which project team members are asked what might go wrong, the premortem operates on the assumption that the 'patient' has died, and so asks what did go wrong." [1]

The pre-mortem analysis seeks to identify threats and weaknesses via the hypothetical presumption of near-future failure. But if that presumption is incorrect, then the analysis may be identifying threats/weaknesses that are not in fact real.

See also

Related Research Articles

Project management is the process of leading the work of a team to achieve all project goals within the given constraints. This information is usually described in project documentation, created at the beginning of the development process. The primary constraints are scope, time, and budget. The secondary challenge is to optimize the allocation of necessary inputs and apply them to meet pre-defined objectives.

Risk management Set of measures for the systematic identification, analysis, assessment, monitoring and control of risks

Risk management is the identification, evaluation, and prioritization of risks followed by coordinated and economical application of resources to minimize, monitor, and control the probability or impact of unfortunate events or to maximize the realization of opportunities.

Business plan

A business plan is a formal written document containing the goals of a business, the methods for attaining those goals, and the time-frame for the achievement of the goals. It also describes the nature of the business, background information on the organization, the organization's financial projections, and the strategies it intends to implement to achieve the stated targets. In its entirety, this document serves as a road-map that provides direction to the business.

In business and engineering, new product development (NPD) covers the complete process of bringing a new product to market, renewing an existing product or introducing a product in a new market. A central aspect of NPD is product design, along with various business considerations. New product development is described broadly as the transformation of a market opportunity into a product available for sale. The products developed by an organisation provide the means for it to generate income. For many technology-intensive firms their approach is based on exploiting technological innovation in a rapidly changing market.

Strategic planning is an organization's process of defining its strategy, or direction, and making decisions on allocating its resources to pursue this strategy.

In the field of management, strategic management involves the formulation and implementation of the major goals and initiatives taken by an organization's managers on behalf of stakeholders, based on consideration of resources and an assessment of the internal and external environments in which the organization operates. Strategic management provides overall direction to an enterprise and involves specifying the organization's objectives, developing policies and plans to achieve those objectives, and then allocating resources to implement the plans. Academics and practicing managers have developed numerous models and frameworks to assist in strategic decision-making in the context of complex environments and competitive dynamics. Strategic management is not static in nature; the models often include a feedback loop to monitor execution and to inform the next round of planning.

A marketing plan may be part of an overall business plan. Solid marketing strategy is the foundation of a well-written marketing plan so that goals may be achieved. While a marketing plan contains a list of actions, without a sound strategic foundation, it is of little use to a business.

SWOT analysis Business planning and analysis technique

SWOT analysis is a strategic planning and strategic management technique used to help a person or organization identify strengths, weaknesses, opportunities, and threats related to business competition or project planning. It is sometimes called situational assessment or situational analysis. Additional acronyms using the same components include TOWS and WOTS-UP.

Marketing strategy is a process that can allow an organization to concentrate its limited resources on the greatest opportunities to increase sales and achieve a sustainable competitive advantage.

In strategic management, situation analysis refers to a collection of methods that managers use to analyze an organization's internal and external environment to understand the organization's capabilities, customers, and business environment. The situation analysis can include several methods of analysis such as the 5C analysis, SWOT analysis and Porter's five forces analysis.

Vulnerability (computing) Exploitable weakness in a computer system

In computer security, a vulnerability is a weakness which can be exploited by a threat actor, such as an attacker, to cross privilege boundaries within a computer system. To exploit a vulnerability, an attacker must have at least one applicable tool or technique that can connect to a system weakness. In this frame, vulnerabilities are also known as the attack surface.

Business process re-engineering

Business process re-engineering (BPR) is a business management strategy, originally pioneered in the early 1990s, focusing on the analysis and design of workflows and business processes within an organization. BPR aimed to help organizations fundamentally rethink how they do their work in order to improve customer service, cut operational costs, and become world-class competitors.

Business analysis is a professional discipline of identifying business needs and determining solutions to business problems. Solutions often include a software-systems development component, but may also consist of process improvements, organizational change or strategic planning and policy development. The person who carries out this task is called a business analyst or BA.

An incident is an event that could lead to loss of, or disruption to, an organization's operations, services or functions. Incident management (IcM) is a term describing the activities of an organization to identify, analyze, and correct hazards to prevent a future re-occurrence. These incidents within a structured organization are normally dealt with by either an incident response team (IRT), an incident management team (IMT), or Incident Command System (ICS). Without effective incident management, an incident can disrupt business operations, information security, IT systems, employees, customers, or other vital business functions.

Software project management is an art and science of planning and leading software projects. It is a sub-discipline of project management in which software projects are planned, implemented, monitored and controlled.

Context analysis is a method to analyze the environment in which a business operates. Environmental scanning mainly focuses on the macro environment of a business. But context analysis considers the entire environment of a business, its internal and external environment. This is an important aspect of business planning. One kind of context analysis, called SWOT analysis, allows the business to gain an insight into their strengths and weaknesses and also the opportunities and threats posed by the market within which they operate. The main goal of a context analysis, SWOT or otherwise, is to analyze the environment in order to develop a strategic plan of action for the business.

A market analysis studies the attractiveness and the dynamics of a special market within a special industry. It is part of the industry analysis and thus in turn of the global environmental analysis. Through all of these analyses, the strengths, weaknesses, opportunities and threats (SWOT) of a company can be identified. Finally, with the help of a SWOT analysis, adequate business strategies of a company will be defined. The market analysis is also known as a documented investigation of a market that is used to inform a firm's planning activities, particularly around decisions of inventory, purchase, work force expansion/contraction, facility expansion, purchases of capital equipment, promotional activities, and many other aspects of a company.

In software engineering, a software development process is the process of dividing software development work into smaller, parallel or sequential steps or subprocesses to improve design, product management. It is also known as a software development life cycle (SDLC). The methodology may include the pre-definition of specific deliverables and artifacts that are created and completed by a project team to develop or maintain an application.

In organizational theory, organizational analysis or industrial analysis is the process of reviewing the development, work environment, personnel, and operation of a business or another type of association. This review is often performed in response to crisis, but may also be carried out as part of a demonstration project, in the process of taking a program to scale, or in the course of regular operations. Conducting a periodic detailed organizational analysis can be a useful way for management to identify problems or inefficiencies that have arisen in the organization but have yet to be addressed, and develop strategies for resolving them.

A project post-mortem is a process used to identify the causes of a project failure, and how to prevent them in the future. This is different from a Retrospective, in which both positive and negative things are reviewed for a project.

References

  1. 1 2 Klein, G. (2007). "Performing a Project Premortem". Harvard Business Review. 85 (9): 18–19.
  2. Kahneman, D. (2011). Thinking, Fast and Slow . Farrar, Straus and Giroux. ISBN   978-0374275631.