My CFO Replaced Me With Her Niece... So I Filed One Memo and Killed Their $52M NASA Portfolio

Added: 2026-05-28

[00:00:00]Welcome. Sit back, relax, and enjoy content that's made to be smooth, simple, and enjoyable. If that's your style, subscribe, and stay a while.

[00:00:09]Email arrived at 6:47 on a Tuesday morning while I was still drinking my first cup of coffee and watching the sprinklers cycle across the lawn. The subject line read, "Organizational refresh. Welcome aboard, Skyler." I read it twice before I understood what I was looking at. My new boss, effective immediately, was a 26-year-old woman I had never heard of who had spent the last 18 months running social media campaigns for a luxury watch brand in Miami. And the CFO who had hired her without consulting me, without consulting the program managers, without consulting anyone who actually understood what we did, was the same woman who 3 months earlier had told me at the company holiday dinner that I was, and I quote, the institutional backbone of this firm. That institutional backbone had just been demoted in writing before I'd finished my coffee. I want to tell you upfront that I don't consider myself a vengeful man. I served 12 years in the Navy before I ever stepped into a private sector job. My father was a machinist in Toledo who used to say that bitterness rusts you faster than salt water. I believed him. I still do. But there is a difference between bitterness and arithmetic. And what happened over the next 11 weeks was more than anything else an arithmetic problem. They didn't understand the numbers. I did. And when you don't understand the numbers in our industry, the numbers eventually understand you. My name doesn't matter for the purposes of this story. What matters is that I was the director of mission assurance at a midsize aerospace systems integrator based outside Huntsville, Alabama. We held four active prime contracts with NASA Marshall Space Flight Center and two subcontract roles supporting Northrup on a classified satellite program. Total annualized contract value across all six instruments, $83 million.

[00:01:57]I was designated key personnel on every single one of them. My ITAR registration, my DD2345 militarily critical technical data agreement, my export control certifications, and my top secret clearance with SEI eligibility had been continuously maintained since I was 24 years old. If you want to understand what that means in practical terms, the government had been quietly investigating, vetting, and revetting me for nearly three decades. That is not a credential you replace with a LinkedIn profile. The woman who decided to replace me anyway was our new CFO, Deianne. She'd been brought in 6 months earlier by the founder's son, Royce, who had inherited the chairman's seed after his father retired. Royce was 41 years old and had a master's in finance from a school I'd never heard of. He liked to talk about disruption and agility and breaking up entrenched silos. Diane was his chosen instrument. She wore expensive shoes, used the word synergy without irony, and had never, as far as I could tell, set foot inside a class 100,000 clean room. Skylar was Diane's niece, her sister's daughter. I learned this not from Diane, who never disclosed it, and not from Royce, who I believe genuinely didn't know, but from our payroll administrator, a quiet woman named Kareem, who had been with the company since 1991, and who pulled me aside in the breakroom one afternoon with an expression I can only describe as Bruno. "I shouldn't be telling you this," she said, "but you should know who you're working for now." The next morning, I drove to the office an hour early and pulled the personnel files I was authorized to access as a senior officer of the company. Skyler's listed qualifications. A bachelor's in communications from a state university in Florida. A certificate in digital innovation leadership from a six-week online program. 18 months at the watch company. No security clearance of any kind. No ITAR familiarization training.

[00:03:55]No ITAR familiarization training. No export control history. No background investigation on file with DCSA.

[00:04:03]Nothing. And this woman was now, according to the org chart Diane had circulated, the senior vice president of program operations, my boss, the person who would be signing off on my contract deliverables, my technical interchange meeting minutes, my CDRL submissions, and when CDRL submissions, and this is the part that made me actually laugh out loud at my desk, my export controlled communications with NASA Marshall. I want you to understand something about how government work actually functions because the people in this story did not. When NASA awards a contract that touches export control technology, the agency does not award it to the company.

[00:04:41]They award it to a specific configuration of people. The proposal we submitted contained rums. Those résumés were evaluated. The technical authority of each named individual was weighed, scored, and recorded. The contract was awarded in part because the government concluded that those specific human beings with those specific clearances and qualifications would be performing those specific tasks. If you change the people, you change the contract. There is no version of this where you don't.

