Capstone coursework · concept draft · 11 September 2026

What this is. A graded assignment from my M.S. in Business Intelligence at Full Sail University, published as a portfolio item showing method. The task was to explain a Week 1 risk finding to the operational staff who would have to act on it, in an email of no more than half a page, supported by a one-page brief, at least one visualization, and an appendix of sources.

What this is not. It is not a client deliverable and not a real proposal. The email below was never sent to NVIDIA. No engagement was ever offered, discussed, or contemplated. The recipients are generic business functions, not real people. Tech Hex is an independent practice and is not affiliated with, endorsed by, sponsored by, or engaged by NVIDIA Corporation.

What it is grounded in. Every factual claim traces to a public, verifiable identifier: a bill number, a public law number, a Congressional Record page, a CBO publication number, or the company’s own quarterly release. Each of those is linked inline below, so any claim can be checked at its source rather than taken on trust. Figures are labeled observed, modeled, or hypothetical. Author: Matthew G. Williams, ORCID 0009-0000-5068-7849.

The problem the brief has to solve

My Week 1 analysis found NVIDIA’s political risk sitting inside its largest revenue line. Data center sales were $89.0 billion of $96.2 billion last quarter, which recomputes to 92.5 percent of the company (NVIDIA Corporation, 2026), and the export rule governing that line has been revised repeatedly since 2022.

Week 2 asked a harder question than what the risk is. It asked how to say it to an operational audience. Operational readers need direction, not options. So the brief is built on a four-part change structure of picture, purpose, process and part, and every section ends in something somebody owns.

The email, as drafted

Reproduced in full. This is the hypothetical artifact the assignment asked for. It was never sent.

The email runs 5.36 inches against the assignment’s half-page ceiling. Type is 11.25pt and no line exceeds 60 characters, which follows the business-email rules in Canavor, Meirowitz and Covey (2013), Truth 24.

The finding that changed the recommendation

An earlier draft recorded a Senate amendment as unverified and left it out, because the source holding that record refuses automated retrieval. Reading the primary documents changed the analysis twice.

First, the amendment was real and it failed. The same short title was offered to the fiscal 2026 defense authorization on 1 August 2025 and ordered to lie on the table (171 Cong. Rec. S5332). I searched the enacted statute in full, all 4,583,378 characters of Public Law 119-60, and the short title appears nowhere in it. The two occurrences of the phrase “remote access” there concern Department of Defense cloud systems, not export control.

Second, and more useful: there are now two bills in one committee with incompatible scopes. That is the thing an operations team actually needs to know, because it decides how much of the estate is in scope.

Two bills, two scopes, one committee

Provision	H.R. 2683, passed the House	S. 3519, same committee
Covered actor	any foreign person	foreign person of concern
Covered channel	any network connection	cloud infrastructure service only
Location	not limited	outside the United States
Trigger	use could pose a serious risk	enumerated categories only
Sunset	none	10 years from enactment
Licensing throughput	silent	report on speed of review

Under the House text the covered population is every foreign person reaching a controlled item over any network. Under the Senate text it is a designated subset reaching it through cloud infrastructure from abroad. That gap is roughly an order of magnitude in covered activity, which is why the inventory I ask for is scoped to the broader definition: a count taken to the narrower one cannot be widened later without redoing the work.

What each function would own

Function	Week	Input required
Trade Compliance	1	Source sign-off; the analyst who inherits the weekly check
Data Center Operations	2	Remote-access arrangement count, by region
Sales Operations	3	Legal review of the drafted attestation workflow
Revenue Planning	4	Decision on adopting the three-scenario interval

The scope is small deliberately. Weick defines a small win as concrete, complete, implemented and of moderate importance (Weick, 1984), and Kouzes and Posner build Challenge the Process on that definition. Four artifacts in four weeks can be finished inside a quarter. A standing monitoring program, proposed cold, cannot.

What I got wrong, and what fixed it

Two corrections are worth recording, because the method is the point of publishing this.

• A tracker is not a source. The first version cited a third-party legislative tracker for the bill’s status. Replacing it with the official bill-status record corrected the citation and surfaced the Senate companion bill, which the earlier analysis did not carry at all.
• The watch list would have missed it. My original trigger watched the committee calendar only. The amendment history shows the provision moving by a route that trigger could not see, so it now watches amendments to moving vehicles as well. A monitor is only as good as the failure mode it anticipates.

What remains open

No probability is attached to any legislative outcome, because no source I read publishes one. Whether Senate Banking reports either bill, and in whose scope, is unknowable from the record and is deliberately left unmodeled. The central estimate the brief asks for, the remote-access share of data center revenue, cannot be produced from outside the company at all. That is the honest limit of an analysis built on public disclosure, and naming it is more useful than filling it with a number.

---

Sources

Every entry links to the document itself.

• 171 Cong. Rec. S5332 (daily ed. Aug. 1, 2025) (amendment SA 3567 to S. 2296). GovInfo
• Canavor, N., Meirowitz, C., & Covey, S. R. (2013). Learn good business writing and communication. Pearson. Truth 24.
• Congressional Budget Office. (2025, April 30). H.R. 2683, Remote Access Security Act: Cost estimate. cbo.gov/publication/61369
• Kouzes, J. M., & Posner, B. Z. (2012). The leadership challenge (5th ed.). Jossey-Bass.
• National Defense Authorization Act for Fiscal Year 2026, Pub. L. No. 119-60, 139 Stat. 717 (2025). GovInfo
• NVIDIA Corporation. (2026, August 27). Financial results for second quarter fiscal 2027. NVIDIA Newsroom
• Remote Access Security Act, H.R. 2683, 119th Cong. (2026). Bill text, PDF
• Remote Access Security Act, S. 3519, 119th Cong. (2025). Bill text, PDF
• U.S. Government Publishing Office. (2026). Bill status for H.R. 2683 and S. 3519, 119th Congress [Data sets]. GovInfo bulk data
• Weick, K. E. (1984). Small wins. American Psychologist, 39(1), 40–49. doi.org/10.1037/0003-066X.39.1.40

© 2026 Matthew G. Williams · Tech Hex · ORCID 0009-0000-5068-7849. Published as a portfolio item from graduate coursework in the M.S. Business Intelligence program at Full Sail University. The proposal reproduced here is hypothetical and was never sent.