Showing posts with label objectives. Show all posts
Showing posts with label objectives. Show all posts

06 March 2024

Business Intelligence: Data Culture (Part II: Leadership, Necessary but not Sufficient)

Business Intelligence
Business Intelligence Series

Continuing the idea from the previous post on Brent Dykes’ article on data culture and Generative AI [1], it’s worth discussing about the relationship between data culture and leadership. Leadership belongs to a list of select words everybody knows about but fails to define them precisely, especially when many traits are associated with leadership, respectively when most of the issues existing in organizations ca be associated with it directly or indirectly.

Take for example McKinsey’s definition: "Leadership is a set of behaviors used to help people align their collective direction, to execute strategic plans, and to continually renew an organization." [2] It gives an idea of what leadership is about, though it lacks precision, which frankly is difficult to accomplish. Using modifiers like strong or weak with the word leadership doesn’t increase the precision of its usage. Several words stand out though: direction, strategy, behavior, alignment, renewal.

Leadership is about identifying and challenging the status quo, defining how the future will or could look like for the organization in terms of a vision, a mission and a destination, translating them into a set of goals and objectives. Then, it’s about defining a set of strategies, focusing on transformation and what it takes to execute it, adjusting the strategic bridge between goals and objectives, or, reading between the lines, identifying and doing the right things, being able to introduce a new order of things, reinventing the organization, adapting the organization to circumstances.

Aligning resumes in aligning the various strategies, aligning people with the vision and mission, while renewal is about changing course in response to new information or business context, identifying and transforming weaknesses into strengths, risks into opportunities, respectively opportunities into certitudes, seeing possibilities and multiplying them.

Leadership is also about working on the system, addressing the systemic failure, addressing structural and organizational issues, making sure that the preconditions and enablers for organizational change are in place, that no barriers exist or other factors impact negatively the change, that the positive aspects of complex systems like emergence or exponential growth do happen in time.

And leadership is about much more - interpersonal influence, inspiring people, Inspiring change, changing mindsets, assisting, motivating, mobilizing, connecting, knocking people out of their comfort zones, conviction, consistency, authority, competence, wisdom, etc. Leadership seems to be an idealistic concept where too many traits are considered, traits that ideally should apply to the average knowledge worker as well.

An organization’s culture is created, managed, nourished, and destroyed through leadership, and that’s a strong statement and constraint. By extension this statement applies to the data culture as well. It’s about leading by example and not by words or preaching, and many love to preach, even when no quire is around. It’s about demanding the same from the managers as managers demand from their subalterns, it’s about pushing the edges of culture. As Dykes mentions, it should be about participating in the data culture initiatives, making expectations explicit, and sharing mental models.

Leadership is a condition necessary but not sufficient for an organizations culture to mature. Financial and other type of resources are needed, though once a set of behaviors is seeded, they have the potential to grow and multiply when the proper conditions are met. Growth occurs also by being aware of what needs to be done and doing it day by day consciously, through self-mastery. Nowadays there are so many ways to learn and search for support, one just needs a bit of curiosity and drive to learn anything. Blaming in general the lack of leadership is just a way of passing the blame one level above on the command chain.

Resources:
[1] Forbes (2024) Why AI Isn’t Going To Solve All Your Data Culture Problems, by Brent Dykes (link)
[2] McKinsey (2022) What is leadership? (link)

Previous Post <<||>> Next Post

03 February 2021

Data Migrations (DM): Conceptualization II (Plan vs. Concept vs. Strategy)

Data Migration
Data Migrations Series

A concept is a document that describes at high level the set of necessary steps and their implications to achieve a desired result, typically making the object of a project. A concept is usually needed to provide more technical and nontechnical information about the desired solution, the context in which a set of steps are conducted, respectively the changes considered, how the changes will be implemented and the further aspects that need to be considered. It can include a high-level plan and sometimes also information that typically belong in a Business Case – goals,objectives, required resources, estimated effort and costs, risks and opportunities.

A concept is used primarily as basis for sign-off as well for establishing common ground and understanding. When approved, it’s used for the actual implementation and solution’s validation. The concept should be updated as the project progresses, respectively as new information are discovered.

Creating a concept for a DM can be considered as best practice because it allows documenting the context, the technical and organizational requirements and dependencies existing between the DM and other projects, how they will be addressed. The concept can include also a high-level plan of the main activities (following to be detailed in a separate document).

Especially when the concept has an exploratory nature (due to incomplete knowledge or other considerations), it can be validated with the help of a proof-of-concept (PoC), the realization of a high-level-design prototype that focuses on the main characteristics of the solution and allows thus identifying the challenges. Once the PoC implemented, the feedback can be used to round out the concept.

Building a PoC for a DM should be considered as objective even when the project doesn’t seem to meet any major challenges. The PoC should resume in addressing the most important DM requirements, ideally by implementing the whole or most important aspects of functionality (e.g. data extraction, data transformations, integrity validation, respectively the import into the target system) for one or two data entities. Once the PoC built, the team can use it as basis for the evolutive development of the solution during the iterations considered.

A strategy is a set of coordinated and sustainable actions following a set of well-defined goals, actions devised into a plan and designed to create value and overcome further challenges. A strategy has the character of a concept though it has a broader scope being usually considered when multiple projects or initiatives compete for the same resources to provide a broader context and handle the challenges, risks and opportunities. Moreover, the strategy takes an inventory of the current issues and architecture – the 'AS-IS' perspective and sketches the to 'TO-BE' perspective by devising a roadmap that bridges the gap between the two.

In the case of a DM a strategy might be required when multiple DM projects need to be performed in parallel or sequentially, as it can help the organization to better manage the migrations.

A plan is a high-level document that describes the tasks, schedule and resources required to carry on an activity. Even if it typically refers to the work or product breakdown structure, it can cover other information usually available in a Business Case. A project plan is used to guide both project execution and project control, while in the context of Strategic Management the (strategic) plan provides a high-level roadmap on how the defined goals and objectives will be achieved during the period covered by the strategy.

For small DM projects a plan can be in theory enough. As both a strategy and a concept can include a high-level plan, the names are in praxis interchangeable.

Previous Post <<||>> Next Post

02 February 2021

Data Migrations (DM): Conceptualization I (Goals, Objectives & Requirements)

Data Migration
Data Migrations Series

One of the nowadays’ challenges is finding the right mix of technologies that allows building a solution for a business need. There are so many choices and the responsible person is easily tempted to use one of the trending technologies just because he wants to learn something new or the technologies seem to fit into the bigger picture, which probably in many cases it would be acceptable. Unfortunately, there’s also the tendency of picking a technology without looking at what functionality it provides, respectively whether the functionality meets intended solutions’ requirements. Moreover, the requirements are sometimes barely defined at the appropriate level of detail, fact that makes from the implementation project a candidate for failure. Sometimes even the goals and objectives aren’t clearly stated, fact that can make a project’s success easily questionable from the beginning. 

A goal is a general statement that reflects the desired result toward which an organization’s effort needs to be directed. For example, a Data Migration (DM)’s primary goal can be formulated as 'to make available all the master and transactional data needed by the business from the legacy systems to the target system(s) within expected timeline and quality with a minimal disruption for the business'. 

An objective is a break down of the goal into several components that should foster a clear understanding on how the goal will be achieved. Ideally the objectives should be SMART (specific, measurable, attainable, relevant, time-bound), even if measurable objectives are sometimes hard to define properly. One can consider them as the tactics used in achieving the goal. For example, the above formulated goal can be broken down into the following objectives:

  • Build a DM concept/strategy
  • Build a flexible and performant infrastructure for DM that can be adapted to further requirements
  • Provide a basis for further DMs
  • Align DM and main project’s requirements and activities
  • Provide an interface and support for the Data Management areas
  • Foster trust, transparency and awareness 
  • Address internal/external compliance requirements
  • Document and communicate accountability for the various activities
  • Cleanse and enrich the data needed by the target system 
  • Archive the DM and project data 

One can attempt defining the objectives directly from the goal(s), though unless one is aware of all the implication a DM has, more likely one will be forced to define and evaluate the individual functional and nonfunctional requirements for the DM first, and attempt consolidating the requirements into a set of objectives. In the end it can be a combination of both, in which some objectives are first formulated, the requirements are defined and evaluated, respectively the objectives are refined to accommodate the requirements. 

ISO 9126, an international standard for the evaluation of software quality, defines about 45-50 attributes that can be used for addressing the requirements of software solutions, attributes that reflect functionality, reliability, usability, efficiency, and maintainability characteristics. One can start with such a list and identify how important are the respective attributes for the solution.  The next step would be to document the requirements into a consolidated list by providing a short argumentation for their use, respectively how they will be addressed as part of the solution. The process can prove to be time-consuming, however it is a useful exercise that usually needs to be done only once and be reviewed occasionally.

The list can be created independently of any other documentation or be included directly into a concept or strategy. The latter will assure in theory that the document provides a unitary view of the migration, considering that each new or obsolete requirement can impact the concept. 

Previous Post <<||>> Next Post

05 January 2021

ERP Implementations: It’s all about Scope II (Nonfunctional Requirements & MVP)

ERP Implementation

Nonfunctional Requirements

In contrast to functional requirements (FRs), nonfunctional requirements (NFRs) have no direct impact on system’s behavior, affecting end-users’ experience with the system, resuming thus to topics like performance, usability, reliability, compatibility, security, monitoring, maintainability, testability, respectively other constraints and quality attributes. Even if these requirements are in general addressed by design, the changes made to the system have the potential of impacting users’ experience negatively.  

Moreover, the NFRs are usually difficult to quantify, and probably that’s why they are seldom made explicit in a formal document or are considered eventually only at high level. However, one can still find a basis for comparison against compliance requirements, general guidelines, standards, best practices or the legacy system(s) (e.g. the performance should not be worse than in the legacy system, the volume of effort for carrying the various activities should not increase). Even if they can’t be adequately described, it’s recommended to list the NFRs in general terms in a formal document (e.g. implementation contract). Failing to do so can open or widen the risk exposure one has, especially when the system lacks important support in the respective areas. In addition, these requirements need to be considered during testing and sign-off as well. 

Minimum Viable Product (MVP)

Besides gaps’ consideration in respect to FRs, it’s important to consider sometimes on whether the whole functionality is mandatory, especially when considering the various activities that need to be carried out (parametrization, Data Migration).

For example, one can target to implement a minimum viable product (MVP) - a version of the product which has just enough features to cover the mandatory or the most important FRs. The MVP is based on the idea that implementing about 80% of the needed functionality has in theory the potential of providing earlier a usable product with a minimum of effort (quick wins), assure that project’s goals and objectives were met, respectively assure a basis for further development. In case of cost overruns, the MVP assures that the business has a workable product and has the opportunity of deciding whether it’s worth of investing more into the project now or later. 

The MVP allows also to get early users’ feedback and integrate it into further enhancements and developments. Often the users understand the capabilities of a system, respectively implementation, only when they are able using the system. As this is a learning process, the learning period can take up to a few months until adequate feedback is available. Therefore, postponing implementation’s continuation with a few months can have in theory a positive impact, however it can come also with drawbacks (e.g. the resources are not available anymore). 

