| Course | DBA 839 Enterprise Data Complexity |
|---|---|
| Topic | Topic 7 |
| Paper type | Unmade decision trace |
| Length | About 950 words, 2 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | DBA |
| Updated | October 2026 |
Free sample paper for DBA 839 Topic 7
Three Systems Behaved as Designed: Tracing a Utility's Consent Failure Back to a Decision Nobody Was Assigned
[Author Name]
College of Doctoral Studies, Grand Canyon University
DBA-839: Enterprise Data Complexity
Topic 7 Unmade Decision Trace
[Instructor Name]
[Date]
The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.
Three Systems Behaved as Designed: Tracing a Utility's Consent Failure Back to a Decision Nobody Was Assigned
The Incident
A composite energy utility serving about 1.3 million households sent a promotional email and text campaign for a home energy audit service to about 410,000 customers. Within two days, the utility received more than 2,000 complaints, many from customers who said they had opted out of marketing, some more than once. About 23,000 of the recipients had, in fact, recorded an opt-out with the utility's call center. The incident exposed the utility to regulatory inquiry under the rules governing commercial messages and the use of customer data, and to reputational damage with customers who already distrusted their utility. This trace does not treat any statute as settled advice; it asks how the failure happened.
Where Consent Lives
Consent to marketing is recorded in three places. The billing system, the oldest, holds a marketing preference that call center staff set when a customer asks by phone; its default for new accounts is no preference recorded. The customer portal, launched four years ago, holds a communication preference set by customers online; its default is yes, with a pre-checked box at registration. The marketing platform, adopted two years ago, holds no consent of its own and reads consent from a feed.
Table 1
Where Customer Marketing Consent Is Recorded, Illustrative
| Location | How consent enters | Default | Read by marketing? |
|---|---|---|---|
| Billing system | Call center staff, by phone | No preference recorded | No |
| Customer portal | Customer online | Yes, pre-checked | Yes |
| Marketing platform | Feed from portal | Inherits portal value | Uses it |
The 23,000 customers had opted out by phone. Their opt-out sat in billing. The marketing platform read the portal, where most of them had registered with the box pre-checked or had never registered at all, and in either case appeared to have consented.
How Each Copy Came to Exist
Project records show that each copy was created by a different project, and each project team made a sound decision about its own field. The billing system's preference was added a decade ago so that call center staff could honor phone requests, and its project charter describes it as a call center field. The portal team, building self-service, needed a place for online preferences and created one, documenting the pre-checked default as a design choice to increase enrollment in outage alerts, which used the same preference. The marketing platform team, needing a consent source, chose the portal because it was the newest and best documented, and recorded that choice in its integration design.
Three Moments the Question Should Have Been Asked
None of the teams asked which record governs consent across the enterprise, and who decides. Three moments should have raised that question. The first was the portal launch, when a second consent field was created beside an existing one. The privacy office was consulted on the wording shown to customers, but not on which field would take precedence if they disagreed. The second was the marketing platform's integration, when a single source had to be chosen; the team chose on technical grounds because no one had told it the choice was not technical. The third was a data quality review two years ago, which noted that billing and portal preferences disagreed for about 6 percent of customers and logged the finding for a future project that was never funded.
Each team reasonably believed the question belonged to someone else. The portal team assumed the privacy office would raise precedence; the privacy office assumed IT would; the marketing team assumed the portal had already been reconciled. Tallon et al. (2013) argued that information needs its own governance distinct from technology governance, because decisions about meaning and use fall between the structures that govern systems.
The Unmade Decision and Its Failures
The incident has failures that are easy to name, and the utility's first instinct was to fix them one by one: a pre-checked box, a feed that read only one source and a quality finding left unfunded. Fixing each would prevent this incident from recurring in exactly this form. But each failure follows from one unmade decision, which record governs consent and who owns it, and unless that decision is made, the next system to need consent will choose a source on its own grounds again. Consent also carries particular weight with customers. Culnan and Armstrong (1999) found that customers are more willing to allow use of their information when they believe the firm follows fair procedures, and Smith et al. (2011) reviewed research showing that perceived control is central to privacy concerns. A customer who opted out and was solicited anyway has learned that the utility's procedures are not fair.
Assigning Consent to a Role
Consent should be formally designated an enterprise data element, owned by the chief privacy officer. That role holds the following decisions from now on: which record is authoritative for consent and how other records are reconciled to it; the default for any new consent field, which should be no consent until a customer gives it; which systems may read consent and from where; how an opt-out in any channel propagates to every other within one business day; and whether any campaign may proceed when sources disagree. Every project that creates, copies or reads consent must obtain that role's approval before launch.
Two immediate steps should precede the longer work. The marketing platform should suppress anyone whose billing record shows an opt-out, so that the stricter of the two sources prevails until the role decides otherwise, and the roughly 6 percent of customers whose records disagree should be contacted only to confirm their preference. Both steps cost little, and both show customers that the utility treats a refusal given by phone as binding.
References
Culnan, M. J., & Armstrong, P. K. (1999). Information privacy concerns, procedural fairness, and impersonal trust: An empirical investigation. Organization Science, 10(1), 104-115. https://doi.org/10.1287/orsc.10.1.104
Smith, H. J., Dinev, T., & Xu, H. (2011). Information privacy research: An interdisciplinary review. MIS Quarterly, 35(4), 989-1015. https://doi.org/10.2307/41409970
Tallon, P. P., Ramirez, R. V., & Short, J. E. (2013). The information artifact in IT governance: Toward a theory of information governance. Journal of Management Information Systems, 30(3), 141-178. https://doi.org/10.2753/MIS0742-1222300306
DBA 839 Topic 7 instructions, in plain terms
The Topic 7 assignment in DBA-839 asks doctoral students to trace a data failure back to its organizational origin. Strong traces describe the incident in general terms without treating any statute as settled advice, map where the data lives with its defaults and entry routes, and reconstruct from project records how each copy came to exist. Students should identify the moments when the governing question should have been raised and explain why each team reasonably thought it belonged elsewhere. The trace should separate the unmade decision from the failures it produced and assign the element to a named role with listed decisions.
How the DBA-839 Topic 7 example is put together
The finished trace starts at the complaint and works backward. Opted-out customers received offers because the marketing platform read consent from the customer portal, where a preference defaults to yes, while the opt-outs had been recorded by call center staff in the billing system. Each system was built by a different project, and each project team documented a sound decision about its own field. The trace then asks the question none of them asked: which record governs consent across the enterprise, and who decides. Working through project charters and change tickets, it finds three points where that question should have been raised, including the portal launch, where the privacy office was consulted on wording but not on precedence. The trace concludes by naming the executive role that should hold consent as an enterprise element.
Reading the DBA 839 Topic 7 rubric
Faculty reward a failure followed to a decision nobody owned. An Excellent trace maps consent across billing, the portal and the marketing platform in a table with defaults. Credit goes to reconstructing each copy from project records and naming three missed moments, including the portal launch. The rubric values Tallon and colleagues on information governance and Culnan and Armstrong and Smith and colleagues on fairness and control. Strong traces separate symptoms from the unmade decision. Top marks go to the chief privacy officer owning consent with listed decisions.
DBA 839 Topic 7 help before you submit
Traces lose the most credit when they stop at the proximate cause. A trace ending with the marketing platform reading the wrong field recommends a configuration fix and leaves the next system free to create a fourth copy. Blaming the call center staff or the portal team is a second common failure, since each acted correctly under instructions that never addressed precedence. Papers also weaken themselves by stating the utility's legal liability as fact, when privacy and marketing rules vary by jurisdiction and the course asks for organizational analysis rather than a legal opinion. Traces built from interviews alone, without the project records, rest on recollection that tends to spare the teams being interviewed. A recommendation naming a committee rather than a role reproduces the diffusion that caused the problem, the point a grader is likeliest to press.
Get a DBA-839 Topic 7 example written to your instructions
Send the DBA-839 Topic 7 instructions and the rubric posted in your classroom, with the incident or case your section assigned. We write a custom example to them, with every copy of the element mapped, project records used as evidence, the missed decision points located and ownership assigned to a role, in 24 to 48 hours. The first one is free.
More DBA 839 papers and DBA samples
- DBA 839 Topic 1: Platform Postmortem Essay
- DBA 839 Topic 2: Post-acquisition Integration Analysis
- DBA 839 Topic 3: Definition Arbitration Memo
- DBA 839 Topic 4: Data Decision Rights Matrix
- DBA 839 Topic 5: Dashboard Disagreement Dq Post
- DBA 839 Topic 6: Architecture Commitment Analysis
- DBA 839 Topic 8: Data Strategy Defense Brief
- DBA 835 Topic 7: Circularity Claim Test
- DBA 833 Topic 7: Out-of-sample Evaluation Report
- DBA 831 Topic 7: Rival Explanation Design Defense
- MGT 805 Topic 7: Divisional Redesign Proposal
DBA 839 Topic 7 questions, answered
What does it mean that nobody made the decision?
Each team made its own decisions competently, but the question spanning all of them, which consent record governs, was never assigned to anyone with authority to answer it. Every project assumed it belonged elsewhere. The example argues that unassigned questions of this kind are where enterprise data failures usually begin, and that finding one means reading project history rather than inspecting systems.
Does the example assess the utility's legal exposure?
Only in general terms. Consent and marketing rules differ across jurisdictions and change over time, so the example notes that exposure exists without stating what any regulator would conclude. Its subject is the organizational origin of the failure. The utility was invented for DBA-839 coursework, and nothing in the example is legal or regulatory advice to any reader or organization.
Why assign ownership to a role instead of a committee?
Because a committee spreads the very authority the incident shows was missing. A role can be held accountable, asked to decide within a set time and replaced if its decisions go badly. The example still gives affected functions a right to be consulted, but it places the final say on precedence and defaults with one executive, so the next conflict has somewhere definite to go.
Where can I find a free DBA 839 Topic 7 sample paper?
The decision trace is shown here complete: the incident, where consent lives, how each copy came to exist, three missed moments, the unmade decision and its failures and the role that now owns consent. Your own DBA 839 Topic 7 prompt gets a free trace.
Why fix the unmade decision instead of each failure in DBA 839 Topic 7?
The pre-checked box, the one-source feed and the unfunded finding all follow from nobody deciding which consent record governs. Until someone owns that, the next system will pick a source on its own grounds.