An organization has a wide variety of decisions to make, ranging from highly structured decisions to unstructured decisions. A structured decision is one that is made quite often, and one in which the decision is based directly on the inputs. With structured decisions, once you know the necessary information you also know the decision that needs to be made. For example, inventory reorder levels can be structured decisions. Once your inventory of widgets gets below a specific threshold, there is a need to order more. Processes like this, based on structured decisions, are good candidates for automation. They can also be referred to as programmed decisions.
For programmed decisions, managers often develop heuristics, or mental shortcuts, to help reach a decision. For example, the retail store manager may not know how busy the store will be the week of a big sale, but might routinely increase staff by 30% every time there is a big sale (because this has been fairly effective in the past). Heuristics are efficient—they save time for the decision maker by generating an adequate solution quickly. Heuristics don’t necessarily yield the optimal solution, but a good solution. Heuristics are often used for programmed decisions, because experience in making the decision over and over helps the decision maker know what to expect and how to react. Programmed decision-making can also be taught fairly easily to another person.
In contrast, an unstructured decision or non programmed decision involves a lot of unknowns. They are generally based on criteria that are not well-defined, and information is more likely to be ambiguous or incomplete. The decision maker may need to exercise some thoughtful judgment and creative thinking to reach a good solution. An information system can support these types of decisions by providing the decision makers with information gathering tools and collaborative capabilities. An example of an unstructured decision might be dealing with a labor issue or setting policy for the implementation of a new technology.
A semi-structured decision is one in which most of the factors needed for making the decision are known but human experience and other outside factors may still impact the decision. A good example of a semi-structured decision is the hiring process. Part of the decision is structured (years of experience, education, etc.) and part of the decision is based on human experience (for example: social skills, problem solving skills etc.) Take a look at how companies are trying to program this decision and use algorithms. Semi-structured and unstructured decisions are more challenging and systems may not be able to assist in the process fully. However, advances in artificial intelligence (explored in Chapter 13) are helping to change this.
Decisions can also be classified into three categories based on the level at which they occur.
Strategic decisions set the course of an organization. Tactical/Managerial decisions are decisions about how things will get done. Finally, operational decisions refer to decisions that employees make each day to make the organization run. For example, think about the restaurant that routinely offers a free dessert when a customer complaint is received. The owner of the restaurant made a strategic decision to have great customer service. The manager of the restaurant implemented the free dessert policy as a way to handle customer complaints, which is a tactical decision. Finally, the servers at the restaurant are making individual decisions each day by evaluating whether each customer complaint received is legitimate and warrants a free dessert. Different information systems are used at each level of the company structure to support the different decision types. We explored transaction processing systems in Chapter 11.
|Level of Decision
|Examples of Decision
|Who Typically Makes Decisions
|Should we merge with another company?
Should we pursue a new product line?
Should we downsize our organization?
|Top Management Teams, CEOs, and Boards of Directors
|What should we do to help facilitate employees from the two companies working together?
How should we market the new product line?
Who should be let go when we downsize?
|How often should I communicate with my new coworkers?
What should I say to customers about our new product?
How will I balance my new work demands?
|Employees throughout the organization
“Chapter 7: Does IT Matter?” from Information Systems for Business and Beyond (2019) by David Bourgeois is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License, except where otherwise noted.
‘11.2 Understanding Decision Making” from Organizational Behavior is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License, except where otherwise noted.