Kyndryl is a company built differently.
Kyn comes from ‘kin’ which represents the strong bonds formed with their people and customers, while dryl is derived from ‘tendril’ which means evoking new growth and connections.
Running some of the world’s most critical IT infrastructure, Kyndryl specialises in designing, building and managing complex, mission-critical technology systems for thousands of enterprise customers across more than 60 countries.
That operating model creates a complex procurement environment. Around 85% of Kyndryl’s purchases are directly in support of customer engagements, meaning third-party decisions can directly affect the commitments the company makes to its customers.
Ben Shanahan, Vice President, Strategy and Operations at Kyndryl, explains that this creates a constant need to balance speed, commercial outcomes and risk.
“That creates significant complexity because our customers expect us to uphold exceptionally high standards and firm commitments,” he notes. “When we engage with suppliers and incorporate their components into a managed service, we need to ensure they meet the same standards and expectations our customers hold us to. Everything has to be rock solid because, ultimately, in most cases we’re the ones accountable for performance at the customer level.”
Matt Friedman, Chief Procurement Officer at Kyndryl, says Procurement has an important role to play in supporting profitable growth while ensuring the right commercial and risk controls are applied.
“It’s a balancing act because we have to support profitable growth,” says Friedman. “Procurement plays an important role in shaping customer deals. We have a number of reciprocal relationships and we work closely together because we manage these things much more holistically.”
The problem Kyndryl set out to solve
Buying at Kyndryl can be complex. A single purchase can touch more than 60 different processes across 12 or more business functions, and in some cases involve more than 40 people. Which activities apply depends on factors such as what is being bought, where it is being bought, the supplier involved, how the purchase will be used, its value and the level of risk.
The challenge was that many of those processes, policies and controls had been designed and managed within individual functions. For the person trying to buy something, that could mean moving between different teams and systems with limited visibility of what applied, what did not, what needed to happen next or how long each step would take.
“The issue was not that these processes didn’t have a purpose,” explains Shanahan. “The issue was that they were fragmented. The requestor shouldn’t need to understand 60 different processes or how a dozen functions work together. They should be able to explain what they need once, and the workflow should determine the right path.”
That became the problem Procure was designed to address: digitally connecting the end-to-end buying journey across Procurement and the wider enterprise. Rather than replacing the core systems each function uses, Procure provides the orchestration layer between them, guiding each request through the right processes, controls and approvals, in the right sequence, with clear ownership and visibility from start to finish.
Read the full story here!