A sketch of the MVP usually results from requirements’ prioritization, however then requirements need to be regarded holistically, as there can be different levels of dependencies existing between them. In addition, different costs can incur if the requirements will be handled later, and other constrains may apply as well. Considering an MVP approach can be a sword with two edges. In the worst-case scenario, the business will get only the MVP, with its good and bad characteristics. The business will be forced then to fill the gaps by working outside the system, which can lead to further effort and, in extremis, with poor acceptance of the system. In general, users expect having their processes fully implemented in the system, expectation which is not always economically grounded.

After establishing an MVP one can consider the further requirements (including improvement suggestions) based on a cost-benefit basis and implement them accordingly as part of a continuous improvement initiative, even if more time will be maybe required for implementing the same.

Previous Post <<||>> Next Post



03 January 2021

Governance: Responsibility (Just the Quotes)

"Weak character coupled with honored place, meager knowledge with large plans, limited powers with heavy responsibility, will seldom escape disaster." ("I Ching" ["Book of Changes"], cca. 600 BC)

"The only way for a large organization to function is to decentralize, to delegate real authority and responsibility to the man on the job. But be certain you have the right man on the job." (Robert E Wood, 1951)

"[...] authority - the right by which superiors are able to require conformity of subordinates to decisions - is the basis for responsibility and the force that binds organization together. The process of organizing encompasses grouping of activities for purposes of management and specification of authority relationships between superiors and subordinates and horizontally between managers. Consequently, authority and responsibility relationships come into being in all associative undertakings where the superior-subordinate link exists. It is these relationships that create the basic character of the managerial job." (Harold Koontz & Cyril O Donnell, "Principles of Management", 1955)

"[...] authority for given tasks is limited to that for which an individual may properly held responsible." (Harold Koontz & Cyril O Donnell, "Principles of Management", 1955)

"If charts do not reflect actual organization and if the organization is intended to be as charted, it is the job of effective management to see that actual organization conforms with that desired. Organization charts cannot supplant good organizing, nor can a chart take the place of spelling out authority relationships clearly and completely, of outlining duties of managers and their subordinates, and of defining responsibilities." (Harold Koontz & Cyril O Donnell, "Principles of Management", 1955)

"Responsibility cannot be delegated. While a manager may delegate to a subordinate authority to accomplish a service and the subordinate in turn delegate a portion of the authority received, none of these superiors delegates any of his responsibility. Responsibility, being an obligation to perform, is owed to one's superior, and no subordinate reduces his responsibility by assigning the duty to another. Authority may be delegated, but responsibility is created by the subordinate's acceptance of his assignment." (Harold Koontz & Cyril O Donnell, "Principles of Management", 1955)

"Viewed internally with respect to the enterprise, responsibility may be defined as the obligation of a subordinate, to whom a superior has assigned a duty, to perform the service required. The essence of responsibility is, then, obligation. It has no meaning except as it is applied to a person." (Harold Koontz & Cyril O Donnell, "Principles of Management", 1955)

"You can delegate authority, but you can never delegate responsibility by delegating a task to someone else. If you picked the right man, fine, but if you picked the wrong man, the responsibility is yours - not his." (Richard E Krafve, The Boston Sunday Globe, 1960)

"Modern organization makes demands on the individual to learn something he has never been able to do before: to use organization intelligently, purposefully, deliberately, responsibly [...] to manage organization [...] to make [...] his job in it serve his ends, his values, his desire to achieve." (Peter F Drucker, The Age of Discontinuity, 1968)

"[Management by objectives is] a process whereby the superior and the subordinate managers of an enterprise jointly identify its common goals, define each individual's major areas of responsibility in terms of the results expected of him, and use these measures as guides for operating the unit and assessing the contribution of each of its members." (Robert House, "Administrative Science Quarterly", 1971)

"'Management' means, in the last analysis, the substitution of thought for brawn and muscle, of knowledge for folkways and superstition, and of cooperation for force. It means the substitution of responsibility for obedience to rank, and of authority of performance for authority of rank. (Peter F Drucker, "People and Performance", 1977)

"[...] the first criterion in identifying those people within an organization who have management responsibility is not command over people. It is responsibility for contribution. Function rather than power has to be the distinctive criterion and the organizing principle." (Peter F Drucker, "People and Performance", 1977)

"The productivity of work is not the responsibility of the worker but of the manager." (Peter F Drucker, "Management in Turbulent Times", 1980)

"By assuming sole responsibility for their departments, managers produce the very narrowness and self-interest they deplore in subordinates. When subordinates are relegated to their narrow specialties, they tend to promote their own practical interests, which then forces other subordinates into counter-advocacy. The manager is thereby thrust into the roles of arbitrator, judge, and referee. Not only do priorities become distorted, but decisions become loaded with win/lose dynamics. So, try as the manager might, decisions inevitably lead to disgruntlement and plotting for the next battle." (David L Bradford & Allan R Cohen, "Managing for Excellence", 1984)

"The man who delegates responsibilities for running the company, without knowing the intimate details of what is involved, runs the enormous risk of rendering himself superfluous." (Harold Geneen, "Managing", 1984)

"Leadership is the total effect you have on the people and events around you. This effect is your influence. Effective leading is being consciously responsible for your organizational influence. [...] The essence of leadership is knowing that YOU CAN NEVER NOT LEAD. You lead by acts of commission and acts of omission." (Kenneth Schatz & Linda Schatz, "Managing by Influence", 1986)

"Looking for differences between the more productive and less productive organizations, we found that the most striking difference is the number of people who are involved and feel responsibility for solving problems." (Michael McTague, "Personnel Journal", 1986)

"Management has a responsibility to explain to the employee how the routine job contributes to the business's objectives. If management cannot explain the value of the job, then it should be eliminated and the employee reassigned." (Douglas M Reid, Harvard Business Review, 1986)

"A systematic effort must be made to emphasize the group instead of the individual. [...] Group goals and responsibilities can usually overcome any negative reactions to the individual and enforce a standard of cooperation that is attainable by persuasion or exhortation." (Eugene Raudsepp, MTS Digest, 1987)

"An individual without information cannot take responsibility; an individual who is given information cannot help but take responsibility." (Jan Carlzon, "Moments of Truth", 1987)

"Executives have to start understanding that they have certain legal and ethical responsibilities for information under their control." (Jim Leeke, PC Week, 1987)

"If responsibility - and particularly accountability - is most obviously upwards, moral responsibility also reaches downwards. The commander has a responsibility to those whom he commands. To forget this is to vitiate personal integrity and the ethical validity of the system." (Roger L Shinn, "Military Ethics", 1987)

[...] quality assurance is the job of the managers responsible for the product. A separate group can't 'assure' much if the responsible managers have not done their jobs properly. [...] Managers should be held responsible for quality and not allowed to slough off part of their responsibility to a group whose name sounds right but which cannot be guaranteed quality if the responsible managers have not been able to do so." (Philip W. Metzger, "Managing Programming People", 1987)

"Responsibility is a unique concept [...] You may share it with others, but your portion is not diminished. You may delegate it, but it is still with you. [...] If responsibility is rightfully yours, no evasion, or ignorance or passing the blame can shift the burden to someone else. Unless you can point your finger at the man who is responsible when something goes wrong, then you have never had anyone really responsible." (Hyman G Rickover, "The Rickover Effect", 1992)

"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)

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

"What do people do today when they don’t understand 'the system'? They try to assign responsibility to someone to fix the problem, to oversee 'the system', to coordinate and control what is happening. It is time we recognized that 'the system' is how we work together. When we don’t work together effectively putting someone in charge by its very nature often makes things worse, rather than better, because no one person can understand 'the system' well enough to be responsible. We need to learn how to improve the way we work together, to improve 'the system' without putting someone in charge, in order to make things work." (Yaneer Bar-Yam, "Making Things Work: Solving Complex Problems in a Complex World", 2004)

"In order to cultivate a culture of accountability, first it is essential to assign it clearly. People ought to clearly know what they are accountable for before they can be held to it. This goes beyond assigning key responsibility areas (KRAs). To be accountable for an outcome, we need authority for making decisions, not just responsibility for execution. It is tempting to refrain from the tricky exercise of explicitly assigning accountability. Executives often hope that their reports will figure it out. Unfortunately, this is easier said than done." (Sriram Narayan, "Agile IT Organization Design: For Digital Transformation and Continuous Delivery", 2015)

"Any software project must have a technical leader, who is responsible for all technical decisions made by the team and have enough authority to make them. Responsibility and authority are two mandatory components that must be present in order to make it possible to call such a person an architect." (Yegor Bugayenko, "Code Ahead", 2018)

"Responsibility means an inevitable punishment for mistakes; authority means full power to make them." (Yegor Bugayenko, "Code Ahead", 2018)

21 May 2020

Project Management: Planing Correctly Misundersood III

Mismanagement

One of the most misunderstood topics in Project Management seems to be the one of planning, and this probably because everyone has a good idea of what it means to plan an activity – we do it daily and most of the times (hopefully) we hit a bull’s-eye (or we have the impression we did that). You must do this and that, you have that dependency, you must coordinate with a few people, you must first reach that milestone before going further, you do one step at a time, and so on. It’s pretty easy, isn’t it?

From a bird’s eyes view project planning is like planning every other activity though there are several important differences. The most important one is of scale – the number of activities and resources involved, the level of coordination and communication, as well the quality with which occur, the level of uncertainty and control, respectively manageability. All these create a complexity that is hardly manageable by just one person. 

Another difference is the detail needed for the planning and targets’ reachability. Some believe that the plan needs to be done down to the lowest level of detail, which even if possible can prove to be an impediment to planning. Projects’ environment share some important characteristics with a battle field in terms of complexity of interactions, their dynamics and logistical requirements. Within an army’s structure there are levels of organization that require different mindsets and levels of planning. A general thinks primarily at strategic level in which troops and actions are seen as aggregations at the needed level of abstraction that makes their organization and planning manageable. The strategy is done however in collaboration with other generals and upper structures, while having defined the strategic goals the general must devise together with the immediate subalterns the tactics. In theory the project manager must regard the project from the same perspective. Results thus three levels of planning – strategic, done with the upper management, tactical done with the team members, respectively logistical, done within the team. That’s a way of breaking the complexity and dividing the responsibilities within the project. 

Projects’ final destination seem to have the character of a wish list more or less anchored in reality. From a technical point the target can be achievable though in big projects the most important challenges are of organizational nature – of being able to allocate and coordinate effectively the resources as needed by the project. The wish-like character is reflected also by the cost, scope, time triangle in respect to the expected quality – to some point in time one is forced to choose between two of them. On the other side, there’s the tendency to see the targets and milestones as fixed, with little room for deviation. One can easily forget that a strategic plan’s purpose is to set the objectives, identify the challenges and the possible lines of action, while a tactical plan’s objective is to devise the means to reach the objectives. Bringing everything together can easily obscure the view and, in extremis, the plan loses its actuality as soon was created (and approved). 

The most confusing aspect is probably the adherence of a plan to a given methodology, one dicing a project and thus a plan to fit a methodology by following blindly the rules and principles imposed by it instead of fitting the methodology to a project. Besides the fact that the methodologies are best practices but not necessarily good practices, what fits for an organization, they tend to be either too general, by specifying the what and not the how, or too restrictive (interpreted). 

22 November 2019

Business Process Management: Business Process (Definitions)

"A business process is a collection of activities that takes one or more kinds of input and creates an output that is of value to the customer. A business process has a goal and is affected by events occurring in the external world or in other processes." (James A Champy & Michael M Hammer, "Reengineering the Corporation", 1993)

