Every HR Platform Now Wants to Map the Work. Where Does the Evidence Come From?

TL;DR: Workday and SAP now describe work as tasks instead of jobs, and both build their task maps from job architecture, skills profiles, and existing HR systems. That shows the work as documented. A workforce intelligence platform built on activity intelligence adds evidence of how the work happens in practice, so the task map can be checked before it drives a hire, reskilling, automation, or redesign decision.

What changed when Workday and SAP started mapping work as tasks?

Within one week in October, the two largest HCM suites both moved from describing work as jobs to describing it as tasks. On October 6, SAP agreed to acquire TechWolf in a deal it framed as giving enterprises an "evidence-based view of work". SAP said TechWolf "is expected to become an intelligent core of the SAP SuccessFactors portfolio." The deal is expected to close in Q4 2026, subject to regulatory approval.

A week later, at Workday Rising, Workday introduced Work Intelligence, which "breaks each job into the tasks people do" and connects those tasks to the skills they require. It's in early access for Workday HCM customers.

Both announcements turn the same idea into product: start AI planning with the work itself, broken into tasks, rather than with headcount. For the wider picture of vendors competing to supply the context AI agents run on, see who is measuring the work in the race to be AI's data layer. This post looks at one narrower shift: the task map inside the HCM suite, and the data it runs on.

Why is the task becoming the unit of workforce planning?

AI rarely takes over a whole job at once. It changes some of the tasks inside a job and leaves others alone, so a plan built on job titles can't show where the work is actually moving. Workday's Nikki Helmer, vice president of talent management and insights, put the problem plainly: "The basic building block of work is shifting from the job to the task – and without that view, most companies are left guessing whether to hire, build skills, automate, or redesign roles, with no way to know which guess is right."

That is the right framing, and it's the same decision Prodoscore was built to support. Hiring, reskilling, automating, and redesigning are all choices about where work should sit. Each one goes better when leaders can see the work at a finer grain than the org chart. The cost of skipping that step shows up later, as the AI layoff regret cycle has shown, when a role is cut before anyone knew what work it owned.

What is a task map built from?

A task map starts from the records a company already keeps about its people and jobs. Workday says its view is built "from inside Workday, where companies already keep their people, jobs, and skills data." SAP describes TechWolf as working "from existing HR and business systems that customers connect," modeling the work "down to the tasks inside a job."

In plain terms, the inputs are job architecture, skills profiles, and system-of-record data. Skills catalogs play a large part, because they connect each task to the capabilities it requires. Prodoscore's Skills Intelligence adds a measured view of those capabilities, drawn from how people engage with the tools they use every day.

These inputs are a sensible place to start. They're structured, they already sit inside the systems the CIO governs, and they cover the whole workforce.

What can't a task map see on its own?

A model of the work is only as current as the data it reads. Job descriptions, skills profiles, and HR records describe the work as it was documented, and documentation tends to lag the way work changes. On their own, these records don't show which tools a team actually spends its time in, where work has already moved to AI tools, or where the documented task list and real activity have drifted apart.

This is a data-architecture question for any task model, whichever vendor builds it. Workday's release says Work Intelligence lets leaders see "how an employee's time shifts to new work," so the vendors are clearly thinking about change over time. The CIO's question is narrower: what is the map checked against? A task list that reflects last year's job description can look complete and still describe work that no longer happens that way.

Activity intelligence answers that question with team-level evidence of how work gets done across the business tools people already use. It shows where time and effort go, which tools carry which work, and how those patterns change after an AI rollout. That is the evidence a leader needs before a task map drives a hire, a reskilling plan, an automation project, or a role redesign. The value sits at the level of decisions and patterns across teams, which is where workforce planning happens.

Do you need a workforce intelligence layer if you already use Workday or SAP SuccessFactors?

Yes, if you want your task map checked against how work actually happens. Workday and SAP SuccessFactors manage the workforce as it exists on paper: jobs, reporting lines, skills profiles, and now tasks. Prodoscore captures how that workforce behaves in practice and feeds that behavioral signal back into the systems you already run. The two layers do different jobs, and the relationship is additive.

Prodoscore isn't positioned to replace a system of record. Its Data API sends activity intelligence and workforce data into your data warehouse, BI tools, or HR dashboards, and the MCP Connector makes the same data available to the AI tools your leaders already use. Prodoscore also has an existing Workday connection for working days, absences, and holidays. With those paths in place, the task map and the planning tools work from observed evidence as well as documented structure. For how this fits into a wider workforce analytics program, the behavioral layer sits beside HCM and talent systems rather than inside them.

What should a CIO ask before a task map drives decisions?

Before a task map is connected to headcount, reskilling, or automation planning, a CIO can ask a short set of questions of any task model:

  1. Which sources does the model read? List the systems behind each task and skill, and note which of them are maintained by hand.
  2. How often does it refresh? A map updated once a year will trail work that changes every quarter.
  3. Does it reflect observed work or documented work? Find out whether any input shows how work happens across the tools people use, or whether every input describes how work is supposed to happen.
  4. How can behavioral data be fed into it? Check whether the model can take in activity data through an API or an AI connector, so the map can be compared with real patterns before it informs a decision.

The answers won't settle every planning question, but they tell you how much weight a task map can carry. A map that's checked against evidence of the work is one the whole executive team, from the CHRO to the CFO, can use with more confidence. Prodoscore adds that evidence to the systems you already run. See how activity intelligence data checks your task map.

Frequently Asked Questions

A task map breaks each job into the tasks people do and connects those tasks to the skills they require. Workday's Work Intelligence and SAP's planned TechWolf acquisition both bring this view into the HCM suite. Leaders use it to decide whether to hire, build skills, automate, or redesign roles as AI changes work.
A workforce intelligence platform gives leaders evidence about how work gets done across the organization, so planning decisions rest on more than job titles and headcount. Prodoscore's platform is built on activity intelligence data, which shows where time and effort go across the business tools teams already use. That evidence feeds into existing HR and planning systems through an API or an MCP connector.
Yes, if you want your planning to reflect how work actually happens. Workday and SAP SuccessFactors manage the workforce as documented, through jobs, skills, and now tasks. A workforce intelligence layer such as Prodoscore adds observed evidence of how that work behaves and feeds it back into those systems, so the two work together.
Documented work is what job descriptions, skills profiles, and HR records say a role involves. Observed work is how the role's tasks actually get done across the tools people use, including work that has shifted to AI tools. Comparing the two shows where a task map has drifted from reality.
Activity intelligence is team-level data about how work gets done across a company's existing business tools. It shows where time and effort go, which tools carry which work, and how those patterns change over time, for example after an AI rollout. Leaders use it as evidence for planning and coaching decisions.

How will visibility impact your business?

Get in Touch