Cutting downtime ~90%

The problem behind the outages

Downtime rarely has a single villain. It’s usually accumulated drift: unclear release ownership, infrastructure changes without a shared rhythm, dependencies that only surface at deploy time, and a backlog that rewards feature speed over operational truth.

At Viusasa, the mandate wasn’t “add another status meeting.” It was restore predictability — for engineering, for ops, and for an audience that expected the product to simply work.

How delivery moved

As Senior Systems & Program Delivery Lead I ran multi-workstream programs across infrastructure, release process, and platform stability. That meant Agile/Jira hygiene that served the work — backlogs tied to risk, not theatre — and clear owners for the paths that used to fail quietly until they failed loudly.

The measurable result: roughly a 90% reduction in system downtime, with release predictability as the mechanism, not a slogan.

This sits alongside earlier hands-on work in the same media ecosystem — backend services and digital platforms at Royal Media Services supporting VOD with 100,000+ daily active users, content, billing, analytics, and DRM-aware pipelines. I know what these platforms feel like from both sides of the wall.

What a partner gets

If your platform is “mostly fine” until it isn’t, you don’t need another dashboard. You need someone who can re-sequence the program around reliability without pretending features don’t matter — and who has already done it under audience pressure.