"A process is a set of linked activities that take an input and transform it to create an output. Ideally, the transformation that occurs in the process should add value to the input and create an output that is more useful and effective to the recipient either upstream or downstream."
(Henry J Johansson, "Business process reengineering: Breakpoint strategies for market dominance", 1993)

"Major operational activities or processes supported by a source system, such as orders, from which data can be collected for the analytic purposes of the data warehouse. Choosing the business process is the first of four key steps in the design of a dimensional model." (Ralph Kimball & Margy Ross, "The Data Warehouse Toolkit" 2nd Ed., 2002)

"The sequence of activities 'enclosing' the production process. These activities are common to all types of products and services, and include defining the job, negotiation with the customer, and reporting project status." (Richard D Stutzke, "Estimating Software-Intensive Systems: Projects, Products, and Processes", 2005)

"The subject areas of a business. The method by which a business is divided up. In a data warehouse, the subject areas become the fact tables." (Gavin Powell, "Beginning Database Design", 2006)

"A structured description of the activities or tasks that have to be done to fulfill a certain business need. The activities or tasks might be manual steps (human interaction) or automated steps (IT steps)." (Nicolai M Josuttis, "SOA in Practice", 2007)

"A structured and measured, managed, and controlled set of interrelated and interacting activities that uses resources to transform inputs into specified outputs." (Nathalíe Galeano, "Competency Concept in VO Breeding Environment", 2008) 

"The codification of rules and practices that constitute a business." (Judith Hurwitz et al, "Service Oriented Architecture For Dummies" 2nd Ed., 2009)

"The defined method for a range of activities that organizations perform. A business process can include anything from the steps needed to make a product to how a supply is ordered or how an invoice is created." (Tony Fisher, "The Data Asset", 2009)

"A structured description of the activities or tasks that have to be done to fulfill a certain business need. The activities or tasks might be manual steps (human interaction) or automated steps (IT steps)." (David Lyle & John G Schmidt, "Lean Integration", 2010)

"An activity as carried out by business people, including the mechanisms involved. This is in the domain of Row Two, the Business Owner’s View. Alternatively, the architect in Row Three sees a system process which is about the data transformations involved in carrying out a business process. In either case, processes can be viewed at a high level or in atomic detail." (David C Hay, "Data Model Patterns: A Metadata Map", 2010)

"A collection of activities performed to accomplish a clearly defined goal." (Linda Volonino & Efraim Turban, "Information Technology for Management" 8th Ed., 2011)

"A collection of activities designed to produce a specific output for a particular customer or market." (International Qualifications Board for Business Analysis, "Standard glossary of terms used in Software Engineering", 2011)

"A process that is intended to contribute to the overall value of an enterprise. The complex interactions between people, applications, and technologies designed to create customer value. A process is composed of activities." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"A business process is a series of steps required to execute a function that is important to an organization. Business processes include things like taking an order or setting up an account or paying a claim. In process analysis, business processes are the focus of opportunities for improvement. Organizations usually have a set of key processes that require support from other areas, like information technology." (Laura Sebastian-Coleman, "Measuring Data Quality for Ongoing Improvement ", 2012)

 "A holistic management approach for the detection, analysis, modeling, implementation, improvement and governance of the activities within or between enterprises." (Michael Fellmann et al, "Supporting Semantic Verification of Process Models", 2012)

"An activity (or set of activities) that is managed by an organization to produce some result of value to that organization, its customers, its suppliers, and/or its partners." (Graham Witt, "Writing Effective Business Rules", 2012)

"The codification of rules and practices that constitute a business." (Marcia Kaufman et al, "Big Data For Dummies", 2013)

"A coordinated set of collaborative and transactional work activities carried out to complete work steps." (Robert F Smallwood, "Information Governance: Concepts, Strategies, and Best Practices", 2014)

"The defined method for a range of activities that organizations perform. A business process can include anything from the steps needed to make a product to how a supply is ordered or how a decision is made." (Jim Davis & Aiman Zeid, "Business Transformation", 2014)

"A set of activities that teams within an organization carry out to accomplish a specific goal." (David K Pham, "From Business Strategy to Information Technology Roadmap", 2016)

"The business activities executed to deliver products or services to external customers. Business process is supported by and consumes IT-services to achieve their objectives." (by Brian Johnson & Leon-Paul de Rouw, "Collaborative Business Design", 2017)

"At its most generic, any set of activities performed by a business that is initiated by an event, transforms information, materials or business commitments, and produces an output. Value chains and large-scale business processes produce outputs that are valued by customers. Other processes generate outputs that are valued by other processes." (Appian)

29 July 2019

IT: Best Practices (Definitions)

"A preferred and repeatable action or set of actions completed to fulfill a specific requirement or set of requirements during the phases within a product-development process." (Clyde M Creveling, "Six Sigma for Technical Processes: An Overview for R Executives, Technical Leaders, and Engineering Managers", 2006)

"A process or method that is generally recognized to produce superior results. The application of these should result in a positive, measurable change." (Tilak Mitra et al, "SOA Governance", 2008)

"A technique or methodology that, through past experience and research, has proven to reliably lead to a desired result. A commitment to using the best practices in any field (for example, in the domain of IT Architecture) ensures leveraging past experience and all of the knowledge and technology at one’s disposal to ensure success." (Allen Dreibelbis et al, "Enterprise Master Data Management", 2008)

"An effective way of doing something. It can relate to anything from writing program code to IT governance." (Judith Hurwitz et al, "Service Oriented Architecture For Dummies" 2nd Ed., 2009)

"A best practice is commonly understood to be a well-proven, repeatable, and established technique, method, tool, process, or activity that is more certain in delivering the desired results. This indicates that a best practice typically has been used by a large number of people or organizations and/or over a long time, with significant results that are clearly superior over other practices. Knowledge patterns can be used to formalize the description of a best practice." (Jörg Rech et al, "Knowledge Patterns" [in "Encyclopedia of Knowledge Management" 2nd Ed.], 2011)

"A specific method that improves the performance of a team or an organization and can be replicated or adapted elsewhere. Best practices often take the form of guidelines, principles, or ideas that are endorsed by a person or governing body that attests to the viability of the best practice." (Gina Abudi & Brandon Toropov, "The Complete Idiot's Guide to Best Practices for Small Business", 2011)

"A technique, method, process, discipline, incentive, or reward generally considered to be more effective at delivering a particular outcome than by other means." (Craig S Mullins, "Database Administration", 2012)

"In general, Best Practices refer to the methods, currently recognized within a given industry or discipline, to achieve a stated goal or objective. In the OPM3 context, Best Practices are achieved when an organization demonstrates consistent organizational project management processes evidenced by successful outcomes." (Project Management Institute, "Organizational Project Management Maturity Model (OPM3)" 3rd Ed, 2013)

"An effective way of doing something. It can relate to anything from writing program code to IT governance." (Marcia Kaufman et al, "Big Data For Dummies", 2013)

"Those methods, processes, or procedures that have been proven to be the most effective, based on real-world experience and measured results." (Robert F Smallwood, "Information Governance: Concepts, Strategies, and Best Practices", 2014)

"Best practices are defined as commercial or professional procedures that are accepted or prescribed as being effective most of the time. It can also be considered a heuristic, in that is a rule of thumb that generally succeeds but is not guaranteed to always work in every instance." (Michael Winburn & Aaron Wheeler, "Cloud Storage Security", 2015)

"A 'benchmarking' approach where organisations determine who the leader in a particular practice is and then copy that approach. Useful for achieving efficiencies but may diminish differentiation if not used with caution at the strategic level." (Duncan Angwin & Stephen Cummings, "The Strategy Pathfinder" 3rd Ed., 2017)

"A proven activity or process that has been successfully used by multiple enterprises." (ISACA) 

"A superior method or innovative practice that contributes to the improved performance of an organization, usually recognized as best by other peer organizations." (American Society for Quality)

12 February 2019

IT: IT Governance (Definitions)

"Framework for the leadership, organizational structures and business processes, standards and compliance to these standards, which ensure that the organization’s IT supports and enables the achievement of its strategies and objectives." (Alan Calder, "IT Governance: Guidelines for Directors", 2005)

"The processes, policies, relationships, and mechanisms that ensure that information technology delivers business value while balancing risk and investment decisions. IT governance ensures accountability and provides rigor for managing IT capabilities in the context of a larger corporate governance framework." (Evan Levy & Jill Dyché, "Customer Data Integration", 2006)

"Addresses the application of governance to an IT organization and its people, processes, and information to guide the way those assets support the needs of the business. It may be characterized by assigning decision rights and measures to processes." (Tilak Mitra et al, "SOA Governance", 2008)

"IT governance is the system and structure for defining policy and monitoring and controlling the policy implementation, and managing and coordinating the procedures and resources aimed at ensuring the efficient and effective execution of services." (Anton Joha & Marijn Janssen, "The Strategic Determinants of Shared Services", 2008)

"The discipline of managing IT as a service to the business, aligning IT objectives with business goals." (Allen Dreibelbis et al, "Enterprise Master Data Management", 2008)

"An integral part of enterprise governance and consists of the leadership and organizational structures and processes that ensure the enterprise’s IT sustains and extends the organization’s strategies and objectives." (Edephonce N Nfuka & Lazar Rusu, IT Governance in the Public Sector in a Developing Country, 2009)

"(1) Locus of IT decision-making authority (narrow definition). (2) The distribution of IT decision-making rights and responsibilities among different stakeholders in the organization, and the rules and procedures for making and monitoring decisions on strategic IT concerns (comprehensive definition)." (Ryan R Peterson, "Trends in Information Technology Governance", 2009)

"Structure of relationships and processes to direct and control the IT enterprise to achieve IT’s goals by adding value while balancing risk versus return over IT and its processes." (IT Governance Institute, "IT Governance Implementation Guide, Using COBIT and Val IT", 2010)

"The discipline of tracking, managing, and steering an IS/IT landscape. Architectural governance is concerned with change processes (design governance). Operational governance looks at the operational performance of systems against contracted performance levels, the definition of operational performance levels, and the implementation of systems that ensure the effective operation of systems." (David Lyle & John G Schmidt, "Lean Integration", 2010)

"Formally established statements that direct the policies regarding IT alignment with organizational goals and allocation of resources." (Linda Volonino & Efraim Turban, "Information Technology for Management 8th Ed", 2011)

"Supervision monitoring and control of an organization's IT assets." (Linda Volonino & Efraim Turban, "Information Technology for Management" 8th Ed, 2011)

"The processes and relationships that lead to reasoned decision making in IT." (Steven Romero, "Eliminating ‘Us and Them’", 2011)

"The function of ensuring that the enterprise's IT activities match and support the organization's strategies and objectives. Governance is very often associated with budgeting, project management, and compliance activities." (Bill Holtsnider & Brian D Jaffe, "IT Manager's Handbook" 3rd Ed, 2012)

"Controls and process to improve the effectiveness of information technology; also, the primary way that stakeholders can ensure that investments in IT create business value and contribute toward meeting business objectives." (Robert F Smallwood, "Information Governance: Concepts, Strategies, and Best Practices", 2014)

"Processes used to ensure that IT resources are aligned with the goals of the organization. Organizations often use frameworks to help them with IT governance." (Darril Gibson, "Effective Help Desk Specialist Skills", 2014)