[00:05:11]The relevant clause is FAR 52215201 and it requires advanced written notification to the contracting officer before any substitution of key personnel with a detailed justification and resume of the proposed substitute for DT justification and resume of the proposed substitute for DTRs 2521579 layers on additional requirements for our classified subcontract the NIS pawn chapter 2 personnel security requirements applied and for any export control technical data which our work absolutely involved. The ITAR part 122 registration of the company itself could be jeopardized by an unauthorized personnel change. I had spent 26 years learning these rules. Skyler had spent 6 weeks learning to write Instagram captions. Royce thought this was a fair trade. The Anne thought she was being clever. The first sign that things were about to get interesting came in my new boss's introductory meeting, which she held in our largest conference room on a Thursday afternoon. Skyler wore a cream colored suit and had clearly rehearsed her opening remarks. She spoke about her vision for modernizing legacy workflows and introducing agile methodologies to our engagement model. She used a slide deck with a lot of gradient backgrounds.

[00:06:29]At one point, she referred to our clean room as the lab. At another point, she pronounced it as a word itar instead of spelling out the letters, which is what every actual practitioner in this industry does. I sat in the back row next to my deputy, a former Air Force major named Rosalind, who had transitioned to civilian life four years earlier. Rosalind leaned over and whispered, "She thinks Houston is where we work." "I know," I said. She just said, "Our biggest customer is in Houston." "I know. Marshall is in Alabama. Rosland. I know. After the meeting, Skylar asked to speak with me privately in what had until that morning been my office. The Anne had reassigned me to a smaller windowless room down the hall, a temporary transition space, while Skyler moved her things into mine.

[00:07:17]I noticed she had brought a small succulent and a framed photograph of herself in a sequin dress at what looked like a Miami nightclub. She placed the photograph on the credenza next to my old NASA Group Achievement Award. So, she said, settling into the chair behind my old desk. I wanted to touch base about roles and responsibilities going forward. I waited. I've been reviewing the OR chart, she continued. And honestly, I think there's a lot of redundancy in your current portfolio.

[00:07:47]Like, you're listed as the technical point of contact on four contracts, plus you're the facility security officer, plus you're the export control liaison, plus you're the program executive.

[00:07:58]That's a lot. It is. I agreed. So, I'm thinking we streamline. I'd like to take over the customerf facing program executive role on the two larger NASA contracts. That'll free you up to focus on the more administrative compliance stuff, the paperwork side. I looked at her for a long moment. I could see very clearly what was happening. She was going to take the visible prestigious work, the meetings with NASA leadership, the program reviews, the presentations to the customer, and leave me with the unglamorous regulatory plumbing. Royce and Deianne would point to her name on the contracts at the next board meeting and call it transformation. And in 6 months, when she had a rolodex and a portfolio, they would quietly let me go.

[00:08:42]That was the plan. It was a perfectly reasonable plan from their perspective.

[00:08:46]The only problem was that it was illegal. "That sounds great," I said.

[00:08:50]"Why don't we set up a meeting next week to walk through the contract requirements together so you understand what you'll be signing off on?" She smiled. "Sounds good. Can you put something on my calendar?" "Absolutely," I said. I walked back to my new windowless office, closed the door, and sat down at my desk. Then I opened a fresh notebook, paper, not digital, because some things you don't want a metadata trail on, and started writing down dates, the dates when Skylar's name had appeared in internal communications, the dates when the or chart had been updated, the date of the all hands meeting, the date Diane had circulated the personnel announcement. I wrote them all down in chronological order. Then I went home that night, made dinner for my wife, helped my son with his algebra homework, watched a baseball game with my father-in-law who lives with us since his stroke, and slept eight straight hours for the first time in a month.

[00:09:47]Because here is what they didn't understand. When you designate someone as key personnel on a federal contract and then you remove that person from their designated responsibilities without notifying the contracting officer, you are not engaging in routine corporate restructuring. You are committing a contract violation. If the substituted personnel does not hold the required clearances, you are committing a security violation. If export control technical data passes through that person's hands without proper authorization, you are committing a federal crime. The penalties are not subtle. ITAR violations can run up to $1 million per occurrence and 20 years of imprisonment. Suspension and debarment from federal contracting can follow.

