CHAPTER 84: The Thing About Structures

POV: Selene Castellano

James came back on Wednesday with a twelve-page printed, stapled document, it was written in the direct style of someone who had learned to say exactly what they meant after years of saying things that missed.

He set it on the desk.

“The structural problem,” he said. “The one Amara and I have been arguing about.”

Selene picked it up.

“Read the third section first,” he said.

She did.

The third section was about accountability without punishment. The problem of governance structures that created fear of failure rather than incentive to be honest about it. The way organizations that punished failure produced people who hid it. The way you could build the most principled foundation in the world and still end up with people managing their failures quietly rather than surfacing them.

“This was what killed your two companies?” Selene asked.

“Indirectly.” He sat down. “The principles were real and the people believed in what they were building but when things went wrong they managed the information rather than confronting it because the structure made confrontation feel like career suicide.” He looked at the document. “By the time the problem was visible it had been invisible so long that nothing could fix it.”

Amara was reading over Selene’s shoulder.

“The solution in the third section,” Amara said. “You’re proposing a failure review process.”

“A structured one,” James said. “Not punitive but genuinely analytical. Like, what went wrong, why, what, how we change and we learn. We proceed to build  into the rhythm of the foundation before anything has gone wrong so that when it does the process already exists.”

“Most foundations would see that as admitting they expect to fail,” Selene said.

“Most foundations do fail. They just don’t admit it until they have to.” He looked at her. “The ones that last are honest about failure before it happens, so they build the infrastructure for it.”

Selene thought about Nene, a woman who had built something strong enough to survive everything thrown at it.

She hadn’t done it by assuming nothing would go wrong.

She’d done it by building for what would.

“Leave the document,” Selene said. “I want Avalon to read it.”

Avalon read it that evening while sitting at the kitchen counter.

When he finished he turned back to the third section and read it again.

“He’s right,” he said.

“I know.”

“This is what Nene did.” He looked at the pages. “Not explicitly, she didn’t have a formal failure review process, but, she had Margaret and Robert Laine, the people whose specific job was to tell her when something wasn’t working before it became something that couldn’t be fixed.”

“She built accountability into the structure,” Selene said. “Before she needed it.”

“Yes.”

Selene looked at him.

“We need that for us too,” she said.

He looked at her.

“Not a failure review process,” she said quickly. “But a version of what you said the other night. The accountability mechanism.”

“You telling me when I’m doing the management thing.”

“Both of us telling each other, not just you.” She paused. “I disappear sometimes when things get hard, I go internal and I stop telling you what’s happening in there and you can’t read me and then you feel shut out and do the management thing and then I feel managed and go more internal.” She looked at him. “That’s our structural problem.”

He was quiet for a moment.

“When did you figure that out?” he said.

“Reading the third section,” she said. “It’s the same problem, managing the information rather than surfacing it because surfacing it feels dangerous.”

He looked at the document.

Then at her.

“What do we do about it?” he said.

“We build the process before we need it,” she said. “We decide now what we do when it happens, not if but when.”

“What do we do?”

She thought about it.

“You ask,” she said. “When you feel me going internal you ask directly.”

“Like what?”

“Like what’s the one thing you’re not telling me right now.” She paused. “Something that assumes I’m already not telling you something and makes it safe to say it.”

“And when I do the management thing,” he said.

“I name it,” she said. “Not as an accusation tho,but more like a signal.”

“What’s the signal.”

“Approximately mentioning,” she said.

He looked at her.

“That’s the management thing,” she said. “Approximately mentioning when you tell me something without actually telling me.”

He paused.

Then he laughed.

“Approximately mentioning,” he said.

“Yes.”

“That’s our accountability mechanism.”

“That’s our accountability mechanism.”

He picked up the document.

Tapped the third section.

“James Okonkwo,” he said. “Keep him.”

“Amara said the same thing.”

“She was right.”

He put the document down and picked up his coffee.

She sat across from him at the kitchen counter and they looked at each other in the way people who had built something together and recognized each other inside it.

Her phone rang.

Amara.

“The financial model,” Amara said without preamble. “Daniel Frost called me.”

“What did he say?”

“He wants to meet. He has questions about the five year projection.” she paused. “Selene. Daniel Frost calling to ask questions means he’s invested enough to have concerns. That’s different from opposition.”

“When?”

“Friday, at his office.” Another pause. “He asked if you’d be there specifically..”

Selene looked at Avalon.

He’d heard.

He gave her the nod that meant go, this is yours.

“Tell him yes,” she said.

“Already did,” Amara said.