storyloom

Chapter 3 - The Question Before the Answer

The second exercise began with a problem that looked easier than the first. A scheduled training session had lost access to one of its primary resources, and Ethan's team had to decide whether to reorganize the session, request assistance, or postpone it. The instructions allowed several workable solutions. The challenge was choosing one without overlooking the people who would have to carry it out.

Ethan stood before his new team with his notes folded in half. Mara watched from the same position near the whiteboard. He could feel her attention, but he resisted the urge to perform for her. Instead, he asked each person to explain the situation from their assigned position before he proposed a plan.

The first two reports were straightforward. The third came from a junior sailor named Petty Officer Devin Shaw, who explained that the replacement resource was technically available but had not been checked since its last maintenance cycle. He couldn't confirm whether it would be ready in time.

Ethan felt impatience rise. The clock was moving, and he could already see a solution that seemed reasonable. He asked Shaw how long the check would take.

“About twenty minutes, sir, assuming nothing is wrong.”

“And if something is wrong?”

“Then I can't give you a time.”

Ethan glanced at the schedule. He could proceed using the existing arrangement, but that would leave the team with little room to adapt if another problem appeared. He could postpone, but the delay would affect several personnel who had already prepared for the session. Or he could request support from another section and accept that his plan would require coordination he hadn't anticipated.

His first instinct was to choose the fastest option. He almost announced it, then stopped.

“What would you recommend?” he asked Shaw.

The sailor seemed startled by the question. He explained that a brief inspection would reduce uncertainty, while a parallel request for backup would prevent the team from losing the entire session if the replacement resource failed. It wasn't the neatest solution, but it preserved options.

Ethan asked the others whether they saw any problems with the approach. Ortiz, assigned to the exercise again, pointed out that the backup request needed to happen immediately. Brooks suggested a small adjustment to the schedule that would give the inspection team enough time without leaving the rest of the personnel idle.

This time, Ethan built his plan from their information rather than forcing their information into a plan he'd already chosen. He assigned responsibilities, asked each person to repeat the critical timing, and made sure Shaw knew he was expected to report a problem as soon as he found one.

The exercise proceeded without a dramatic failure. The resource passed inspection, the backup request was canceled, and the session began with a manageable delay. Ethan's report was less polished than the one he'd written after the first exercise, but it explained the uncertainties, the alternatives, and why he'd selected his approach.

Mara read it in silence. Ethan waited, prepared for another blunt correction.

“What changed?” she asked.

“I asked questions before deciding.”

“Anything else?”

He considered the answer. “I let the team affect the plan.”

She nodded. “That's closer.”

He felt a small rush of satisfaction, then caught himself waiting for her to say he'd done well. The realization was uncomfortable. Even his improvement seemed tied to her approval, as though he needed an authority figure to confirm that he was becoming the person he wanted to be.

“Was that good enough?” he asked.

“For this exercise, your decisions were sound. Whether the lesson stays with you is something you can't establish in one morning.”

She said it without cruelty. Ethan understood that she wasn't withholding praise to make him work harder. She simply couldn't promise that a single success had changed a habit he'd spent years building.

During the afternoon debrief, Commander Mercer informed Ethan that his assessment would remain open for the rest of the week. He would receive feedback, but there would be no immediate determination about his leadership standing. Ethan asked whether the cafeteria incident had already affected the review.

“It is part of the record,” Mercer said. “So is what you've done since. We evaluate conduct, not just outcomes.”

He left the office frustrated by the lack of a clear finish line. Yet, beneath the frustration, he recognized something new: he'd begun to think of the people around him as participants in his decisions rather than obstacles to his authority.

That evening, Daniel invited him to get dinner off base. Ethan almost declined, then agreed. They sat in a small restaurant near the installation, away from the familiar crowd that usually gathered after work. Daniel talked about his younger brother, who had recently started an apprenticeship and kept calling for advice about every minor disagreement at work.

“He thinks asking questions makes him look incompetent,” Daniel said. “I keep telling him the boss would rather answer a question than repair a mistake.”

Ethan pushed a piece of food around his plate. “Do you think I make people afraid to question me?”

Daniel took a moment before answering. “Sometimes. You don't always mean to. But when someone disagrees with you, you act like they're trying to take something away from you.”

Ethan wanted to deny it. Instead, he remembered Ortiz warning him about the resource, Shaw admitting uncertainty, and Caleb saying he'd been afraid to interrupt. Each had offered useful information. His reaction had taught them whether he was safe to speak to.

“I don't want to be that kind of leader,” he said.

“Then don't make me tell you that again.”

Daniel's tone held affection, but it also carried the fatigue of someone who had been trying to reach a friend for a long time. Ethan realized that an apology to Mara would not repair every relationship damaged by his behavior. He would have to change how he treated Daniel, his team, and the people whose work he rarely noticed.

The next day, he sent Mara the brief apology he'd drafted. She replied with a simple acknowledgment and said they could discuss it during their scheduled meeting. There was no reassurance, no statement that everything was forgiven. Ethan found himself disappointed, then ashamed of that disappointment.

He had apologized because he'd done something wrong. He had no right to demand that she make him feel better about it.

Their meeting took place late that afternoon. Mara listened while he described what he'd learned from the exercises and admitted that he'd treated the cafeteria as a place where rank entitled him to decide who belonged. He didn't blame the other officers or the atmosphere of the room.

When he finished, Mara folded her hands. “The important question isn't whether you feel bad about what happened. It's what you'll do when you feel that same need to prove yourself again.”

Ethan thought about the next difficult decision, the next person who might challenge him, and the familiar temptation to silence discomfort by asserting control. He had no perfect answer.

“I'll try to recognize it before I act,” he said.

“Good. And when you fail?”

“I'll own it.”

May you like

Mara studied him for a moment, then nodded. It wasn't forgiveness, but it was the first answer he'd given her that didn't depend on whether she liked him.

As he left, Ethan understood that the real test wouldn't be a controlled exercise with an observer taking notes. It would happen when he was tired, embarrassed, or afraid of losing face, and no one was waiting to remind him what he was supposed to learn.

Related Stories

Other posts