[00:10:31]Companies have died over less. Diane didn't know this. Royce didn't know this. Skyler genuinely had no idea. And I was not under any obligation required to tell them what I was required to do by law by my clearance obligations by the terms of my DD2345 by the standard practice of every facility security officer in the country was to notify the appropriate authorities when a security relevant event occurred at my company and the unauthorized removal of designated key personnel from their contract responsibilities combined with the placement of unclearared personnel in positions of authority over export controlled material. was very very much a security relevant event. I spent the next 4 days documenting, not in a frenzy, not in anger. Methodically, the way you build a case file when you've done it for 30 years. I pulled contract numbers. I cross- referenced clause requirements. I made a clean log of every meeting Skyler had been included in where export controlled material had been discussed in her presence. I noted with timestamps the moments when I had personally observed her viewing CUI mark documents on her monitor without the appropriate need to know justification on file. I saved emails. I saved teams messages. I saved her introductory slide deck in which she had clearly described her intent to assume technical authority over contracts on which she held no clearance and no contractually approved role. On Tuesday of the following week, I had the meeting with Skylar to walk through contract requirements. She showed up 10 minutes late with an iced coffee. I had prepared a binder for her with tabs. I walked her through the FAR clauses, the DEFER supplements, the ITAR registration requirements, the NICE palm personnel security requirements, the CMMC controls, and the specific key personnel substitution procedures she would need to initiate before assuming any of the customer-f facing roles she had described. She blinked at me. Wait, I need to do all that just to be on a customer call. To be on a customer call where export controlled technical data is discussed. Yes. What if it's a general meeting? All of our customer meetings touch export controlled material at some level. We design components that fall under USML category 15. What's that? Spacecraft systems and associated equipment. She stared at me, but like even just on a kickoff call.

[00:12:55]Even then, the kickoff call typically includes a review of technical baselines.

[00:13:00]Okay, she said slowly. But in my last job, in your last job, I said gently, you sold watches. She didn't respond to that. After a moment, she said she'd loop in Diane and left the meeting. The binder remained on the table. I picked it up and took it back to my office. The next morning, I was copied accidentally, I'm sure, on an email chain between Diane and Royce. The subject line was workaround. In the chain, Diane explained that according to me, the regulatory stuff is going to take months. She proposed that they front Skyler as the senior executive on the contracts for customer optics while having me continue handling the compliance side quietly in the background. Royce responded with a single line, "Just make it work. We need to show the board momentum." I read that email three times. Then I forwarded it to my personal email, printed two copies, blocked one in my home safe, and put the other in a folder in my office that no one but me had the combination to. That was Wednesday morning. By Thursday afternoon, I had drafted a formal memorandum to our company's general counsel with copies to the chairman of the board and the audit committee chair outlining what I described as a potential compliance exposure related to recent organizational changes. I used careful neutral language. I did not editorialize. I attached redacted excerpts of the relevant federal regulations and contract clauses. I recommended that the company immediately submit a key personnel substitution request to all affected contracting officers with full disclosure of Skyler's qualifications. I noted that failure to do so could be construed as a material misrepresentation under the False Claims Act. I sent the memo at 4:37 on a Friday afternoon. Then I went home and grilled steaks for my family.

[00:14:49]My son asked me why I seemed in such a good mood. I told him I had just done something I should have done a long time ago, which was to write everything down.

[00:14:58]Monday morning at 84 a.m., my office phone rang. It was the general counsel, a man named Boyd, who had been with the company since the founders era, and who had personally counseledled three different DCSA inspections during his tenure. Boyd's voice was calm, but there was an edge to it. I had heard before in his discussions of other people's careers. I got your memorandum, he said.

[00:15:21]Yes. Where is Royce? I don't know. I assume in his office. Don't assume anything. Are you in the building? Yes.

[00:15:30]Do not leave. Do not speak to Diane. Do not speak to Skyler. Do not respond to any emails about this matter from anyone other than me. I'm calling an emergency meeting of the audit committee for 240 p.m. I'm also placing a call to outside counsel. Sit tight. I sat tight. At 2:14 p.m. PM, I was summoned to the boardroom. Boyd was there. The audit committee chair, a retired Air Force two star named Halverson was there. Two outside attorneys from a Washington firm I recognized were on the speaker phone.

[00:16:06]Royce was there looking pale. Diane was there looking furious. Skyler was not there. Halverson opened by asking me to walk through the timeline. I did calmly in order with reference to my binder. I did not raise my voice. I did not craze my voice. I did not characterize anyone's motives. I simply laid out what had happened, what regulations applied, and what the company's exposure was.

[00:16:32]When I finished, there was a long silence. Then Halverson turned to Royce and said, "Son, do you have any idea what you've done?" Royce started to speak. Halverson cut him off. You moved an uncleared person into a position of authority over four NASA contracts and a classified subcontract without notifying the contracting officers without conducting a personnel security review and apparently without consulting the one man in this entire company whose name is on every relevant export license. Is that an accurate summary?

