Measured in months, access and sign-offs, a records design and an interview design appear in this DDBA 8300 brief, which keeps the costlier interviews because only they reach the cancellation question. Searches like "ddba 8300 week 8 assignment example", "ddba8300 week 8 sample" and "ddba 8300 week 8 example" land here.
What a finished DDBA 8300 Week 8 feasibility brief looks like
A two-column price sheet takes up most of three pages. Time rows estimate months from approval to finished data: about two for the records route, closer to five for interviews, since former members must first be found. Access rows name what each route needs: a de-identified export of visits and cancellation dates from the point-of-sale vendor for one, and for the other a way to reach former members that the chain's privacy policy permits. Permission rows list sign-offs, the owner, the vendor's data agreement and the review board, with interviews of identifiable people facing fuller review. The Belmont Report's principle of respect for persons explains the recruitment plan: an opt-in invitation added to the cancellation page rather than cold calls to lapsed accounts. A verdict paragraph keeps the interviews and states the date by which enough volunteers must appear.
How a DDBA 8300 Week 8 example is structured
Question first, then the two designs that could approach it, each summarized in a sentence, so the prices that follow attach to something definite. The price sheet does the comparing. Beneath it, a paragraph examines the tempting conclusion that the records route should win because it is faster and needs lighter review. The brief refuses it: visit logs show that usage thins in the weeks before a cancellation, which is useful, but they are silent on the reasons, and the question asks for reasons. Recruitment then gets its own section, estimating how many cancellations a month the chain processes and what share might accept a follow-up call, with the estimate labeled as an assumption. The brief closes on a go or no-go date: if too few volunteers appear by then, the question narrows.
Two designs, one question
Why members cancel an unlimited plan could be approached through membership records or through conversations with people who left. Both are summarized in a sentence before any cost is counted, so the prices compare like with like.
The price sheet
Months, access routes and sign-offs, set in two columns. The records design is cheaper on every row. Laying the costs out openly is what lets the brief then argue that cheapness is not the deciding row.
The cheaper route, refused
Visit logs would show usage thinning before cancellation and the months when members leave most. The brief grants that and notes the logs cannot say whether price, crowding or a moved address drove anyone out, which is the question.
Recruitment as an estimate
An opt-in line on the cancellation page invites a short follow-up call. The brief estimates monthly cancellations and a plausible acceptance share, labels both as assumptions, and shows the months needed to reach twelve conversations.
The go or no-go date
If fewer than eight volunteers have agreed by the end of the third month, the study narrows to members who cancel at renewal. Setting the date now makes a later change a plan rather than a retreat.
Where marks go in DDBA 8300 Week 8
Specific prices earn more than general reassurance. A brief stating that access is likely and the timeline reasonable has described optimism, and graders want months, routes and named approvals they could question. The comparison counts for as much as the figures: pricing only the chosen design hides whether it was chosen because it was affordable, which the week is designed to expose. The refusal of the cheaper route shows doctoral judgment, holding the question steady while costs push against it. Recruitment estimates are judged for honesty; an assumed acceptance rate presented as a fact, or no estimate at all, weakens every date that depends on it. Ethical routing is read closely, and cold contact with former customers without a permitted channel is marked down. The go or no-go date earns credit for turning risk into a decision.
Get a DDBA 8300 Week 8 example written to your instructions
Describe the question, the two designs you are weighing, and whatever access you already have, then add the Week 8 prompt and rubric. A priced comparison with recruitment estimates and a go or no-go date comes back within 24-48h, and the first sample is free. Organizations and contacts are described by type throughout, so it can be drafted before your site has said yes.
DDBA 8300 Week 8 questions, answered
Should feasibility ever change which tradition a study uses?
It can narrow the question, and a narrowed question may then call for a different tradition, but cost alone should not pick one. The honest sequence is question first, design second, price third. If the price is unpayable, the brief says so and revises the question openly. Switching to a cheaper design while keeping the original question produces a study that answers something nobody asked.
Do de-identified records really face lighter review?
Often, though your institution's review board decides. Many boards treat analysis of existing, de-identified records as eligible for a lighter category of review, while interviews with identifiable people usually need consent procedures and fuller scrutiny. The brief should describe the expected route as an expectation, name the board that will decide, and leave time in the schedule in case the decision goes the other way.
What makes a recruitment estimate credible?
A basis in something observable and honesty about its guesses. Start from how many cancellations or customers pass a contact point each month, then apply an acceptance share labeled as an assumption. Showing what happens at half that share tells the committee how fragile the timeline is, and that serves better than a single confident figure, and it turns the estimate into a date someone can check.