"The framework of rules and practices by which an organization structures its technology decision-making process in order to ensure alignment of the organization's business strategy with its operations." (David K Pham, "From Business Strategy to Information Technology Roadmap", 2016)

"Set of methods and techniques for reaching full alignment between business strategy and IT strategy." (Dalia S Vugec, "IT Strategic Grid: A Longitudinal Multiple Case Study", 2019)

"The processes that ensure the effective and efficient use of IT in enabling an organization to achieve its goals." (Lili Aunimo et al, "Big Data Governance in Agile and Data-Driven Software Development: A Market Entry Case in the Educational Game Industry", 2019)

"The structures, processes, and mechanisms by which the current and future use of ICT is directed and controlled." (Konstantinos Tsilionis & Yves Wautelet, "Aligning Strategic-Driven Governance of Business IT Services With Their Agile Development: A Conceptual Modeling-Based Approach", 2021)

"IT governance (ITG) is defined as the processes that ensure the effective and efficient use of IT in enabling an organization to achieve its goals." (Gartner)

"The system by which the current and future use of IT is directed and controlled, Corporate Governance of IT involves evaluating and directing the use of IT to support the organisation and monitoring this use to achieve plans." (ISO/IEC 38500)

01 February 2017

Data Management: Data Strategy (Definitions)

"A business plan for leveraging an enterprise’s data assets to maximum advantage." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

[enterprise data strategy:] "A data strategy supporting the entire enterprise." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

[data management strategy:] "Selected courses of actions setting the direction for data management within the enterprise, including vision, mission, goals, principles, policies, and projects." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"A data strategy is a plan for maintaining and improving the quality, integrity, security, and access of the enterprise data. It typically includes business plans that describe how the data will be used to support the enterprise business strategy and goals." (Dewey E Ray, "Valuing Data: An Open Framework", 2018)

"A data strategy is not an algorithm, buzzword, IT project, technology or application, collection of data in storage, department or team, or project or tactic. A data strategy is a set of organization-wide objectives leading to highly efficient processes that turn data resources into outcomes that help the organization fulfill its mission." (Harvinder Atwal, "Practical DataOps: Delivering Agile Data Science at Scale", 2019)

"A data strategy is a plan designed to improve all the ways you acquire, store, manage, share, and use data." (Evan Levy, "TDWI Data Strategy Assessment Guide", 2021)

"A data strategy is a central, integrated concept that articulates how data will enable and inspire business strategy." (MIT CISR)

"A data strategy is a common reference of methods, services, architectures, usage patterns and procedures for acquiring, integrating, storing, securing, managing, monitoring, analyzing, consuming and operationalizing data." (DXC.Technology) [source]

"A data strategy is a highly dynamic process employed to support the acquisition, organization, analysis, and delivery of data in support of business objectives." (Gartner)

30 December 2016

Strategic Management: Leadership (Just the Quotes)

"Such cases also occur in strategy, since strategy is directly linked to tactical action. In strategy too decisions must often be based on direct observation, on uncertain reports arriving hour by hour and day by day, and finally on the actual outcome of battles. It is thus an essential condition of strategic leadership that forces should be held in reserve according to the degree of strategic uncertainty." (Carl von Clausewitz, "On War", 1832)

"Do not confuse objectives with methods. When the nation becomes substantially united in favor of planning the broad objectives of civilization, then true leadership must unite thought behind definite methods." (Franklin D Roosevelt, 1937)

"No amount of study or learning will make a man a leader unless he has the natural qualities of one." (Archibald Wavell, "Generals and Generalship", 1941)

"Leadership is interpersonal influence, exercised in a situation, and directed, through the communication process, toward the attainment of a specified goal or goals." (Robert K Tanenbaum, "Leadership and Organization", 1961)

"The leadership and other processes of the organization must be such as to ensure a maximum probability that in all interactions and all interactions and all relationships with the organization each member will, in the light of his background, values, and expectations, view the experience as supportive and one which builds and maintains his sense of personal worth and importance." (Rensis Likert, "New patterns of management", 1961)

"Leadership is lifting a person's vision to higher sights, the raising of a person's performance to a higher standard, the building of a personality beyond its normal limitations." (Peter Drucker, "Management: Tasks, Responsibilities, Challenges", 1973)

"A leader is one who, out of madness or goodness, volunteers to take upon himself the woe of the people. There are few men so foolish, hence the erratic quality of leadership in the world." (John Updike, "They Thought They Were Better", TIME magazine, 1980)

"Leadership cannot really be taught. It can only be learned." (Harold Geneen & Alvin Moscow, "Managing", 1984)

"Leadership is practiced not so much in words as in attitude and in actions [...]" (Harold Geneen & Alvin Moscow, "Managing", 1984)

"Leadership is the very heart and soul of business management." (Harold Geneen, "Managing", 1984)

"With the changes in technological complexity, especially in information technology, the leadership task has changed. Leadership in a networked organization is a fundamentally different thing from leadership in a traditional hierarchy." (Edgar Schein, "Organizational Culture and Leadership", 1985)

"A leader must have the courage to act against an expert's advice. (James Callaghan, The Harvard Business Review, 1986)

"The very essence of leadership is that you have to have a vision. It's got to be a vision you articulate clearly and forcefully on every occasion. You can't blow an uncertain trumpet." (Theodore Hesburg, TIME magazine, 1987)

"Leadership is always dependent upon the context, but the context is established by the relationships." (Margaret J Wheatley, "Leadership and the New Science: Discovering Order in a Chaotic World", 1992)

"We have created trouble for ourselves in organizations by confusing control with order. This is no surprise, given that for most of its written history, leadership has been defined in terms of its control functions." (Margaret J Wheatley, "Leadership and the New Science: Discovering Order in a Chaotic World", 1992)

"All great leaders have understood that their number one responsibility is cultivating their own discipline and personal growth. Those who cannot lead themselves cannot lead others." (John C Maxwell, "Developing the Leader Within You", 1993)

"In effective personal leadership, visualization and affirmation techniques emerge naturally out of a foundation of well thought through purposes and principles that become the center of a person's life." (Stephen Covey, "Daily Reflections for Highly Effective People", 1994)

"The problem with most leaders today is they don't stand for anything. Leadership implies movement toward something, and convictions provide that direction. If you don't stand for something, you'll fall for anything." (Don Shula, "Everyone's a Coach: You Can Inspire Anyone to be a Winner", 1995)

"Leadership is knowing what to do next, knowing why that's important, and knowing how to bring the appropriate resources to bear on the need at hand." (Bobb Biehl. The on My Own Handbook, 1997)

"The basis of leadership is the capacity of the leader to change the mindset, the framework of the other person." (Warren Bennis, "Managing People is Like Herding Cats", 1997)

"Too many companies believe people are interchangeable. Truly gifted people never are. They have unique talents. Such people cannot be forced into roles they are not suited for, nor should they be. Effective leaders allow great people to do the work they were born to do." (Warren Bennis, "Organizing Genius: The Secrets of Creative Collaboration", 1997)

"An effective leader leaves a legacy; they leave their footprints on the road for others to follow. A good leader develops themselves and they develop others. They bring people together rather than divide them." (Joseph O’Connor, "Leading With NLP: Essential Leadership Skills for Influencing and Managing People", 1998)

"Good leaders are ethical, responsible and effective. Ethical because leadership connects you to others through shared values. Responsible because leadership means self-development and not simply giving orders, however charismatically, to get others to do what you want. Effective because shared values and goals give the strongest motivation for getting tasks done. There are no guarantees, but this sort of leadership will bring you closer to people and give you the greatest chance of success." (Joseph O’Connor, "Leading With NLP: Essential Leadership Skills for Influencing and Managing People", 1998)

"Leadership comes from our natural striving to constantly reinvent ourselves. You do not need external permission to be a leader. Nor do you need any qualifications or position of authority. Leadership does not depend on what you do already. Many people in positions of authority are not leaders; they may have the title but not the substance. Others have the substance, but no title. Leadership comes from the reality of what you do and how you think, not from your title or nominal responsibilities. Leadership blooms when the soil and climate is right, but the seed comes from within." (Joseph O’Connor, "Leading With NLP: Essential Leadership Skills for Influencing and Managing People", 1998)

"Leadership has long been associated with authority - we tend to concentrate on the leader, to think of them as innately superior in some way, and take the followers for granted. But formal authority is only one possible part of leadership. Many leaders do not have it. In some cases, perhaps ‘companionship’ better describes the relationship between leader and followers." (Joseph O’Connor, "Leading With NLP: Essential Leadership Skills for Influencing and Managing People", 1998)

"Leadership is about inspiring people through a shared set of values." (Joseph O’Connor, "Leading With NLP: Essential Leadership Skills for Influencing and Managing People", 1998)

"Good leaders make people feel that they're at the very heart of things, not at the periphery. Everyone feels that he or she makes a difference to the success of the organization. When that happens, people feel centered and that gives their work meaning." (Warren Bennis, "Managing People Is Like Herding Cats", 1999)

"Making good judgments when one has complete data, facts, and knowledge is not leadership - it's bookkeeping." (Dee Hock, "Birth of the Chaordic Age", 1999)

"The most dangerous leadership myth is that leaders are born — that there is a genetic factor to leadership. This myth asserts that people simply either have certain charismatic qualities or not. That's nonsense; in fact, the opposite is true. Leaders are made rather than born. And the way we become leaders is by learning about leadership through life and job experiences, not with university degrees. (Warren Bennis, "Managing People Is Like Herding Cats", 1999)

"The aim of leadership should be to improve the performance of man and machine, to improve quality, to increase output, and simultaneously to bring pride of workmanship to people. Put in a negative way, the aim of leadership is not merely to find and record failures of men, but to remove the causes of failure: to help people to do a better job with less effort." (W Edwards Deming, "Out of the Crisis", 2000)

"The higher you want to climb, the more you need leadership. The greater the impact you want to make, the greater your influence needs to be. Whatever you will accomplish is restricted by your ability to lead others." (John C. Maxwell, "Leadership 101: What Every Leader Needs to Know", 2002)

"The true measure of leadership is influence - nothing more, nothing less." (John C Maxwell, Leadership 101: What Every Leader Needs to Know, 2002)

"Leadership is seeing the possibilities in a situation while others are seeing the limitations." (John C Maxwell, "The 21 Irrefutable Laws of Leadership", 2007)

"Personal and organizational effectiveness is proportionate to the strength of leadership." (John C Maxwell, "The 21 Irrefutable Laws of Leadership", 2007)

"The ability to plan for what has not yet happened, for a future that has only been imagined, is one of the hallmarks of leadership." (Warren Bennis, "Organizing Genius: The Secrets of Creative Collaboration", 2007)

"The most powerful demonstration of leadership is not a clenched fist of brute force but an open hand of humble assistance." (Mike Huckabee, "From Hope to Higher Ground", 2007)

"Leadership is the capacity to influence others through inspiration motivated by passion, generated by vision, produced by a conviction, ignited by a purpose." (Myles Munroe, "Charge: Finding the Leader Within You", 2008)

"Listening to the inner voice - trusting the inner voice - is one of the most important lessons of leadership." (Warren Bennis, "On Becoming a Leader", 2009)