[00:17:04]Royce looked at Diane. Diane looked at the floor.

[00:17:08]That is not an accurate summary, Diane said. We did not transfer any authority.

[00:17:14]Skyler was an internal title only. I cleared my throat. Halverson nodded at me to speak. Deianne, I said, your direct email to the program managers on the Marshall 3 contract dated the 14th identified Skyler as the primary technical point of contact going forward. I have the email. I also have the calendar invite for her introductory call with the NASA program executive on the 22nd, which was cancelled only because the executive himself emailed me to ask who Skyler was. Deianne went very still.

[00:17:47]He emailed you? Halverson said, "Yes, sir. The NASA program executive emailed me on the 16th to ask why an uncleared individual was being introduced as the technical lead. I told him the matter was under review and that I would follow up. I did not follow up because I wanted to first complete my documentation.

[00:18:06]Harrisonson took off his glasses and set them on the table. He looked at Royce.

[00:18:11]NASA noticed before the board did, he said. Do you understand what that means?

[00:18:16]It meant, although Halverson didn't spell it out, that the federal customer had already flagged the issue. It meant that whatever the company did next, the contracting officer was going to ask hard questions. It meant that the only viable path forward was full immediate voluntary disclosure to NASA, to DCSA, to the State Department's DDTC for the ITAR concerns, and to the Defense Office of Hearings and Appeals for the classified subcontract. It meant that anything other than full transparency could be construed as a cover up, which would multiply the damage by an order of magnitude. It also meant that Royce, as the responsible corporate officer, was personally exposed. The meeting ran for 3 hours. By the end of it, several things had been decided. Skylar would be removed from her position, effective immediately, pending a transition to a non-contract touching role. Diane would be placed on administrative leave pending an internal investigation.

[00:19:12]Outside council would draft a voluntary disclosure letter to NASA's contracting officer for each of the four affected contracts. The board would convene an emergency session to consider Royce's status, and I would be reinstated to my prior responsibilities with a written confirmation of my key personnel status on all relevant contracts, retroactive to the date Diane had originally circulated her ORC chart. I went back to my old office that evening to retrieve a few things. Skyler's succulent was still on the credenza. So was the photograph from the Miami nightclub. I left them where they were. What happened next took about 11 weeks to fully play out and I will compress it for you. The voluntary disclosure letters went out. NASA Marshall responded with a request for a full audit of our personnel security practices. The audit was conducted on site over 4 days by a team that included DCSA, the NASA Office of Inspector General and an export control specialist from DDTC. The audit found, among other things, that during the 3 weeks Skylar had held her unauthorized position, she had been included as a recipient on at least nine email threads containing export control technical data. Two of those threads included drawings classified as USML category 15A1 propulsion systems. Three included CUI marked documents under NASA's information security program. None of this had been authorized. The consequences came in waves. First wave, NASA suspended performance on the smaller of our two prime contracts penny resolution of the security incident. The contract was valued at 6 million annually. Second wave, Northrop, our prime on the classified subcontract, was notified by us and independently by DCSA. They terminated the subcontract for cause that was 11 million in annualized revenue. Third wave, the largest of our NASA contracts, a $31 million instrument development effort was placed under what's called a stop work. While DDTC conducted its own review, stop work means no billable hours, no progress payments, no nothing.

[00:21:10]The company was bleeding $300,000 a week in standing costs against zero revenue.

[00:21:15]Fourth wave, two of our commercial customers who had been considering us for follow-on work quietly withdrew.

[00:21:21]They had read about the audit through industry channels. Fifth wave, the board terminated Royce. They did not call it a termination. They called it a planned leadership transition, but everyone in the building knew. He cleaned out his office on a Saturday morning when no one was around to see it. Six wave. Diane resigned, effective immediately with no severance. There was a rumor she had been threatened with referral to the US attorney's office for false statements made during the internal investigation, but I never confirmed that. Seventh wave, Skyler simply disappeared. One day she was on the org chart in a strategic communications adviser role. The next day her name was gone. I heard later from a former colleague that she had moved back to Florida. By the time all of this had played out, the company had lost contracts representing approximately $52 million in annualized revenue. Two of the four NASA contracts were eventually reinstated after the company entered into a consent agreement with DDTC that included a $4 million civil penalty, a three-year monitoring period, and mandatory remedial training for the entire executive team. The classified subcontract was never coming back. Northrop does not forgive that kind of thing. I want to be very clear about something. I did not destroy this company. The company destroyed itself. I simply refused to participate in the destruction and I documented the truth at every step. That is not revenge. That is what people in my profession call compliance. But I will admit when I sat down with the new interim CEO, a calm, methodical retired three star named Hollyy, brought in by the board, and he asked me what I needed to stay, I gave him a list. restoration of all duties, written authority over personnel security decisions touching any contract, a direct reporting line to the audit committee for any compliance concerns with no intermediate approvals, and the title of chief mission assurance officer reporting directly to the CEO.

