| Course | DB FPX 8750 Seminar: Strategy and Innovation Literature Review |
|---|---|
| Assessment | Assessment 1 |
| Paper type | Search and screening plan |
| Length | About 1,100 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 1
Searching Four Traditions for One Question: A Search and Screening Plan on Late Termination of New Product Projects, With Terms From Rival Literatures, Exclusions Defined, the Survivor Problem Addressed, and a Protocol Written First
Student Name
Capella University
DB FPX 8750: Seminar: Strategy and Innovation Literature Review
Instructor Name
Month Day, Year
Why a Protocol Comes First
Tranfield et al. (2003) argue that traditional narrative reviews in management often lack thoroughness and can be biased by the reviewer's choices, and they propose adapting systematic review methods, including a protocol written before the search, to management research. This plan follows that advice. Writing the search terms, databases, and screening rules before reading prevents the review from drifting toward sources that confirm the conceptual framework already drafted, which proposed that sponsors' presence and sunk costs lengthen termination delay while written stop criteria and outside views shorten it.
The Review Question
The review asks: what does research show about the factors that affect how quickly organizations stop new product development projects once evidence indicates they will fail? The question is phrased neutrally, about factors in general, so that the search does not favor the four relations in the draft framework. It is also limited to evidence about decisions rather than advice about them, which excludes a large practitioner literature on how to run gate reviews that rarely reports what happened when its recommendations were followed. The review will, however, note where that practitioner advice agrees or conflicts with the empirical findings, since managers in the study's population are more likely to have read it.
Terms Drawn From Rival Traditions
The same phenomenon is studied under different names in at least four research traditions, and a search using one tradition's vocabulary would miss the others. Organizational behavior studies escalation of commitment, using terms such as escalation, sunk cost, entrapment, and persistence, following work such as Staw (1976). New product development research studies project termination and go/kill decisions, using terms such as stage-gate, go/no-go, project termination, kill decision, and project abandonment, following Cooper (1990). Strategy and finance research studies real options and staged investment, using terms such as abandonment option, staged investment, and option to abandon. Project management research studies project failure and troubled projects, using terms such as project failure, de-escalation, and project exit. The search string combines one block of object terms, new product, product development, research and development project, or innovation project, with a block of decision terms drawn from all four traditions. Each tradition's terms were chosen by reading two recent review articles from that tradition and listing the words they use for the phenomenon.
Databases and Limits
Searches will run in Business Source Complete, ABI/INFORM, Web of Science, and PsycINFO, the last because escalation research is often published in psychology journals. Results are limited to peer-reviewed empirical studies and systematic reviews published in English from 1976, the year of Staw's foundational experiment, to the present. Backward searching through the bibliographies of every included study, and forward searching of the five most cited, will follow the database runs.
Refusal Defined as Carefully as Inclusion
A study is included if it examines a decision to continue or stop a new product, research and development, or innovation project, and reports empirical evidence about a factor associated with that decision or its timing. A study is excluded if it examines escalation in settings unrelated to projects, such as personal investment decisions, unless it uses a new product scenario; if it models abandonment options mathematically without empirical data on decisions; if it examines project success without examining continuation decisions; or if it is a conference abstract, practitioner article, or book chapter without peer review. Each exclusion has a reason: the first keeps the review on organizational projects, the second on actual decisions, the third on the decision rather than the outcome, and the fourth on work whose methods can be appraised.
The Survivor Problem Addressed in Advance
The literature on new product decisions faces a survivor problem. Case studies and retrospective surveys tend to describe projects that firms were willing to discuss, often those that succeeded or were stopped in a way managers consider sensible, and firms whose project failures were most costly may no longer exist to be studied. A review that simply summarizes published findings would inherit that bias. The plan addresses it in three ways: each included study will be coded for how its sample of projects or decisions was obtained, experimental studies, which do not depend on which firms survive, will be analyzed separately from field studies, and the review will report how many field studies sampled only surviving firms.
Screening Stages
Screening will run in three stages, each with its own rule. At the title stage, records are removed only if the title shows clearly that the study falls outside the object block, for example a study of personal financial investment. At the abstract stage, the full inclusion and exclusion criteria are applied, and any record that cannot be judged from the abstract passes to the next stage rather than being excluded. At the full-text stage, each remaining study is read and either included or excluded with a single recorded reason drawn from the list above. Keeping uncertain records until the full text is read reduces the chance of excluding relevant studies on the strength of a vague abstract.
What Will Be Extracted
From each included study, a standard form will record the tradition it comes from, the design, the sample and how it was obtained, the setting, the factors examined, how the continue-or-stop decision or its timing was measured, the main findings with effect sizes where reported, and the authors' stated limitations. Extracting the same fields from every study, whichever tradition it belongs to, is what will later allow findings from escalation experiments and field studies of stage-gate systems to be compared on equal terms. The projects that cost a firm its existence rarely appear in anyone's sample.
Reasons Attached to Every Choice
The plan's reporting will follow the structure of the PRISMA 2020 statement (Page et al., 2021), including a flow diagram showing records identified, screened, excluded with reasons, and included. Two screeners, the author and a colleague from the doctoral program, will screen a random 20% of titles and abstracts independently, and disagreements will be recorded and resolved by discussion, with the rate of agreement reported.
Conclusion
The plan searches four traditions that study the same phenomenon under different names, defines exclusions with reasons, addresses the survivor problem before it can distort the findings, and writes every rule down before the first article is read.
References
Cooper, R. G. (1990). Stage-gate systems: A new tool for managing new products. Business Horizons, 33(3), 44-54. https://doi.org/10.1016/0007-6813(90)90040-I
Page, M. J., McKenzie, J. E., Bossuyt, P. M., Boutron, I., Hoffmann, T. C., Mulrow, C. D., Shamseer, L., Tetzlaff, J. M., Akl, E. A., Brennan, S. E., Chou, R., Glanville, J., Grimshaw, J. M., Hróbjartsson, A., Lalu, M. M., Li, T., Loder, E. W., Mayo-Wilson, E., McDonald, S., ... Moher, D. (2021). The PRISMA 2020 statement: An updated guideline for reporting systematic reviews. BMJ, 372, Article n71. https://doi.org/10.1136/bmj.n71
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
Tranfield, D., Denyer, D., & Smart, P. (2003). Towards a methodology for developing evidence-informed management knowledge by means of systematic review. British Journal of Management, 14(3), 207-222. https://doi.org/10.1111/1467-8551.00375
The Capella DB FPX 8750 Assessment 1 instructions
The first assessment in DB FPX 8750 asks you to plan a systematic search for your literature review. You identify the research traditions that address your question, collect the vocabulary each uses, build search strings for each database, state inclusion and exclusion criteria before running the searches, plan how sources will be screened, consider biases in what gets published or studied, such as survivorship, and write the protocol in enough detail for someone else to repeat it. Guidance on systematic reviews in management, such as Tranfield, Denyer and Smart, supports the plan.
How this DB FPX 8750 Assessment 1 example is built
Sources, terms, screening, then the survivor problem. The opening states the question the review will serve, since screening rules without a question are arbitrary. The second block names the databases and any hand searching, with reasons rather than a list. The third sets out search terms, including the vocabulary used by traditions that disagree with each other, which is what stops the review from finding only one side. The fourth states inclusion and exclusion criteria and the procedure for borderline cases. The fifth addresses survivorship directly: what kinds of firms are absent from this literature and how the review will avoid concluding things about them. The closing estimates what the protocol will return. Headings follow the prompt and methodological choices carry sources.
Where the marks sit in the DB FPX 8750 Assessment 1 scoring guide
Capella's criteria for the plan cover the identification of traditions, the search terms, the exclusions, the screening process, the treatment of bias and the completeness of the protocol. Traditions reach Distinguished when each is named with the vocabulary it uses, since a search built on one field's terms will miss studies in another. Terms score higher when they come from rival literatures, such as "project abandonment," "escalation" and "stage-gate kill decisions." Exclusions earn credit when defined before any search is run, so they cannot be shaped by what turns up. Screening is judged on whether the stages and criteria are stated. Survivorship should be addressed, since firms rarely publish on projects they killed. The protocol should be repeatable by someone else. A Proficient plan lists databases; a Distinguished one would find what a narrow search misses.
Common DB FPX 8750 Assessment 1 mistakes, and how to avoid them
Search plans often use a handful of obvious keywords from one field, which returns a comfortable but narrow set of sources. Another weakness is setting exclusions after reading the results, which quietly biases the review. Screening is described vaguely, like "relevant articles were selected." Survivorship and publication bias are ignored, although studies of successful projects dominate the literature. The protocol is too thin to repeat. The number of expected results is guessed without a pilot search. Running a short pilot search in two databases, noting the terms that appear in the best hits and adding them to the strings, strengthens the plan and prepares the critical review in Assessment 2.
Get a DB FPX 8750 Assessment 1 example written to your instructions
Send the Assessment 1 instructions and the scoring guide from your DB FPX 8750 courseroom, along with the question your review will serve. We write a custom example against those exact criteria and return it in 24 to 48 hours. The first custom sample is free, and a protocol written before the reading saves more time than any other document in the sequence. 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 2: Critical Literature Review
- DB FPX 8750 Assessment 3: Theoretical Position Paper
- DB FPX 8840 Assessment 1: Topic Proposal
- DB FPX 8740 Assessment 1: Topic Feasibility Memo
- DB FPX 8850 Assessment 1: Search Strategy Write-up
- DB FPX 8730 Assessment 1: Innovation Portfolio Review
DB FPX 8750 Assessment 1 questions, answered
How do I search traditions that use different vocabulary?
Find one paper from each tradition and mine its keywords and reference list. Resource based work, industrial organization economics and behavioral strategy describe overlapping phenomena in incompatible language, and a term set built from only one of them will return a literature that appears to agree with itself. Listing the alternate terms is part of the plan.
What is the survivorship problem in strategy research?
Published studies overwhelmingly examine firms that still exist, so practices associated with success may simply be practices of firms that lasted long enough to be studied. Your plan cannot fix that, but it can state where the review will be cautious and can deliberately seek work on failure where any exists.
Should the plan predict how many sources it will find?
An estimate helps, and being wrong is not penalized. What the estimate does is force a check on whether the protocol is workable: a plan returning four hundred records needs tighter screening, and one returning eleven needs wider terms. Discovering that now costs an afternoon rather than a month.
Where can I find a free DB FPX 8750 Assessment 1 sample paper?
The search and screening plan for late project termination is here in full, with terms from rival literatures, exclusions defined first, the survivor problem addressed and a protocol written before searching.
What is the survivorship problem in DB FPX 8750 Assessment 1?
Studies tend to examine projects or firms that lasted, because failed ones leave few records. A review that ignores this can overstate what leads to success.