PART 14:

“It’s not,” Ethan agreed, “but it’s also not a catastrophe. People found out that a jet got fixed. That’s not bad for your company.” A pause. “No,” Raymond admitted. “It’s actually the PR team is calling it a positive development.” “Then we’re all fine,” Ethan said. He spent the morning dealing with the communication system on the corporate turboprop, which had finally consented to replicate its intermittent fault on the ground long enough for him to trace it to a corroded connection in a section of the wiring harness that the original

installer had routed closer to a heat source than was advisable. It was deeply satisfying work, the kind that required patience and methodical thinking and rewarded both without drama. He fixed it, documented the repair, and called the client. His phone had 17 new voicemails by noon. He listened to two of them.

One was from a journalist at a national publication who wanted to do a profile. One was from a man who introduced himself as a talent scout for a television production company and said the words heartwarming story in a way that made Ethan put the phone back in his pocket and not pick it up again for an hour. At 12:30, Victoria called.

“You’ve seen the coverage?” she said. “Some of it.” “What’s your read?” He considered. “I don’t love the way they told it. The single father angle is it flattens things, makes it a different kind of story than it actually is.” “What kind of story is it actually?” “A technical problem got solved because someone looked where the standard procedure said not to bother looking.

That’s the whole story. The single father part is just context.” “The single father part is what 3 million people are sharing,” Victoria said, not defensively, just accurately. “I know.” “We can use that if you’re willing,” she said, “for the program, not the version that makes you into a character, the version that talks about the actual gap in technical education that made the situation possible, why a small independent shop could see something that a 200-person team missed.

” He thought about it. He’d been turning this question over since the first article went up, not whether to engage because some form of engagement was now probably inevitable, but how to engage in a way that moved toward the thing he actually cared about rather than the thing the media wanted to make him into.

“I’ll do one interview,” he said. “One. The one that best lets me talk about the program, not about me. You pick it.” “That’s going to be a hard negotiation,” Victoria said. “You’re hot right now. Everyone’s going to tell you they’ll let you talk about whatever you want. Then we find the one that actually means it.

” A pause. He could hear her writing something. She was always writing something. “I’ll have David make some calls,” she said. “In the meantime, the foundation director wants to meet with you again next week. She’s been working on the preliminary framework and she has questions.” “What kind of questions?” “The kind that come from someone who’s done this long enough to know which parts of a plan are solid and which parts are going to fall apart under pressure.

A brief pause. She liked you for what it’s worth. She told me you didn’t try to sell her anything. I wasn’t selling anything. That’s why she liked you, Victoria said. Look. The second meeting with Patricia Osay happened on a Wednesday morning in a different space, not the main Ashford building, but the foundation’s own office, which occupied two floors of a building on the other side of the city and had the feeling of a place where serious work actually happened rather than being discussed.

The walls had photographs and framed reports from past initiatives. There was a whiteboard in the conference room covered in handwriting that hadn’t been erased yet, still carrying the residue of someone else’s hard thinking. Patricia had the preliminary framework document in front of her. Printed, not on a screen, which told Ethan something about her working style.

It was eight pages and covered with her notations, different ink colors indicating different passes through the material. She pushed it across the table to him. He read it slowly. She waited without visible impatience, which he appreciated. The framework was good. Rigorous, clearly built on actual research with an honest acknowledgement of the points where the design was still speculative.

She’d structured it around a three-phase model, a foundational phase focused on the core principles and hands-on exposure, a technical phase with direct aircraft access and graduated responsibility, and a transition phase focused on either employment placement or independent practice. Each phase had draft assessment criteria and rough timelines.

What was missing was the philosophy. Not through any failure of intelligence or effort, the framework was smart, but it was the architecture without the foundation. It described what students would do without articulating why they would do it in that order, and without that why, the order could be changed without anyone understanding what would break.

He put it down and looked at her. “This is well done,” he said. “But,” she said, “the sequencing assumes students will understand why the order matters. They won’t at first. And if they don’t understand why, then when something breaks in the sequence, which it will, they won’t know how to recover it.” Patricia picked up her pen.

“Explain.” “My father didn’t teach me procedures first,” Ethan said. “He taught me to think about systems first. What is this thing trying to do? What would it need to do that? What can go wrong with those needs? Only after that did we talk about procedures because by then I understood that the procedure was a compressed version of the thinking, a shortcut that only works if you’ve done the long version first.

👉 [Tap here for the Next Part ] 👈