"A leader’s most important job is creating and constantly adjusting this strategic bridge between goals and objectives." (Richard Rumelt, "Good Strategy Bad Strategy", 2011)

"Hope without a strategy doesn't generate leadership. Leadership comes when your hope and your optimism are matched with a concrete vision of the future and a way to get there. People won't follow you if they don't believe you can get to where you say you're going." (Seth Godin, "Tribes: We need you to lead us", 2011)

"Leadership requires creating conditions that enable employees to do the kinds of experimentation that entrepreneurship requires." (Eric Ries, "The Lean Startup", 2011) 

"Restructuring is a favorite tactic of antisocials who have reached a senior position in an organization. The chaos that results is an ideal smokescreen for dysfunctional leadership. Failure at the top goes unnoticed, while the process of restructuring creates the illusion of a strong, creative hand on the helm." (Manfred F R Kets de Vries, "The Leader on the Couch", 2011)

"When organizations are unable to make new strategies - when people evade the work of choosing among different paths in the future - then you get vague mom-and-apple-pie goals everyone can agree on. Such goals are direct evidence of leadership's insufficient will or political power to make or enforce hard choices." (Richard Rumelt, "Good Strategy Bad Strategy", 2011)

"Sustainable leadership does no harm to and actively improves the surrounding environment." (Andy Hargreaves, "Sustainable Leadership", 2012)

"The exercise of true leadership is inversely proportional to the exercise of power." (Stephen Covey, "The 8th Habit: From Effectiveness to Greatness", 2013)

"The leader is one who mobilizes others toward a goal shared by leaders and followers. [...] Leaders, followers and goals make up the three equally necessary supports for leadership." (Garry Wills, "Certain Trumpets: The Nature of Leadership", 2013)

"Ultimately, leadership is not about glorious crowning acts. It's about keeping your team focused on a goal and motivated to do their best to achieve it, especially when the stakes are high and the consequences really matter. It is about laying the groundwork for others' success, and then standing back and letting them shine." (Chris Hadfield, "An Astronaut's Guide to Life on Earth", 2013)

"And when a leader embraces their responsibility to care for people instead of caring for numbers, then people will follow, solve problems and see to it that that leader's vision comes to life the right way, a stable way and not the expedient way." (Simon Sinek, "Leaders Eat Last: Why Some Teams Pull Together and Others Don't", 2014)

"Most leadership strategies are doomed to failure from the outset. As people have been noting for years, the majority of strategic initiatives that are driven from the top are marginally effective - at best." (Peter Senge, "The Dance of Change: The challenges to sustaining momentum in a learning organization", 2014)

"Truly human leadership protects an organization from the internal rivalries that can shatter a culture. When we have to protect ourselves from each other, the whole organization suffers. But when trust and cooperation thrive internally, we pull together and the organization grows stronger as a result." (Simon Sinek, "Leaders Eat Last: Why Some Teams Pull Together and Others Don't", 2014)

"The more intentional you are about your leadership growth, the greater your potential for becoming the leader you're capable of being. Never stop learning." (John C. Maxwell, "The Leadership Handbook", 2015)

"Leadership is not about being in charge. Leadership is about taking care of those in your charge." (Simon Sinek, "Together is Better: A Little Book of Inspiration", 2016)

"The traditional approach to leadership values decision-making conviction and consistency; good leaders 'stick to their guns'. By contrast, the emerging approach recognizes that in fast-changing environments, decisions often need to be reversed or adapted, and that changing course in response to new information is a strength, not a weakness. If this tension is not managed wisely, leaders run the risk of seeming too rigid, on the one hand, or too wishy-washy on the other." (Jennifer Jordan et al, "Every Leader Needs to Navigate These 7 Tensions", Harvard Business Review, 2020) [source]

"Leadership is a potent combination of strategy and character. But if you must be without one, be without the strategy." (Norman Schwarzkopf)

"Leadership is the capacity to translate vision into reality." (Warren Bennis)

"Leadership means that a group, large or small, is willing to entrust authority to a person who has shown judgement, wisdom, personal appeal, and proven competence." (Walt Disney)

"The first responsibility of a leader is to define reality." (Max DePree)

25 December 2016

Strategic Management: Decision-Making (Just the Quotes)

"The quality of a decision is like the well-timed swoop of a falcon which enables it to strike and destroy its victim." (Sun Tzu, "The Art of War", cca. 5th century BC) 

"To give a satisfactory decision as to the truth it is necessary to be rather an arbitrator than a party to the dispute." (Aristotle, "De Caelo", cca. 5th century BC)

"Men must be decided on what they will NOT do, and then they are able to act with vigor in what they ought to do." (Mencius, cca. 3rd century BC)

"To be guided in one's decisions by the present, and to prefer what is sure to what is uncertain (though more attractive), is an expedient, a narrow rule of policy. Not thus do states nor even individual men make their way to greatness." (Marquis de Vauvenargues, "Reflections and Maxims", cca. 1746)

"As mathematical and absolute certainty is seldom to be attained in human affairs, reason and public utility require that judges and all mankind in forming their opinions of the truth of facts should be regulated by the superior number of the probabilities on the one side or the other whether the amount of these probabilities be expressed in words and arguments or by figures and numbers." (William Murray, 1773) 

"Deliberate with caution, but act with decision and promptness." (Charles C Colton, "Lacon", 1820)

"The man who insists upon seeing with perfect clearness before he decides, never decides." (Henri-Frédéric Amiel, [journal entry] 1856)

"It [probability] is the very guide of life, and hardly can we take a step or make a decision of any kind without correctly or incorrectly making an estimation of probabilities." (William S Jevons, "The Principles of Science: A Treatise on Logic and Scientific Method", 1874)

"General propositions do not decide concrete cases. The decision will depend on a judgment or intuition more subtle than any articulate major premise." (Oliver W Holmes, [Lochner v. New York, 198 US 76] 1905)

Decide: "To succumb to the preponderance of one set of influences over another set." (Ambrose Bierce, "The Cynic's Dictionary", 1906)

"After a person has collected data and studied a proposition with great care so that his own mind is made up as to the best solution for the problem, he is apt to feel that his work is about completed. Usually, however, when his own mind is made up, his task is only half done. The larger and more difficult part of the work is to convince the minds of others that the proposed solution is the best one - that all the recommendations are really necessary. Time after time it happens that some ignorant or presumptuous member of a committee or a board of directors will upset the carefully-thought-out plan of a man who knows the facts, simply because the man with the facts cannot present his facts readily enough to overcome the opposition. It is often with impotent exasperation that a person having the knowledge sees some fallacious conclusion accepted, or some wrong policy adopted, just because known facts cannot be marshalled and presented in such manner as to be effective." (Willard C Brinton, "Graphic Methods for Presenting Facts", 1919)

"Certainly thinking is pleasant, but the pleasure of thinking must be subordinated to the art of making decisions." (Émile A Chartier [Alain], "On Happiness", 1928)

"Amid the pressure of great events, a general principle gives no help [in decision making]." (Georg W Hegel, "Lectures on the Philosophy of History", 1837)

"The great decisions of human life have as a rule far more to do with the instincts and other mysterious unconscious factors than with conscious will and well-meaning reasonableness. The shoe that fits one person pinches another; there is no recipe for living that suits all cases. Each of us carries his own life-form - an indeterminable form which cannot be superseded by any other." (Carl G Jung, "The Aims of Psychotherapy", 1931)

"Human decisions affecting the future [...] cannot depend on strict mathematical expectation." (John M Keynes, "The General Theory of Employment, Interest and Money", 1936)

"An adjustive effort of any kind is preceded by a decision to act or not act along a given line, and the decision is itself preceded by a definition of the situation, that is to say, an interpretation, or point of view, and eventually a policy and a behavior pattern. In this way quick judgments and decisions are made at every point in everyday life. Thus when approached by a man or beast in a lonely spot we first define the situation, make a judgment, as to whether the object is dangerous or harmless, and then decide ("make up our mind") what we are going to do about it." (William I Thomas, "Primitive Behavior", 1937)

"The fundamental gospel of statistics is to push back the domain of ignorance, prejudice, rule-of-thumb, arbitrary or premature decisions, tradition, and dogmatism and to increase the domain in which decisions are made and principles are formulated on the basis of analyzed quantitative facts." (Robert W Burgess, "The Whole Duty of the Statistical Forecaster", Journal of the American Statistical Association , Vol. 32, No. 200, 1937)

"A person can and will accept a communication as authoritative only when four conditions simultaneously obtain: (a) he can and does understand the communication; (b) at the time of his decision he believes that it is not inconsistent with the purpose of the organization; (c) at the time of his decision, he believes it to be compatible with his personal interest as a whole; and (d) he is able mentally and physically to comply with it." (Chester I Barnard, "The Functions of the Executive", 1938)

"Much of the waste in business is due to lack of information. And when the information is available, waste often occurs because of lack of application or because of misapplication." (John R Riggleman & Ira N Frisbee, "Business Statistics", 1938)

"The fine art of executive decision consists in not deciding questions that are not now pertinent, in not deciding prematurely, in not making decision that cannot be made effective, and in not making decisions that others should make. Not to decide questions that are not pertinent at the time is uncommon good sense, though to raise them may be uncommon perspicacity. Not to decide questions prematurely is to refuse commitment of attitude or the development of prejudice. Not to make decisions that cannot be made effective is to refrain from destroying authority. Not to make decisions that others should make is to preserve morale, to develop competence, to fix responsibility, and to preserve authority.
From this it may be seen that decisions fall into two major classes, positive decisions - to do something, to direct action, to cease action, to prevent action; and negative decisions, which are decisions not to decide. Both are inescapable; but the negative decisions are often largely unconscious, relatively nonlogical, "instinctive," "good sense." It is because of the rejections that the selection is good." (Chester I Barnard, "The Functions of the Executive", 1938)

"The making of decisions, as everyone knows from personal experience, is a burdensome task. Offsetting the exhilaration that may result from correct and successful decision and the relief that follows the termination of a struggle to determine issues is the depression that comes from failure, or error of decision, and the frustration which ensues from uncertainty." (Chester I Barnard, "The Functions of the Executive", 1938)

"The function of knowledge in the decision-making process is to determine which consequences follow upon which of the alternative strategies. It is the task of knowledge to select from the whole class of possible consequences a more limited subclass, or even (ideally) a single set of consequences correlated with each strategy." (Herbert A Simon, "Administrative Behavior", 1947)

"The executive is primarily concerned with decisions which facilitate or hinder other decisions." (Chester I Barnard, "Organization and Management: Selected Papers", 1948)

"The function of knowledge in the decision-making process is to determine which consequences follow upon which of the alternative strategies." (Herbert A Simon, "Public Administration", 1950)

"Scientists whose work has no clear, practical implications would want to make their decisions considering such things as: the relative worth of (1) more observations, (2) greater scope of his conceptual model, (3) simplicity, (4) precision of language, (5) accuracy of the probability assignment." (C West Churchman, "Costs, Utilities, and Values", 1956)

"A decision is the action an executive must take when he has information so incomplete that the answer does not suggest itself." (Arthur W Radford, [Time] 1957)

"Many individuals and organization units contribute to every large decision, and the very problem of centralization and decentralization is a problem of arranging the complex system into an effective scheme." (Herbert A. Simon, "Administrative Behavior", 1957) 

