Showing posts with label failure. Show all posts
Showing posts with label failure. Show all posts

14 September 2024

Data Management: Data Culture (Part V: Quid nunc? [What now?])

Data Management Series
Data Management Series

Despite the detailed planning, the concentrated and well-directed effort with which the various aspects of data culture are addressed, things don't necessarily turn into what we want them to be. There's seldom only one cause but a mix of various factors that create a network of cause and effect relationships that tend to diminish or increase the effect of certain events or decisions, and it can be just a butterfly's flutter that stirs a set of chained reactions. The butterfly effect is usually an exaggeration until the proper conditions for the chaotic behavior appear. 

The butterfly effect is made possible by the exponential divergence of two paths. Conversely, success needs probably multiple trajectories to converge toward a final point or intermediary points or areas from which things move on the "right" path. Success doesn't necessarily mean reaching a point but reaching a favorable zone for future behavior to follow a positive trend. For example, a sink or a cone-like structure allow water to accumulate and flow toward an area. A similar structure is needed for success to converge, and the structure results from what is built in the process. 

Data culture needs a similar structure for the various points of interest to converge. Things don't happen by themselves unless the force of the overall structure is so strong that allows things to move toward the intended path(s). Even then the paths can be far from optimal, but they can be favorable. Probably, that's what the general effort must do - bring the various aspects in the zone for allowing things to unfold. It might still be a long road, though the basis is there. 

A consequence of this metaphor is that one must identify the important aspects, respectively factors that influence an organization's culture and drive them in the right direction(s) – the paths that converge toward the defined goal(s). (Depending on the area of focus one can consider that there are successions of more refined goals.)

The structure that allows things to converge is based on the alignment of the various paths and implicitly forces. Misalignment can make a force move in other direction with all the consequences deriving from this behavior. If its force is weak, probably will not have an impact over the overall structure, though that's relative and can change in time. 

One may ask for what's needed all this construct, even if it doesn’t reflect the reality. Sometimes, even a not entirely correct model can allow us to navigate the unknown. Model's intent is to depict what's needed for a initiative to be successful. Moreover, success doesn’t mean to shoot bulls eye but to be first in the zone until one's skillset enables performance.

Conversely, it's important to understand that things don't happen by themselves. At least this seems to be the feeling some initiatives let. One needs to build and pull the whole structure in the right direction and the alignment of the various forces can reduce the overall effort and increase the chances for success. Attempting to build something just because it’s written in documentation without understanding the whole picture (or something close to it) can easily lead to failure.

This doesn’t mean that all attempts that don’t follow a set of patterns are doomed to failure, but that the road will be more challenging and will probably take longer. Conversely, maybe these deviations from the optimal paths are what an organization needs to grow, to solidify the foundation on which something else can be built. The whole path is an exploration that doesn’t necessarily match what is written in books, respectively the expectations!

Previous Post <<||>> Next Post

01 September 2024

Data Management: Data Governance (Part I: No Guild of Heroes)

Data Management Series
Data Management Series

Data governance appeared around 1980s as topic though it gained popularity in early 2000s [1]. Twenty years later, organizations still miss the mark, respectively fail to understand and implement it in a consistent manner. As usual, the reasons for failure are multiple and they vary from misunderstanding what governance is all about to poor implementation of methodologies and inadequate management or leadership. 

Moreover, methodologies tend to idealize the various aspects and is not what organizations need, but pragmatism. For example, data governance is not about heroes and heroism [2], which can give the impression that heroic actions are involved and is not the case! Actions for the sake of action don’t necessarily lead to change by themselves. Organizations are in general good at creating meaningless action without results, especially when people preoccupy themselves, miss or ignore the mark. Big organizations are very good at generating actions without effects. 

People do talk to each other, though they try to solve their own problems and optimize their own areas without necessarily thinking about the bigger picture. The problem is not necessarily communication or the lack of depth into business issues, people do communicate, know the issues without a business impact assessment. The challenge is usually in convincing the upper management that the effort needs to be consolidated, supported, respectively the needed resources made available. 

Probably, one of the issues with data governance is the attempt of creating another structure in the organization focused on quality, which has the chances to fail, and unfortunately does fail. Many issues appear when the structure gains weight and it becomes a separate entity instead of being the backbone of organizations. 

As soon organizations separate the data governance from the key users, management and the other important decisional people in the organization, it takes a life of its own that has the chances to diverge from the initial construct. Then, organizations need "alignment" and probably other big words to coordinate the effort. Also such constructs can work but they are suboptimal because the forces will always pull in different directions.

Making each manager and the upper management responsible for governance is probably the way to go, though they’ll need the time for it. In theory, this can be achieved when many of the issues are solved at the lower level, when automation and further aspects allow them to supervise things, rather than hiding behind every issue. 

When too much mircomanagement is involved, people tend to busy themselves with topics rather than solve the issues they are confronted with. The actual actors need to be empowered to take decisions and optimize their work when needed. Kaizen, the philosophy of continuous improvement, proved itself that it works when applied correctly. They’ll need the knowledge, skills, time and support to do it though. One of the dangers is however that this becomes a full-time responsibility, which tends to create a separate entity again.

The challenge for organizations lies probably in the friction between where they are and what they must do to move forward toward the various objectives. Moving in small rapid steps is probably the way to go, though each person must be aware when something doesn’t work as expected and react. That’s probably the most important aspect. 

So, the more functions are created that diverge from the actual organization, the higher the chances for failure. Unfortunately, failure is visible in the later phases, and thus self-awareness, self-control and other similar “qualities” are needed, like small actors that keep the system in check and react whenever is needed. Ideally, the employees are the best resources to react whenever something doesn’t work as per design. 

Previous Post <<||>> Next Post 

Resources:
[1] Wikipedia (2023) Data Management [link]
[2] Tiankai Feng (2023) How to Turn Your Data Team Into Governance Heroes [link]


08 April 2024

Business Intelligence: Why Data Projects Fail to Deliver Real-Life Impact (Part III: Failure through the Looking Glass)

Business Intelligence
Business Intelligence Series

There’s a huge volume of material available on project failure – resources that document why individual projects failed, while in general projects fail, why project members, managers and/or executives think projects fail, and there seems to be no other pleasant activity at the end of a project than to theorize why a project failed, the topic culminating occasionally with the blaming game. Success may generate applause, though is failure that attracts and stirs the most waves (irony, disapproval, and other similar behavior) and everybody seems to be an expert after the consumed endeavor. 

The mere definition of a project failure – not fulfilling project’s objectives within the set budget and timeframe - is a misnomer because budgets and timelines are estimated based on the information available at the beginning of the project, the amount of uncertainty for many projects being considerable, and data projects are no exceptions from it. The higher the uncertainty the less probable are the two estimates. Even simple projects can reveal uncertainty especially when the broader context of the projects is considered. 

Even if it’s not a common practice, one way to cope with uncertainty is to add a tolerance for the estimates, though even this practice probably will not always accommodate the full extent of the unknown as the tolerances are usually small. The general expectation is to have an accurate and precise landing, which for big or exploratory projects is seldom possible. 

Moreover, the assumptions under which the estimates hold are easily invalidated in praxis – resources’ availability, first time right, executive’s support to set priorities, requirements’ quality, technologies’ maturity, etc. If one looks beyond the reasons why projects fail in general, quite often the issues are more organizational than technological, the lack of knowledge and experience being one of the factors. 

Conversely, many projects will not get approved if the estimates don’t look positive, and therefore people are pressured in one way or another to make the numbers fit the expectations. Some projects, given their importance, need to be done even if the numbers don’t look good or can’t be quantified correctly. Other projects represent people’s subsistence on the job, respectively people self-occupation to create motion, though they can occasionally have also a positive impact for the organizations. These kinds of aspects almost never make it in statistics or surveys. Neither do the big issues people are afraid to talk about. Where to consider that in the light of politics and office’s grapevine the facts get distorted.

Data projects reflect all the symptoms of failure projects have in general, though when words like AI, Statistics or Machine Learning are used, the chances for failure are even higher given that the respective fields require a higher level of expertise, the appropriate use of technologies and adherence to the scientific process for the results to be valid. If projects can benefit from general receipts, respectively established procedures and methods, their range of applicability decreases when the mentioned areas are involved. 

