Adrian’s POV
"Why did you speak up in that presentation?" Adrian asks.
Leah looks surprised by the question. Her expression shifts—confusion, then consideration. She takes a moment before answering, and Adrian appreciates that. She isn't scrambling to provide what she thinks he wants to hear. She's actually thinking.
"Because the numbers were wrong," she says finally. Her voice is calm, matter-of-fact. "And because the company was about to make a major financial commitment based on flawed mathematical assumptions. I was new to the company, so I had less invested in maintaining the status quo. The people who've been here longer have built careers based on how things currently work. They have more to lose by challenging the system. But I have responsibility too. If I see something wrong and I don't say anything, I'm part of the problem."
Adrian processes this. It's a genuine answer—honest reflection about motivation and responsibility, not an attempt to impress him.
"Most people wouldn't have done that," Adrian says. He's moved to sit on the edge of his desk, positioning himself at a less formal height than standing. It's a subtle shift in power dynamics—making himself less physically imposing. "Most people are trained to stay silent. They're trained through years in corporate environments to believe that challenging authority is dangerous."
"Most people are afraid," Leah replies quietly. "Or they've been trained to be afraid. They've learned through experience that speaking up has consequences."
"It does," Adrian says. "Speaking up can have significant consequences. You violated protocol. You corrected authority publicly. You made a senior executive look incompetent in front of the CEO. In many organizations, that would result in immediate termination."
Leah's expression doesn't change visibly, but Adrian notices her shoulders tense slightly. She understands what he's saying. She understands that she took a real risk in that moment. She understands that her continued employment isn't guaranteed by merit alone.
"But you didn't terminate me," she says quietly. It's not a question, just a statement of fact. She's acknowledging the decision he made.
"No," Adrian says. "I didn't. Because accuracy mattered more than protocol in that moment. Competence mattered more than rank. And people who see what's wrong and have the courage to say something despite the risk are rare enough to be valuable."
He stands up again, returning to his full height. He wants her to understand something fundamental about how he operates, and sometimes physical positioning helps communicate that.
"That doesn't mean protocol doesn't matter," Adrian continues. "In this specific case, the breach was justified by the significance of what you found. But you can't make a habit of publicly correcting supervisors or challenging authority in front of the entire organization. You have to be strategic about when you challenge hierarchy and how you do it. The cost has to be worth the benefit."
"I understand," Leah says.
"Do you?" Adrian's question is genuine, not rhetorical. "You're from a freelance background. You made decisions independently and reported to clients, not supervisors within a larger structure. This environment is different. There are relationships, alliances, and power dynamics here that extend beyond competence."
"I've worked with clients," Leah says. "I understand hierarchy to some degree. I understand that I need to respect your position and the authority that comes with it."
"Respect isn't fear," Adrian says. "You can respect authority without being afraid of it. I want competent people who understand structure but aren't paralyzed by it. Fear makes people stay silent when they should speak. It makes them choose safety over accuracy."
He walks toward the window, looking out at the city, wanting her to understand this without having to maintain direct eye contact.
"Most of my team operates from fear," Adrian continues, his voice quieter now but no less authoritative. "It makes them compliant, which has value. Compliance is predictable. But it also limits people. It makes them defend existing systems instead of improving them."
He turns back to face her.
"I need you to be different," he says. "I need you to challenge assumptions, question data, and think independently. But you also have to understand the structure you're operating within. It exists to organize how we work together. You can move independently inside it. You just can't pretend it isn't there."
"I can do that," Leah says. "I understand the distinction you're making."
Adrian studies her for a long moment, trying to determine whether she truly understands or is simply telling him what he wants to hear. Her expression seems genuine. Her words feel rooted in comprehension rather than performance.
"Good," Adrian says finally. "Then we understand each other."
He walks back to his desk and sits down in his chair, which positions him at the center of the office, back to the window with the city behind him. It's a subtle but clear dismissal. He's done with this conversation. He's returned to his position of authority. He's re-established the hierarchy that her presence and questions briefly disrupted.
But Leah doesn't leave immediately. She stands there for a moment longer, her hand on the edge of the desk, like she's processing something, like there's something else she wants to say but isn't certain if she should interrupt his return to work.
"What?" Adrian asks. He's not impatient, just direct. He's waiting.