Chapter 353: Design
"That’s not the point," she said. "The point is alphabetical assignment systems are lazy administrative design and someone should say so."
The person beside her laughed.
She looked up.
She registered Sean with the same completeness he’d registered her. One look. The specific duration of someone taking an accurate read rather than a social one.
"Caldwell," she said. She’d read his lanyard.
"Yes," he said.
"Northfield," she said, touching her own. "Dani Reeves."
"Sean Miller."
She held the look for one more second. The filing second. The one where the information went somewhere useful.
Then she turned back to her paperwork.
====
The case study briefing was at two PM in the main hall.
All twenty-four students. Four tables of six, mixed by school. The faculty had arranged it so no two students from the same university sat together at the same table, which was deliberate and was the right call.
Sean was placed at the table nearest the window.
He read the twenty-page briefing packet while the faculty finished their introductions. Not performing the reading. Actually reading. The three scenarios were more sophisticated than he’d expected. Not undergraduate sophisticated. The kind of problem design that came from someone who understood that real complexity couldn’t be manufactured, only found.
He was on page fourteen when someone sat down across from him.
He looked up.
She was twenty-one. He placed that from the third-year lanyard. Five foot five. British-Indian, the specific quality of someone whose background sat in two places with equal comfort. Dark eyes that were doing the same thing his were doing, which was reading the room and filing what they found. Dark hair pulled back practically. The composed energy of someone who had been the most capable person in most rooms she’d entered and had learned to wear that without announcing it.
She looked at his page fourteen.
"You read fast," she said.
"I read ahead," he said. "The introductions cover what’s in the first three pages."
She glanced at the front of the room where the faculty were still introducing the weekend’s structure.
"Pages one through four actually," she said. "The logistics section on page three is redundant with the verbal briefing but the scenario parameters on page four aren’t being covered."
He looked at her.
She looked at him with the specific expression of someone who had just recognized something and was deciding what to do with the recognition.
"Priya Thorne," she said. "Westmore."
"Sean Miller. Caldwell."
"You’re the freshman," she said. Not dismissive. Just accurate. "Marsh’s nomination."
"You know Marsh," he said.
"I know of him," she said. "His Fischer paper from four years ago is the cleanest model for asymmetric information in infrastructure investment I’ve read. I cited it twice." She looked at the briefing packet. "Scenario two is the interesting one."
He looked at scenario two.
He’d reached the same conclusion on page eleven.
"The constraint isn’t capital," he said. "It’s the stakeholder alignment problem in the third paragraph."
She looked at him.
"Yes," she said. "Exactly that." She held his gaze for a moment with the specific quality of someone recalibrating. "Most people will spend the whole weekend on the capital question."
"I know," he said.
"We’re going to be in the same working group," she said. She’d already checked the table assignments on the back page of the packet.
"I know," he said.
She looked at him.
"You read the table assignments first," she said.
"I read everything first," he said. "Then the important things again."
She was quiet for a moment.
Not thrown. The opposite. The specific stillness of someone who had found what they were looking for and was deciding how to proceed now that they’d found it.
"The faculty think the stakeholder problem is a secondary constraint," she said. "The briefing frames it that way. They’ll expect us to come back with a capital solution."
"Yes," he said.
"We should give them the capital solution," she said. "And the stakeholder problem underneath it. So they understand both."
"That’s the correct approach," he said.
"I know," she said. Simply. The same way he would have said it.
The briefing started properly.
They both went back to their packets.
But something had settled between them at the table. The specific thing that settled when two people who thought well found each other in a room and understood what that meant without needing to say it.
====
The afternoon was an outdoor navigation exercise.
Six groups of four students. Mixed schools. Orienteering through three kilometers of hill country terrain with markers to find and decisions to make at each one.
Sean’s group included Marcus, a quiet third-year from Crestfield named Tom, and Dani Reeves.
Dani had changed into trail shoes and lightweight gear with the efficiency of someone who had done this before. She carried her group map without looking at it, which meant she’d memorized it before they started, which meant she understood that terrain and paper were two different things and the terrain was the one that mattered.
Sean noted this without commenting on it.
The first kilometer was straightforward. The trail was marked and the decisions were simple and Tom from Crestfield fell into a comfortable rhythm at the back while Marcus navigated with enthusiasm and moderate accuracy.
The second kilometer had a fork that wasn’t on the map.
Marcus stopped.
He looked at the map. He looked at the fork. He looked at the map again.
"Left," said Dani. Not looking at the map.
"The map shows right," said Marcus.
"The map shows the trail as it was when it was drawn," said Dani. "The terrain shows what’s actually here. Left fork has fresh foot traffic and a sight line to the next elevation marker. Right fork has overgrowth at the entrance."
Marcus looked at the right fork.
There was overgrowth at the entrance.
"Left," he said.
They went left.
The marker was four hundred meters along.
Sean walked beside Dani on the wider section of trail after the fork.