| Course | DB FPX 8750 Seminar: Strategy and Innovation Literature Review |
|---|---|
| Assessment | Assessment 2 |
| Paper type | Critical literature review |
| Length | About 1,120 words, 5 pages |
| Format | APA 7 student paper |
| School | Capella University |
| Program | Doctor of Business Administration (DBA) |
| Updated | September 2026 |
Free sample paper for DB FPX 8750 Assessment 2
Bias or Option Value? A Critical Literature Review of Two Accounts of Late Project Termination, With Each Stated at Its Strongest, Assumptions Surfaced, Evidence Tested for Discrimination, and a Test Proposed
Student Name
Capella University
DB FPX 8750: Seminar: Strategy and Innovation Literature Review
Instructor Name
Month Day, Year
Two Accounts of the Same Behavior
Organizations often keep funding new product projects after evidence suggests they will fail. The search plan for this review drew studies from four traditions, and two of them offer competing explanations for that behavior. The escalation account holds that continuing is usually a mistake produced by psychological and social forces. The real options account holds that continuing can be a reasonable choice when a small further investment buys information that could reveal a large payoff. Both describe the same observable behavior, a project funded past its first negative signal, and they disagree about whether that behavior is an error.
The Escalation Account at Its Strongest
The escalation account begins with Staw (1976), whose participants poured more money into a failing course of action when they had chosen it themselves. Later research extended the finding to organizations. Sleesman et al. (2012) combined decades of studies in a meta-analysis and organized the determinants of escalation into project, psychological, social, and structural factors, finding support for several, including sunk costs and personal responsibility. In new product development specifically, Schmidt and Calantone (2002) reported that the managers who launched a product project read its warning signs more generously, and funded it longer, than managers who inherited it. At its strongest, the account explains not only that projects run long but who keeps them running and when. It predicts that continuation will be more likely where the decision maker started the project, where much has already been spent, and where stopping would be publicly visible. And it has an experimental base, which allows causal claims about the mechanisms, at least in controlled settings.
The Real Options Account at Its Strongest
The real options account treats a new product project as a series of small investments, each of which buys the right, but not the obligation, to invest further. McGrath (1999) argued that failure is an expected part of entrepreneurial activity and that real options reasoning helps firms by limiting what they lose on each step while keeping access to large gains. On this view, a project that shows disappointing early results may still be worth one more stage if the cost of that stage is small and the information it produces could change the forecast substantially. Continuing is not escalation; it is buying an option. At its strongest, this account explains why some projects that looked weak at an early gate later succeeded, and why a firm that stopped every project at its first negative signal would stop too many.
Assumptions Surfaced, Not Findings Compared
Comparing the accounts' findings is less revealing than comparing their assumptions. The escalation account assumes that the evidence at the time of the decision was sufficient to justify stopping, so that continuing represents a departure from what a neutral decision maker would do. The real options account assumes that the evidence was incomplete in a way that further investment could resolve, and that the organization would in fact stop if the next stage's information were bad. Adner and Levinthal (2004) identified the weak point in the second assumption. They argued that real options reasoning loses its discipline when organizations fail to abandon options as the logic requires, and when the goals of a project are redefined along the way, so that each new stage is judged against a different target. An organization that says it is buying an option but never exercises its right to walk away is escalating under another name. An option that is never abandoned is not an option; it is a commitment described in option language.
Evidence Tested for Discrimination
The key question for this review is whether existing evidence can tell the accounts apart. Much of it cannot. A field study showing that projects often continue after negative gate reviews is consistent with both: escalation says they should have stopped, options reasoning says the next stage might have been worth buying. To discriminate, a study would need to observe what the organization did when the next stage produced bad information. If it stopped, options reasoning describes the behavior; if it continued again, escalation does. The experimental evidence discriminates better but at a cost. The experiment by Behrens and Ernst (2014), in which 137 managers made go or stop calls on a scripted losing project, showed that graphical aids and advice from a consultant both lowered the rate of continuation. Because the experiment defined the project as losing, it shows that escalation can occur and can be reduced, but it does not show how often real projects that continue are losing rather than option-worthy.
Survivorship Applied Where It Bites
Survivorship distorts the options account more than the escalation account. Examples of projects that looked weak at an early gate and later succeeded are memorable and often published; projects that looked weak, continued, and failed are less often written about, and firms that failed because of them may not survive to be studied. A literature built on surviving successes will overstate how often continuing past negative evidence pays off. The escalation literature, resting largely on experiments in which the losing project is defined by the researcher, is less exposed to this bias, although its field studies face the same problem.
The Dispute Left Open, With a Test
The review does not settle the dispute, because the evidence available cannot. It can specify a test. In a set of firms, identify every gate review at which a project continued despite negative evidence, and record what the decision makers said the next stage was meant to learn. Then follow each project to its next review. If projects are stopped when the next stage's information is bad, and if the information sought was specified in advance, the options account describes the behavior. If projects continue regardless of what the next stage shows, or if the target changes between reviews, escalation does. The proposed study of midsize manufacturers can apply this test to its retrospective cases, since gate documents should show both the information sought and what happened next.
Conclusion
Escalation of commitment and real options reasoning explain the same behavior in opposite ways. Their assumptions differ on whether the evidence at the time was sufficient and whether the organization would actually stop. Most field evidence cannot distinguish them, survivorship inflates the options account, and a test based on what happens at the following review could tell them apart.
References
Adner, R., & Levinthal, D. A. (2004). What is not a real option: Considering boundaries for the application of real options to business strategy. Academy of Management Review, 29(1), 74-85. https://doi.org/10.2307/20159010
Behrens, J., & Ernst, H. (2014). What keeps managers away from a losing course of action? Go/stop decisions in new product development. Journal of Product Innovation Management, 31(2), 361-374. https://doi.org/10.1111/jpim.12100
McGrath, R. G. (1999). Falling forward: Real options reasoning and entrepreneurial failure. Academy of Management Review, 24(1), 13-30. https://doi.org/10.2307/259034
Schmidt, J. B., & Calantone, R. J. (2002). Escalation of commitment during new product development. Journal of the Academy of Marketing Science, 30(2), 103-118. https://doi.org/10.1177/03079459994362
Sleesman, D. J., Conlon, D. E., McNamara, G., & Miles, J. E. (2012). Cleaning up the big muddy: A meta-analytic review of the determinants of escalation of commitment. Academy of Management Journal, 55(3), 541-562. https://doi.org/10.5465/amj.2010.0696
Staw, B. M. (1976). Knee-deep in the big muddy: A study of escalating commitment to a chosen course of action. Organizational Behavior and Human Performance, 16(1), 27-44. https://doi.org/10.1016/0030-5073(76)90005-2
Reading the DB-FPX8750 Assessment 2 instructions
Assessment 2 in DB FPX 8750 has you review the literature critically rather than descriptively. You identify the competing explanations for your topic, present each in its strongest form, uncover the assumptions behind each, examine whether the evidence cited for each could also be explained by the other, and propose what kind of study would tell them apart. The search plan from Assessment 1 provides the sources, and both traditions should be represented by their strongest recent work. Critical review guidance, such as Alvesson and Sandberg on problematization, supports the approach.
How this DB FPX 8750 Assessment 2 example is built
Question, accounts, assumptions, discriminating evidence. The opening fixes the question narrowly, since competing explanations can only be compared on something specific. Each account then receives a block, stated in its own terms with its strongest evidence, before any criticism. A middle block surfaces the assumptions underneath each account and shows that the disagreement is at that level rather than at the level of findings, which is the analytical core. The fourth block asks whether the available evidence could distinguish the accounts, examining measurement and design rather than counting studies. A fifth handles the survivor bias where it bears on the question. The closing states what evidence would settle the dispute. Headings name explanations, and every account carries its own citations.
Where the marks sit in the DB FPX 8750 Assessment 2 scoring guide
The scoring guide weighs the statement of each account, the surfacing of assumptions, the test of evidence and the proposed discriminating study. Each account reaches Distinguished when stated as its best advocates would state it. Assumptions score higher when made explicit, such as whether managers are assumed to have accurate forecasts. Evidence earns credit when tested for whether it discriminates, since late termination fits both bias and rational waiting for information. A good proposed test would produce different results under each account, such as whether delays shrink when new information stops arriving. Sources should be current and drawn from both traditions. Balance matters, since the paper will be read by scholars from both traditions. Distinguished reviews move the debate forward.
DB FPX 8750 Assessment 2 help from the desk
Critical reviews often present one account fairly and the other as a straw man, which undercuts the critique. Another weakness is summarizing studies without asking what they assume. Evidence is counted rather than tested, so the review does not notice that most studies fit both accounts. The proposed test is vague or missing. Sources come mostly from one tradition. The writer's preference shows too early, coloring how the rival account is presented. Setting the two accounts side by side, with their assumptions and the evidence each claims, then asking which findings only one account predicts, gives the review a critical edge and prepares the position paper in Assessment 3.
Get a DB FPX 8750 Assessment 2 example written to your instructions
Send the Assessment 2 instructions and your DB FPX 8750 scoring guide, together with the screening plan and question from your first assessment. We write a custom example against those criteria and return it in 24 to 48 hours. The first custom sample is free, and the section that surfaces assumptions is the part worth reading twice. The paper above is an original model document written by our desk, not a submitted student paper and not an official Capella University document.
More DB FPX 8750 papers and DBA samples
- DB FPX 8750 Assessment 1: Search and Screening Plan
- DB FPX 8750 Assessment 3: Theoretical Position Paper
- DB FPX 8840 Assessment 2: Literature Alignment Paper
- DB FPX 8740 Assessment 2: Unit of Analysis Argument
- DB FPX 8850 Assessment 2: Thematic Synthesis
- DB FPX 8730 Assessment 2: Design Process Case Study
DB FPX 8750 Assessment 2 questions, answered
What does critical mean in a doctoral literature review?
Examining what a body of work takes for granted, not finding fault with individual studies. A critical review asks what has to be true for an explanation to work, whether that condition holds, and what the field would look like if it did not. Study level criticism is useful but it is not what the word is doing here.
How do I identify a tradition's assumptions?
Look at what it never argues for. If every paper in a stream treats firms as profit maximizing without defending it, that is an assumption rather than a finding. Introductions and theory sections reveal them fastest, since that is where authors state what they are building on rather than what they are testing.
Can I conclude that one tradition is right?
You can conclude that one account fits the evidence better on this question, with reasons, and that is a legitimate ending. What is harder to defend is a verdict on the traditions themselves, since they usually differ in what they are trying to explain. Naming the scope of your conclusion protects it.
Where can I find a free DB FPX 8750 Assessment 2 sample paper?
This page presents the full critical review of bias and option value accounts of late termination, with each stated at its strongest, assumptions surfaced, evidence tested for discrimination and a test proposed.
What does critical mean in DB FPX 8750 Assessment 2?
Examining what each body of research assumes and whether its evidence really supports its claims over rival explanations, not simply finding fault.