DB-FPX9801 Proposal Writing help

What DB-FPX9801 actually grades

This course grades a document that has to convince readers who are not reading for style. Alignment is judged before anything else, and it is mechanical: the business problem names a condition, the purpose sentence promises exactly what will be done about it, the questions ask only what the purpose promised, the design can answer those questions, the instrument measures those constructs, and the analysis plan operates on the data that instrument produces. Break one link and every criterion downstream weakens, which is why practiced readers start at the analysis plan and work backwards toward the problem.

The business problem carries the most weight and takes the most attempts. Voluntary separations running at 27 percent among 340 hourly associates across one fiscal year, against a sector figure nearer 18 percent, is evidence that a problem exists; the problem itself is what the organization does not know about the cause, and the doctoral version of it is the distance between what practice does and what evidence supports. Give every magnitude a denominator and a window, because low morale cannot be tested while twelve exits from forty-one branch managers between January and December can.

The method criteria reward defensibility rather than ambition. Question type fixes design: how much, how many and what relates to what belong to quantitative work, while how and why a practice unfolds inside a firm belongs to qualitative work. Then the proposal has to prove it is buildable: the population, the sampling frame you can genuinely reach, the instrument and its permission status, the person with authority to grant access, and the analysis fixed before a single response exists. Reviewers reject the promise that participants will be recruited from a mid sized manufacturer faster than they reject a modest design, because it describes a hope.

How we help in this course

Send the section you are drafting, the guide, and the setting you have in mind, and the sample arrives with an alignment table already built: each question beside its construct, its data source, the instrument that measures it, the test that will answer it, and the criterion it serves. Where access is uncertain we design around data you can obtain and write the fallback into the text.

A premium original deliverable inside 24 to 48 hours, drafted to the Distinguished descriptors in the guide you upload, moved through an eight person pipeline that includes a reader whose only assignment is tracing the chain backwards from the analysis plan to the problem and reporting where it snaps. Revisions cost nothing and continue until the criteria clear, and chair or faculty comments re-enter the same cycle free.

The assessments, one by one

Assessment 1

Assessment 1 of DB-FPX9801, Proposal Writing, usually asks for the front end of the doctoral project: a problem statement carrying evidence, a purpose sentence written in the verbs its design can support, and research questions that ask only what the purpose promised. Read the full Assessment 1 manual.

Assessment 2

Assessment 2 of DB-FPX9801, Proposal Writing, usually asks for the evidence half of the proposal: a review with a search method a reader could repeat, evidence organized by claim rather than by author, and a framework applied closely enough to this setting that it will still be visible when the instrument is built. Read the full Assessment 2 manual.

Assessment 3

Assessment 3 of DB-FPX9801, Proposal Writing, usually asks for the half of the document that decides whether the project can be built at all: the design with its rejected alternatives, the population and the frame you can genuinely reach, the instrument and its permission status, and an analysis. Read the full Assessment 3 manual.

How to actually write DB-FPX9801: where to begin

Settle the scoring guide and the purpose sentence before writing anything else. Each criterion becomes a heading with the Distinguished language pasted underneath, then the purpose gets drafted in the verbs its design demands: this quantitative correlational study will examine the relationship between, or this qualitative descriptive study will explore how. The assessments in this course usually ask for pieces of the proposal rather than the whole document at once, and your scoring guide decides which piece and in which order.

Then build the alignment table, because it finds the flaw a reader would find. Say the question asks whether perceived supervisor support predicts intent to stay among branch managers, controlling for tenure and pay band, which is a regression with three predictors the sample has to carry. Detecting a moderate association, a correlation near .30, at the conventional five percent alpha with 80 percent power takes roughly 84 usable responses. Surveys of working managers rarely return better than 20 to 25 percent, so 84 usable responses implies a frame of somewhere between 340 and 420 people. If the firm employs 260 managers the design is already broken, and the honest choices are to widen the population across sites, switch to a construct held in existing records, or move to a qualitative design where fifteen interviews is defensible. Doing that arithmetic in front of the reader outweighs any paragraph about why the topic matters.

Then write the literature section as an argument with a visible method. State the databases, the date window, the search terms and the inclusion rule, and report how many studies survived it, because a reader who cannot reconstruct the search cannot trust the gap. Organize by claim rather than by author: here are three things the evidence settles, here is one it does not, and the unsettled one is where the study sits.

