CIO.com just published an article I co-wrote with Shail Khiyara (ex-CxO UiPath) on LLM Orchestration (GenAI).
Let me explain why we think this is an important topic for tech executives:
- LLM Orchestration layers will coordinate much of the enterprise functions (RBAC, integration to enterprise assets, etc)
- There is a need to avoid spaghetti code and minimize tech debt in GenAI application assets
- One needs a migration path to commercial Orchestration solutions as they come to market (from today’s homegrown solutions)
- CIO offices need solid paths to scalability and complexity management
In the article we suggest some strategies that CIOs should be applying _now_ as they build out their GenAI stacks. They revolve around:
- Vendor and tool selection (what vendor stacks, customization capabilities, compliance tooling, etc)
- Architecture development (monitoring, centralized governance, etc)
- Talent onboarding and retention (there is a very scarce talent pool today)
Just to be clear, the LLM Orchestration layer is NOT the same as the orchestration tools currently in place in the enterprise today. This is an emerging layer in the GenAI stack.
I am excited about this article we wrote with Shail Khiyara as he’s lived this journey before with the deployment of automation at scale, given his CxO roles at UiPath, BluePrism and Automation Anywhere. And with our shared experience we are bringing a wealth of insights to the table.
I’d love to broaden this conversation in our community as we find ways to better develop and deploy GenAI assets in the enterprise. We’re in a fast moving journey and sharing lessons is the best way to improve the way we do this work.
