When the Society for Information Management published its IT Trends Study a decade ago, it captured what was keeping CIOs awake at night: aligning IT with the business, securing data, delivering faster, controlling cost, and earning credibility with the executives signing the checks. The striking thing, looking back, is how little the list has changed. The technology stack turned over completely. The pressures did not.
If you lead enterprise IT, operations, or digital transformation today, you are still being measured on most of those same eight concerns. What has changed is the honest answer to them. For years the implied solution was a big platform migration, a multi-year program, a rip-and-replace bet. The organizations making real progress now do something quieter: they leave their systems of record in place and put an orchestration layer on top.
That is what Kinetic Data is. Kinetic is an enterprise workflow orchestration platform that acts as a modernization layer over the systems you already run — meaning it sits above your ITSM tool, your HR system, your ERP, and your homegrown apps, coordinates work across all of them, and gives users a single clean experience, without replacing any of the systems underneath. Below, the eight concerns from that study, and where each one actually stands today.
1. Alignment of IT with the business
The original worry was that IT spoke a different language than the business it served. That gap rarely closes with a reorg or a new title. It closes when IT can deliver a working process for a business problem in weeks instead of quarters.
The obstacle is almost never a lack of systems. It is the gaps between them — the manual handoffs, the email approvals, the spreadsheet someone maintains to track what the systems can’t. Orchestration targets exactly those gaps. You model the cross-system process once, route it through the systems of record that already hold the data, and the business gets the outcome it asked for without IT proposing yet another tool the business has to learn.
2. Security and privacy
Security was a top concern then and it has only climbed. The difference is that buyers — especially in government and regulated industries — now audit for it, and “trust us” is not an acceptable answer.
This is one of two things Kinetic can claim that most workflow tools cannot. Kinetic carries a government-grade security posture: IL5 authorization, CAC-based authentication, and more than twenty years of work in defense and intelligence environments. That heritage shapes the whole platform. Every step a workflow takes is logged, attributable, and auditable by default — not a feature you switch on, but how the engine runs. When a regulator or an internal auditor asks who approved what, when, and on whose authority, the record exists.
The fastest way to weaken your security posture is to over-customize the backend systems that hold your sensitive data. Orchestrate above them instead.
3. IT’s speed of delivery
Speed was the concern most tied to a specific fix in the old playbook: adopt Agile, adopt DevOps, ship faster. Useful, but it addressed how IT builds, not how long a request waits in a queue.
Most delivery delay lives in the seams between systems — a provisioning request that bounces from a portal to a ticket to an approver’s inbox to a manual entry in a second system. Because Kinetic layers on top of existing systems instead of migrating them, deployments measure in days, not quarters. USDA, for example, stood up workflows on Kinetic without replacing the systems underneath. When the orchestration layer handles the routing, the approvals, and the provisioning across systems automatically, the wait time that frustrates users disappears — and it does so without a build-from-scratch project.
4. Innovation
Innovation, in the study, mostly meant freeing IT from pure cost-cutting so it could improve agility and customer experience. The barrier was that the team’s capacity was consumed keeping fragile, hand-built integrations alive.
Custom internal apps are how a lot of “innovation” historically shipped, and they are also how teams end up trapped — every one-off build is something to maintain, patch, and eventually rewrite. An orchestration layer is faster to launch than a custom app, easier to govern, and far less brittle, because it reuses the systems of record rather than reinventing them. The capacity you reclaim from maintenance is the capacity you spend on the next problem.
5. Agility and flexibility
Agility was the concern about being able to change course when the business does. Rigid systems make that expensive. So does the opposite failure — a sprawl of disconnected tools no one can change in concert.
A practical middle path is a unified service catalog that fronts many systems through one experience, so when a process changes you change the orchestration, not five separate backends. Self-service portals, no-code workflow building, and pre-built connectors all support this. Worth being clear: those are table stakes. Every vendor in this space offers them. They matter, but they are not why Kinetic is different — the modernization-layer architecture and the security posture are. Treat the connectors as plumbing and judge the platform on what sits above them.
6. Cost reduction and cost control
The old framing — return on incrementalism — has aged remarkably well. The expensive path was always the multi-year, all-or-nothing replacement. The disciplined path is to modernize in increments, capturing value at each step while the systems of record keep doing their job.
This is also the right lens for AI, which wasn’t on the original list and now dominates every IT budget conversation. The principle worth holding onto: build with AI, run with Kinetic. AI is genuinely useful at design-time to help create workflows, and as a step inside a running workflow to classify a request, extract a field, recommend a route, or summarize a case. But execution stays deterministic — repeatable, governed, auditable. You don’t want to burn AI compute re-deciding a process that follows the same steps every time, and in a regulated environment you can’t afford execution you can’t trace. AI advises. Humans decide. Workflows execute.
7. IT credibility
Credibility was the soft concern with hard consequences: if executives don’t trust IT to deliver, they route around it. Trust is rebuilt with a track record of shipped outcomes, not with strategy decks.
The fastest credibility win is usually a visible, high-friction process — onboarding, access requests, a service-heavy approval chain — turned from a multi-week ordeal into something that just works. Pick one, orchestrate it across the systems involved, and let the result speak. A process that used to take weeks and now takes minutes is an argument no slide can match.
8. The CIO leadership role
The study foresaw the CIO becoming a “chief integration officer” — the person who connects technology, ideas, and processes across functions. That prediction landed. The modern CIO’s job is less about owning every system and more about making a fragmented estate work as one for the people who use it.
That is precisely the job an orchestration layer is built for. Rather than forcing the entire experience into one vendor’s stack, Kinetic complements your systems of record, gives you control of the user experience, and reduces the backend customization and license sprawl that quietly erode both budget and agility.
What’s next
The eight concerns endured because they were never really about technology — they were about delivering reliable outcomes across systems you don’t fully control. That is solvable now, without the rip-and-replace bet the old playbook assumed.
See how the platform works as a modernization layer, explore solutions for IT teams and for government, or look at the case studies for proof from organizations that started exactly where you are. When you’re ready, contact us to talk through your own service-delivery and orchestration challenges.
Share this article