"Years ago a statistician might have claimed that statistics deals with the processing of data [...] today’s statistician will be more likely to say that statistics is concerned with decision making in the face of uncertainty." (Herman Chernoff & Lincoln E Moses, "Elementary Decision Theory", 1959)

"As the decision-making function becomes more highly automated, corporate decision making will perhaps provide fewer outlets for creative drives than it now does." (Herbert A Simon," Management and Corporations 1985", 1960)

"The decision which achieves organization objectives must be both (1) technologically sound and (2) carried out by people. If we lose sight of the second requirement or if we assume naively that people can be made to carry out whatever decisions are technically sound we run the risk of decreasing rather than increasing the effectiveness of the organization." (Douglas McGregor, "The Human Side of Enterprise", 1960)

"The mathematical and computing techniques for making programmed decisions replace man but they do not generally simulate him." (Herbert A Simon, "Corporations 1985", 1960)

"Another approach to management theory, undertaken by a growing and scholarly group, might be referred to as the decision theory school. This group concentrates on rational approach to decision-the selection from among possible alternatives of a course of action or of an idea. The approach of this school may be to deal with the decision itself, or to the persons or organizational group making the decision, or to an analysis of the decision process. Some limit themselves fairly much to the economic rationale of the decision, while others regard anything which happens in an enterprise the subject of their analysis, and still others expand decision theory to cover the psychological and sociological aspect and environment of decisions and decision-makers." (Harold Koontz, "The Management Theory Jungle," 1961)

"[There is a] persistent human temptation to make life more explicable by making it more calculable; to put experience in some logical scheme that, by its order and niceness, will make what happens seem more understandable, analysis more bearable, decision simpler." (E E Morison, Management and the Computer of the Future, 1962)

"A leader is a man who makes decisions. Sometimes they turn out right and sometimes they turn out wrong; but either way, he makes them." (Mutual Benefit Life Insurance Co, "Leadership in the Office", 1963)

