Shipping at scale without losing trust.

A fixed price and an evolving roadmap are a contradiction. Someone has to hold it, deliberately, for years.

The engagement was sold as a fixed commercial commitment and delivered as an Agile product practice. Those two things want opposite behaviors. Fixed fee rewards a scope you can close; Agile rewards a scope you can revise. Left unmanaged, the gap between them gets paid for by whoever is least able to refuse — usually the delivery team, in unpaid scope, and eventually in quality.

A second tension ran alongside it. The work was continuous product development — portal functionality, marketing functionality, frontend and backend, QA, release management — but the decisions that unblocked it were not ours. Product direction, roadmap input, approvals and acceptance all sat client-side. An agency team can be fully staffed and still be stalled, and the commercial clock does not stop while a decision is pending.

So the mandate was less about tracking a plan than about protecting two things at once: a roadmap that could genuinely change, and a commercial envelope that could not.

The same discipline covered the wider portfolio — KPMG’s global Adobe delivery across ten markets, plus financial services, loyalty and travel accounts — but the multi-year telecom engagement is where the model was proved.

I shaped the delivery rhythm around a small number of repeatable questions: What changed? What is at risk? Who owns the next move? What must be true to release? What does leadership need to decide?

Clients trusted the delivery story because it stayed specific, useful, and consistent when the pressure increased.

The portfolio delivered visible outcomes while sustaining the client and commercial confidence needed to keep moving.

Across the work, I led more than 15 major TELUS releases on schedule, sustained 98% client satisfaction, and held budget variance within ±5% across a $4M+ portfolio.