| Course | DBAX 9104C Business Consulting Research Project Stage 4 |
|---|---|
| Week | Week 8 |
| Paper type | Disclosure decisions |
| Length | About 810 words, 5 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | Doctor of Business Administration (DBA) |
| Updated | October 2026 |
Free sample paper for DBAX 9104C Week 8
State It, Generalize It or Drop It: Disclosure Decisions for a Consulting Study of a Single-Office Structural Engineering Firm, Where a Few True Details Would Name the Firm and Its Principals
Student Name
Walden University
DBAX 9104C: Business Consulting Research Project Stage 4
Instructor Name
Month Day, Year
State It, Generalize It or Drop It: Disclosure Decisions for a Consulting Study of a Single-Office Structural Engineering Firm, Where a Few True Details Would Name the Firm and Its Principals
The Problem With True Details
A small firm can be recognized from a handful of true details. My consulting study examined why a single-office structural engineering firm was losing design work on mid-size commercial projects to larger competitors. The firm has 23 employees, three principals and one specialty that is unusual in its region. Anyone in the regional building industry who read "a 23-person structural firm in a mid-sized Southern city founded in 1994 that specializes in parking structures" would know which firm it is, and from there which principal said what. Kaiser (2009) calls this deductive disclosure: identifying participants from details that seem harmless one at a time. This document decides, for each identifying detail, what the published study may state and what the client report may say, and records the reason.
Two Readers, Two Needs
The published study will sit in the university's repository, readable by anyone, including competitors and clients of the firm. The client report goes only to the three principals. The principals already know who they are and who said what, so the client report can say more about the firm itself; but it must still protect employees and the principals from each other where a remark was made in confidence. Tolich (2004) distinguishes external confidentiality, protecting participants from outsiders, from internal confidentiality, protecting them from others inside the same setting who can recognize them. Both matter here.
The Decisions
Table 1
Identifying Details and Disclosure Decisions
| Detail | Published study | Client report | Reason | |
|---|---|---|---|
| Specialty in parking structures | Generalized to "structural engineering for commercial buildings" | Stated | Specialty identifies the firm regionally; principals know it | |
| City | Generalized to "a mid-sized metropolitan area in the Southeast" | Stated | City plus specialty would identify the firm | |
| Headcount (23) | Range: "20 to 30 employees" | Stated | Exact count narrows the field | |
| Founding year (1994) | Dropped | Dropped | Adds nothing to findings | |
| Two named projects, a hospital garage and a mixed-use podium | Dropped | Dropped | Projects are public and identify the firm; findings rest on bid records, not these projects | |
| Quotations from principals | Shortened; attributed by role | Shortened; attributed by role | Principals asked not to be quoted to each other | |
| The principal with the only marketing role | Attributed as "a firm leader" | Attributed as "a firm leader" | A role held by one person names that person | |
| Finding about a disagreement between two principals over pursuing public work | Stated as "leaders disagreed about pursuing public-sector work" | Stated the same way | Finding needed; who held which view is not | |
Decisions agreed with the principals in a meeting on September 18.
Detail by Detail
The specialty was the hardest call. Parking structures matter to the findings: the firm's competitors for that work are national firms with in-house parking divisions, which explains part of why bids were lost. Dropping the specialty from the published study removes that context. The compromise is to keep the finding, that the firm competes against much larger specialist divisions, without naming the specialty. A reader loses some precision; the firm is not identified.
The two named projects were dropped from both documents. They were vivid examples of lost bids, but the findings rest on 64 bid records over four years, not on any two projects. Saunders et al. (2015) argue that anonymization requires weighing what each detail adds to the findings against the risk it creates; these projects added color, not evidence.
The disagreement between principals is the most sensitive finding. Two principals favored bidding for public-sector work, which pays slowly but steadily; one opposed it. The disagreement explains why the firm had not diversified. It must be reported, because it bears on the research question. But stating who held which view would expose a confidence, since each principal spoke to me separately. Both documents state the disagreement and not the positions.
Where Disguise Would Change the Finding
One detail could not be disguised without changing a finding. The firm's size matters: the study found that clients on mid-size projects increasingly prefer firms that can provide structural, civil and mechanical services together, which a 20 to 30 person firm cannot. Changing the size to disguise the firm would change the finding. The range "20 to 30 employees" keeps the finding true while widening the field of firms it could describe.
Review by the Firm
The principals reviewed the decision table, not the findings. They asked for one change: that the founding year be dropped from the client report too, since it would appear in any version that circulated beyond them. That request was accepted. They did not review or change any finding, which keeps the decisions about disclosure separate from decisions about content.
References
Kaiser, K. (2009). Protecting respondent confidentiality in qualitative research. Qualitative Health Research, 19(11), 1632-1641. https://doi.org/10.1177/1049732309350879
Saunders, B., Kitzinger, J., & Kitzinger, C. (2015). Anonymising interview data: Challenges and compromise in practice. Qualitative Research, 15(5), 616-632. https://doi.org/10.1177/1468794114550439
Tolich, M. (2004). Internal confidentiality: When confidentiality assurances fail relational informants. Qualitative Sociology, 27(1), 101-106. https://doi.org/10.1023/B:QUAS.0000015546.20441.4a
DBAX 9104C Week 8 instructions, in plain terms
This week asks you to decide, detail by detail, what your published study and your client report may say about the organization and its people. List every detail that could identify the organization or an individual: specialty, location, size, history, named projects, quotations, roles held by one person and sensitive findings about individuals. For each, decide whether the published study states, generalizes or drops it, and decide separately for the client report. Give the reason for each decision. Explain the hardest cases in prose, especially where disguising a detail would change a finding. Distinguish protection from outsiders from protection between people inside the organization. Report what the organization reviewed and whether it changed any decision.
How the DBAX 9104C Week 8 example is put together
The document begins with deductive disclosure in Kaiser's sense and describes the firm. A section separates the two readers, the public repository and the three principals, using Tolich's distinction between external and internal confidentiality. The eight-row table follows. Prose explains the hard calls: the specialty is generalized but the finding that the firm competes with larger specialist divisions stays; two public projects are dropped because the findings rest on 64 bid records, as Saunders and colleagues' weighing of detail against risk suggests; and a disagreement over public-sector work is reported without saying who held which view. A section explains why firm size became a range rather than a disguise. The principals reviewed only the decision table and asked that the founding year be dropped everywhere.
Reading the DBAX 9104C Week 8 rubric
The table carries most of the credit when it covers more than names: graders look for size, location, specialty, roles held by one person and sensitive findings. Separate decisions for the published study and the client report show the writer understands that the two readers know different things. Reasons should be specific, not a repeated "to protect confidentiality." Instructors reward honest treatment of cases where disguise would alter a finding, since that is where judgment is tested. Internal confidentiality, protecting people from colleagues and from each other, earns credit when it is applied to a real case such as a disagreement. Limiting the client's review to disclosure rather than findings shows independence. Sources on confidentiality in qualitative research should be applied, not just cited.
Common DBAX 9104C Week 8 mistakes, and how to avoid them
Most students list names and job titles and stop. Write a short description of the organization as an industry insider would recognize it, then underline every detail in it; those are your rows. Ask of each detail whether a finding depends on it. If not, drop or generalize it. If it does, find the most general form that keeps the finding true, such as a size range. Remember that people inside the organization can recognize each other from roles and opinions, so report disagreements without positions where they were shared in confidence. Let the organization review your decisions, not your findings. If you are unsure whether a detail identifies anyone, a tutor can read your description as an outsider would.
Get a DBAX 9104C Week 8 example written to your instructions
Paste the Week 8 prompt and rubric and list, in general terms, the kinds of detail your study holds about the organization. A decision table covering both documents returns within 24-48h, free the first time. It is built for an invented engineering firm, so no identifying fact about your client ever reaches the desk.
More DBAX 9104C papers and DBA samples
- DBAX 9104C Week 1: Two-Audience Discussion
- DBAX 9104C Week 2: Coherence Read Log
- DBAX 9104C Week 3: Two-Language Restatement
- DBAX 9104C Week 4: Recommendation Trace
- DBAX 9104C Week 5: Recommendation Cut Record
- DBAX 9104C Week 6: Evidence and Action Split
- DBAX 9104C Week 7: Client Deliverable Memo
- DBAX 9104C Week 9: Independence Rehearsal
- DBAX 9104C Week 10: Two Contribution Statements
- DBAX 9104C Week 11: Final Reconciliation Record
- DBAX 9104 Week 8: Contribution Sentence Drafts
- DBAX 9103C Week 8: Unwelcome Findings Paper
- DBAX 9103 Week 8: Results Number Audit
- DBAX 9102C Week 8: Study Feasibility Section
DBAX 9104C Week 8 questions, answered
Where can I find a free DBAX 9104C Week 8 sample paper?
The decision table and the explanation of each hard case are reproduced in full on this page, readable by anyone without paying.
What firm does the DBAX 9104C Week 8 document concern?
A 23-person single-office structural engineering firm with three principals and a regional specialty in parking structures.
How is the firm's specialty handled in the published study?
It is generalized to structural engineering for commercial buildings, while the finding about competing with larger specialist divisions stays.
How is the disagreement between principals reported?
As a disagreement about pursuing public-sector work, without saying which principal held which view.
What did the principals review?
Only the decision table; they asked that the founding year be dropped from the client report too, and did not see the findings.