Key question New
AI-processed · Author-approved
How do easily modifiable technologies, contracts, and capabilities combine to make IT outsourcing successful?
Loads Spotify's player; Spotify may set cookies. This device remembers your choice.
Key findings
- The analysis identifies five distinct configurations that are sufficient for high outsourcing success, demonstrating equifinality across projects.
- In early-stage vendor relationships, high technology malleability and strong relational governance act as substitutes; either path is sufficient for success without relying on the other.
- In mature vendor relationships, strong client adaptation capability can substitute for high vendor knowledge advantage and formal incentive contracts.
- A cross-stage configuration combining strong client adaptation capability, high vendor knowledge advantage, and high-powered contracts succeeds regardless of relationship maturity.
- Technology malleability appears primarily front-loaded in early-stage arrangements, while internal client capabilities and formal governance become more decisive as partnerships mature.
What it means for you
CIO / IT Executive
Review upcoming outsourcing contracts to ensure budget is allocated for training internal business users on low-code/RPA tools, specifically preparing to shift from relying on vendor knowledge to leveraging internal client adaptation capabilities as mature partnerships progress.
IT Manager
Audit all early-stage vendor projects on Monday morning to confirm that either strong relational governance (high trust/communication) or high technology malleability tools (RPA/low-code) are actively in place to guarantee project success.
Business Strategist
Draft a transitional sourcing playbook that pairs high-powered formal incentive contracts with access to vendor expertise for cross-stage projects, ensuring this setup is deployed regardless of whether the vendor relationship is new or mature.
Researcher
Design a longitudinal fsQCA or qualitative study to investigate how the front-loading of malleable technologies in early outsourcing stages systematically impacts the development of internal client adaptation capabilities over time.
Policymaker
Incorporate guidelines into public-sector IT procurement frameworks that legally accommodate flexible, adaptive client-side software modifications, reflecting the operational reality that modern outsourcing success relies heavily on client-side direct tool adaptation rather than fixed vendor boundaries.
Summary
This study examines how easily modifiable technologies, such as robotic process automation and low-code tools, interact with governance and organizational capabilities to achieve outsourcing success. The authors gathered survey data from 91 outsourced automation projects in the United Kingdom and analyzed the data using fuzzy-set qualitative comparative analysis (fsQCA).
Problem
Traditional outsourcing models assume a fixed boundary where external vendors manage technical adaptations and clients focus on governance. Emerging malleable technologies enable client users to adapt solutions directly, raising questions about what combinations of governance, client capabilities, vendor expertise, and technology malleability lead to project success across relationship stages.
Transcript
Expert: And I’m Alex Ian Sutherland.
Host: Today we are discussing a study titled "Malleable Technologies in Digital Sourcing: A Configurational Study of Outsourcing Success," authored by Oliver Krancher and Ilan Oshri, published in the proceedings of the International Conference on Information Systems, 2026.
Expert: This study investigates how easily modifiable technologies, such as robotic process automation and low-code platforms, interact with governance and organizational capabilities to achieve outsourcing success.
Host: In traditional IT outsourcing, organizations typically operate under a clear division of labor: external vendors handle technical work, while clients manage and govern the contract. Where does that model encounter challenges today?
Expert: Traditional research assumed that the service boundary between client and vendor was fixed, largely because software changes required specialist programming expertise held by vendors. However, contemporary automation and low-code tools feature visual interfaces that non-specialist client users can understand and modify.
Host: Meaning client teams can make changes directly rather than submitting formal change requests to the vendor.
Expert: Exactly. The authors define malleability relationally: it is the degree to which client users experience modification possibilities as accessible and easy to enact in practice. When clients can adapt solutions themselves, the division of labor becomes fluid. The study asks what combinations of governance, client capabilities, vendor expertise, and technology malleability lead to outsourcing success across different stages of a relationship.
Host: Alex, how did the authors investigate these combinations?
Expert: The authors collected survey data from 91 outsourced automation projects across multiple sectors in the United Kingdom. They analyzed the data using fuzzy-set qualitative comparative analysis, or fsQCA. Instead of looking for single, isolated effects, this method identifies distinct configurations—or combinations of conditions—that are sufficient to produce high outsourcing success.
Host: What were the key configurations identified in the study?
Expert: The analysis identified five sufficient configurations, illustrating equifinality—the idea that multiple distinct paths lead to the same positive outcome. A central finding is that the effective combinations depend on relationship maturity. In early-stage vendor relationships, high technology malleability and strong relational governance act as substitutes.
Host: So in a new partnership, an organization can succeed either through high-touch relational governance or by using a malleable technology?
Expert: Exactly. Early on, uncertainty is high. Teams can navigate this either by investing heavily in trust, communication, and close ties, or by using malleable solutions that allow client users to experiment and adapt workflows directly. Both paths proved sufficient in early stages.
Host: What patterns emerged in mature relationships?
Expert: In mature partnerships, a different substitution pattern appeared. Strong client adaptation capability substituted for vendor knowledge advantage and formal incentive contracts. Experienced clients that built internal capacity to monitor and fine-tune solutions achieved success without relying on superior vendor expertise or high-powered contracts. Alternatively, organizations without strong internal adaptation capability succeeded through the traditional path: relying on a vendor with superior knowledge governed by high-powered contracts.
Host: Did technology malleability play a role in those mature relationships?
Expert: Interestingly, malleability did not appear as a core condition in the mature configurations. The authors suggest its role is primarily front-loaded, supporting early learning and capability building. Once a relationship is established, success depends more on developed organizational capabilities and formal contract governance.
Host: The study also noted a cross-stage configuration. What did that look like?
Expert: That configuration combined strong client adaptation capability, high vendor knowledge advantage, and high-powered contracts. This hybrid arrangement succeeded regardless of relationship maturity, showing that vendor expertise and internal client capability can operate collaboratively under clear contractual incentives.
Host: What are the primary business implications for technology and sourcing leaders?
Expert: First, assess technology malleability from the perspective of the users who will operate the system, rather than treating it as an inherent product feature. Second, for early-stage automation initiatives, selecting solutions that users can easily adapt offers a viable alternative to establishing extensive relational coordination. Finally, as sourcing relationships mature, leaders should decide whether to invest in internal adaptation capabilities to reduce vendor dependency, or rely on vendor expertise managed through formal, outcome-based contracts.
Host: The traditional boundary between client and vendor is clearly evolving into an adaptable interface. Thank you for breaking down the study, Alex.
Expert: You are welcome, Anna.
Host: And thank you for listening to A.I.S. Insights. Join us next time as we examine practical insights from emerging research.
Malleability, outsourcing configurations, service boundary, digital sourcing, governance, capabilities, fsQCA