DB FPX 8740 Assessment 1 Topic Feasibility Memo example

Reviewed by Blythe Cavendish, PhD Seminar: Strategy and Innovation Topic Development Capella University Free custom sample in 24 to 48h

This DB FPX 8740 Assessment 1 sample paper is a topic feasibility memo asking whether a doctoral student can study how manufacturers kill failing new products. It was written for Capella DB FPX 8740, Seminar: Strategy and Innovation Topic Development, a course in the Doctor of Business Administration (DBA) with the catalog code DB-FPX8740. The paper applies four tests, covering significance, researchability, access and time, and assesses access and time realistically rather than hopefully. It offers reformulations that would make the topic workable if the first version fails, and states its verdict plainly at the end, with the revised topic the student should carry into the next assessment.

CourseDB FPX 8740 Seminar: Strategy and Innovation Topic Development
AssessmentAssessment 1
Paper typeTopic feasibility memo
LengthAbout 1,080 words, 5 pages
FormatAPA 7 student paper
SchoolCapella University
ProgramDoctor of Business Administration (DBA)
UpdatedSeptember 2026

Free sample paper for DB FPX 8740 Assessment 1

1

Can I Study How Manufacturers Kill Failing Products? A Topic Feasibility Memo That Applies Four Tests, Assesses Access and Time Realistically, Offers Reformulations, and States a Verdict Plainly

Student Name

Capella University

DB FPX 8740: Seminar: Strategy and Innovation Topic Development

Instructor Name

Month Day, Year

What this part is doingThe title poses the feasibility question. Feasibility memos are judged on applying tests rather than discussing them, so the verdict is promised.
2

The Proposed Topic

I direct product development at a composite 320-employee manufacturer of agricultural spray equipment in Nebraska. In the past six years, our company has spent about 4.2 million dollars on three new product projects that were eventually canceled, each after the evidence against it had been available for more than a year. The proposed topic is how midsize manufacturers decide to stop new product development projects that are failing, and why those decisions are often made late.

Four Tests, Applied

Test 1: significance. The topic passes. Late termination wastes money and engineering time that could be spent on better projects, and the problem is not confined to my company. Schmidt and Calantone (2002) found that managers who initiated a new product project were less likely to see it as failing, more committed to it, and more likely to keep funding it than managers who took over a project someone else had started. The problem has costs a reader outside my firm would recognize.

What I Bring, and the Risk in It

I bring to the topic direct experience of three canceled projects, access to their full records, and relationships with peers at other manufacturers. The same experience is a risk. I was the sponsor of one of the three projects, and my view of why it ran long is not neutral. My company's cases can inform the design, as a pilot of the interview approach, but they should not be among the cases analyzed, and the memo treats them as excluded from the start. My position in the industry may also make peers more willing to talk and, at the same time, more careful about what they say to someone who competes with them for some customers. Test 2: a gap in the literature. The topic passes conditionally. Research on escalation of commitment is extensive, beginning with Staw's (1976) experiment showing that people personally responsible for a failing decision committed more resources to it. Research on new product development has examined termination as well; Behrens and Ernst (2014), in an experiment with 137 research and development managers deciding within a simulated stage-gate system, found that visual decision aids and consultant advice each reduced decisions to keep funding a losing project, and that using both together had the strongest effect. What appears less studied is how termination decisions are actually made inside midsize manufacturers, with small teams, owners involved in decisions, and informal gate processes. That gap must be confirmed in a fuller review. Test 3: access. The topic passes with risk, as discussed below. Test 4: time. The topic fails in its current form, as discussed below.

What this part is doingEach test ends with a verdict. Scorers reward memos that apply the tests rather than describe them.
3

Access Assessed Realistically

Studying termination decisions requires access to people and documents that companies rarely share: gate records, internal emails, and the managers who made decisions they may now regret. My own company would give access, but studying my own decisions raises obvious problems of bias. Other manufacturers are more difficult. Through an industry association of equipment manufacturers, I know product development leaders at about 15 comparable firms. A realistic estimate is that four to six might agree to discuss a canceled project, and fewer would share documents. Managers are also likely to describe past decisions in ways that make them look reasonable, a problem of retrospective accounts that the design would need to address. Any firm that agrees will also need assurance that project names, products, and financial figures will be disguised, since a canceled product can reveal a strategy a competitor would value. I expect to offer written confidentiality terms and to let each firm review how its cases are described before publication.

Time Treated as a Constraint

The program allows about 18 months for data collection and analysis. Termination decisions are infrequent; a midsize manufacturer might cancel one project every two or three years. Following decisions as they happen, which would avoid the problems of recall, is impossible in 18 months unless the study covers many firms. In its current form, which implies observing termination decisions as they unfold, the topic cannot be completed in the time available. A decision that happens once every few years cannot be watched as it happens in a program that allows eighteen months.

Reformulations Offered

