These are composite stories based on real OpsAlign engagements. The names are fictional. The pain is not.
Rachel was hired to lead the IT integration after a major acquisition. On paper, the combined organisation looked formidable — 340 engineers, three data centres, two ITSM platforms, and decades of accumulated domain knowledge. In practice, it was two separate tribes who had never worked together and weren't sure they wanted to.
The acquired company had strong event management. The acquiring company had stronger change controls. Both had serious gaps she hadn't found yet. Every week without clarity was a week of decisions made on instinct rather than evidence.
Customers were already feeling it. Service tickets from the acquired company's clients had increased 34% since close. The CEO asked Rachel in her third week whether the integration was "on track." She said yes. She had no data to back that up.
"A client called the CEO directly to complain about three outages in ten days. The CEO forwarded the email to me with one line: 'Rachel — what's happening and when does it stop?' I had no answer. I didn't even have a clear picture of which team was responsible."
Two different problems. The same platform.
Franklin had been CIO of the same financial services group for nine years. In that time he'd watched the technology estate grow in complexity faster than the team's capability to manage it. Twelve core systems. Four overlapping monitoring tools. A Problem Management function that existed on paper but not in practice. Three senior engineers — all over 55 — who carried institutional knowledge in their heads and nowhere else.
The P1 incidents were the most visible symptom. Six in the last year, each one requiring the same three people to fix it, each one resolved without a permanent fix, each one followed by the same post-mortem that went nowhere. Franklin had written the same root cause recommendation four times in three years. Nobody funded it.
What changed was the renewal pipeline. Three of the firm's largest enterprise clients were approaching contract renewal — and all three had IT stability as a contractual condition. The Chief Revenue Officer sent Franklin a single message: "We are going to lose Hartwell, Meridian, and Cavanaugh if you can't show them a plan by Q3."
"I went to the CFO with a $400K investment proposal. She asked me what the ROI was. I said 'significant.' She said 'come back when you have a number.' I'd been having that conversation for three years. I didn't have a number because I didn't have a way to generate one."