Employees aren’t waiting for sign-off from the CIO anymore.
HR coordinators are building their own onboarding workflows in Airtable. Sales ops teams are connecting Salesforce to Slack using Zapier and ChatGPT prompts they found on Reddit. And customer success managers are sending personalized follow-up sequences without touching the marketing automation platform.
Employees are getting used to building their own workflows and automating their own tasks with no-code tools – often with the help of LLMs.
Here’s what’s happening – and how IT departments need to change to keep up.
1. AI and no-code tools have changed who can build technology.
No-code platforms let employees who can’t write a line of code build their own solutions directly. Problems that used to require the dev team can now be fixed by the people building the workflows.
An operations manager can have a new workflow up and running in an afternoon – all without filing a ticket with the dev team.
This shift is already happening. In fact, Gartner forecasts that by the end of 2026, at least 80% of people using low-code tools in large enterprises won’t be in IT.
AI is only speeding things up. Employees are using LLMs to troubleshoot the problems they run into with no-code tools – or even ‘vibe code’ their own basic applications from scratch.
2. Pandora’s box has been opened.
Does the idea of employees vibe coding their own shadow software bring you out in a cold sweat?
Granted, it’s hardly ideal from a security standpoint. But the IT department’s role is changing. It’s shifting from managing software and developing internal applications to empowering citizen developers with the infrastructure they need.
None of this means IT becomes irrelevant. … But the idea that IT should control every technology decision? That’s finished.
Because there’s no going back from here. Your tech-savvy employees now have a choice. Raise a ticket with the dev team that won’t get looked at for three weeks. Or use an LLM and no-code platform to build their own workaround in an afternoon.
The more ubiquitous AI becomes, the more of your workforce will feel comfortable vibe coding their own fixes. The only question is whether IT is part of that conversation or completely bypassed by it.
3. CIOs who resist are becoming the bottleneck.
None of this means IT becomes irrelevant. Security, governance, and infrastructure still need specialists. But the idea that IT should control every technology decision? That’s finished.
CIOs who cling to controlling every technology decision aren’t protecting the business. They’re becoming the bottleneck their teams have to work around. And those workarounds? They’re creating the exact security and governance gaps IT was supposed to prevent.
The shift in practice is straightforward. IT sets the guardrails – what tools are approved, what data can live where, what security standards apply. Then they step back and let teams operate within those boundaries. The operations manager building a workflow tool in a no-code platform doesn’t need IT to scope it or approve it. She just needs IT to vet it once it’s built.
That’s the role: making sure the organization runs securely while everyone else gets on with solving their own problems.
The modern IT department
CIOs who embrace this shift will help their businesses thrive. The ones who resist will watch their influence drain away as teams find ways to work around them.
Shadow IT used to mean someone buying Dropbox on a credit card. Now it means entire workflows running on vibe-coded tools IT doesn’t know exist.
The irony? By gatekeeping, CIOs are creating the exact risks they were trying to prevent: teams building critical workflows on tools that haven’t been vetted because the official approval process takes six months.
The CIOs getting this right aren’t trying to control every technology decision anymore. They’re doing something more important: making sure the organization can move fast without breaking things.
That means vetting platforms once, setting security boundaries, then stepping back. Operations teams can build workflows without waiting months for development cycles.
IT’s job becomes enablement, not gatekeeping. And the organizations making that shift are the ones pulling ahead.
