Chapter 11 - When the General Asked One Question
The preliminary staffing meeting for the new emergency-response initiative was held on a rainy Thursday morning.
I arrived fifteen minutes early.
The conference room was on the fourth floor of a government building in Washington.
There were no chandeliers.
No cameras.
No applause.
Just a long table, a projection screen, several senior officials, and a pot of coffee that looked as though it had been sitting on the burner since dawn.
I felt at home immediately.
Admiral Whitaker was already seated.
Beside him sat General Brooks, two civilian agency representatives, and a senior Air Force officer named Lieutenant General Marcus Bell.
Bell was broad-shouldered and quiet.
He had a reputation for asking questions that made unprepared people reconsider their career choices.
I'd met him twice before.
Once during a disaster-response exercise.
Once during an interagency readiness briefing.
He remembered me.
"Colonel Merrick."
"Sir."
He pointed to a chair.
"Come show us why everyone keeps talking about your spreadsheets."
For a second, the old phrase hit me like a slap.
Then I noticed the small smile at the corner of his mouth.
He wasn't mocking me.
He was inviting me to prove something.
I sat.
"With pleasure, sir."
The meeting began with a briefing on the proposed initiative.
The problem was straightforward to describe and extraordinarily difficult to solve.
During major emergencies, multiple organizations could be responsible for different parts of the same supply chain.
A hospital might need medication.
A military airlift unit might be able to transport it.
A civilian airport might control the landing schedule.
A state agency might manage ground distribution.
A private supplier might have the inventory.
And a communications outage might prevent any of them from seeing the same information at the same time.
Everyone could be doing their assigned job correctly.
And people could still die waiting for the pieces to connect.
The proposed initiative sought to improve that coordination.
Not by giving one organization unlimited authority.
Not by replacing existing emergency systems.
But by creating stronger planning standards, shared assumptions, and procedures for resolving conflicts when resources were scarce.
The civilian representative finished her presentation.
Then General Bell looked at me.
"Colonel Merrick, tell me what's wrong with this proposal."
The room became quiet.
I studied the screen.
The briefing was polished.
The objectives were ambitious.
The timeline was optimistic.
Too optimistic.
"How much time do I have, sir?"
Bell smiled.
"Start with two minutes."
I stood.
"Respectfully, the proposal assumes that the participating organizations will produce compatible information during the first twelve hours of an emergency."
"Is that unreasonable?"
"It's untested."
I pointed toward the chart.
"It also assumes transportation capacity can be reassigned without delay."
A civilian official frowned.
"That's the purpose of coordination."
"Yes, ma'am."
I turned toward her.
"But coordination isn't the same as control."
I continued.
"If a regional airport loses power, a supplier's inventory database remains operational, and the receiving hospital is operating under emergency restrictions, whose information becomes authoritative?"
Nobody answered immediately.
I looked at Bell.
"Sir, we're designing a system around the assumption that everyone will agree on what is happening."
"And they won't?"
"Not always."
"Then what would you do?"
"Build the disagreement into the design."
He leaned forward.
"Explain."
I went to the whiteboard.
For the next twenty minutes, I did what I'd spent most of my adult life doing.
I examined assumptions.
Identified failure points.
Separated urgent needs from merely loud ones.
And explained why a system that worked beautifully during a demonstration might collapse during the first real emergency.
I drew three columns.
What we know.
What we believe.
What we must verify.
Then I circled the last one.
"Most serious planning failures don't begin with a lack of information."
I looked around the table.
"They begin when we stop distinguishing facts from assumptions."
The room was silent.
General Bell tapped his pen.
"All right."
He pointed at the board.
"What's your first recommendation?"
"Independent validation before we promise anything operational."
"Second?"
"Defined authority for resolving conflicts between participating organizations."
"Third?"
"A realistic exercise involving incomplete, delayed, and contradictory information."
Bell nodded.
"Fourth?"
I paused.
"Protection against inappropriate outside influence over system design."
Admiral Whitaker looked at me.
So did General Brooks.
I continued evenly.
"Commercial partners can provide valuable capabilities."
"But procurement, access, and operational decisions must be governed by established rules."
Bell leaned back.
"That's a fairly pointed recommendation."
"It's a general principle, sir."
"One you feel strongly about?"
"Yes, sir."
He watched me.
Then asked a question that surprised everyone.
"Colonel Merrick, why didn't you apply for a command position earlier in your career?"
I stood still.
It wasn't the kind of question I'd expected.
"Sir, I've served in command and staff assignments appropriate to my career path."
"I've read your record."
"Yes, sir."
"Your evaluations suggest you could have pursued several different assignments."
I nodded.
"Then why stay so deeply involved in logistics planning?"
I thought about giving him the professional answer.
The one about operational readiness.
Strategic mobility.
Integrated sustainment.
All of it would have been true.
But it wouldn't have been complete.
"Because people often notice logistics only after it fails, sir."
Bell waited.
I continued.
"A pilot can be ready to fly."
"A surgeon can be ready to operate."
"A unit can be ready to move."
"But if the fuel, medicine, equipment, or transportation isn't there, readiness doesn't matter."
I looked toward the screen.
"I wanted to work on the part of the mission that makes everyone else's work possible."
Bell sat quietly.
Then he nodded.
"Good answer."
The meeting continued for another hour.
By the end, we had identified specific tasks, a realistic development schedule, and several areas requiring legal and operational review.
Nobody promised miracles.
Nobody declared the problems solved.
We simply agreed on the next responsible steps.
It was the best meeting I'd attended in months.
As the participants began gathering their papers, General Bell approached me.
"Colonel."
"Sir."
He held out his hand.
"That was impressive."
"Thank you."
He glanced toward the whiteboard.
"Your work doesn't need better publicity."
I smiled slightly.
"No, sir."
"It needs the right people listening."
I shook his hand.
Then he lowered his voice.
"And for what it's worth, your command has spoken highly of your integrity."
My expression changed.
He noticed.
"I'm aware there's a review involving outside use of certain materials."
"Yes, sir."
"I'm not asking about it."
"Understood."
He paused.
"But I want you to hear something clearly."
I looked at him.
"You're not expected to resolve that matter by sacrificing your own future."
For a moment, I couldn't speak.
He continued.
"Your responsibility is to cooperate honestly and perform your assigned duties."
"Yes, sir."
"Nothing more."
I nodded.
"Thank you, sir."
He started to walk away.
Then stopped.
"One last thing."
"Sir?"
"The next time someone calls you the queen of spreadsheets, tell them General Bell would like to see whether they can do your job."
I laughed.
A real laugh.
The kind I hadn't heard coming from my own throat in a long time.
That afternoon, I received another message from Mitchell.
We need to meet.
This time, I responded.
I agree.
We can discuss our marriage in a private setting with appropriate boundaries.
His reply arrived seconds later.
No investigators. No lawyers. Just us.
I stared at the words.
Then answered.
Our personal conversation can remain separate from the investigation.
But I won't promise secrecy about matters I'm obligated to report.
For ten minutes, he didn't reply.
Finally, one message appeared.
You really don't trust me anymore.
I looked at the screen.
He hadn't asked whether I was hurt.
He hadn't asked how I was managing.
He hadn't congratulated me on my new responsibilities.
He'd asked whether I trusted him.
I typed my answer slowly.
I don't know whether I can.
May you like
Then I set down the phone.
For once, I let the truth stand without trying to make it easier for him to hear.