"Don't make decisions and commitments ahead of time that you don't have to make." (Milton J Roedel, Managers' Meeting, 1963)

"The mediation of theory and praxis can only be clarified if to begin with we distinguish three functions, which are measured in terms of different criteria: the formation and extension of critical theorems, which can stand up to scientific discourse; the organization of processes of enlightenment, in which such theorems are applied and can be tested in a unique manner by the initiation of processes of reflection carried on within certain groups toward which these processes have been directed; and the selection of appropriate strategies, the solution of tactical questions, and the conduct of the political struggle. On the first level, the aim is true statements, on the second, authentic insights, and on the third, prudent decisions." (Jürgen Habermas, "Introduction to Theory and Practice", 1963)

"Solving the decision model consists of finding a strategy for action, the expected relative value of which is at least as great as the expected relative value of any other strategy in a specified set. The prescriptive criterion of a strategy will be maximisation of the decision maker’s expected relative value." (Peter C Fishburn, "Decision and Value Theory", 1964)

"Decisions should be based on facts, objectively considered - what I call the fact-founded, thought-through approach to decision making." (Marvin Bower, "The Will to Manage", 1966)

"In large-scale organizations, the factual approach must be constantly nurtured by high-level executives. The more layers of authority through which facts must pass before they reach the decision maker, the greater the danger that they will be suppressed, modified, or softened, so as not to displease the 'brass"' For this reason, high-level executives must keep reaching for facts or soon they won't know what is going on. Unless they make visible efforts to seek and act on facts, major problems will not be brought to their attention, the quality of their decisions will decline, and the business will gradually get out of touch with its environment." (Marvin Bower, "The Will to Manage", 1966)

"Interaction and decision making relies heavily on group processes." (Rensis Likert, "The Human Organization", 1967)

"Somewhere deep down we know that in the final analysis we do decide things and that even our decisions to let someone else decide are really our decisions, however pusillanimous." (Harvey G Cox, "On Not Leaving It to the Snake", 1967)

"There is a difference between attacking a decision and attacking the man who made the decision." (Maurice S Trotter, "Supervisor's Handbook on Insubordination", 1967)

"Analysis is not a scientific procedure for reaching decisions which avoid intuitive elements, but rather a mechanism for sharpening the intuition of the decision maker." (James R Schlesinger, "Memorandum to Senate Committee on Government Operations", 1968)

"Now we are looking for another basic outlook on the world - the world as organization. Such a conception - if it can be substantiated - would indeed change the basic categories upon which scientific thought rests, and profoundly influence practical attitudes. This trend is marked by the emergence of a bundle of new disciplines such as cybernetics, information theory, general system theory, theories of games, of decisions, of queuing and others; in practical applications, systems analysis, systems engineering, operations research, etc. They are different in basic assumptions, mathematical techniques and aims, and they are often unsatisfactory and sometimes contradictory. They agree, however, in being concerned, in one way or another, with ‘systems’, ‘wholes’ or ‘organizations’; and in their totality, they herald a new approach." (Ludwig von Bertalanffy, "General System Theory", 1968)

"Policy-making, decision-taking, and control: These are the three functions of management that have intellectual content." (Anthony S Beer, "Management Science" , 1968)

"Like all systems, the complex system is an interlocking structure of feedback loops [...] This loop structure surrounds all decisions public or private, conscious or unconscious. The processes of man and nature, of psychology and physics, of medicine and engineering all fall within this structure [...]" (Jay W Forrester, "Urban Dynamics", 1969)

"Each of us uses models constantly. Every person in his private life and in his business life instinctively uses models for decision making. The mental image of the world around you which you carry in your head is a model. […] A mental image is a model. All our decisions are taken on the basis of models." (Jay W Forrester, "Counter-Intuitive Behaviour of Social Systems", Technological Review 73, 1971)

"A somewhat deeper analysis suggests that a decision is a deliberate act of selection, by the mind, of an alternative from a set of competing alternatives in the hope, expectation, or belief that the actions envisioned in carrying out the selected alternative will accomplish certain goals. Decision is the selection of a mental state: it is a commitment to certain actions or inactions. Other people may observe our actions but they do not directly observe our decisions." (Peter C Fishburn, "Personalistic Decision Theory: Exposition and Critique", 1972)

"Decisions must be made at the lowest possible level for management at the top to retain its effectiveness." (Saxon Tate, "The Time Trap", 1972)

"The advantages of having decisions made by groups are often lost because of powerful psychological pressures that arise when the members work closely together, share the same set of values and, above all, face a crisis situation that puts everyone under intense stress." (Irving Janis, "Victims of Groupthink", 1972)

"The basic proposition is that the greater the uncertainty of the task, the greater the amount of information that has to be processed between decision-makers during the execution of the task. If the task is well understood prior to performing it much of the activity can be pre-planned. If it is not understood, then during the actual task execution more knowledge is acquired which leads to changes in resource allocations, schedules, and priorities." (Jay R Galbraith, "Organization Design", 1972)

"The human condition can almost be summed up in the observation that, whereas all experiences are of the past, all decisions are about the future. It is the great task of human knowledge to bridge this gap and to find those patterns in the past which can be projected into the future as realistic images." (Kenneth E Boulding, [foreword] 1972)

"The most powerful factor in the decision making in an organization is precedent. The older the larger the organization, the more powerful the precedent." (Lyle E Schaller, "The Change Agent", 1972)

"Executives do many things in addition to making decisions. But only executives make decisions. The first managerial skill is, therefore, the making of effective decisions." (Peter F Drucker, "Management: Tasks, Responsibilities, Practices", 1973)

"Managers, therefore, need to be skilled in making decisions with long futurity on a systematic basis. Management has no choice but to anticipate the future, to attempt to mold it, and to balance short-range and long-range goals.[…] “Short range” and “long range” are not determined by any given time span. A decision is not short range because it takes only a few months to carry it out. What matters is the time span over which it is effective. […] The skill we need is not long-range planning. It is strategic decision-making, or perhaps strategic planning." (Peter F Drucker, "Management: Tasks, Responsibilities, Practices", 1973)

"One has to make a decision when a condition is likely to degenerate if nothing is done."(Peter F Drucker, "Management: Tasks, Responsibilities, Practices", 1973)

"Statistics is a body of methods and theory applied to numerical evidence in making decisions in the face of uncertainty." (Lawrence Lapin, "Statistics for Modern Business Decisions", 1973)

"The manager does not handle decisions one at a time; he juggles a host of them, dealing with each intermittently, all the while attempting to develop some integration among them." (Henry Mintzberg, "The Nature of Managerial Work", 1973)

"The manager faces the real danger of becoming a major obstruction in the flow of decisions and information." (Henry Mintzberg, "The Nature of Managerial Work, 1973)

"Information may be accumulated in files, but it must be retrieved to be of use in decision making." (Kenneth J. Arrow, "The Limits of Organization", 1974)

"The purpose of organizations is to exploit the fact that many (virtually all) decisions require the participation of many individuals for their effectiveness. In particular, [...] organizations are a means of achieving the benefits of collective action in situations in which the price system fails." (Kenneth J Arrow, "The Limits of Organization", 1974)

"The more any quantitative social indicator is used for social decision-making, the more subject it will be to corruption pressures and the more apt it will be to distort and corrupt the social processes it is intended to monitor." (Donald T Campbell, "Assessing the impact of planned social change", 1976)

"The most dominant decision type [that will have to be made in an organic organization] will be decisions under uncertainty." (Henry L Tosi, "Management", 1976)

"Perhaps the fault [for the poor implementation record for models] lies in the origins of managerial model-making - the translation of methods and principles of the physical sciences into wartime operations research. [...] If hypothesis, data, and analysis lead to proof and new knowledge in science, shouldn’t similar processes lead to change in organizations? The answer is obvious-NO! Organizational changes (or decisions or policies) do not instantly pow from evidence, deductive logic, and mathematical optimization." (Edward B Roberts, "Interface", 1977)

"The essence of the phenomenon of gambling is decision making. The act of making a decision consists of selecting one course of action, or strategy, from among the set of admissible strategies. Richard A Epstein, The Theory of Gambling and Statistical Logic, 1977)

"The greater the uncertainty, the greater the amount of decision making and information processing. It is hypothesized that organizations have limited capacities to process information and adopt different organizing modes to deal with task uncertainty. Therefore, variations in organizing modes are actually variations in the capacity of organizations to process information and make decisions about events which cannot be anticipated in advance." (John K Galbraith, "Organization Design", 1977)

"It is change, continuing change, inevitable change, that is the dominant factor in society today. No sensible decision can be made any longer without taking into account not only the world as it is, but the world as it will be... This, in turn, means that our statesmen, our businessmen, our everyman must take on a science fictional way of thinking." (Isaac Asimov, "My Own View", Encyclopedia of Science Fiction, 1978)

"Our theory of management is that the time to get a decision doubles for every two levels of management; thus, parallel instead of serial decisions are best solutions." (Eberhardt Rechtin, [Speech] 1978)

"In general individual decision makers must be assumed to have multidimensional values which attach nonmonetary subjective cost or value to (1) the process of making and executing individual or group decisions, (2) the end result of such decisions, and (3) the rewards (and perhaps behavior) of other individuals involved in the decision process." (Vernon L Smith, "Relevance of laboratory experiments to testing resource allocation theory", 1980)

"Managers often try to give others the feeling that they are participating in the decision process. When a manager involves people in a problem for which he has adequate information and clear criteria for making an acceptable decision, he is engaging in pseudoconsultation. When he involves others in lengthy discussions of trivial problems, he is engaging in pseudoparticipation. Most people recognize these ceremonies as a waste of time." (Dale E Zand, "Information, Organization, and Power", 1981)

"Superordinate goals - the goals above all others [..] play a pragmatic role by influencing implementation at the operational level. Because an executive cannot be everywhere at once, many decisions are made without his knowledge. What superordinate goals do, in effect, is provide employees with a "compass" and point their footsteps in the right direction [... to] independent decisions." (Richard T Pascale & Anthony G Athos, "The Art of Japanese Management", 1981)

"Some problems are so complex that you have to be highly intelligent and well informed just to be undecided about them." (Laurence J Peter, Peter's Almanac, 1982) 

"Managerial accounting calls attention to problems and the need for action. It also aids in planning and decision making. It is aimed more at control and less at valuation than financial accounting." (John A Reinecke & William F Schoell, "Introduction to Business", 1983)

"We try to make management decisions that, if everything goes right, will preclude future problems. But everything does not always go right, and managers therefore must be problem solvers as well as decision makers." (James L Hayes, "Memos for Management: Leadership", 1983)

"By assuming sole responsibility for their departments, managers produce the very narrowness and self-interest they deplore in subordinates. When subordinates are relegated to their narrow specialties, they tend to promote their own practical interests, which then forces other subordinates into counter-advocacy. The manager is thereby thrust into the roles of arbitrator, judge, and referee. Not only do priorities become distorted, but decisions become loaded with win/lose dynamics. So, try as the manager might, decisions inevitably lead to disgruntlement and plotting for the next battle." (David L Bradford & Allan R Cohen, "Managing for Excellence", 1984)

"Management manages by making decisions and by seeing that those decisions are implemented." (Harold Geneen & Alvin Moscow, Managing, 1984)

"The formal structure of a decision problem in any area can be put into four parts: (1) the choice of an objective function denning the relative desirability of different outcomes; (2) specification of the policy alternatives which are available to the agent, or decisionmaker, (3) specification of the model, that is, empirical relations that link the objective function, or the variables that enter into it, with the policy alternatives and possibly other variables; and (4) computational methods for choosing among the policy alternatives that one which performs best as measured by the objective function." (Kenneth Arrow, "The Economics of Information", 1984)

"Ethical pressures and decisions are viewed through the prism of one's own personal values. The distinction between personal and organizational values, however, often becomes blurred, especially the longer one stays with a particular organization and/or advances up the hierarchial ladder." (Warren H Schmidt & Barry Z Posner, Public Administration Review, 1986)

"[Management science techniques] have had little impact on areas of decision-making where the management problems do not lend themselves to explicit formulation, where there are ambiguous or overlapping criteria for action, and where the manager operates through intuition." (James L McKenney & Peter G W Keen, Harvard Business Review on Human Relations, 1986)

"Nothing creates more self-respect among employees than being included in the process of making decisions." (Judith M. Bardwick, "The Plateauing Trap", 1986)

"Operating managers should in no way ignore short-term performance imperatives [when implementing productivity improvement programs.] The pressures arise from many sources and must be dealt with. Moreover, unless managers know that the day-to-day job is under control and improvements are being made, they will not have the time, the perspective, the self-confidence, or the good working relationships that are essential for creative, realistic strategic thinking and decision making." (Robert H Schaefer, Harvard Business Review, 1986)

"People will make reasonable decisions if they are given proper information." (Thom Serrani, Management Review, 1986)

"Some management groups are not good at problem solving and decision making precisely because the participants have weak egos and are uncomfortable with competition." (Chris Argyris, Harvard Business Review, 1986)

"The style of participative management is at its best when the supervisor can draw out the best in his people, allow decisions to be made at the point of influence and contribution, and create a spirit that everyone is in it together and that if something is unknown, they'll learn it together." (Joseph A Raelin, "Clash of Cultures: Managers and Professionals", 1986)

"Decisions should be pushed down as far as possible, to the level of competence. This allows senior managers more time for making decisions of a more complex nature." (Robert Heller, "The Pocket Manager", 1987)

"Despite the codes of ethics, the ethics programs, and the special departments corporations don't make the ultimate decisions about ethics. Ethical choices are made by individuals." (M Euel Wade Jr., [speech] 1987)

"Managers exist to plan, direct and control the project. Part of the way they control is to listen to and weigh advice. Once a decision is made, that's the way things should proceed until a new decision is reached. Erosion of management decisions by [support] people who always 'know better' undermines managers' credibility and can bring a project to grief." (Philip W Metzger, "Managing Programming People", 1987)

"Most managers are not capable of making decisions involving complex technological matters without help lots of it. [...] The finest technical people on the job should have a dual role: doing technical work and advising management." (Philip W Metzger, "Managing Programming People", 1987)

"Participative management is, simply stated, involving the right people at the right time in the decision process." (Wayne Barlow, 1987)

"People in the corporate world play to a higher audience that equates action with results. The constant pressure is to demonstrate that you are a tough manager capable of making tough decisions." (Charles J Bodenstab, Inc. Magazine, 1987)

"There's a tendency to think of conflicts of interest as an administrative problem: identifying potential or actual conflicts and then resolving them.... But often, resolving them requires a leadership decision, not an administrative one." (Ira Millstein, 1987)

"Visuals act as punctuation points in your presentation. They offer relief to the audience and make the audience's commitment a series of short decisions to stay tuned instead of one long, unattractive obligation." (Ed Brenner, 1987)

"Whenever decisions are made strictly on the basis of bottom-line arithmetic, human beings get crunched along with the numbers." (Thomas R Horton, Management Review, 1987)

"The major fault in this process - and thus, in the way we were making decisions - is that it lacks an organizing framework. In pursuing a variety of goals and objectives, in whatever situation we manage, we often fail to see that some of them are in conflict and that the achievement of one might come at the expense of achieving another. In weighing up the actions we might take to reach our goals and objectives, we have no way to account for nature's complexity and only rarely factor it in." (Allan Savory & Jody Butterfield, "Holistic Management: A new framework for decision making", 1988)

"A holistic perspective is essential in management. If we base management decisions on any other perspective, we are likely to experience results different from those intended because only the whole is reality." (Allan Savory & Jody Butterfield, "Holistic Management: A new framework for decision making", 1988)

"No decision in business provides greater potential for the creation of wealth (or its destruction, come to think of it) than the choice of which innovation to back." (Robert Heller, "The Decision Makers", 1989)

"You need to understand that informed intuition, rather than analytical reason, is the most trustworthy decision-making tool to use." (Geoffrey Moore, "Crossing the Chasm", 1991)

"A model for simulating dynamic system behavior requires formal policy descriptions to specify how individual decisions are to be made. Flows of information are continuously converted into decisions and actions. No plea about the inadequacy of our understanding of the decision-making processes can excuse us from estimating decision-making criteria. To omit a decision point is to deny its presence - a mistake of far greater magnitude than any errors in our best estimate of the process." (Jay W Forrester, "Policies, decisions and information sources for modeling", 1994)

"Pure rationality and limited rationality share a common perspective, seeing decisions as based on evaluation of alternatives in terms of their consequences for preferences. This logic of consequences can be contrasted with a logic of appropriateness by which actions are matched to situations by means of rules organized into identities." (James G March,"A Primer on Decision Making: How Decisions Happen", 1994)

"The risk of making a decision that's wrong is so enormous that sometimes it just crushes people so that they can't make any decision at all because they're afraid of making the wrong decision." (James M McPherson, "An Exchange With a Civil War Historian", 1995) 

"The science of statistics may be described as exploring, analyzing and summarizing data; designing or choosing appropriate ways of collecting data and extracting information from them; and communicating that information. Statistics also involves constructing and testing models for describing chance phenomena. These models can be used as a basis for making inferences and drawing conclusions and, finally, perhaps for making decisions." (Fergus Daly et al, "Elements of Statistics", 1995)

"Most managers are not capable of making decisions involving complex technological matters without helplots of it. [...] The finest technical people on the job should have dual role: doing technical work and advising management." (Philip W Metzger & John Boddie, "Managing a Programming Project: People and Processes", 1996)

"So we pour in data from the past to fuel the decision-making mechanisms created by our models, be they linear or nonlinear. But therein lies the logician's trap: past data from real life constitute a sequence of events rather than a set of independent observations, which is what the laws of probability demand. [...] It is in those outliers and imperfections that the wildness lurks." (Peter L Bernstein, "Against the Gods: The Remarkable Story of Risk", 1996)

"Under conditions of uncertainty, both rationality and measurement are essential to decision-making. Rational people process information objectively: whatever errors they make in forecasting the future are random errors rather than the result of a stubborn bias toward either optimism or pessimism. They respond to new information on the basis of a clearly defined set of preferences. They know what they want, and they use the information in ways that support their preferences." (Peter L Bernstein, "Against the Gods: The Remarkable Story of Risk", 1996)

"Until we can distinguish between an event that is truly random and an event that is the result of cause and effect, we will never know whether what we see is what we'll get, nor how we got what we got. When we take a risk, we are betting on an outcome that will result from a decision we have made, though we do not know for certain what the outcome will be. The essence of risk management lies in maximizing the areas where we have some control over the outcome while minimizing the areas where we have absolutely no control over the outcome and the linkage between effect and cause is hidden from us." (Peter L Bernstein, "Against the Gods: The Remarkable Story of Risk", 1996)

"Whenever we make any decision based on the expectation that matters will return to 'normal', we are employing the notion of regression to the mean." (Peter L Bernstein, "Against the Gods: The Remarkable Story of Risk", 1996)

"Delay time, the time between causes and their impacts, can highly influence systems. Yet the concept of delayed effect is often missed in our impatient society, and when it is recognized, it’s almost always underestimated. Such oversight and devaluation can lead to poor decision making as well as poor problem solving, for decisions often have consequences that don’t show up until years later. Fortunately, mind mapping, fishbone diagrams, and creativity/brainstorming tools can be quite useful here."(Stephen G Haines, "The Manager's Pocket Guide to Strategic and Business Planning", 1998)

"Within image theory, it is suggested that important components of decision-making processes are the different 'images' that a person may use to evaluate choice options. Images may represent a person's principles, goals, or plans. Decision options may then match or not match these images and be adopted, rejected, considered further, depending on circumstances." (Deborah J Terry & Michael A Hogg, "Attitudes, Behavior, and Social Context: The Role of Norms and Group Membership", 1999) 

"Data have to be filtered in some manner to make them intelligible. This filtration may be based upon a person's experience plus his presuppositions and assumptions, or it may be more formalized and less subjective, but there will always be some method of analysis. If experience is the basis for interpreting the data, then the interpretation is only as good as the manager's past experience. If the current situation is outside the manager’s experience, then his interpretation of the data may well be incorrect. Likewise, flawed assumptions or flawed presuppositions can also result in flawed interpretations. However, in the absence of formal and standardized data, most managers use the scat-of-the-pants approach. and in the end, about all they can say that some days appear to be better than others." (Donald J Wheeler," Understanding Variation: The Key to Managing Chaos" 2nd Ed., 2000)

"Faced with the overwhelming complexity of the real world, time pressure, and limited cognitive capabilities, we are forced to fall back on rote procedures, habits, rules of thumb, and simple mental models to make decisions. Though we sometimes strive to make the best decisions we can, bounded rationality means we often systematically fall short, limiting our ability to learn from experience." (John D Sterman, "Business Dynamics: Systems thinking and modeling for a complex world", 2000)

"Just as dynamics arise from feedback, so too all learning depends on feedback. We make decisions that alter the real world; we gather information feedback about the real world, and using the new information we revise our understanding of the world and the decisions we make to bring our perception of the state of the system closer to our goals." (John D Sterman, "Business dynamics: Systems thinking and modeling for a complex world", 2000)

"No plea about inadequacy of our understanding of the decision-making processes can excuse us from estimating decision making criteria. To omit a decision point is to deny its presence - a mistake of far greater magnitude than any errors in our best estimate of the process." (Jay W Forrester, "Perspectives on the modelling process", 2000)

"The robustness of the misperceptions of feedback and the poor performance they cause are due to two basic and related deficiencies in our mental model. First, our cognitive maps of the causal structure of systems are vastly simplified compared to the complexity of the systems themselves. Second, we are unable to infer correctly the dynamics of all but the simplest causal maps. Both are direct consequences of bounded rationality, that is, the many limitations of attention, memory, recall, information processing capability, and time that constrain human decision making." (John D Sterman, "Business Dynamics: Systems thinking and modeling for a complex world", 2000)

"Diversity and independence are important because the best collective decisions are the product of disagreement and contest, not consensus or compromise." (James Surowiecki, "The Wisdom of Crowds", 2005)

"The fact that cognitive diversity matters does not mean that if you assemble a group of diverse but thoroughly uninformed people, their collective wisdom will be smarter than an expert's. But if you can assemble a diverse group of people who possess varying degrees of knowledge and insight, you're better off entrusting it with major decisions rather than leaving them in the hands of one or two people, no matter how smart those people are." (James Surowiecki, "The Wisdom of Crowds", 2005)

"The key to good decision making is not knowledge. It is understanding. We are swimming in the former. We are desperately lacking in the latter." (Malcolm Gladwell, "Blink: The Power of Thinking Without Thinking", 2005)

"[...] under the right circumstances, groups are remarkably intelligent, and are often smarter than the smartest people in them. Groups do not need to be dominated by exceptionally intelligent people in order to be smart. Even if most of the people within a group are not especially well-informed or rational, it can still reach a collectively wise decision." (James Surowiecki, "The Wisdom of Crowds", 2005)

"Decisions are always made with insufficient information. If you really knew what was going on, the decision would make itself." (Jack McDevitt, "Odyssey", 2006)

"Decision making is the process of identifying problems and opportunities and then resolving them. Decision making involves effort before and after the actual choice." (Richard L Daft & Dorothy Marcic, "Understanding Management" 5th Ed., 2006)

"Acquired patterns and the logic to employ them combine with our inherent qualities to create a unique decision-maker. As time goes by, experience and knowledge are focused through the prism of talent, which can itself be sharpened, focused, and polished. This mix is the source of intuition, an absolutely unique tool that each of us possesses and that we can continuously hone into an ever-finer instrument." (Garry Kasparov, "How Life Imitates Chess", 2007)

"It's not enough to be talented. It's not enough to work hard and to study late into the night. You must also become intimately aware of the methods you use to reach your decisions." (Garry Kasparov, "How Life Imitates Chess", 2007)

"Sometimes the hardest thing to do in a pressure situation is to allow the tension to persist. The temptation is to make a decision, any decision, even if it is an inferior choice." (Garry Kasparov, "How Life Imitates Chess", 2007)

"Stay committed to your decisions, but stay flexible in your approach." (Anthony Robbins, "Awaken the Giant Within", 2007)

"Checking the results of a decision against its expectations shows executives what their strengths are, where they need to improve, and where they lack knowledge or information."(Peter Drucker, "The Effective Executive", 2009) 

"When you face a problem, solve it then and there if you have the facts necessary to make a decision. Don't keep putting off decisions. [...] In fact, merely writing the facts on a piece of paper and stating our problem clearly goes a long way toward helping us to reach a sensible decision." (Dale Carnegie, "How To Enjoy Your Life And Your Job" , 2010) 

"[...] a model is a tool for taking decisions and any decision taken is the result of a process of reasoning that takes place within the limits of the human mind. So, models have eventually to be understood in such a way that at least some layer of the process of simulation is comprehensible by the human mind. Otherwise, we may find ourselves acting on the basis of models that we don’t understand, or no model at all.” (Ugo Bardi, “The Limits to Growth Revisited”, 2011)

"[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)

"Because people face trade-offs, making decisions requires comparing the costs and benefits of alternative courses of action. In many cases, however, the cost of an action is not as obvious as it might first appear. […] The opportunity cost of an item is what you give up to get that item. When making any decision, decision makers should be aware of the opportunity costs that accompany each possible action." (N Gregory Mankiw, "Principle of Economics" 6th ed., 2012)

"Image theory is an attempt to describe decision making as it actually occurs. […] The concept of images is central to the theory. They represent visions held by individuals and organisations that constitute how they believe the world should exist. When considering individuals, the theory refers to these images as the value image, trajectory image and strategic image. The value image is based on an individual’s ethics, morals and beliefs. The trajectory images encompass the decision maker’s goals and aspirations. Finally, for each trajectory image, a decision maker may have one or more strategic images that contain their plans, tactics and forecasts for their goal. […] In an organisational decision-making setting, these images are referred to as culture, vision and strategy." (Christopher B Stephenson, "What causes top management teams to make poor strategic decisions?", 2012) 

"Good decision-making is like playing chess and you must avoid making hasty decisions without thinking of how that particular decision will impact on different aspects of your work and organization. The worst kind of decision-making is to decide to delay a difficult decision until later or to pass it to someone else to have to make. You will never excel and be valued by your colleagues if you get into these habits of procrastination and passing responsibility to others." (Nigel Cumberland, "Secrets of Success at Work: 50 techniques to excel", 2014)

"In general, when building statistical models, we must not forget that the aim is to understand something about the real world. Or predict, choose an action, make a decision, summarize evidence, and so on, but always about the real world, not an abstract mathematical world: our models are not the reality - a point well made by George Box in his oft-cited remark that 'all models are wrong, but some are useful'." (David Hand, "Wonderful examples, but let's not close our eyes", Statistical Science 29, 2014)

"After you think, you act. After you act, you learn. Make decisions, but decisions will have risks of mistakes. But make sure you avoid disastrous mistakes and avoid making the same mistake twice." (Sukanto Tanoto, [Keynote speech] 2015) 

"So everyone has and uses mental representations. What sets expert performers apart from everyone else is the quality and quantity of their mental representations. Through years of practice, they develop highly complex and sophisticated representations of the various situations they are likely to encounter in their fields - such as the vast number of arrangements of chess pieces that can appear during games. These representations allow them to make faster, more accurate decisions and respond more quickly and effectively in a given situation. This, more than anything else, explains the difference in performance between novices and experts." (Anders Ericsson & Robert Pool, "Peak: Secrets from the New Science of Expertise", 2016)

[...] just because we act, and something changes, it doesn’t mean we were responsible for the result. Humans seem to find this simple truth difficult to grasp - we are always keen to construct an explanatory narrative, and even keener if we are at its centre. Of course sometimes this interpretation is true - if you flick a switch, and the light comes on, then you are usually responsible. But sometimes your actions are clearly not responsible for an outcome: if you don’t take an umbrella, and it rains, it is not your fault (although it may feel that way). But the consequences of many of our actions are less clear-cut. [...] We have a strong psychological tendency to attribute change to intervention, and this makes before-and-after comparisons treacherous." (David Spiegelhalter, "The Art of Statistics: Learning from Data", 2019)

"Ideally, a decision maker or a forecaster will combine the outside view and the inside view - or, similarly, statistics plus personal experience. But it’s much better to start with the statistical view, the outside view, and then modify it in the light of personal experience than it is to go the other way around. If you start with the inside view you have no real frame of reference, no sense of scale - and can easily come up with a probability that is ten times too large, or ten times too small." (Tim Harford, "The Data Detective: Ten easy rules to make sense of statistics", 2020)

"The traditional approach to leadership values decision-making conviction and consistency; good leaders 'stick to their guns'. By contrast, the emerging approach recognizes that in fast-changing environments, decisions often need to be reversed or adapted, and that changing course in response to new information is a strength, not a weakness. If this tension is not managed wisely, leaders run the risk of seeming too rigid, on the one hand, or too wishy-washy on the other." (Jennifer Jordan et al, "Every Leader Needs to Navigate These 7 Tensions", Harvard Business Review, 2020) [source]

"To make the best decisions in business and in life, we need to be adept at many different forms of thinking, including intuition, and we need to know how to incorporate many different types of inputs, including numerical data and statistics (analytics). Intuition and analytics don't have to be seen as mutually exclusive at all. In fact, they can be viewed as complementary." (Ben Jones, "Avoiding Data Pitfalls: How to Steer Clear of Common Blunders When Working with Data and Presenting Analysis and Visualizations", 2020) 

"The process of asking, acquiring, analyzing, integrating, deciding, and iterating should become second nature to you. This should be a part of how you work on a regular basis with data literacy. Again, without a decision, what is the purpose of data literacy? Data literacy should lead you as an individual, and organizations, to make smarter decisions." (Jordan Morrow, "Be Data Literate: The data literacy skills everyone needs to succeed", 2021)

"[…] whenever people make decisions after being supplied with the standard deviation number, they act as if it were the expected mean deviation." (Nassim N Taleb, "Statistical Consequences of Fat Tails: Real World Preasymptotics, Epistemology, and Applications" 2nd Ed., 2022)

"A decision is an action you must take when you have information so incomplete that the answer does not suggest itself." (Arthur Radford)

"After a battle is over people talk a lot about how decisions were methodically reached, but actually there's always a hell of a lot of groping around." (Frank J Fletcher)

"Decisions must be made at the lowest possible level for management at the top to retain its effectiveness." (Saxon Tate)

"If decisions were a choice between alternatives, decisions would come easy. Decision is the selection and formulation of alternatives." (Kenneth Burke)

"Long range planning does not deal with future decisions but with the future of present decisions." (Peter F Drucker)

"No great marketing decisions have ever been made on quantitative data." (John Sculley)

"Nothing is so exhausting as indecision, and nothing is so futile." (Bertrand Russell)

"Often greater risk is involved in postponement than in making a wrong decision." (Harry A Hopf)

"Our theory of management is that the time to get a decision doubles for every two levels of management; thus, parallel instead of serial decisions are best solutions." (Eberhardt Rechtin)

"Participative management is, simply stated, involving the right people at the right time in the decision process." (Wayne Barlow)

"The fact is you'll never have all the information you need to make a decision - if you did, it would be a foregone conclusion, not a decision." (David Mahoney)

"When possible make the decisions now, even if action is in the future. A revised decision usually is better than one reached at the last moment." (William B Given Jr.)

"Whenever decisions are made strictly on the basis of bottom-line arithmetic, human beings get crunched along with the numbers." (Thomas R Horton)
Related Posts Plugin for WordPress, Blogger...

About Me

My photo
IT Professional with more than 24 years experience in IT in the area of full life-cycle of Web/Desktop/Database Applications Development, Software Engineering, Consultancy, Data Management, Data Quality, Data Migrations, Reporting, ERP implementations & support, Team/Project/IT Management, etc.