[00:23:20]He said yes to all of it before I had finished reading the list. Holly is a good man. We have rebuilt much of what was lost. The NASA Marshall contracts that were reinstated are running clean.

[00:23:32]We have won two new awards in the past year, both with my signature on the proposals as the senior technical executive. The $4 million fine was painful but survivable. The company is smaller now, leaner, and considerably more humble. I still think about Royce sometimes. The last I heard, he was working as a consultant for a private equity firm in Dallas. I don't know what he tells them about his time as chairman. I imagine the story has been smoothed over considerably. I think about Diane almost never. I think about Skylar occasionally and not with any malice. She was 26 years old and her aunt put her in a job she was unprepared for in an industry she didn't understand. The blame is not really hers. It belongs to the adults in the room who should have known better. The lesson, if there is one, and my father always insisted there had to be one or you weren't telling the story right, is this. There are industries where you can fake it. There are industries where charisma and a good slide deck and an aunt with influence will get you a long way. Defense and aerospace are not those industries. The federal government has spent 80 years building a regulatory structure specifically designed to identify, vet, and protect the people who do this work. That structure exists for a reason. The reason is national security. When you treat it as an inconvenience to be routed around, the structure does not bend. It breaks you.

[00:24:57]My father, the machinist from Toledo, never understood my work. He thought I sat in offices and read regulations. He wasn't entirely wrong. But on the day my voluntary disclosure letter went to NASA's contracting officer, I thought about him and about something he told me when I was 19 years old and getting ready to ship out for the first time.

[00:25:18]Son, he said, the rules aren't there to slow you down. The rules are there because somebody somewhere did something stupid and somebody else paid for it.

[00:25:28]Your job every day of your life is to make sure you're not the somebody else.

[00:25:33]I never have been and I don't intend to start now. I've thought a lot in the years since about why this whole thing happened. Not the regulations part, the human part. Why a man like Royce, who had every advantage his father could give him, looked at a working company and decided the people who built it were the problem. Why Diane, who was genuinely capable in her own field, chose to use her position to slip her niece past every safeguard the federal government had spent decades constructing. Why Skyler, who was honestly not a bad young woman, didn't stop for one minute and ask whether she belonged in the chair she'd been handed.

[00:26:13]I think the answer at the bottom of it is that none of them respected the work.

[00:26:17]They saw titles and salaries and customer logos. They didn't see the 26 years of vetting, the clean rooms, the late nights reading clause language, the quiet phone calls with contracting officers who trusted me because I had earned that trust one careful conversation at a time. They thought the company was a brand. It wasn't. It was a chain of obligations and every link was a human being who had agreed to take national security seriously. Cause and effect doesn't care about your intentions. Diane didn't intend to lose her job. Royce didn't intend to lose his father's company. Skyler didn't intend to end up back in Florida with her career quietly amputated. They intended to consolidate power, save some money on a senior salary, and make Royce look bold in front of the board. But when you violate the rules that hold a system together, the system doesn't pause to ask what you meant. It simply enforces itself. That's what I try to explain to my own son. on the night I came home from the boardroom meeting. The rules will always win in the end. The only question is whether you're standing with them or against them when they do. If there's anything I want a younger person to take from my story, it's this. Build your character before you need it. The integrity I leaned on during those 11 weeks was not something I manufactured in the moment. It was the slow accumulation of small choices I'd made over 30 years. Every time I told the truth on a security questionnaire, every time I declined a shortcut, every time I documented a meeting instead of trusting my memory, develop your mind seriously.

[00:27:48]Read the regulations. Learn the technical work. Be the person in the room who actually understands what's being decided. And steal your nerves quietly because there will come a day when staying calm and methodical is the only thing standing between you and ruin. I am not a hero in this story. I'm just a man who refused to lie, who kept his paperwork in order, and who trusted that the truth, properly documented, would speak for itself. It did.