Then cut scope until it fits one project. Three research questions usually means three studies, and a doctoral project earns its name by answering one question well enough that a practitioner could act. Write the feasibility paragraph plainly: who signs the site permission, what data already exists and who owns it, how long collection runs, and what the study becomes if the site withdraws. Sketch the ethics position here as well, because DB-FPX9802 asks the same questions in a stricter form, and a proposal that already knows whose data it touches clears that stage months earlier than one that leaves it blank.

Developing the analysis

Business evidence disagrees with itself more than proposals admit, and this criterion rewards arbitration rather than accumulation. Engagement and performance, transformational leadership and results, workforce diversity and firm outcomes: each carries meta analytic support, contested moderators and a pile of single site studies pointing sideways. Weigh the design before the number. A correlation of .21 across 900 employees at one insurer and an experimental effect in a 60 person field trial are different species of evidence.

Weigh setting as hard as statistics. Results from listed multinationals rarely transfer intact to a 90 person family firm with one HR generalist and no succession process. Attribute frameworks to the people who built them rather than to the textbook that compressed them, so Barney for the resource based view and Kotter for the change sequence, and read enough of the original to know what its author actually claimed. Where the evidence runs out, write that it runs out.

Citations that survive faculty review

A DBA proposal leans on four source types, and evaluators separate them instantly. Peer reviewed empirical articles pulled through the Capella library, mostly from the last five years by way of Business Source Complete and ABI/INFORM, carry every claim about what causes what. Seminal theory is cited to the original whatever its age, since a 1991 article is not stale when it is the thing being applied. Public data, the Bureau of Labor Statistics on separations and tenure, Census business datasets and trade association surveys, establishes magnitude and context rather than mechanism.

Consulting reports and vendor papers can describe a practice and cannot support a causal claim, label what it is and never rest the gap on it. Then run the mechanical checks a reviewer runs first: every in text citation present in the list, every reference cited in the text, DOIs where they exist, and one consistent current APA throughout, because fifteen reference errors make a reader distrust the analysis before reaching it.

The mistakes that land Basic instead of Distinguished

• A problem built from a symptom. Poor morale cannot be studied, while grievances filed per hundred employees in a named quarter can.
• A purpose promising causation a survey cannot deliver. Cross sectional data supports association, and the verb has to admit it.
• A literature review written as consecutive summaries. One paragraph per article means no synthesis happened and the gap is asserted.
• A sample that does not exist. Needing 120 respondents from a population of 260 with no access commitment fails at execution, not at review.
• A framework that appears once. Theory that never touches the instrument or the discussion is decoration.

DB-FPX9801 questions students actually ask

What makes a business problem researchable at doctoral level?

Three properties: it is unknown, it is bounded, and somebody would act on the answer. Unknown means the literature has not already settled it, which the search demonstrates. Bounded means one population, one setting and one window, so why night shift supervisors resign within their first year at four named distribution centers is workable while employee retention is a subject heading. Actionable means a decision changes once the answer exists, and the proposal should name that decision and the person who makes it. Test a candidate by writing the finding sentence in advance, because a question whose answer you cannot picture is not yet a question.

How many sources does the literature section need?

Nobody grades the count and everybody notices the composition. Forty sources of which thirty are peer reviewed empirical studies from the last five years, the rest split between seminal theory and current public data, reads as current work; a hundred references with textbooks and web pages filling half of them reads as padding. The criterion is really about coverage: every construct in your questions needs its own body of evidence, including the variables you plan to control for. Sort the list into empirical, theoretical and data before submitting, and a construct with no empirical citations behind it is exactly the hole a reviewer finds.

Can I run the project inside my own employer?

Usually yes, and the proposal has to handle three risks in writing. Access first, since permission must come from someone with authority to grant it and an encouraging manager is not always that person. Bias second, because you already believe you know the answer, so state the expectation and say how it will be kept out of the interview guide and the coding. Position third, because studying people you supervise makes volunteering less than voluntary, and the protocol in the next course will have to move recruitment to someone with no authority over participants. Naming all three matters: a reviewer who spots an insider study that never mentions insider risk returns it for that alone.

Keep going