Three reformulations would make the topic feasible. Reformulation A: study past termination decisions retrospectively through interviews with the managers involved and any available gate documents, in six to eight midsize manufacturers, focusing on the period between the first negative evidence and the cancellation. This is feasible in time, but it depends on recall. Anchoring each interview to the gate documents for the period would reduce, though not remove, that weakness. Reformulation B: study the design of termination criteria rather than termination decisions, comparing how midsize manufacturers write and apply their gate criteria for stopping projects. Documents are easier to obtain and the timing problem disappears, but the study would say less about how decisions are actually made. Reformulation C: study current projects at a small number of firms over 12 months, recording each gate review and whether stop criteria were applied, without waiting for a cancellation. It trades depth on termination for real-time records. This captures decisions as they happen, but it may observe few actual stop decisions.

A Verdict Stated Plainly

The topic is significant and probably fills a gap, but it is not feasible as originally framed. Reformulation A is the most promising, provided the design reduces recall bias by using documents to anchor interviews and by interviewing more than one person per decision. The next step is a fuller literature search to confirm the gap and to see how earlier retrospective studies of project termination handled the same problems. If the search shows that retrospective termination studies in midsize firms already exist, the topic would narrow further, for example to the role of owners in gate decisions, which is a feature of midsize family and founder-led manufacturers that larger-firm studies rarely capture.

What this part is doingThe verdict chooses among reformulations and states the next step. Scorers reward memos that end with a decision rather than a list.
4

Conclusion

Applied to the proposed topic, the four tests show that it matters, likely fills a gap, raises serious but manageable access problems, and fails on time as first framed. Reformulated as a retrospective study of past terminations in six to eight firms, it becomes feasible.

5

References

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

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

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-FPX8740 Assessment 1 instructions

The first assessment in DB FPX 8740 asks you to judge whether a proposed research topic is feasible for a doctoral study. You state the topic, apply tests of significance, researchability, access to data or participants and time needed, assess each honestly, consider alternative formulations that might pass where the original fails and reach a clear verdict. A topic that is interesting but impossible to study within the program is not feasible, and saying so is a valid result. Guidance on doctoral research design and feasibility, such as Creswell and Creswell, supports the memo.

How the DB-FPX8740 Assessment 1 example is put together

Interest, then four tests, then a verdict. The opening states the interest in a paragraph, without the justification that belongs to a later assessment. The memo then applies each feasibility test in turn: access to the people or firms required, availability of a measure for the central construct, the time the phenomenon takes relative to a study, and whether the data that would answer the question is something organizations retain. Each test gets a finding rather than a discussion. A short block then considers reformulations that would pass the failed tests, which is the constructive half of the memo. The closing states a verdict and its confidence. Headings name the tests, and every claim about what data exists carries evidence rather than assumption.

Reading the DB FPX 8740 Assessment 1 scoring guide

Capella's scoring guide rates the statement of the topic, the tests applied, the realism of the access and time assessments, the reformulations and the verdict. The topic reaches Distinguished when stated precisely enough to test. Tests score higher when applied consistently, each with evidence, such as whether manufacturers publish data on terminated products. Access earns credit when assessed realistically, recognizing that firms rarely discuss failed products with outsiders. Time is judged on whether the estimate reflects the actual steps, like recruiting product managers across several firms. Reformulations should offer workable alternatives, such as studying termination decisions from public product announcements. The verdict should be plain. A Proficient memo applies the tests; a Distinguished one would save a student from a study that cannot be finished.

DB FPX 8740 Assessment 1 help: mistakes that cost marks

Feasibility memos often confirm the topic without testing it, which defeats the purpose. Another weakness is treating access as easy because the writer knows someone in the industry. Time estimates ignore recruitment, approval and analysis. Significance is argued at length while researchability is skipped. Reformulations are missing, so a failing topic has no way forward. The verdict hedges, leaving the student no clearer about whether to proceed. Writing the four tests as headings, with evidence and a pass or fail for each, then proposing a revised topic where needed, keeps the memo honest and prepares the unit of analysis argument in Assessment 2.

Get a DB FPX 8740 Assessment 1 example written to your instructions

Send the Assessment 1 instructions and the scoring guide from your DB FPX 8740 courseroom, plus the interest you are considering. 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 memo that reaches an honest verdict early is worth more than months spent finding out later. 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 8740 papers and DBA samples

DB FPX 8740 Assessment 1 questions, answered

Is it acceptable to conclude my topic is not feasible?

It is often the most valuable outcome available, and the criteria are written to permit it. A memo that identifies why a topic cannot be studied, and offers a reformulation that could be, demonstrates exactly the judgment the seminar exists to develop. Discovering the same thing during the proposal costs considerably more.

How do I judge access before I have asked anyone?

Look at what comparable published studies achieved and how they got there. If the literature on your topic consists of survey work with mid level managers rather than interviews with executives, that tells you something about access. Your own network is evidence too, provided you describe it rather than assume it.

What makes a strategy topic fail on time?

Outcomes that take years to appear. Whether a strategic choice worked may not be visible for half a decade, so a study of outcomes is frequently infeasible while a study of the decision process or the early commitments is not. Recognizing that distinction is one of the more useful moves this memo can make.

Where can I find a free DB FPX 8740 Assessment 1 sample paper?

The product termination feasibility memo is here in full, applying four tests, assessing access and time realistically, offering reformulations and stating its verdict plainly.

Is it acceptable to conclude my topic is not feasible in DB FPX 8740 Assessment 1?

Yes. A clear finding that a topic cannot be studied, with a better alternative, shows the judgment the seminar is building.