The enterprise context
During my time at Quinnox, I was responsible for implementing a Security-as-a-Service solution for HSBC. The solution was used across nearly 100 countries.
This was a client engagement delivered through Quinnox, and an important part of my progression from enterprise delivery into broader engineering and product leadership.
My responsibility
My responsibility was the implementation of the solution. The engagement took place during 2010–2014, across my early enterprise delivery and team leadership roles.
The geographic reach gives a sense of the operating context: a single enterprise capability used across a global banking footprint.
The reported outcome
The solution was associated with estimated deployment cost savings of approximately $2.8 million per month. That figure is a retrospective estimate from the engagement, rather than an independently audited savings measure.
The combination of geographic reach and deployment economics is what makes this experience significant in my career. It connected technical implementation with a business outcome at enterprise scale.
A lasting perspective
The questions raised by global delivery remain relevant to the work I do today: how does a shared capability reach the people who need it, what does it take to operate across organizational boundaries, and how do engineering choices translate into business value?
The value of a shared capability is realized through the work of making it useful across the enterprise.
Let’s compare notes.
Building enterprise capabilities or leading an engineering organization?
Start a conversation