Your Workforce Changed. Did Your Visibility?

A CIO said something to me recently that stuck.

He told me he needs to understand not only where AI is being used today, but how it is changing what his teams spend time on, what they will spend time on next, and how their focus and capabilities will shift as a result.

That is the bigger issue.

After more than 20 years of working with cybersecurity and IT leaders, I believe we are at a major turning point in how organizations need to think about the workforce.

Your workforce is no longer just employees. It includes employees, contractors, consultants, MSPs, interns, and now AI agents. And every time work moves between those resources, something changes:

• Capacity changes.
• Capability changes.
• Ownership changes.
• Dependencies change.
• Risk changes.
• Human focus should change.
• Investment decisions may need to change.

The problem is that most organizations do not have a living view of any of it. They have headcount reports, org charts, job descriptions, budgets, open roles, tools, projects, and control assessments. But those things do not tell leaders who and what is actually doing the work.

And now AI is making that lack of visibility impossible to ignore.

AI Adoption Is Not the Same as Workforce Transformation

Most organizations are measuring AI adoption. How many employees are using it? Which tools have been deployed? How many use cases are in production? How much time is AI supposedly saving?

Those are reasonable questions, but they do not go far enough. The more important question is different.

Is it increasing output? Reducing outside spend? Allowing employees to focus on higher-value work? Changing hiring plans? Eliminating duplication? Reducing burnout? Or is AI simply being added on top of the existing workload without any real redesign of how the work gets done?

If an AI agent takes on part of a function, something else should change. Human time should move. Roles should evolve. Capabilities should shift. Capacity should be redirected. Priorities, and the workforce plan itself, may need to change.

But organizations cannot manage those changes if they cannot see them.

Strategy Is Often Not the Problem

Most CIOs and CISOs I speak with are not short on strategy. They know where they want to go. The harder question is whether they truly understand the workforce required to get there.

Can they clearly see where their teams are spending their time today? Which capabilities are strong? Which are thin or missing? Where does too much knowledge sit with one person? Where is an MSP performing work that could or should be done differently? Where are contractors and consultants adding critical capability? Where are people overloaded? What work could be automated? What should move to an AI agent? And when that happens, where should human capacity go next?

These are execution questions. They are also workforce questions, investment questions, operational risk questions, and leadership questions.

A strategy can be completely right and still fail to move because the organization does not have enough visibility into the workforce ecosystem responsible for executing it. That is what I believe more leaders need to confront.

Headcount Is Not Workforce Intelligence

A company can know exactly how many employees it has and still know very little about its workforce.

Headcount does not show where time is actually being spent. It does not show which capabilities exist, or where critical gaps are hiding. It does not show where the organization is too dependent on one person, one contractor, one consultant, or one MSP. It does not show where work is being duplicated, or where burnout is creating risk. It does not show what AI agents are doing now or what work they should be doing next. And it does not show whether another budget request is truly necessary.

For CFOs, this creates a particularly important issue. When a CIO or CISO asks for more budget, more headcount, another consultant, or additional outside support, what data is available to evaluate that request?

What work is not getting done today, and why? Is the problem capacity? Capability? Maturity? Prioritization? Leadership bandwidth? Could existing resources be redirected? Could an MSP or consultant be used differently? Could the work be automated, or handed to an AI agent? And what is the risk of doing nothing?

Those questions require more than a budget spreadsheet. They require workforce intelligence.

The Ability to Communicate Upward Matters Too

There is another side to this problem that I do not think gets enough attention.

Cybersecurity and IT leaders are constantly being asked to explain why initiatives are not moving faster, why more investment is needed, why certain work cannot wait, and where risk is increasing. But what data do they have to tell that story?

Most can show headcount, budget, projects, open roles, tools, control gaps, and maybe some maturity data. But that still does not tell the full execution story. Where is the workforce actually spending its time? What capabilities exist today? Where are the gaps and the critical dependencies? Where is burnout creating risk? How are MSPs, contractors, and consultants contributing? What work is moving to AI agents? What capacity is being created? And what specifically must change to execute the strategy?

Without that information, leaders are too often left trying to communicate a very complex execution problem with incomplete workforce data. That makes it harder to get funding. Harder to defend investment decisions. Harder to prove where risk sits. Harder to explain why the strategy is not moving. And harder to make the right decision about what to build, buy, automate, hire, retain, reduce, or change.

Workforce Intelligence Has to Be Living

This is the part I feel most strongly about.

A one-time snapshot is not enough. Every workforce change alters capability. Someone leaves. Someone joins. A contractor rolls off. A consultant comes in. An MSP takes on more responsibility. A critical employee becomes overloaded. An AI agent begins performing work previously done by a person. A business priority changes. A new regulation changes the work. A new technology changes the skills required.

The workforce does not stand still. So workforce intelligence cannot stand still either.

Organizations need a living view of the workforce ecosystem that keeps pace with change. Not just who is employed. Not just what their titles are. Not just what their job descriptions say. But who and what is actually doing the work, where time is going, what capabilities exist, where the gaps and dependencies are, and what needs to change to execute the strategy.

This Is the Next Workforce Problem Leaders Have to Solve

For more than 13 years, CyberSN has been defining cybersecurity and IT work through our taxonomies. That foundation has taught me something very clearly.

And now that AI agents are part of the workforce, that truth matters even more. The way work gets done is changing faster than most organizations can see, document, measure, or manage.

The organizations that succeed will not simply be the ones that adopt the most AI. They will be the ones that understand how work is changing, how human focus should shift, what capabilities they truly have, where risk is emerging, and how the entire workforce ecosystem needs to evolve to execute the strategy.

That is what workforce intelligence should make possible. And I believe it is quickly becoming essential.

---

About CyberSN Workforce Intelligence

CyberSN's Workforce Intelligence Engagement gives cybersecurity and IT leaders a living view of the workforce ecosystem: where time is being spent, what capabilities exist, where dependencies and gaps are forming, how MSPs, contractors, and consultants are contributing, and what work should move to AI agents, across employees and every other resource doing the work.

The result is stronger strategy, more defensible budget decisions, reduced operational risk, and greater confidence that the workforce can actually execute the plan.