A problem statement about discretionary price overrides, a purpose statement derived from it phrase by phrase and a trace table joining the two make up GB730's Unit 2 memo. Searches like "gb 730 unit 2 assignment example", "gb730 unit 2 sample" and "gb730 unit 2 example" land here.
What a finished GB730 Unit 2 problem and purpose memo looks like
Three parts fill four pages. Part one is the problem, about 300 words at two levels: a broad problem, that distributors adopting price recommendation software often see sales staff override its prices without evidence on whether overrides win or lose value, and a specific problem, that some sales leaders at industrial distributors lack evidence on how override decisions relate to quote conversion and margin. Evidence carries both levels, from price waterfall research on leakage between list and pocket price, through studies of delegating pricing authority to salespeople, to Merritt's own [37] percent override rate. Part two is the purpose statement, a single paragraph naming design, population, variables and setting. Part three is a trace table matching every element of the purpose to the problem phrase that required it.
How a GB730 Unit 2 example is structured
The memo is organized around one demand: the problem must produce the purpose rather than merely precede it. Every noun in the purpose statement must appear, or be clearly implied, in the problem, whether sales leaders, industrial distributors, override decisions, conversion or margin. The trace table makes that demand checkable. The memo also shows its own revision. The first draft problem claimed that overrides erode margin, which presupposed an answer; the revision states that the relationship is unknown and that both directions have support, since delegation research finds salespeople sometimes hold customer information software lacks. The purpose then commits to an explanatory sequential mixed methods design, examining associations in quote records first and explaining them through interviews second, and the memo argues that the commitment follows from a problem with two unknowns: what happens, and why.
A problem that presupposes nothing
The revised statement treats the effect of overrides as unknown. Research pointing both ways, including studies where delegated pricing authority raised performance under some market conditions and lowered it under others, justifies that neutrality.
Evidence at three levels
Industry work on price leakage, scholarly research on pricing delegation and Merritt's internal figures each support a different part of the problem. The memo labels which source does which job, so none is asked to carry weight it cannot.
The purpose, element by element
Design, population, phenomenon, variables and setting each appear once, in a fixed order. Nothing enters the purpose statement that the problem statement did not first make necessary.
The trace table
Twelve rows match purpose phrases to problem phrases. Two rows were empty in the first draft, which is how the missing population and the presupposed answer were found and repaired.
What the memo leaves for later
Research questions, instruments and sample size belong to later units. The memo marks where each will attach, so the chain can continue without reopening the problem statement every time.
Where marks go in GB730 Unit 2
A problem that already contains its answer is the defect GB730 instructors return most often in Unit 2, since stating that overrides erode margin leaves nothing to study. Alignment is checked literally: a population, variable or setting named in the purpose but absent from the problem signals that the purpose was written first. Evidence should be current and scholarly for the broad problem and organizational for the specific one, each source doing a stated job. Purpose statements that list several designs, or name a design without saying what it will do with which data, are sent back. Precision about population matters, because sales leaders and sales representatives are different people with different stakes. A visible trace, whether table or annotation, shows that the chain holds instead of asking the reader to trust it.
Get a GB730 Unit 2 example written to your instructions
Share the topic, any problem and purpose drafts that exist and the Unit 2 memo guidance with its rubric. A custom memo, ready within 24-48h, pairs a problem that presupposes no answer with a purpose derived from it, element by element, alongside a trace table proving the match. No payment is asked for the first.
GB730 Unit 2 questions, answered
How long should a GB730 problem statement be?
Usually 250 to 400 words, though sections vary. Length matters less than containing the parts: the problem itself, evidence at scholarly and organizational levels, what is unknown and why it matters. A problem statement running to several pages is usually a literature review in disguise, and instructors tend to ask for it to be cut back.
Can the purpose statement change later?
Yes, and it usually does, but every change has to travel through the chain. If the design shifts from mixed to quantitative in Unit 4, the purpose statement and research questions change with it. Keeping the trace table current makes those revisions visible rather than leaving mismatches for a committee to discover at proposal.
Does the problem need a gap in the literature?
Applied doctorates often frame the problem around a business need, with the literature showing what is known and unknown. A gap statement helps, but it should follow from the business problem rather than replace it. Saying nobody has studied this exact firm is not a gap; saying research has not examined overrides of algorithmic price guidance is.