Many data projects have an exploratory nature – seeing what’s possible - and therefore a considerable percentage will not reach production. Moreover, even those that reach that far might arrive to be stopped or discarded sooner or later if they don’t deliver the expected value, and probably many of the models created in the process are biased, irrelevant, or incorrectly apply the theory. Where to add that the mere use of tools and algorithms is not Data Science or Data Analysis. 

The challenge for many data projects is to identify which Project Management (PM) best practices to consider. Following all or no practices at all just increases the risks of failure!

Previous Post <<||>> Next Post

06 April 2024

Business Intelligence: Why Data Projects Fail to Deliver Real-Life Impact (Part II: There's Value in Failure)

Business Intelligence
Business Intelligence Series

"Results are nothing; the energies which produce them
and which again spring from them are everything."
(Wilhelm von Humboldt,  "On Language", 1836)

When the data is not available and is needed on a continuous basis then usually the solution is to redesign the processes and make sure the data becomes available at the needed quality level. Redesign involves additional costs for the business; therefore, it might be tempting to cancel or postpone data projects, at least until they become feasible, though they’re seldom feasible. 

Just because there’s a set of data, this doesn’t mean that there is important knowledge to be extracted from it, respectively that the investment is feasible. There’s however value in building experience in the internal resources, in identifying the challenges and the opportunities, in identifying what needs to be changed for harnessing the data. Unfortunately, organizations expect that somebody else will do the work for them instead of doing the jump by themselves, and this approach more likely will fail. It’s like expecting to get enlightened after a few theoretical sessions with a guru than walking the path by oneself. 

This is reflected also in organizations’ readiness to do the required endeavors for making the jump on the maturity scale. If organizations can’t approach such topics systematically and address the assumptions, opportunities, and risks adequately, respectively to manage the various aspects, it’s hard to believe that their data journey will be positive. 

A data journey shouldn’t be about politics even if some minds need to be changed in the process, at management as well as at lower level. If the leadership doesn’t recognize the importance of becoming an enabler for such initiatives, then the organization probably deserves to keep the status quo. The drive for change should come from the leadership even if we talk about data culture, data strategy, decision-making, or any critical aspect.

An organization will always need to find the balance between time, scope, cost, and quality, and this applies to operations, tactics, and strategies as well as to projects.  There are hard limits and lot of uncertainty associated with data projects and the tasks involved, limits reflected in cost and time estimations (which frankly are just expert’s rough guesses that can change for the worst in the light of new information). Therefore, especially in data projects one needs to be able to compromise, to change scope and timelines as seems fit, and why not, to cancel the projects if the objectives aren’t feasible anymore, respectively if compromises can’t be reached.

An organization must be able to take the risks and invest in failure, otherwise the opportunities for growth don’t change. Being able to split a roadmap into small iterative steps that allow besides breaking down the complexity and making progress to evaluate the progress and the knowledge resulted, respectively incorporate the feedback and knowledge in the next steps, can prove to be what organizations lack in coping with the high uncertainty. Instead, organizations seem to be fascinated by the big bang, thinking that technology can automatically fill the organizational gaps.

Doing the same thing repeatedly and expecting different results is called insanity. Unfortunately, this is what organizations and service providers do in what concerns Project Management in general and data projects in particular. Building something without a foundation, without making sure that the employees have the skillset, maturity and culture to manage the data-related tasks, challenges and opportunities is pure insanity!

Bottom line, harnessing the data requires a certain maturity and it starts with recognizing and pursuing opportunities, setting goals, following roadmaps, learning to fail and getting value from failure, respectively controlling the failure. Growth or instant enlightenment without a fair amount of sweat is possible, though that’s an exception for few in sight!

Previous Post <<||>> Next Post

22 March 2024

Business Intelligence: Dashboards (Part I: Dashboards Are Dead & Other Crap)

Business Intelligence
Business Intelligence Series

I find annoying the posts that declare that a technology is dead, as they seem to seek the sensational and, in the end, don't offer enough arguments for the positions taken; all is just surfing though a few random ideas. Almost each time I klick on such a link I find myself disappointed. Maybe it's just me - having too great expectations from ad-hoc experts who haven't understood the role of technologies and their lifecycle.

At least until now dashboards are the only visual tool that allows displaying related metrics in a consistent manner, reflecting business objectives, health, or other important perspective into an organization's performance. More recently notebooks seem to be getting closer given their capabilities of presenting data visualizations and some intermediary steps used to obtain the data, though they are still far away from offering similar capabilities. So, from where could come any justification against dashboard's utility? Even if I heard one or two expert voices saying that they don't need KPIs for managing an organization, organizations still need metrics to understand how the organization is doing as a whole and taken on parts. 

Many argue that the design of dashboards is poor, that they don't reflect data visualization best practices, or that they are too difficult to navigate. There are so many books on dashboard and/or graphic design that is almost impossible not to find such a book in any big library if one wants to learn more about design. There are many resources online as well, though it's tough to fight with a mind's stubbornness in showing no interest in what concerns the topic. Conversely, there's also lot of crap on the social networks that qualify after the mainstream as best practices. 

Frankly, design is important, though as long as the dashboards show the right data and the organization can guide itself on the respective numbers, the perfectionists can say whatever they want, even if they are right! Unfortunately, the numbers shown in dashboards raise entitled questions and the reasons are multiple. Do dashboards show the right numbers? Do they focus on the objectives or important issues? Can the number be trusted? Do they reflect reality? Can we use them in decision-making? 

There are so many things that can go wrong when building a dashboard - there are so many transformations that need to be performed, that the chances of failure are high. It's enough to have several blunders in the code or data visualizations for people to stop trusting the data shown.

Trust and quality are complex concepts and there’s no standard path to address them because they are a matter of perception, which can vary and change dynamically based on the situation. There are, however, approaches that allow to minimize this. One can start for example by providing transparency. For each dashboard provide also detailed reports that through drilldown (or also by running the reports separately if that’s not possible) allow to validate the numbers from the report. If users don’t trust the data or the report, then they should pinpoint what’s wrong. Of course, the two sources must be in synch, otherwise the validation will become more complex.

There are also issues related to the approach - the way a reporting tool was introduced, the way dashboards flooded the space, how people reacted, etc. Introducing a reporting tool for dashboards is also a matter of strategy, tactics and operations and the various aspects related to them must be addressed. Few organizations address this properly. Many organizations work after the principle "build it and they will come" even if they build the wrong thing!

Previous Post <<||>> Next Post

20 March 2021

Business Intelligence: New Technologies, Old Challenges I (Introduction)

Business Intelligence

Each important technology has the potential of creating divides between the specialists from a given field. This aspect is more suggestive in the data-driven fields like BI/Analytics or Data Warehousing. The data professionals (engineers, scientists, analysts, developers) skilled only in the new wave of technologies tend to disregard the role played by the former technologies and their role in the data landscape. The argumentation for such behavior is rooted in the belief that a new technology is better and can solve any problem better than previous technologies did. It’s a kind of mirage professionals and customers can easily fall under.

Being bigger, faster, having new functionality, doesn’t make a tool the best choice by default. The choice must be rooted in the problem to be solved and the set of requirements it comes with. Just because a vibratory rammer is a new technology, is faster and has more power in applying pressure, this doesn’t mean that it will replace a hammer. Where a certain type of power is needed the vibratory rammer might be the best tool, while for situations in which a minimum of power and probably more precision is needed, like driving in a nail, then an adequately sized hammer will prove to be a better choice.

A technology is to be used in certain (business/technological) contexts, and even if contexts often overlap, the further details (aka requirements) should lead to the proper use of tools. It’s in a professional’s duties to be able to differentiate between contexts, requirements and the capabilities of the tools appropriate for each context. In this resides partially a professional’s mastery over its field of work and of providing adequate solutions for customers’ needs. Especially in IT, it’s not enough to master the new tools but also have an understanding about preceding tools, usage contexts, capabilities and challenges.

From an historical perspective each tool appeared to fill a demand, and even if maybe it didn’t manage to fill it adequately, the experience obtained can prove to be valuable in one way or another. Otherwise, one risks reinventing the wheel, or more dangerously, repeating the failures of the past. Each new technology seems to provide a deja-vu from this perspective.

Moreover, a new technology provides new opportunities and requires maybe to change our way of thinking in respect to how the technology is used and the processes or techniques associated with it. Knowledge of the past technologies help identifying such opportunities easier. How a tool is used is also a matter of skills, while its appropriate use and adoption implies an inherent learning curve. Having previous experience with similar tools tends to reduce the learning curve considerably, though hands-on learning is still necessary, and appropriate learning materials or tutoring is upon case needed for a smoother transition.

In what concerns the implementation of mature technologies, most of the challenges were seldom the technologies themselves but of non-technical nature, ranging from the poor understanding/knowledge about the tools, their role and the implications they have for an organization, to an organization’s maturity in leading projects. Even the most-advanced technology can fail in the hands of non-experts. Experience can’t be judged based only on the years spent in the field or the number of projects one worked on, but on the understanding acquired about implementation and usage’s challenges. These latter aspects seem to be widely ignored, even if it can make the difference between success and failure in a technology’s implementation.

Ultimately, each technology is appropriate in certain contexts and a new technology doesn’t necessarily make another obsolete, at least not until the old contexts become obsolete.

Previous Post <<||>>Next Post

28 August 2019

Information Security: Data Breach (Definitions)

[data loss:] "Deprivation of something useful or valuable about a set of data, such as unplanned physical destruction of data or failure to preserve the confidentiality of data." (David G Hill, "Data Protection: Governance, Risk Management, and Compliance", 2009)

"The unauthorized disclosure of confidential information, notably that of identifying information about individuals." (David G Hill, "Data Protection: Governance, Risk Management, and Compliance", 2009)

"A failure of an obligation to protect against the release of secure data." (Janice M Roehl-Anderson, "IT Best Practices for Financial Managers", 2010)

"The release of secure information to an untrusted environment. Other terms for this occurrence include unintentional information disclosure, data leak, and data spill." (Craig S Mullins, "Database Administration", 2012)

"The unauthorized movement or disclosure of sensitive information to a party, usually outside the organization, that is not authorized to have or see the information." (Olivera Injac & Ramo Šendelj, "National Security Policy and Strategy and Cyber Security Risks", 2016)

"An incident in which sensitive, protected or confidential data has been viewed, stolen or used by an unauthorized body." (Güney Gürsel, "Patient Privacy and Security in E-Health", 2017)

[data leakage:] "The advertent or inadvertent sharing of private and/or confidential information." (Shalin Hai-Jew, "Beware!: A Multimodal Analysis of Cautionary Tales in Strategic Cybersecurity Messaging Online", 2018)

"A security incident involving unauthorized access to data." (Boaventura DaCosta & Soonhwa Seok, "Cybercrime in Online Gaming", 2020)

"An incident where information is accessed without authorization." (Nathan J Rodriguez, "Internet Privacy", 2020)

"A process where large amounts of private data, mostly about individuals, becomes illegally available to people who should not have access to the information." (Ananda Mitra & Yasmine Khosrowshahi, "The 2018 Facebook Data Controversy and Technological Alienation", 2021)

"This refers to any intentional or unintentional leak of secure or private or confidential data to any untrusted system. This is also referred to as information disclosure or data spill." (Srinivasan Vaidyanathan et al, "Challenges of Developing AI Applications in the Evolving Digital World and Recommendations to Mitigate Such Challenges: A Conceptual View", 2021) 

"When the information is stolen or used without consent of the system’s owner, the data stolen may cover confidential information like credit cards or passwords." (Kevser Z Meral, "Social Media Short Video-Sharing TikTok Application and Ethics: Data Privacy and Addiction Issues", 2021)

[data loss:] "The exposure of proprietary, sensitive, or classified information through either data theft or data leakage." (CNSSI 4009-2015)

30 July 2019

IT: False Negative (Definitions)

"Spam that is mistaken for legitimate email." (Andy Walker, "Absolute Beginner’s Guide To: Security, Spam, Spyware & Viruses", 2005)

"Failing to report an event that should have been reported." (W Roy Schulte & K Chandy, "Event Processing: Designing IT Systems for Agile Companies", 2009)

"A subject who is identified as failing to have experienced the event of interest (e.g., exposure, disease) but has truly experienced the event is termed a false negative." (Herbert I Weisberg, "Bias and Causation: Models and Judgment for Valid Comparisons", 2010)

"An incorrect result, which fails to detect a condition or return a result that is actually present." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"An incorrect result as reported by a detective device, such as an IDS, an antivirus program, or a biometric security device. For example, an antivirus program may not “catch” a virus-infected file, or a fingerprint reader may incorrectly fail the fingerprint of the true user." (Mark Rhodes-Ousley, "Information Security: The Complete Reference, Second Edition, 2nd Ed.", 2013)

"A test result that incorrectly reports that a condition being tested for is absent, when, in fact, it is present (e.g., an intrusion detection subsystem falsely reports no attacks in the attack space of an enterprise system)." (O Sami Saydjari, "Engineering Trustworthy Systems: Get Cybersecurity Design Right the First Time", 2018)

"A condition when using optimistic locking whereby a row that was not updated since it was selected cannot be updated without first being selected again. Optimistic locking support does not allow a false positive to happen, but a false negative might happen. See also false positive." (Sybase, "Open Server Server-Library/C Reference Manual", 2019)

[false-negative result:] "A test result which fails to identify the presence of a defect that is actually present in the test object." (Software Quality Assurance)

09 December 2018

Data Science: Failure (Just the Quotes)

"Every detection of what is false directs us towards what is true: every trial exhausts some tempting form of error. Not only so; but scarcely any attempt is entirely a failure; scarcely any theory, the result of steady thought, is altogether false; no tempting form of error is without some latent charm derived from truth." (William Whewell, "Lectures on the History of Moral Philosophy in England", 1852)

"Scarcely any attempt is entirely a failure; scarcely any theory, the result of steady thought, is altogether false; no tempting form of Error is without some latent charm derived from Truth." (William Whewell, "Lectures on the History of Moral Philosophy in England", 1852)

"We learn wisdom from failure much more than from success. We often discover what will do, by finding out what will not do; and probably he who never made a mistake never made a discovery." (Samuel Smiles, "Facilities and Difficulties", 1859)

"[…] the statistical prediction of the future from the past cannot be generally valid, because whatever is future to any given past, is in tum past for some future. That is, whoever continually revises his judgment of the probability of a statistical generalization by its successively observed verifications and failures, cannot fail to make more successful predictions than if he should disregard the past in his anticipation of the future. This might be called the ‘Principle of statistical accumulation’." (Clarence I Lewis, "Mind and the World-Order: Outline of a Theory of Knowledge", 1929)

"Science condemns itself to failure when, yielding to the infatuation of the serious, it aspires to attain being, to contain it, and to possess it; but it finds its truth if it considers itself as a free engagement of thought in the given, aiming, at each discovery, not at fusion with the thing, but at the possibility of new discoveries; what the mind then projects is the concrete accomplishment of its freedom." (Simone de Beauvoir, "The Ethics of Ambiguity", 1947)

"Common sense […] may be thought of as a series of concepts and conceptual schemes which have proved highly satisfactory for the practical uses of mankind. Some of those concepts and conceptual schemes were carried over into science with only a little pruning and whittling and for a long time proved useful. As the recent revolutions in physics indicate, however, many errors can be made by failure to examine carefully just how common sense ideas should be defined in terms of what the experimenter plans to do." (James B Conant, "Science and Common Sense", 1951)

"Catastrophes are often stimulated by the failure to feel the emergence of a domain, and so what cannot be felt in the imagination is experienced as embodied sensation in the catastrophe. (William I Thompson, "Gaia, a Way of Knowing: Political Implications of the New Biology", 1987)

"What about confusing clutter? Information overload? Doesn't data have to be ‘boiled down’ and  ‘simplified’? These common questions miss the point, for the quantity of detail is an issue completely separate from the difficulty of reading. Clutter and confusion are failures of design, not attributes of information." (Edward R Tufte, "Envisioning Information", 1990)

"When a system is predictable, it is already performing as consistently as possible. Looking for assignable causes is a waste of time and effort. Instead, you can meaningfully work on making improvements and modifications to the process. When a system is unpredictable, it will be futile to try and improve or modify the process. Instead you must seek to identify the assignable causes which affect the system. The failure to distinguish between these two different courses of action is a major source of confusion and wasted effort in business today." (Donald J Wheeler, "Understanding Variation: The Key to Managing Chaos" 2nd Ed., 2000)

"[…] in cybernetics, control is seen not as a function of one agent over something else, but as residing within circular causal networks, maintaining stabilities in a system. Circularities have no beginning, no end and no asymmetries. The control metaphor of communication, by contrast, punctuates this circularity unevenly. It privileges the conceptions and actions of a designated controller by distinguishing between messages sent in order to cause desired effects and feedback that informs the controller of successes or failures." (Klaus Krippendorff, "On Communicating: Otherness, Meaning, and Information", 2009)

"To get a true understanding of the work of mathematicians, and the need for proof, it is important for you to experiment with your own intuitions, to see where they lead, and then to experience the same failures and sense of accomplishment that mathematicians experienced when they obtained the correct results. Through this, it should become clear that, when doing any level of mathematics, the roads to correct solutions are rarely straight, can be quite different, and take patience and persistence to explore." (Alan Sultan & Alice F Artzt, "The Mathematics that every Secondary School Math Teacher Needs to Know", 2011)

"A very different - and very incorrect - argument is that successes must be balanced by failures (and failures by successes) so that things average out. Every coin flip that lands heads makes tails more likely. Every red at roulette makes black more likely. […] These beliefs are all incorrect. Good luck will certainly not continue indefinitely, but do not assume that good luck makes bad luck more likely, or vice versa." (Gary Smith, "Standard Deviations", 2014)

"We are seduced by patterns and we want explanations for these patterns. When we see a string of successes, we think that a hot hand has made success more likely. If we see a string of failures, we think a cold hand has made failure more likely. It is easy to dismiss such theories when they involve coin flips, but it is not so easy with humans. We surely have emotions and ailments that can cause our abilities to go up and down. The question is whether these fluctuations are important or trivial." (Gary Smith, "Standard Deviations", 2014)

"Although cascading failures may appear random and unpredictable, they follow reproducible laws that can be quantified and even predicted using the tools of network science. First, to avoid damaging cascades, we must understand the structure of the network on which the cascade propagates. Second, we must be able to model the dynamical processes taking place on these networks, like the flow of electricity. Finally, we need to uncover how the interplay between the network structure and dynamics affects the robustness of the whole system." (Albert-László Barabási, "Network Science", 2016)

More quotes in "Failure" at the-web-of-knowledge.blogspot.com.

28 December 2016

Strategic Management: Managers (Just the Quotes)

"The manager must never be lacking in knowledge of the special profession which is characteristic of the undertaking: the technical profession in industry, commercial in commerce, political in the State, military in the Army, religious in the Church, medical in the hospital, teaching in the school, etc. The technical function has long been given the degree of importance which is its due, and of which we must not deprive it, but the technical function by itself cannot endure the successful running of a business; it needs the help of the other essential functions and particularly of that of administration. This fact is so important from the point of view of the organization and management of a business that I do not mind how often I repeat it in order that it may be fully realized." (Henri Fayol, "Industrial and General Administration", 1916)

"Managers today come up against a few more communication barriers. One is the pressure of time. Listening carefully takes time, and managers have little of that to spare. In today’s business culture especially, with its emphasis on speed, already pressed managers may give short shrift to the slower art of one-on-one communication." (Carl Rogers & Fritz Roethlisberger, "Barriers and gateways to communication", Harvard Business Review, 1952)

"Managers are the basic and scarcest resource of any business enterprise." (Peter F Drucker, "The Practice of Management", 1954)

"[...] 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 delegations from a superior to a subordinate may be made in large or small degree. The tendency to delegate much authority through the echelons of an organization structure is referred to as decentralization of authority. On the other hand, authority is said to be centralized wherever a manager tends not to delegate authority to his subordinates." (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)

"It is highly important for managers to be honest and clear in describing what authority they are keeping and what role they are asking their subordinates to assume." (Robert Tannenbaum & Warren H Schmidt, Harvard Business Review, 1958)

"We have overwhelming evidence that available information plus analysis does not lead to knowledge. The management science team can properly analyse a situation and present recommendations to the manager, but no change occurs. The situation is so familiar to those of us who try to practice management science that I hardly need to describe the cases." (C West Churchman, "Managerial acceptance of scientific recommendations", California Management Review Vol 7, 1964)

"The successful manager must be a good diagnostician and must value a spirit of inquiry." (Edgar H Schein, "Organizational Psychology", 1965)

"Managers need all the information they want. Most MIS designers 'determine' what information is needed by asking managers what information they would like to have. This is based on the assumption that managers know what information they need and want." (Russell L Ackoff, "Management Misinformation Systems", 1967)

"Most MIS [Management Information Systems] designers 'determine' what information is needed by asking managers what information they would like to have. This is based on the (often erroneous) assumption that managers know that information they need and want it." (Russell L Ackoff, Management Science, 1967)

"Targets set by individual managers are relevant to the company's goals because the entire management group is involved in the total planning process." (Walter S Wilkstrom, "Managing by-and-with Objectives", 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)

"The myth of efficiency lies in the assumption that the most efficient manager is ipso facto the most effective; actually the most efficient manager working on the wrong task will not be effective." (R Alec Mackenzie, "The Time Trap", 1972)

"It is more important for the manager to get his information quickly and efficiently than to get it formally." (Henry Mintzberg, "The Nature of Managerial Work", 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)

"The manager is a servant. His master is the institution he manages and his first responsibility must therefore be to it." (Peter F Drucker, "Management: Tasks, Responsibilities, Practices", 1973)

"The prime occupational hazard of the manager is superficiality." (Henry Mintzberg, "The Nature of Managerial Work", 1973)

"A manager [...] sets objectives [...] organizes [...] motivates and communicates [...] measure[s] [...] develops people. Every manager does these thingsknowingly or not. A manager may do them well, or may do them wretchedly, but always does them." (Peter F Drucker, "People and Performance", 1977)

"Above all, innovation is not invention. It is a term of economics rather than of technology. [...] The measure of innovation is the impact on the environment. [...] To manage innovation, a manager has to be at least literate with respect to the dynamics of innovation." (Peter F Drucker, "People and Performance", 1977)

"[...] when a variety of tasks have all to be performed in cooperation, syncronization, and communication, a business needs managers and a management. Otherwise, things go out of control; plans fail to turn into action; or, worse, different parts of the plans get going at different speeds, different times, and with different objectives and goals, and the favor of the 'boss' becomes more important than performance." (Peter F Drucker, "People and Performance", 1977)

"Managers are not confronted with problems that are independent of each other, but with dynamic situations that consist of complex systems of changing problems that interact with each other. I call such situations messes. Problems are extracted from messes by analysis. Managers do not solve problems, they manage messes." (Russell L Ackoff, "The future of operational research is past", 1979)

"Managers construct, rearrange, single out, and demolish many objective features of their surroundings. When people act they unrandomize variables, insert vestiges of orderliness, and literally create their own constraints." (Karl E Weick, "Social Psychology of Organizing", 1979)

"Overly optimistic goals nearly always result in one of two extremes. If the goal is seen as a must, then the division manager must 'go for broke. This can result in reckless risk taking. More commonly [...] ultraconservative action. The reasoning is: "Why take any chances to achieve an unattainable goal."(Bruce Henderson, "Henderson on Corporate Strategy", 1979)

"The performance of profit center managers is [usually] measured over a moderate time span. The penalty for unsatisfactory absolute performance over the short-term is severe. The proper balance between known performance and potential future benefits is never clear." (Bruce Henderson, "Henderson on Corporate Strategy", 1979)

"A competent manager can usually explain necessary planning changes in terms of specific facts which have contributed to the change. The existing fear, or attitude of failure, which results from missed completion dates should be replaced by a more constructive fear of failing to keep a plan updated." (Philip F Gehring Jr. & Udo W Pooch, "Advances in Computer Programming Management", 1980)

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

"Knowledge specialists may ascribe a degree of certainty to their models of the world that baffles and offends managers. Often the complexity of the world cannot be reduced to mathematical abstractions that make sense to a manager. Managers who expect complete, one-to-one correspondence between the real world and each element in a model are disappointed and skeptical." (Dale E Zand, "Information, Organization, and Power", 1981)

"In management, there are few things as dangerous as a comprehensive, accurate answer to the wrong question. This is pseudo-knowledge. It easily misleads management into erroneous actions. Pseudo-knowledge has mushroomed with the advent of computers, which have made available masses of data that answer questions managers found too costly to ask before. In too many instances, however, the data are collected but not used because they answer irrelevant questions." (Dale E. Zand, "Information, Organization, and Power", 1981)

"Knowledge-based organizations require managers to be problem-centered rather than territory-centered." (Dale E Zand, "Information, Organization, and Power", 1981)

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

"Managing upward relies on informal relationships, timing, exploiting ambiguity, and implicit communication. And the irony of it all is that these most subtle skills must be learned and mastered by younger managers who not only lack education and directed experience in benign guerilla warfare but are further misguided by management myths which contribute to false expectations and a misleading perception of reality." (Richard T Pascale & Anthony G Athos, "The Art of Japanese Management", 1981)

"At the core of every manager’s job is the requirement to make things happen toward a goal or consistent with a plan. Managers need to set goals and initiate actions to achieve them." (Richard Boyatzis, "Competent Manager", 1982)

"Coaching subordinates isn't an addition to a manager's job; it's an integral part of it." (George S Odiorne, "How Managers Make Things Happen", 1982)

"Managers are being confronted by a wider range of external pressures that must be taken into account in their major decisions [...] includ[ing] environmental protection, employment opportunities for minorities and all sorts of disadvantaged, shielding the consumer, and conforming to increasing government regulations." (Boris Yavitz & William H Newman, "Strategy in Action, 1982)

"One important function of strategy is to counteract a tendency of professional managers to become too conservative and bureaucratic." (Boris Yavitz & William H Newman, "Strategy in Action", 1982)

"Because the importance of training is so commonly underestimated, the manager who wants to make a dramatic improvement in organizational effectiveness without challenging the status quo will find a training program a good way to start." (Theodore Caplow, "Managing an Organization", 1983)

"Effective managers live in the present but concentrate on the future." (James L Hayes, "Memos for Management: Leadership", 1983)

"If managers are careless about basic things telling the truth, respecting moral codes, proper professional conductwho can believe them on other issues?" (James L Hayes, "Memos for Management: Leadership", 1983)

"Individual contributors who gather and disseminate know-how and information should also be seen as middle managers, because they exert great power within the organization." (Andrew S Grove, "High Output Management", 1983)

"Leadership is a manager's ability to get subordinates to develop their capabilities by inspiring them to achieve." (John A Reinecke & William F Schoell, "Introduction to Business", 1983)

"Managers have an awareness that they are the direct representatives of the employees." (Takashi Ishihara, "Cherry Blossoms and Robotics", 1983)

"Organizational values are best transmitted when they are acted out, and not merely announced, by the people responsible for training, or by the people who become role-models for recruits. The manager of an organization is a role-model ex officio and may have an astonishing ability to communicate organizational values to recruits in fleeting contacts with them. That is the age-old secret of successful generalship, and it is applied every day by charismatic leaders in other fields, whose commitments to their roles is so dramatic that they strike awe into the recruits who observe them in action." (Theodore Caplow, "Managing an Organization", 1983)

"There is an especially efficient way to get information, much neglected by most managers. That is to visit a particular place in the company and observe what's going on there." (Andrew S Grove, "High Output Management", 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)

"Most managers are reluctant to comment on ineffective or inappropriate interpersonal behavior. But these areas are often crucial for professional task success. This hesitancy is doubly felt when there is a poor relationship between the two. [...] Too few managers have any experience in how to confront others effectively; generally they can more easily give feedback on inadequate task performance than on issues dealing with another's personal style." (David L Bradford & Allan R Cohen, "Managing for Excellence", 1984)

"Most managers are rewarded if their unit operates efficiently and effectively. A highly creative unit, in contrast, might appear ineffective and uneven, and rather crazy to an outside or inside observer." (William G Dyer, "Strategies for Managing Change", 1984)

"One of the most important tasks of a manager is to eliminate his people's excuses for failure." (Robert Townsend, "Further Up the Organization", 1984)

"It seems to me that we too often focus on the inside aspects of the job of management, failing to give proper attention to the requirement for a good manager to maintain those relationships between his organization and the environment in which it must operate which permits it to move ahead and get the job done." (Breene Kerr, Giants in Management, 1985)

"The key mission of contemporary management is to transcend the old models which limited the manager's role to that of controller, expert or morale booster. These roles do not produce the desired result of aligning the goals of the employees and the corporation. [...] These older models, vestiges of a bygone era, have served their function and must be replaced with a model of the manager as a developer of human resources." (Michael Durst, "Small Systems World", 1985)

"A real challenge for some organizations is to build more qualitative information into their formal systems. One method used in some companies is to request a written narrative with each submission of statistics from the field. Another method is to hold periodic, indepth discussions involving several managers from different levels so that each can contribute whatever qualitative data are available to him." (Larry E Greiner et al, "Human Relations", 1986)

"[In a crisis:] Resist the pressure to take premature action. Talk to your people individually to find the crisis heroes, the handful of managers who have a clear understanding of the situation, see it the way you do, and can deal with any ambiguity involved. After you find them, tell them what you expect and lean on them hard." (Gerald C Meyers, "When It Hits the Fan", 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)

"Managers who are skilled communicators may also be good at covering up real problems." (Chris Argyris, Harvard Business Review, 1986)

"Most managers, most of the time, treat the happenings of the past as if they were the permanent or given nature of things, rather than simply things that occurred in the past." (Kenneth and Linda Schatz, "Management By Influence" 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)

"The inherent conflict between managers and professionals results basically from a clash of cultures: the corporate culture, which captures the commitment of managers, and the professional culture, which socializes professionals." (Joseph A Raelin, Harvard Business School, 1986)

"The practice of declaring codes of ethics and teaching them to managers is not enough to deter unethical conduct." (Saul W Gellerman, Harvard Business Review, 1986)

"The 'management by objectives' school [...] suggests that detailed objectives be spelled out at all levels in the corporation. This method is feasible at lower levels of management, but it becomes unworkable at the upper levels. The top manager must think out objectives in detail, but ordinarily some of the objectives must be withheld, or at least communicated to the organization in modest doses. A conditioning process that may stretch over months or years is necessary in order to prepare the organization for radical departures from what it is currently striving to attain." (H Edward Wrapp, Harvard Business Review on Human Relations, 1986)

"Top managers are currently inundated with reams of information concerning the organizational units under their supervision. Behind this information explosion lies a seemingly logical assumption made by information specialists and frequently accepted by line managers: if top management can be supplied with more 'objective' and 'accurate' quantified information, they will make 'better' judgments about the performance of their operating units. [...] A research study we have recently completed indicates that quantified performance information may have a more limited role than is currently assumed or envisioned; in fact, managers rely more on subjective information than they do on so called 'objective' statistics in assessing the overall performance of lower-level units." (Larry E. Greiner et al, Harvard Business Review on Human Relations, 1986)

"[Computer and other technical managers] must become business managers or risk landing on the technological rubbish heap." (Jim Leeke, PC Week, 1987)

"How you measure the performance of your managers directly affects the way they act." (John Dearden, Harvard Business Review, 1987)

"Management: The definition that includes all the other definitions in this book and which, because of that, is the most general and least precise. Its concrete, people meaning - the board of directors and all executives with the power to make decisions - is no problem, except for the not-so-little matter of where to draw the line between managers who are part of 'the management' and managers who are not. (Robert Heller, "The Pocket Manager", 1987)

"Management skills are only part of what it takes. [...] Managers must also be corporate warriors or leaders. These unique individuals are the problem identifiers. They possess a strong sense of vision; view firefighting as an opportunity to do things differently and smarter; and are business strategists who help identify key corporate growth issues." (John W Aldridge, Management Review, December 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)

"Managers jeopardize product quality by setting unreachable deadlines. They don’​​​​​​t think about their action in such terms; they think rather that what they’​​​​​​re doing is throwing down an interesting challenge to their workers, something to help them strive for excellence." (Tom DeMarco & Timothy Lister, "Peopleware: Productive Projects and Teams", 1987)

"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 a dual role: doing technical work and advising management." (Philip W Metzger, "Managing Programming People", 1987)

"Most of us managers are prone to one failing: A tendency to manage people as though they were modular components."  (Tom DeMarco & Timothy Lister, "Peopleware: Productive Projects and Teams", 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)

[...] 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)

"Setting and communicating the right expectations is the most important tool a manager has for imparting that elusive drive to the people he supervises." (Andrew S. Grove, "One-On-One With Andy Grove", 1987)

"Setting goals can be the difference between success and failure. [...] Goals must not be defined so broadly that they cannot be quantified. Having quantifiable goals is an essential starting point if managers are to measure the results of their organization's activities. [...] Too often people mistake being busy for achieving goals." (Philip D Harvey & James D Snyder, Harvard Business Review, 1987)

"Telling a manager he's got to reach 25% growth isn't particularly relevant if his market isn't growing at all." (Ian A Cole, Business Week, 1987)

"The manager must decide what type of group is wanted. If cooperation, teamwork, and synergy really matter, then one aims for high task interdependence. One structures the jobs of group members so that they have to interact frequently [...] to get their jobs done. Important outcomes are made dependent on group performance. The outcomes are distributed equally. If frenzied, independent activity is the goal, then one aims for low task interdependence and large rewards are distributed competitively and unequally." (Gregory P Shea & Richard A Guzzo, Sloan Management Review, 1987)

"The major problems of our work are not so much technological as sociological in nature. Most managers are willing to concede the idea that they’​​​​​​ve got more people worries than technical worries. But they seldom manage that way. They manage as though technology were their principal concern. They spend their time puzzling over the most convoluted and most interesting puzzles that their people will have to solve, almost as though they themselves were going to do the work rather than manage it. […] The main reason we tend to focus on the technical rather than the human side of the work is not because it’​​​​​​s more crucial, but because it’​​​​​​s easier to do." (Tom DeMarco & Timothy Lister, "Peopleware: Productive Projects and Teams", 1987)

"The most successful managers are those that can quickly grasp how their bosses think." (Amy Bermar, PC Week, 1987)

"The way to get higher productivity is to train better managers and have fewer of them." (William Woodside, "Thriving on Chaos", 1987)

"When they [managers] can't manage because of too much oversight, it permeates the entire organization." (Frank C Carlucci, "Frank Carlucci on Management in Government", 1987)

"There's a burnout problem among programmers just as there is in any group. You can't expect a programmer to sit for weeks, months, years, doing the same type of programming, and not slack off. [...] Preventing stagnation is the manager's job. [...] Get them totally away from their current jobs." (Philip W Metzger, "Managing Programming People", 1987)

"To be effective, a manager must accept a decreasing degree of direct control." (Eric G Flamholtz & Yvonne Randal, "The Inner Game of Management", 1987)

"[Well-managed modern organizations] treat everyone as a source of creative input. What's most interesting is that they cannot be described as either democratically or autocratically managed. Their managers define the boundaries, and their people figure out the best way to do the job within those boundaries. The management style is an astonishing combination of direction and empowerment. They give up tight control in order to gain control over what counts: results." (Robert H Waterman, "The Renewal Factor", 1987)

"Rather than allowing them [subordinates] the autonomy to get involved and do the work in their own ways, what happens all too often is the manager wants the workers to do it the manager's way." (Edward L Deci, Nation's Business, 1988)

"Some people are excited about learning a new piece of software. Other people get very depressed. Good managers anticipate both situations they involve the persons to be affected in the process of selecting a particular program, and they provide time and resources for training. Training is the key in both cases." (Jonathan P Siegel, "Communications", 1988)

"The future prospects of management science will be much enhanced if (a) the diversity of issues confronting managers is accepted, (b) work on developing a rich variety of problem-solving methodologies is undertaken, and (c) we continually ask the question: 'What kind of issue can be managed with which sort of methodology?'." (Robert L Flood & Michael C Jackson, "Creative Problem Solving: Total Systems Intervention", 1991)

"A manager of people needs to understand that all people are different. This is not ranking people. He needs to understand that the performance of anyone is governed largely by the system that he works in, the responsibility of management." (W Edwards Deming, "The New Economics for Industry, Government, Education", 1993)

"Pressure can also make managers act out of character. Degrees of panic will cause a normally good manager to lose self-confidence and focus. Under stress, even a good plan can be abandoned." (Wheeler L Baker, "Crisis Management: A Model for Managers", 1993)

"Industrial managers faced with a problem in production control invariably expect a solution to be devised that is simple and unidimensional. They seek the variable in the situation whose control will achieve control of the whole system: tons of throughput, for example. Business managers seek to do the same thing in controlling a company; they hope they have found the measure of the entire system when they say 'everything can be reduced to monetary terms'." (Stanford Beer, "Decision and Control", 1994)

"The trouble is that no manager can really handle the full-scale isomorph of his enterprise unless he is the only employee. To delegate is to embark on a series of one-many transformations. The manager can at best settle for a homomorph consisting of all the ones." (Stanford Beer, "Decision and Control", 1994)

"Experience is the consequence of activity. The manager literally wades into the swarm of 'events' that surround him and actively tries to unrandomize them and impose some order: The manager acts physically in the environment, attends to some of it, ignores most of it, talks to other people about what they see and are doing."  (Karl E Weick, "Sensemaking in Organizations", 1995)

"Managers are incurably susceptible to panacea peddlers. They are rooted in the belief that there are simple, if not simple-minded, solutions to even the most complex of problems. And they do not learn from bad experiences. Managers fail to diagnose the failures of the fads they adopt; they do not understand them. […] Those at the top feel obliged to pretend to omniscience, and therefore refuse to learn anything new even if the cost of doing so is success." (Russell L Ackoff, "A Lifetime Of Systems Thinking", Systems Thinker, 1999)

"The manager [...] is understood as one who observes the causal structure of an organization in order to be able to control it [...] This is taken to mean that the manager can choose the goals of the organization and design the systems or actions to realize those goals [...]. The possibility of so choosing goals and strategies relies on the predictability provided by the efficient and formative causal structure of the organization, as does the possibility of managers staying 'in control' of their organization's development. According to this perspective, organizations become what they are because of the choices made by their managers." (Ralph D Stacey et al, "Complexity and Management: Fad or Radical Challenge to Systems Thinking?", 2000)

"The whole way of thinking focuses attention, for most, on the designed system, but it never proves sufficient, and they [the managers] have to 'get things done anyway', almost despite the system. What they are not encouraged to do, by this very way of thinking itself, is to pay attention to the detailed interactions between them, through which they "get things done." [This] is a thoroughly stressful daily experience for people." (Ralph D. Stacey et al, "Complexity and Management: Fad or Radical Challenge to Systems Thinking?", 2000)

"Managers cannot learn from doing things right, only from doing them wrong." (Russell L Ackoff, "A Little Book of F-laws: 13 common sins of management", 2006)

"The less sure managers are of their opinions, the more vigorously they defend them. Managers do not waste their time defending beliefs they hold strongly – they just assert them. Nor do they bother to refute what they strongly believe is false." (Russell L Ackoff, "A Little Book of F-laws: 13 common sins of management", 2006)

"The lower the rank of managers, the more they know about fewer things. The higher the rank of managers, the less they know about many things." (Russell L Ackoff, "A Little Book of F-laws: 13 common sins of management", 2006)

"The other element of systems thinking is learning to influence the system with reinforcing feedback as an engine for growth or decline. [...] Without this kind of understanding, managers will hit blockages in the form of seeming limits to growth and resistance to change because the large complex system will appear impossible to manage. Systems thinking is a significant solution." (Richard L Daft, "The Leadership Experience" 4th Ed., 2008)

"Almost by definition, one is rarely privileged to 'control' a disaster. Yet the activity somewhat loosely referred to by this term is a substantial portion of Management, perhaps the most important part. […] It is the business of a good Manager to ensure, by taking timely action in the real world, that scenarios of disaster remain securely in the realm of Fantasy." (John Gall, "The Systems Bible: The Beginner's Guide to Systems Large and Small"[Systematics 3rd Ed.], 2011)

18 December 2016

Strategic Management: Organizations (Just the Quotes)

"The whole object of the organization is to get cooperation, to get to each individual the benefit of all the knowledge and all the experience of all individuals." (Hamilton M Barksdale, 1909)

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

"Organization planning is the process of defining and grouping the activities of the enterprise so that they may be most logically assigned and effectively executed. It is concerned with the establishment of relationships among the units so as to further the objectives of the enterprise." (Ernest Dale, "Planning and developing the company organization structure", 1952)

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

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

"The concept of leadership has an ambiguous status in organizational practice, as it does in organizational theory. In practice, management appears to be of two minds about the exercise of leadership. Many jobs are so specified in content and method that within very broad limits differences among individuals become irrelevant, and acts of leadership are regarded as gratuitous at best, and at worst insubordinate." (Daniel Katz & Robert L Kahn, "The Social Psychology of Organizations", 1966)

"Most of our beliefs about complex organizations follow from one or the other of two distinct strategies. The closed-system strategy seeks certainty by incorporating only those variables positively associated with goal achievement and subjecting them to a monolithic control network. The open-system strategy shifts attention from goal achievement to survival and incorporates uncertainty by recognizing organizational interdependence with environment. A newer tradition enables us to conceive of the organization as an open system, indeterminate and faced with uncertainty, but subject to criteria of rationality and hence needing certainty." (James D Thompson, "Organizations in Action", 1967)

"'Structure follows strategy' is one of the fundamental insights we have acquired in the last twenty years. Without understanding the mission, the objectives, and the strategy of the enterprise, managers cannot be managed, organizations cannot be designed, managerial jobs cannot be made productive. [...] Strategy determines what the key activities are in a given business. And strategy requires knowing 'what our business is and what it should be'." (Peter F Drucker, "Management: Tasks, Responsibilities, Practices", 1973)

"We never like to admit to ourselves that we have made a mistake. Organizational structures tend to accentuate this source of failure of information." (Kenneth E Boulding, "Toward a General Social Science", 1974)

"A company is a multidimensional system capable of growth, expansion, and self-regulation. It is, therefore, not a thing but a set of interacting forces. Any theory of organization must be capable of reflecting a company's many facets, its dynamism, and its basic orderliness. When company organization is reviewed, or when reorganizing a company, it must be looked upon as a whole, as a total system." (Albert Low, "Zen and Creative Management", 1976)

"Five coordinating mechanisms seem to explain the fundamental ways in which organizations coordinate their work: mutual adjustment, direct supervision, standardization of work processes, standardization of work outputs, and standardization of worker skills." (Henry Mintzberg, "The Structuring of Organizations", 1979)

"We find that the manager, particularly at senior levels, is overburdened with work. With the increasing complexity of modern organizations and their problems, he is destined to become more so. He is driven to brevity, fragmentation, and superficiality in his tasks, yet he cannot easily delegate them because of the nature of his information. And he can do little to increase his available time or significantly enhance his power to manage. Furthermore, he is driven to focus on that which is current and tangible in his work, even though the complex problems facing many organizations call for reflection and a far-sighted perspective." (Henry Mintzberg, "The Structuring of Organizations", 1979)

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

"[Organizational] change is intervention, and intervention even with good intentions can lead to negative results in both the short and long run. For example, a change in structure in going from application of one theory to another might cause the unwanted resignation of a key executive, or the loss of an important customer. [...] the factor of change, acts as an overriding check against continual organizational alterations. It means that regardless of how well meant a change is, or how much logic dictates this change, its possible negative effects must be carefully weighed against the hoped-for benefits." (William A Cohen, "Principles of Technical Management", 1980)

"Knowledge-based organizations require managers to be problem-centered rather than territory-centered." (Dale E Zand, "Information, Organization, and Power", 1981)

"Organizations are social beings and their success depends on trust, subtlety and intimacy." (William Ouchi, "Theory Z", 1981)

"The models of management which individuals and organizations use come from a variety of sources. Sometimes the model comes from a theory. The theory may emerge from someone's thoughts about the desired characteristics of a manager, or about the characteristics of competent managers. Sometimes the model comes from a panel. A group of people, possibly in the job or at levels above the job within the organization, generates a model through discussion of what is needed to perform a management job competently." (Richard Boyatzis, "Competent Manager", 1982)

"Every company has two organizational structures: the formal one is written on the charts; the other is the everyday living relationship of the men and women in the organization." (Harold Geneen & Alvin Moscow, Managing, 1984)

"Any approach to the study of organizations is built on specific assumptions about the nature of organizations and how they are designed and function." (Richard L Daft & Karl E Weick, "Toward a model of organizations as interpretation systems", Academy of Management Review Vol 9 (2), 1984)

"[...] an examination of cultural issues at the organizational level is absolutely essential to a basic understanding of what goes on in organizations, how to run them, and how to improve them." (Edgar H Schein, "Organizational Culture and Leadership", 1985)

"Organizational cultures are created by leaders, and one of the decisive functions of leadership may well be the creation, the management, and - if and when that may become necessary - the destruction of culture." (Edgar Schein, "Organizational Culture and Leadership", 1985)

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

"Organizations are complex and paradoxical phenomena that can be understood in many different ways. Many of our taken-for-granted ideas about organizations are metaphorical, even though we may not recognize them as such. For example, we frequently talk about organizations as if they were machines designed to achieve predetermined goals and objectives, and which should operate smoothly and efficiently. And as a result of this kind of thinking, we often attempt to organize and manage them in a mechanistic way, forcing their human qualities into a background role. By using different metaphors to understand the complex and paradoxical character of organizational life, we are able to manage and design organizations in ways that we may not have thought possible before." (Gareth Morgan, "Images of Organization", 1986)

"Action often creates the orderly relations that originally were mere presumptions summarized in a cause map. Thus language trappings of organizations such as strategic plans are important components in the process of creating order. They hold events together long enough and tightly enough in people's heads so that they act in the belief that their actions will be influential and make sense." (Karl E Weick, "Organizational culture as a source of high reliability", 1987)

"All organizations engage in the three basic activities of strategy, tactics, and logistics. Strategy defines the job. Tactics does the job. Logistics provides the resources to get the job done - not only material resources, but also manpower, funds, and data." (Robert L Siegel, 1987)

"Organizations exist for only one purpose: to help people reach ends together that they could not achieve individually." (Robert H Waterman, "The Renewal Factor", 1987)

"[Successful organizations] comprehend uncertainty. They set direction, not detailed strategy. They are the best strategists precisely because they are suspicious of forecasts and open to surprise. They think strategic planning is great as long as no one takes the plans too seriously." (Robert H Waterman, "The Renewal Factor", 1987)

"[Well managed modern organizations] treat everyone as a source of creative input. What's most interesting is that they cannot be described as either democratically or autocratically managed. Their managers define the boundaries, and their people figure out the best way to do the job within those boundaries. The management style is an astonishing combination of direction and empowerment. They give up tight control in order to gain control over what counts: results." (Robert H Waterman, "The Renewal Factor", 1987)

"When they [managers] can't manage because of too much oversight, it permeates the entire organization." (Frank C Carlucci, "Frank Carlucci on Management in Government", 1987)

"Inertial pressures prevent most organizations from radically changing strategies and structures." (Michael T Hannan, "Organizational Ecology", 1989) 

"The importance of top management commitment to organizational change is so well accepted that it is almost cliché to repeat the fact. We would therefore expect managerial values to be just as important in this area as in others that require strategic direction and leadership" (Thomas A Kochan,"The Mutual Gains Enterprise", 1994) 

"Enterprise Engineering is not a single methodology, but a sophisticated synthesis of the most important and successful of today's change methods. 'Enterprise Engineering' first explains in detail all the critical disciplines (including continuous improvement, radical reinvention of business processes, enterprise redesign, and strategic visioning). It then illustrates how to custom-design the right combination of these change methods for your organization's specific needs." (James Martin, "The Great Transition, 1995)

"Now that knowledge is taking the place of capital as the driving force in organizations worldwide, it is all too easy to confuse data with knowledge and information technology with information." (Peter Drucker, "Managing in a Time of Great Change", 1995)

"Organizations are presumed to talk to themselves over and over to find out what they are thinking." (Karl E Weick, "Sensemaking in Organizations", 1995)

"Commonly, the threats to strategy are seen to emanate from outside a company because of changes in technology or the behavior of competitors. Although external changes can be the problem, the greater threat to strategy often comes from within. A sound strategy is undermined by a misguided view of competition, by organizational failures, and, especially, by the desire to grow." (Michael E Porter, "What is Strategy?", Harvard Business Review, 1996)

"Management is a set of processes that can keep a complicated system of people and technology running smoothly. The most important aspects of management include planning, budgeting, organizing, staffing, controlling, and problem solving. Leadership is a set of processes that creates organizations in the first place or adapts them to significantly changing circumstances. Leadership defines what the future should look like, aligns people with that vision, and inspires them to make it happen despite the obstacles." (John P Kotter, "Leading Change", 1996) 

"Strategy is creating fit among a company’s activities. The success of a strategy depends on doing many things well - not just a few - and integrating among them. If there is no fit among activities, there is no distinctive strategy and little sustainability. Management reverts to the simpler task of overseeing independent functions, and operational effectiveness determines an organization’s relative performance."  (Michael E Porter, "What is Strategy?", Harvard Business Review, 1996)

"There are several world view assumptions present in enterprise engineering. The first assumption is that the enterprise can be viewed as a complex system. This is necessary because systems in organizations are systems of organized complexity. Complexity is the result of the multiplicity and intricacy of man’s interaction with other components of the system. Secondly, the enterprise is to be viewed as a system of processes. These processes are engineered both individually and holistically. The final assumption is the use of engineering rigor in transforming the enterprise. The enterprise engineering paradigm views the enterprise as a complex system of processes that can be engineered to accomplish specific organizational objectives. In the Enterprise Engineering paradigm, the enterprise is viewed as a complex system of processes that can be engineered to accomplish specific organizational objectives." (Donald H Liles, "Enterprise modeling within an enterprise engineering framework", 1996)

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

"This is what systems thinking is all about: the idea of building an organization in which each piece, and partial solution of the organization has the fit, alignment, and integrity with your overall organization as a system, and its outcome of serving the customer." (Stephen G Haines, "The Systems Thinking Approach to Strategic Planning and Management", 2000)

"True systems thinking, on the other hand, studies each problem as it relates to the organization’s objectives and interaction with its entire environment, looking at it as a whole within its universe. Taking your organization from a partial systems to a true systems state requires effective strategic management and backward thinking." (Stephen G Haines, "The Systems Thinking Approach to Strategic Planning and Management", 2000)

"Organizations are (1) social entities that (2) are goal-directed, (3) are designed as deliberately structured and coordinated activity systems, and (4) are linked to the external environment." (Richard Daft, "The Leadership Experience", 2002)

"The key element of an organization is not a building or a set of policies and procedures; organizations are made up of people and their relationships with one another. An organization exists when people interact with one another to perform essential functions that help attain goals." (Richard Daft, "The Leadership Experience" , 2002)

"Organizations are not systems but the ongoing patterning of interactions between people. Patterns of human interaction produce further patterns of interaction, not some thing outside of the interaction. We call this perspective complex responsive processes of relating." (Ralph Stacey, 2005)

"Today’s big companies do very little to enhance the productivity of their professionals. In fact, their vertically oriented organization structures, retrofitted with ad hoc and matrix overlays, nearly always make professional work more complex and inefficient." (Lowell L Bryan & Claudia Joyce, "The 21st century organization", 2005)

"An ecology provides the special formations needed by organizations. Ecologies are: loose, free, dynamic, adaptable, messy, and chaotic. Innovation does not arise through hierarchies. As a function of creativity, innovation requires trust, openness, and a spirit of experimentation - where random ideas and thoughts can collide for re-creation." (George Siemens, "Knowing Knowledge", 2006)

"Businesses are themselves a form of design. The design of a business encompasses its strategy, organizational structure, management processes, culture, and a host of other factors. Business designs evolve over time through a process of differentiation, selection, and amplification, with the market as the ultimate arbiter of fitness [...] the three-way coevolution of physical technologies, social technologies, and business designs [...] accounts for the patterns of change and growth we see in the economy." (Eric D Beinhocker, "The Origin of Wealth. Evolution, complexity, and the radical remaking of economics", 2006)

"Change pressures arise from different sectors of a system. At times it is mandated from the top of a hierarchy, other times it forms from participants at a grass-roots level. Some changes are absorbed by the organization without significant impact on, or alterations of, existing methods. In other cases, change takes root. It causes the formation of new methods (how things are done and what is possible) within the organization." (George Siemens, "Knowing Knowledge", 2006)

"Hierarchy adapts knowledge to the organization; a network adapts the organization to the knowledge." (George Siemens, "Knowing Knowledge", 2006)

"Synergy occurs when organizational parts interact to produce a joint effect that is greater than the sum of the parts acting alone. As a result the organization may attain a special advantage with respect to cost, market power, technology, or employee." (Richard L Daft, "The Leadership Experience" 4th Ed., 2008)

"Systems thinking is a mental discipline and framework for seeing patterns and interrelationships. It is important to see organizational systems as a whole because of their complexity. Complexity can overwhelm managers, undermining confidence. When leaders can see the structures that underlie complex situations, they can facilitate improvement. But doing that requires a focus on the big picture." (Richard L Daft, "The Leadership Experience", 2008)

"The butterfly effect demonstrates that complex dynamical systems are highly responsive and interconnected webs of feedback loops. It reminds us that we live in a highly interconnected world. Thus our actions within an organization can lead to a range of unpredicted responses and unexpected outcomes. This seriously calls into doubt the wisdom of believing that a major organizational change intervention will necessarily achieve its pre-planned and highly desired outcomes. Small changes in the social, technological, political, ecological or economic conditions can have major implications over time for organizations, communities, societies and even nations." (Elizabeth McMillan, "Complexity, Management and the Dynamics of Change: Challenges for practice", 2008)

"In a complex society, individuals, organizations, and states require a high degree of confidence - even if it is misplaced - in the short-term future and a reasonable degree of confidence about the longer term. In its absence they could not commit themselves to decisions, investments, and policies. Like nudging the frame of a pinball machine to influence the path of the ball, we cope with the dilemma of uncertainty by doing what we can to make our expectations of the future self-fulfilling. We seek to control the social and physical worlds not only to make them more predictable but to reduce the likelihood of disruptive and damaging shocks (e.g., floods, epidemics, stock market crashes, foreign attacks). Our fallback strategy is denial." (Richard N Lebow, "Forbidden Fruit: Counterfactuals and International Relations", 2010)

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

"An organization's strategy is simply its plan for success. It's nothing more than the collection of intentional decisions a company makes to give itself the best chance to thrive and differentiate from competitors." (Patrick Lencioni, "The Advamtage: Why Organizational Health Trumps Everything Else In Business", 2012)

"In the context of an organization, to have autonomy is to be empowered, not just feel empowered. […] But it does not mean being a lone wolf or being siloed or cut off from the rest of the organization." (Sriram Narayan, "Agile IT Organization Design: For Digital Transformation and Continuous Delivery", 2015)

"Some hierarchy is essential for the effective functioning of an organization. Eliminating hierarchy has the frequent side effect of slowing down decision making and diffusing accountability." (Sriram Narayan, "Agile IT Organization Design: For Digital Transformation and Continuous Delivery", 2015)

"Whatever way we organize, the unit of organization is a team, and any team can turn into a silo if it acts in an insular manner. Therefore, in a sense, we can’t eliminate silos but only try to design around their side effects." (Sriram Narayan, "Agile IT Organization Design: For Digital Transformation and Continuous Delivery", 2015)

"Professional organizations had believed that by hiring well qualified, technically capable people, quality control would take care of itself. [...] Managers rationalized that quality control lapses could not be helped and were simply another cost of doing business. Now 
wasn't the only perfectionist in the university business." (Garth Peterson)
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.