The whiteboard had become crowded.

Blue arrows crossed green ones. Service names overlapped. Ownership boundaries had been added, erased, and redrawn. Someone had circled Shared Database three separate times. The marker tray held four uncapped pens, one nearly dry eraser, and enough whiteboard dust to suggest that architecture diagrams, like production systems, rarely stayed tidy for long.

The projector continued displaying Slide 12. Nobody had looked at it in almost twenty minutes. Rocky noticed first.

He glanced from the glowing screen to the whiteboard that now held everyone's attention. With a quiet smile, he picked up the remote and switched the projector off.

The sudden absence of its soft hum made the room feel strangely calmer.

"I think," he said, "the whiteboard has officially taken over."

"It usually does," Priya replied.

"It just takes PowerPoint a while to realise it."

A ripple of laughter circled the room.

Aditya stepped back to study the diagram.

"What are we missing?"

Nobody answered immediately, not because there wasn't an answer.

Because there were too many. Rahul looked thoughtfully at the release flow. "We still need better dependency checks."

Meher nodded.

"We also need better documentation."

Ritu spoke without looking up.

"Documentation ages."

Everyone looked towards them.

"They don't."

"They?"

"Assumptions."

Silence.

"They stay young forever."

Meher smiled.

"That's annoyingly profound."

"I've had tea."

Dev stared at the board.

"So..."

He hesitated, "...are we documenting every dependency now?"

Rahul looked hopeful.

"I have a template."

Priya immediately groaned.

"Of course you do."

"It already exists."

"That somehow makes it worse."

Rahul shrugged.

"I work in Release."

"Templates are our love language."

Even Rocky laughed; the room relaxed again. The tension that had followed the previous night's outage had dissolved into something more familiar.

Curiosity...People had stopped defending decisions and started exploring them.

Aditya uncapped another marker.

"I don't think we can document everything."

Rahul sighed dramatically.

"There goes Version One."

"But..."

Aditya drew a circle around the entire diagram.

"...we can document what matters."

He underlined Shared Database.

"Places where one team's change becomes another team's surprise."

Priya nodded.

"I like that."

"Smaller."

"Maintainable."

"Realistic."

Rahul quietly crossed something out in his notebook.

"My template just got shorter."

"Congratulations."

Meher smiled.

"It's only twenty-eight pages now."

"It was never twenty-eight."

"Twenty-seven?"

"...Twenty-six."

A soft notification sounded from someone's laptop.

Nobody looked.

Five minutes earlier, every engineer in the room would have instinctively checked Teams; now the conversation mattered more.

Outside the glass walls, people crossed the engineering floor carrying coffee, laptops, and hurried conversations. Somewhere near the pantry, the coffee machine hissed loudly before surrendering another cup. A burst of laughter drifted in from the Product pod, followed almost immediately by someone saying, "Can we take this offline?"

Meher tilted her head.

"We're literally in an office."

Priya didn't miss a beat.

"They mean another meeting."

"Obviously."

Kavya had spoken exactly once since entering the room.

Most of the morning she had listened quietly, occasionally writing short notes in a notebook instead of typing on a laptop. Aditya had noticed that early on. It wasn't unusual to see architects with diagrams.

It was unusual to see one who preferred paper. She looked at the whiteboard for a long moment before standing.

Nobody stopped talking; they simply... made room. She walked to the board, picked up a black marker, and studied the web of arrows.

Not the boxes...the arrows.

After a few seconds, she drew three small dots beside one connection.

Returns.

Authorization.

Shared Database.

Then she capped the marker.

"What changed?" she asked.

The room looked puzzled.

Rahul answered first.

"The database."

She nodded.

"What else?"

"The schema."

Priya replied.

"The default value."

Another nod.

"What didn't change?"

Silence.

Dev frowned.

"The service?"

"Yes."

She looked at him.

"What else?"

Nobody answered.

Kavya turned back to the whiteboard.

"The conversation."

The room fell completely silent. She continued gently.

"The database changed."

"The service didn't."

"The release process didn't."

She looked around the room.

"But neither did the understanding between the teams."

No accusation... no lecture... just an observation.

"We've spent the morning talking about dependencies."

She tapped one of the arrows.

"I think this one is different."

Aditya watched her carefully.

"How?"

She smiled faintly.

"It isn't a software dependency."

Her marker rested lightly against the board.

"It's a communication dependency."

Nobody interrupted.

"If Returns changes something..."

"...Authorization shouldn't discover it from production."

Rahul slowly lowered his pen.

"They should already know."

"Exactly."

The room grew thoughtful; even Rocky had stopped taking notes.

Priya leaned back.

"So..."

"...architecture review isn't really about code."

Kavya looked at her.

"It's about conversations."

Nobody spoke for several seconds, not because anyone disagreed. Because everyone had mentally replayed the previous night's deployment.

The SQL had been reviewed.

The rollback had been reviewed.

Performance had been reviewed.

Nobody had asked one simple question.

"Who else depends on this?"

Aditya looked back at the whiteboard.

He drew one final box above everything else.

People

Then arrows flowed downward.

People.

Teams.

Services.

Database.

He stepped back.

"I think..."

A small smile appeared.

"...that's actually the architecture."

Ritu nodded once.

"Finally."

Rahul quietly closed his CAB folder.

"I can add another approval."

Everyone looked at him; he shook his head.

"It won't solve this."

"No," Aditya agreed.

"It won't."

Rahul smiled.

"I don't say that often."

"We noticed," Priya replied.

The room laughed. Rocky stood and walked towards the whiteboard. He looked at the sleeping projector behind him. Then at the crowded whiteboard. Then at the untouched stack of printed handouts still sitting neatly on the conference table.

"I spent most of yesterday evening building forty-one slides."

He smiled.

"And we've just replaced them with one whiteboard."

Meher looked at the board.

"It's cheaper."

"Much."

"And the licensing is excellent."

Rocky laughed.

"I'll mention that to Finance."

"They'll ask for a business case."

"With appendices," Rahul added.

"And a CAB approval," Priya finished.

The room erupted again; the laughter lingered longer this time. Not because the joke was especially clever, but because it belonged to all of them.

As the laughter faded, Aditya picked up the eraser. Nobody expected what he did next. He erased the entire whiteboard.

Every box... every arrow.... every note.

Dev looked alarmed.

"We needed that."

"We still have it."

Aditya tapped the side of his head.

"No."

He looked around the room.

"We have each other."

He smiled.

"Now let's build the version we'll actually maintain."

Nobody reached for the projector; nobody reopened the slides. Instead, eight engineers stepped closer to the now-empty whiteboard. Fresh markers clicked open. Outside, another ordinary Wednesday continued at Solstice Systems.

Inside War Room A, the RCA had quietly ended.

The architecture workshop had just begun.