DBA 839 Topic 5 dashboard disagreement dq post example

Enterprise Data Complexity Grand Canyon University Free custom sample in 24 to 48h

This DBA 839 Topic 5 sample paper explains, through a main post and one reply, why a composite software company's two churn dashboards disagree while both are correct. It belongs to GCU DBA 839, Enterprise Data Complexity, listed as DBA-839, a requirement of the Grand Canyon University DBA. Customer success counts accounts at notice, 2.1 percent; finance counts net revenue at contract end, 3.4 percent. An illustrative quarter of 2,000 accounts and 40 million dollars shows the gap. Wang and Strong's fitness for use, Weill and Ross on decision rights and Khatri and Brown on data owners frame the unmade decision, and a third dashboard is rejected.

CourseDBA 839 Enterprise Data Complexity
TopicTopic 5
Paper typeDashboard disagreement DQ post
LengthAbout 410 words, 1 pages
FormatDiscussion post, APA 7 citations
SchoolGrand Canyon University (GCU)
ProgramDBA
UpdatedOctober 2026

Free sample paper for DBA 839 Topic 5

1

Topic 5 DQ 1: Initial Post and Reply

Two Churn Figures, Both Correct: The Decision Nobody Has Made

Initial Post

At a composite software company I am using for this question, the customer success dashboard reported 2.1 percent churn for the last quarter, and the finance dashboard reported 3.4 percent for the same quarter. Executives assume one must contain an error. I think neither does.

The gap comes from two choices. The first is timing: customer success records a loss when a cancellation notice arrives, while finance records it when the contract actually ends, often a quarter or two later. The second is the unit of count: customer success counts accounts, so a large customer and a small one weigh the same, while finance counts recurring revenue, net of upgrades from customers who stayed.

An illustrative quarter shows how far apart these can drift. Suppose the company has 2,000 accounts and 40 million dollars in annual recurring revenue. Forty-two small accounts give notice, 2.1 percent of accounts. Meanwhile two large customers whose notices arrived last quarter reach the end of their contracts, taking 1.6 million dollars, and existing customers upgrade by 0.24 million. Finance reports revenue churn of 1.36 million, 3.4 percent. Both figures are right; they answer different questions. Wang and Strong (1996) judged data by how well it serves the people using it, and by that test each figure serves its own team.

Account churn at notice is the better early warning for the retention team, since it arrives sooner and treats every customer as worth saving. Net revenue churn at contract end is the better measure for the board, since it shows what the business actually lost. The company has never said which measure governs which decision. Weill and Ross (2004) argued that governance is about assigning decision rights and accountability, and Khatri and Brown (2010) applied the same idea to data, giving each shared definition an owner able to rule on it. Churn has no such owner here, so each team keeps its own and the executive meeting argues.

The real question, I think, is not which dashboard is wrong but who decides which measure the board sees.

Reply to Elena

Elena, you suggest a third, reconciled dashboard. I understand the appeal, but it would add a third figure without settling which one governs anything, and next quarter someone would ask why it differs from the other two. Would assigning an owner who decides which measure goes where do more than a new view of the same disagreement?

References

Khatri, V., & Brown, C. V. (2010). Designing data governance. Communications of the ACM, 53(1), 148-152. https://doi.org/10.1145/1629175.1629210

Wang, R. Y., & Strong, D. M. (1996). Beyond accuracy: What data quality means to data consumers. Journal of Management Information Systems, 12(4), 5-33. https://doi.org/10.1080/07421222.1996.11518099

Weill, P., & Ross, J. W. (2004). IT governance: How top performers manage IT decision rights for superior results. Harvard Business School Press.

The DBA-839 Topic 5 assignment instructions

The Topic 5 discussion in DBA-839 asks doctoral students why dashboards built from the same data disagree. Strong posts reject the assumption that one figure must be wrong, then decompose the gap into the specific choices behind each measure, such as when an event is recognized and what unit is counted. Students should illustrate the gap with numbers, explain which decision each measure suits and argue from the governance literature that shared definitions need an owner with authority to rule. The reply should test a classmate's proposed fix by asking whether it would produce a decision or only another figure.

