For a moment, nobody spoke.

The projector continued displaying the deployment dashboard, its reassuring green charts quietly insisting that everything was now healthy. The irony wasn't lost on anyone in the room. Less than ten hours earlier, the same systems had painted the screen in angry shades of red while Teams notifications arrived faster than anyone could read them.

Now the graphs were calm; only the people weren't.

Aditya looked from the projector to the whiteboard.

"The dashboard answered the question we asked," he said. "Now let's answer the one it couldn't."

He stood, uncapped a blue marker and walked towards the whiteboard.

The familiar squeak of marker against laminate filled the room.

Instead of writing Authorization, he simply drew a large rectangle in the centre.

Returns Platform

Beneath it he wrote a single phrase.

Schema Migration

He stepped back.

"Forget last night for a minute."

His eyes moved around the room.

"If this migration had succeeded..."

"...what systems would still have cared?"

Nobody answered immediately, not because they didn't know.

Because there wasn't one answer.

"There," Priya said first, pointing towards the whiteboard. "That's already a different conversation."

"It should be."

Aditya nodded.

"Root cause tells us why something failed."

He tapped the marker against the board.

"I want to know why it was able to fail."

The distinction settled naturally over the room.

Rocky, who had instinctively reached for the presentation remote again, stopped halfway. He looked at the sleeping projector, then quietly placed the remote back on the table.

Nobody noticed; everyone was looking at the whiteboard.

Rahul was the first to stand. He carried his notebook with him, though he didn't open it.

"The migration touched a shared table."

"Yes."

"Returns owns it."

"Yes."

"But Authorization reads it."

Aditya nodded.

"What else?"

Rahul frowned thoughtfully.

"I'm not sure."

"Good."

The answer surprised him.

Aditya smiled.

"Being unsure is useful."

He drew another rectangle beside the first.

Shared Database

"If we already knew every dependency..."

"...we wouldn't be sitting here."

Priya leaned forward in her chair.

"Notifications."

Everyone looked towards her; she shrugged.

"It reads return status before sending customer emails."

She frowned.

"Actually..."

"...does it still?"

She looked at Dev.

"You worked on that integration."

Dev thought for a few seconds.

"I think it does."

"You think?"

"I..."

He hesitated.

"I should check."

"Exactly."

Aditya smiled.

"We're discovering assumptions already."

Meher stood next; she had remained unusually quiet since the beginning of the meeting, fingers absent-mindedly tracing circles around the rim of her coffee cup.

She walked to the whiteboard and took another marker.

"If Notifications depends on it..."

She drew another box.

"...Customer Communications probably does too."

She connected it with a dotted line.

"And Product Analytics."

Another dotted line.

"They generate return trend reports every morning."

Rahul looked up.

"I hadn't thought about Analytics."

"Nobody ever does."

Meher smiled.

"Which is exactly why Analytics breaks at quarter-end."

Even Rocky laughed.

"Fair."

Ritu finally rose from their chair, carrying tea in one hand and a marker in the other. They stared at the growing diagram for a long moment before erasing one of the arrows Aditya had drawn.

Nobody objected.

"You've connected systems."

They drew a different symbol.

"What actually matters..."

"...is ownership."

They wrote beside the line.

Returns Team

Another.

Commerce Platform

Another.

Customer Experience

"There."

They stepped back.

"The dependency isn't technical."

"It's organisational."

Silence.

Rocky folded his arms.

"...Explain."

"When something breaks..."

Ritu looked around the room.

"...the first question isn't."

"What failed?"

"It's."

"Who owns it?"

Nobody argued.

Because every person in the room had lived through enough production incidents to know that the first fifteen minutes of almost every outage involved figuring out who should be invited to the call.

Rahul quietly nodded.

"That's true."

"I spend half my releases updating distribution lists."

Priya smiled.

"And the other half?"

"Waiting for people to accept calendar invites."

A notification chimed softly from someone's laptop.

Everyone instinctively glanced down.

Teams.

Someone from Infrastructure had posted in the engineering channel.

Reminder: Please complete your mandatory Cybersecurity Awareness module by Friday.

The room remained silent.

Meher looked around.

"Timing."

Priya shook her head.

"If ransomware ever attacks..."

"...we'll apparently be very aware."

Even Dev laughed.

The interruption lasted barely a few seconds before everyone returned to the whiteboard.

That, Aditya thought, was another engineering habit.

Distractions happened, and context returned surprisingly quickly.

Dev had remained seated, as his laptop was still open to the deployment timeline. He hadn't looked at it in several minutes.

Instead, he was studying the dependency map slowly spreading across the whiteboard. Finally, he spoke.

"I still should've known."

The room became quiet again.

Not awkward.

Just attentive.

"I wrote the migration."

"I reviewed it."

"I tested rollback."

He looked towards Aditya.

"I never even thought about asking who else used that field."

Before Aditya could answer, Meher spoke.

"I reviewed the application changes."

She shrugged lightly.

"I didn't ask either."

Priya nodded.

"I reviewed production readiness."

"I missed it."

Rahul added quietly,

"I verified the release checklist."

"I never asked about downstream services."

Ritu closed their notebook.

"I approved architecture."

"They weren't documented."

The admissions came one after another.

Not defensive... not apologetic... simply factual.

The room slowly realised something. The outage hadn't slipped past one person. It had slipped through a collective blind spot.

Aditya looked at Dev.

"If four senior engineers..."

He glanced around the room.

"...and Release Management..."

"...and Architecture..."

"...all missed the same thing..."

He let the sentence hang.

"...then we didn't have an engineering failure."

"We had a visibility failure."

Nobody moved because the wording mattered. Dev's shoulders relaxed for the first time that morning. Not because he had been absolved. Because the mistake had finally been described accurately.

Rahul picked up his notebook again almost reflexively.

"I'm still adding dependency verification."

Priya groaned.

"Rahul..."

"What?"

"We've just spent twenty minutes proving checklists aren't enough."

"I know."

He smiled sheepishly.

"But I physically cannot attend an RCA without adding at least one checkbox."

The room burst into laughter.

"It's part of my job description."

Meher looked at him.

"Is it actually?"

"I've never read the whole document."

"You should."

"It's forty-three pages."

"You're joking."

"I wish."

The laughter faded naturally and Aditya looked back at the whiteboard.

Returns.

Shared Database.

Notifications.

Analytics.

Customer Communications.

Ownership.

Question marks.

Half-finished arrows.

The diagram was untidy.

Incomplete.

Alive.

He smiled.

"This," he said quietly, "looks much more like the platform I know."

Nobody disagreed because real systems never resembled architecture diagrams. They resembled conversations. And this conversation, Aditya realised, was finally asking the right questions