Inside the DBA 839 Topic 5 example

The finished post opens by stating the disagreement plainly: the customer success dashboard shows lower churn than the finance dashboard for the same quarter. It then decomposes the gap in two moves. Customer success records a loss when a cancellation notice arrives and counts accounts, so a large customer and a small one weigh the same. Finance records the loss when the contract ends and counts recurring revenue, net of upgrades from customers who stayed. Once those two choices are visible, the figures stop contradicting each other and start answering different questions. The post argues that neither dashboard is faulty and that the executive team has never said which measure governs the board report and which governs the retention team's targets. It closes by putting that unmade decision to classmates as the real subject of the question.

Where the marks sit in the DBA 839 Topic 5 rubric

Faculty reward a disagreement decomposed, not blamed. An Excellent post splits the gap into timing, notice against contract end, and unit, accounts against net revenue. Credit goes to an illustrative quarter producing 2.1 and 3.4 percent from the same events. The rubric values matching account churn to retention and revenue churn to the board, with Wang and Strong on fitness for use. Strong posts cite Weill and Ross and Khatri and Brown on owners for shared definitions. Top marks go to a reply rejecting a reconciled third dashboard.

DBA 839 Topic 5 help: mistakes that cost marks

The commonest weakness in posts on this question is hunting for the bug. A response attributing the gap to a join error or a stale extract answers a question the case does not raise, since both queries are sound. Some posts correctly identify the two definitions and then declare one of them the true churn, which turns a governance question into a matter of taste. Others stop at description and never say which decision each measure should serve, leaving the executive team exactly where it began. A doctoral post is expected to rest its central claim on at least one source, and posts built on personal experience alone read as practitioner commentary. Replies that merely agree with a classmate earn little, whereas one that tests a proposed fix against the diagnosis shows the reasoning a doctoral discussion rewards.

Get a DBA-839 Topic 5 example written to your instructions

Send the DBA-839 Topic 5 discussion prompt and the rubric from your classroom, with any readings the question names. We write a custom example to them, with the disagreement decomposed into timing and unit of count, each measure matched to a decision and a substantive reply included, in 24 to 48 hours. The first one is free.

More DBA 839 papers and DBA samples

DBA 839 Topic 5 questions, answered

Why would two correct dashboards show different churn?

Because churn is a family of measures rather than one. Teams choose when to recognize a loss, at notice or at contract end, and what to count, accounts or revenue, and each choice suits a different purpose. Two dashboards making different choices will disagree every period while both remain accurate. The example reads the gap as a difference in definition rather than as a defect.

Should the company build one reconciled churn dashboard?

The example argues against it. A blended figure matches neither team's working definition, so both would keep their own dashboards and the company would have three numbers instead of two. What the company lacks is a rule stating which measure governs which decision and who holds authority to alter a definition. Once that rule exists, two dashboards can coexist without a quarterly argument.

Does a DQ post at this level need citations?

In most doctoral sections the rubric expects the central claim to rest on a source, and the example cites the data governance literature for the idea that definitions need an owner with authority to settle them. Requirements vary by section and instructor, so the rubric in your classroom is the guide. The software company in the post was invented for coursework.

Where can I find a free DBA 839 Topic 5 sample paper?

All of the discussion is on this page: an opening post decomposing two churn figures and naming the unmade decision, plus a response to a classmate. Share your DBA 839 Topic 5 prompt for a free post.

How can churn be 2.1 and 3.4 percent at once in DBA 839 Topic 5?

Forty-two small accounts gave notice, 2.1 percent of 2,000. Separately, two large contracts ended, taking 1.6 million dollars, offset by 0.24 million in upgrades, which is 3.4 percent of 40 million in revenue.